FoFiX 4.0.0 Development Thread

[fuzion]

The only working themes that I know of are MLv4 and the 4x themes in my sig.

[acrox999]

Good to see the game's back and active. Well done guys.

[amak11]

Is there older/other themes working with current source of fofix 4 ? I have only Megalight V4 theme working and i cant change for any other.
BTW. I don't know where to get any video for background. Do you know where can i find any ?

The current WIP themes are: RB3, GHM, GHSH, GHVH, GH5, and GH80's

The only themes available as fuzion said for the git sources are 4x and MLv4

[weirdpeople]

Is there older/other themes working with current source of fofix 4 ? I have only Megalight V4 theme working and i cant change for any other.
BTW. I don't know where to get any video for background. Do you know where can i find any ?

The current WIP themes are: RB3, GHM, GHSH, GHVH, GH5, and GH80's

The only themes available as fuzion said for the git sources are 4x and MLv4

uberlight may be compatible, i just cant remember if i pushed it or not when i made it compatible lol ill have to look and see, if not ill push an updated verstion

[jstump91]

For those of you on Git, this is a friendly reminder that you must recompile the native modules after any changes are made to their source code, as I am about to push some changes to them. That section of the page states that you must do so any time the source code to the native modules changes.

This is the only time I am going to post a reminder of this in advance, as this is the first time that the native modules are being modified after they were first put in and the documentation on compiling them was written.

(If you don't feel like checking whether any future updates contain changes to the native modules, it's perfectly OK to just recompile them after any update that brings in new changes, whether or not the native modules are actually affected.)

[fuzion]

I updated the RunningFromSource docs. If you were having trouble with 3rd party modules, check out the new version: http://github.com/stump/fofix/blob/mast ... pendencies

[MasterPhW]

I updated the RunningFromSource docs. If you were having trouble with 3rd party modules, check out the new version: http://github.com/stump/fofix/blob/mast ... pendencies

Cython has been updated to 0.13.
Should we stay with 0.12.1 (not available from the site, btw) or should we update to 0.13.

[fuzion]

I updated the link. Use 0.13: http://www.lfd.uci.edu/~gohlke/pythonlibs/#cython

[santagada]

I'm running fofix from git (rev 7a8c28e1) and I got it to compile the opengl extension module on mac. I have two questions:

1 - Sometimes text is appearing in the wrong places of one over the other. Specially where I have to select the difficulty I can't find the labels (easy... expert) anywhere, is this a problem only on the mac or for everyone (I tested using all the default themes).

2 - If I clean my patches where should I submit them, just make a fork in github or do you use another system for it?

[fuzion]

1. Probably a theme issue.
2. You can put the output of git diff on pastebin and post it in the irc channel. Make a fork if you intend to do more than a few patches.

[jstump91]

2. You can put the output of git diff on pastebin and post it in the irc channel. Make a fork if you intend to do more than a few patches.

For one-off or low-volume patch submission, I like git format-patch and git am much better because it keeps the author info and original commit message and it works a lot better with allowing contributors to keep their own history (which is kind of the whole point of using a DVCS).

santagada: When you have changes to submit, commit them and use git format-patch to turn them into a nice submittable patch. We'd be happy to explain more about this on IRC if you need it.

[Borisdsp]

No news?
11 months without a release

-- Edit: 20 Nov 2010, 22:42 --

No news?
11 months without a release

[jstump91]

The last thing remaining to be done before we can make an alpha release is replacing the video playing code with something other than gstreamer. This is so that which codecs are supported does not vary across systems, so that we do not have to ship even more large dependency libraries with the Windows build, so that we do not have to ship patented or otherwise legally-encumbered code with the Windows build, and so that we can get rid of one of many huge messes in FoFiX's source code.

We have decided on only supporting the Theora video codec in an Ogg container (with audio in Vorbis, if audio is present). In preparation for getting rid of gstreamer in favor of direct use of libtheora, videos are now loaded from the .ogv file extension, and even though gstreamer is still in use right now, it will refuse to play anything other than Theora in Ogg (with Vorbis audio, if audio is present).

(Themers using intro or credits videos and fretters using background videos should be sure to take note of this change.)

My goal is to have the non-gstreamer Theora player code ready, and to make an alpha release containing it, by Thanksgiving.

[demoj]

u sir r amazing

[jstump91]

Alpha status update:

The Theora video player is all ready to go, but the build setup caused unexpected difficulties on Windows. That's why we weren't able to get the alpha out by Thanksgiving - it was rather involved to fix.

Those of you following Git might be in need of more dependency packages - a Win32 dependency pack for Windows users and some library development packages (those of libogg, libtheora, libglib, and libswscale) for GNU/Linux - to build the new video module. The RunningFromSource.mkd file has been updated with this information.

As for the alpha, we should have it out within 24 hours.

Some notes about the new video code:

• It only supports Theora video inside Ogg. If you were using anything else, you will have to transcode it.
• Audio for the intro video currently does not work, but we expect to get it working not long after this alpha.
• Very high resolutions of video might not be particularly efficient at the current moment, but there is a lot of room for optimization.
• Time seeking (video_start_time and video_end_time) has not been reimplemented yet, but we are actually considering dropping it. If you want to use a subrange of a video, extract the right part as its own file.