MFH Mod (FoFiX) 3.0xx (v3.030) (OLD)

[Azzco]

Im sorry I really do not like Beta 3.

What happened to customizable HO/PO's?
[I know there still technically there.]

Now lots of carefully placed ho/po's in lots of songs will be worthless because whenever you do GH2 Sloppy or more ho/po you get
CHEATER

At the end of the song.

Sorry I think you should either make the default HO/PO less strict or take out changing you Ho/po messing up your scores.
:/

I don't know about how you fret but most songs generally does not have "Carefully placed Ho/Po's" AFAIK.

In the latest revisions GH2 sloppy is only regarded a handicap (causes score penalty, but allows score saving) and so is wide/widest hit windows.

There's work on RB2 style custom Ho/Po's planned after FoFiX 3.100, and fretters will have more control over how the songs should be played. It's also my understanding that there will be a RB2 Sloppy, like there is a GH2 sloppy, which basically is GH2 sloppy with added support for custom Ho/Po's (I.E. forcing strum or Ho/Po note).

The main problem I have with the GH2 Ho/Po system is the lack of reverse tapping (holding higher fret and tapping lower). I like the penalty for hitting the wrong note in between present in that system before no penalty at all (which is the case in GH2 Sloppy).

Short: GH2 sloppy will give you a high penalty in the future, and not act as a total cheat like Jurgen.

[Nickman]

Im sorry I really do not like Beta 3.

What happened to customizable HO/PO's?
[I know there still technically there.]

Now lots of carefully placed ho/po's in lots of songs will be worthless because whenever you do GH2 Sloppy or more ho/po you get
CHEATER

At the end of the song.

Sorry I think you should either make the default HO/PO less strict or take out changing you Ho/po messing up your scores.
:/

I agree with you. it is unnecesary.
Jurgen is a cheat, of course, but hitwindow and failing are only normal options.

Read this http://code.google.com/p/fofix/issues/detail?id=509

[jiiiiimmmy]

I think I have figured out why the careers sometimes continues to state "Play to advance" even when you have completed a song.

If you sort the songs by putting a number (Ex: 1.) in front of the song name the game doesn't change the songs status.
If you sort the songs by putting a number after the unlock_id (Ex: unlock_id = gh2_1.1) the game changes the status correctly when a song is completed.

The downfall of the correct sorting is that when you enter the unlock require like this (Ex: unlock_require = gh2_1) for the encore the game looks for gh2_1. Since there are (.1, .2, .3) after the unlock_id's the game cannot find the corresponding tier and leaves the encore unlocked.

If unlock_require doesn't look for anything after a period is entered in the unlock_id then we would have a more solid way of sorting songs for a career mode.

I'm sorry if this has been discussed before, but I do not recall anyone ever figuring out this problem and or discussing it. I know this has also been on the "Bugs that have not been confirmed" list for awhile now.

If anyone has fixed this problem before without further coding please PM me the solution.

PS
Sorry if any of that confused anybody. It seems sort of confusing unless you already know what I'm talking about.

[Borisdsp]

Read this http://code.google.com/p/fofix/issues/detail?id=509

Ok, this mean that if you play with hit window in wide you will have less score, but you wont be a "cheater", ok, it is a good new. I hope this issue will be fix soon.
Thank you

[Hiasl]

can someone tell me when beta4 will come out.

[Borisdsp]

can someone tell me when beta4 will come out.

I think final version will be out soon.

[akedrou]

also it's still not flipping through the different results screens like it should

What do you mean? I still have no idea what you're talking about... There's only one screen?
The problem with your result_star is that scale (the .0017) is very small with the new system. Try adjusting it. The wiki hasn't been updated to reflect that. (If my .5, .5, .5, .5 worked, you should probably try basing your changes on that, rather than going back to what's in an outdated wiki and then asking why it won't work. The changes were made less than a week ago! The values are x, y, size, and horizontal spacing.)

[Azzco]

also it's still not flipping through the different results screens like it should

What do you mean? I still have no idea what you're talking about... There's only one screen?

Could slantyr perhaps be talking about the handicap pop ups?

[hannon]

are we going to be required to reboot when we change key sets? from normal to alternative

i have two controllers my imac keyboard and xplorer guitar
would like to be able to switch without needing to manually reboot.

[KillerQ]

can someone tell me when beta4 will come out.

I think final version will be out soon.

Yep - that's the plan... Could be as early as this evening!!

Yea!

Matt...

[Super_Crazy_Dude]

can someone tell me when beta4 will come out.

I think final version will be out soon.

Yep - that's the plan... Could be as early as this evening!!

Yea!

Matt...

I Mean theirs only 5 more things to do

[Qstick]

4 now

[Super_Crazy_Dude]

yeah!!!! YUMMY DROOL

[myfingershurt]

FoFiX issue 33's implementation seems to cause a crash when Jurgen's text has no theme.ini setting:

Log, r953:

File "X:\Games\FretsOnFire\FoFiX\src\Session.py", line 66, in signalMessage
handler.handleMessage(sender, message)
File "X:\Games\FretsOnFire\FoFiX\src\Session.py", line 87, in handleMessage
return f(sender, **message.__dict__)
File "X:\Games\FretsOnFire\FoFiX\src\World.py", line 248, in handleSceneCreate
d
scene = SceneFactory.create(engine = self.engine, name = name, owner = owner
, session = self.session, **args)
File "X:\Games\FretsOnFire\FoFiX\src\SceneFactory.py", line 40, in create
return getattr(m, name + "Client")(engine = engine, owner = owner, session =
session, **args)
File "X:\Games\FretsOnFire\FoFiX\src\Scene.py", line 223, in __init__
self.createClient(**args)
File "X:\Games\FretsOnFire\FoFiX\src\GuitarScene.py", line 227, in createClien
t
if float(self.jurgenText[2]) < 0.00035:
IndexError: list index out of range

[Qstick]

fixed