Frets on Fire 1.3.110

[vedicardi]

If MFH could adapt his mod for this that'd be epic

[NinjAstar]

If MFH could adapt his mod for this that'd be epic

Until that happens its best to stay with 1.2.451.

[Bozo999]

Every Frets On Fire version looks the same.

[Azzco]

Every Frets On Fire version looks the same.

This version was just a minor bugfix there's no new features and no new art so that's not a surprise. AFAIK most FoF relases are bug fixes and feature addition, and the theme has remained the same.
If you want it to look any different there's mods and I guess that's what the developers had in mind when the made a folder for mods in fof/data.

Just trying to say that that wasn't one of the brightest posts. ;)

[BlackFate]

Every Frets On Fire version looks the same.

You are clearly wrong.

Fretsonfire version 1.1.324-



Fretsonfire version 1.2.451-



Same? I think not.

Mike.

[acrox999]

Yeah. He's stupid. Never played an older version of FOF.

[RedShadow]

in my computer it didnt even started...
blackfriday told me it was only for Intel macs...
i think that was a bad move

[cb88]

1.3.110 crashes more than 1.2.512 or the previous version for me

laggy on the menus and completely locks up after selecting the difficulty

crashes every time settings are applied It seems this python was compiled with visual c++ (crahes with a visual c++ runtime error) which i have experienced being a very buggy compiler (and also having very poor standards compliance) so I suspect that is part of the problem compile with GCC and mingw and I bet it will be more stable

also the versions have gotten progressively slower each release I have a geforce2 mx 400 and it is plenty to play this game (1.3.110 plays fine on a nearly identical Linux box I have)

[wakethefallen]

honestly, if there was a way to select your own hitwindows/hopos, then I would keep a copy of this on my
desktop right beside MFH 3.00

[raph666]

crashes every time settings are applied It seems this python was compiled with visual c++ (crahes with a visual c++ runtime error) which i have experienced being a very buggy compiler (and also having very poor standards compliance) so I suspect that is part of the problem compile with GCC and mingw and I bet it will be more stable

At first I thought "What the hell, let's try another compiler" but I quickly realized there was something very wrong. "It seems this python was compiled with visual c++"
This is not how it works. The error is referencing to the Visual C++ Runtime and actually comes from a segmentation fault caused by the game (running with the verbose flag shows "pygame parachute").
This said, I also thought the linux version was much stabler than the windows version, there is definitely something wrong with it but the visual c++ runtime error does not come from the packaging as you will get the same error when running from source code.

[cb88]

I can see where you are coming from on that....

when i say this python i was meaning all of the binaries in general ... but anyway
so is it the runtime itself crashing or is it a runtime error? are you implying that you recompiled it with a compiler other than visual c++?

trying FoFix atm... perhaps I will fare better

[raph666]

are you implying that you recompiled it with a compiler other than visual c++?

No, you cannot do that. As I said, It is not compiled with visual c++ to begin with. It is run through the python interpreter-compiler.

[cb88]

python itself WAS compiled with visual c++

did you try recompiling python is what I mean to ask obviously you wouldn't recompile the python sources .py etc...... although it is possible to compile the runtime (python that is) in so it seems like a compiled program.

[KrazzyKlown]

:crying: What happened to RF?

He said there'd be a Rockmeter and J Power. Maybe he moved on...

[eggyegg500]

ALL the versions start and when i go and start a game Bfore the fretboard starts moving the game says:an error occured see frets on fire.exe.log for details