FoFiX 4.0.0 Development Thread

[akedrou]

FoFiX 4.0.0 Development Thread


Well we're here - this is the thread for the coming FoFiX v 4.0.0. What you can expect to find here from us is information about major changes and fixes.

This is NOT the place for bug reports. Things are going to be shaky for a while and if you all post every last bug report in here this thread will become a nightmare in no time. So learn to use the Issue Tracker over at Google Code. Don't be afraid.

So you are aware, this is going to be a pretty big task. If you're testing via our Git repository, make sure you have a copy of 3.121 if you want to play. Particularly at first, there are going to be a good number of things broken.

That said, we're working on getting things going again for real. Dev meetings happen every Sunday at 7 PM Eastern Time in #fofix on OFTC (check it out via Mibbit).
And check out the Google Code page for information on running from source and the alpha downloads!

Links

FoFiX project homepage / latest news
FoFiX downloads
Credits


=====================================================================

If you'd like to dig through the thousand-plus posts in the old FoFiX 3.1xx thread you are more than welcome to.

[jstump91]

Something to keep in mind when it comes to this thread...

There is no excuse for not knowing the forum rules if you are running 4.x development code from SVN. Also, please, please, please read this post first if you are considering following 4.x development using SVN.

These rules are more important than ever now that development will be taking place at a very fast pace. Things will be broken from time to time. Be sure to keep a copy of 3.120 final handy to fall back on if the breakage affects you.

Other than that: to all developers, congratulations on getting us to 3.120, and happy hacking!

To all users, thank you very much for helping us squeeze enough bugs out to get to this release. (Especially if you obeyed the forum rules when doing so.) We also assure you that the pre-3.120 feature-freeze debacle will not happen again.

With the release of 3.120, we can now freely develop major new features. Let's go to town!

[kristijan_mkd]

Let's go mates, good luck on this one.

[amich45]

YESSSSSSSSSSSSSSSSSSS

Best of luck, great job so far.

[fofgh3]

Sorry I am way behind... where is MFH?

[akedrou]

Sorry I am way behind... where is MFH?

Around, but in the real world, doing real world things like making boats of money. Hopefully he'll be able to spend some time on the project soon, but in the meantime stump and myself (along with evilynux, Q, blazin and the rest of the coders) have stepped up to do the things that need doing in his absence.

[weirdpeople]

Also in 4.0 will yall be adding support for solo buttons so you will be able to tap the solo's and during bigrockendings? made an issue for it a while back

[amak11]

Any chance network support will come in this version coming up. Also anything about animated loading screens and menus

[akedrou]

Also in 4.0 will yall be adding support for solo buttons so you will be able to tap the solo's and during bigrockendings? made an issue for it a while back

Any chance network support will come in this version coming up. Also anything about animated loading screens and menus

Anything about "is this going to be in 4.0" - the answer is maybe. Find the relevant issue on Google Code, star it, and we'll be more likely to do it. Also depends on how feasible it is, etc, etc, etc.

...But to answer your questions: in a perfect world the answer is yes to both of those. They are being considered. Whether they make it in is another story. We shall see!

[jstump91]

Also in 4.0 will yall be adding support for solo buttons so you will be able to tap the solo's and during bigrockendings? made an issue for it a while back

Any chance network support will come in this version coming up. Also anything about animated loading screens and menus

Anything about "is this going to be in 4.0" - the answer is maybe. Find the relevant issue on Google Code, star it, and we'll be more likely to do it. Also depends on how feasible it is, etc, etc, etc.

...But to answer your questions: in a perfect world the answer is yes to both of those. They are being considered. Whether they make it in is another story. We shall see!

@original posters: In addition, there is a certain (big and bold) link in the second post in this thread that clearly states (big and bold) that you are not to ask when specific things are going to be finished. This has always been a rule when dealing with the FoFiX developers.

[weirdpeople]

Also in 4.0 will yall be adding support for solo buttons so you will be able to tap the solo's and during bigrockendings? made an issue for it a while back

Any chance network support will come in this version coming up. Also anything about animated loading screens and menus

Anything about "is this going to be in 4.0" - the answer is maybe. Find the relevant issue on Google Code, star it, and we'll be more likely to do it. Also depends on how feasible it is, etc, etc, etc.

...But to answer your questions: in a perfect world the answer is yes to both of those. They are being considered. Whether they make it in is another story. We shall see!

@original posters: In addition, there is a certain (big and bold) link in the second post in this thread that clearly states (big and bold) that you are not to ask when specific things are going to be finished. This has always been a rule when dealing with the FoFiX developers.

yeah i forgot about that but i know this next version will be Awesome :)

(also one other thing is the wammy bar fix on rb guitars is another issue that i think needs to be fixed )

[OzzyOzrock]

ONLINE PLAY?!? **** YES.

[Typhus]

Ok! Let's move on.

Up until now I've been running on Python 2.4, so I think now it's a perfect time to step into the next stage and go Python 2.6.

I hope you guys keep up your awesome work!

A big THANK YOU to all of you (developers), who made my life happier.

Hasta!

[amak11]

Could you guys work on optimizing the game a little bit. Just to say using the Py 2.4 version, running 4 players eats 1.5 gigs of memory. That way a lot of us can move up to the py 2.6 version without issues. Also thank you guys for all the work you've done

[KTownEgghead]

Hey, 4.0 discussion. Nice :)