FoFix Lag!

[Ambiguity]

I hear the most lag stories from users with really good PC specs, for some reason it seems to effect stock PCs less so. I've updated my graphics card and haven't experienced serious lag(unless using py2.6 builds), so I'm wondering if it's not a dual-core+ processor incompatibility problem.

[slashfan7964]

That's possible. You'd think a quad-core would work better since it takes care of more.

[Spikehead777]

The biggest bottleneck I have with FoFiX is my CPU.

Here's my specs:

Intel Pentium Dual CPU E2180 @ 2.00 GHz
3GB RAM
nVidia GeForce GT240
Windows Vista Home Premium 32-Bit

Depending on game mode and song, I may pull anywhere from 20-60 fps. I guess that shows how heavily CPU-based this game is. Oh yeah, I also tend to play with my Wii GHWT Guitar, so I have to use GlovePIE. I also noticed improvement when I changed GlovePIE's update speed to 120 fps and changed it's priority so it runs on the opposite core.

I don't know what optimizations are being made, but they need to be made, especially with the switch from PyGL 2.4 to PyGL 2.6.

[acrox999]

I think its the rock meters and stuffs making the game slow. I run the game at the highest graphics settings, removed rockmeter.ini and guess what?

I got constant 75FPS.

[Ambiguity]

I don't know what optimizations are being made, but they need to be made, especially with the switch from PyGL 2.4 to PyGL 2.6.

As far as I know the current version of FoFiX can't run all the cores a processor has, 4.0 is supposed to allow you to run them all(don't quote me on this though, I'm not a dev or a tester).

[acrox999]

Yes, 4.0 allows you to use all cores. But only applicable to Win32 users.

[GrifSam]

I think its the rock meters and stuffs making the game slow. I run the game at the highest graphics settings, removed rockmeter.ini and guess what?

I got constant 75FPS.

so either putting the game on no-fail mode or putting in a light meter will reduce the lag? ill try that

[acrox999]

Rockmeter.ini is only available in 4.0. I was just messing around to get the game faster. Perhaps a lighter rock meter files including stars, score box etc. should do. Try Uberlight theme.

[GrifSam]

Rockmeter.ini is only available in 4.0. I was just messing around to get the game faster. Perhaps a lighter rock meter files including stars, score box etc. should do. Try Uberlight theme.

i just found out that turning on no-fail reduces that lag my a whole bunch, now fofix for me is smooth. thanks for saying that thing about the rockmeter.ini thing otherwise i wouldn't figure this out! I use the Lego Rock Band Theme (light) and that works great!

[acrox999]

I guess the process of the rockmeters takes lots of resources.

[Spikehead777]

Rockmeter.ini is only available in 4.0. I was just messing around to get the game faster. Perhaps a lighter rock meter files including stars, score box etc. should do. Try Uberlight theme.

i just found out that turning on no-fail reduces that lag my a whole bunch, now fofix for me is smooth. thanks for saying that thing about the rockmeter.ini thing otherwise i wouldn't figure this out! I use the Lego Rock Band Theme (light) and that works great!

I tested toggling No-Fail, with no improvement.

And as someone mentioned earlier, yes, the latest stable version of FoFiX (3.121 Final, r1988) only uses a single core. Like I said before, I have a 2.00 GHz dual core processor, with FoFiX running on the first core, and then GlovePIE on the second core.

One of the biggest problems with lag I'm seeing, is that input seems like it is checked per frame, instead of as it is received. So if you're playing Through the Fire and Flames at 3 FPS, chances are, you're going to be missing loads of notes. What effect might putting the input events in a separate thread have? The way I see it, the inputs will be read, time-stamped (in microseconds since the start of the song), and then written to an input buffer that the game reads, checks for valid hits, and then empties. This might also help improve Jurgen's ability to play (since for some reason, he refuses to play at low FPS, just because he says the game lags too much, or so I hear).

[nefarious]

It's always used a single core which is why it runs so badly on low end dual/quad cores at high resolutions regardless of how good of a video card you have and how much memory you have. 3.2GHz OC on my dual core machine was the stable point I found where the fret board wasn't jerking off (best way to describe it) like everything else is smooth but the board starts jerking like it's trying to keep up with everything.

I've actually gone back to running customs on GH3 because it runs A LOT better.

[aander91]

Quickset>PURE SPEED

[enricodosi]

Hmm no way bout the graphich card.

I run fofix with an an overclocked dual core, i can run smooth every new game (eg modern warfare 2) but fofix still lags... tried everything... i'm desperate.

[Ambiguity]

Hmm no way bout the graphich card.

I run fofix with an an overclocked dual core, i can run smooth every new game (eg modern warfare 2) but fofix still lags... tried everything... i'm desperate.

As far as I know the current version of FoFiX can't run all the cores a processor has, 4.0 is supposed to allow you to run them all(don't quote me on this though, I'm not a dev or a tester).

Yes, 4.0 allows you to use all cores. But only applicable to Win32 users.