FoFiX 3.120+ - black screen

[Quenox]

Just decided to run FoF on my laptop, downloaded latest version. AMD Turion 64 X2 processor, ATI Radeon 2600M graphics. The screen only flickers up for a second, then immediately crashes. Doesn't even create a fofix.ini to speak of, in any location. Running it from a folder on the root of the drive too. Here is my fofix.log, 3.120 py2.6:

(D) Checking MIDI output ports for a wavetable or synth for sound generation...
(D) MIDI output port count = 1
(D) MIDI Output port 0 found: Microsoft GS Wavetable SW Synth
(D) GameEngine class init (GameEngine.py)...
(D) FoFiX v3.120 RC 1 starting up...
(D) pygame version: 1.9.0release-svn2553
(D) Initializing audio.
(D) Audio configuration: (44100, -16, 2)
(D) Initializing pygame.mixer & audio system at 44100 Hz.
(D) Initializing video.

And fretsonfire.log for 3.100, it doesn't work for me either:

(D) Checking MIDI output ports for a wavetable or synth for sound generation...
(D) MIDI output port count = 1
(D) MIDI Output port 0 found: Microsoft GS Wavetable SW Synth
(D) GameEngine class init (GameEngine.py)...
(D) FoFiX v3.100 final starting up...
(D) pygame version: 1.7.1release
(D) Initializing audio.
(D) Audio configuration: (44100, -16, 1)
(D) Initializing pygame.mixer & audio system at 44100 Hz.
(D) Initializing video.

I was using 3.something on my desktop before, and it has a Athlon 64 X2 Black Box.

[death_au]

Same error here =/
<snip>

This one at least proves once and for all it's not the shaders at fault.
And some of the images are being displayed, just not the menu-like ones... Thanks for the info and screenshots. I don't know if they help yet, but they're definitely something to ponder.

@Quenox, you're problem seems unrelated to this issue (I think). Did you also get a fofix.exe.log?

[daStorm]

This one at least proves once and for all it's not the shaders at fault.

I agree. Originally I planned to exchange my GeForce 4 MX (don't laugh) by another graphics card, but I guess now I can skip that.

[death_au]

Just managed to test 3.120 Final (py2.6, pyogl3) and 3.120 Beta 2 (py2.4, pyogl2) on my parent's computer:
AMD Athlon XP 2400+, ATI Radeon 9250
and.... I got the black screen error. No closer to a solution, but at least I've managed to replicate it. I might have an AMD desktop at home, so I'll try again on that (I'll have more access to that one than the one at my parents' place).
Being an AMD thing makes no sense to me. Especially when 3.100 works fine. If I can replicate the issue at home, I'll start rolling back svn revisions in an attempt to find where the code changed to cause the problem.

[Gittarero]

What needs to happen is for someone who has the problem to go through each build from 3.100 final to 3.120 final. Then we can pin point between exactly which builds the problem has appeared...

If someone from the team can organise the builds I'd be more than happy to go through them all and report back.

Best idea for now, no?

Edit: Hadn't seen the post above me which is basically saying the same thing

[death_au]

Well I've narrowed it down further. It's between 3.100 final and 3.120 beta 1. So that's somewhere between r1075 and r1352
I've re-opened FoFiX issue 888 and am updating my progress on the issue both there and here.

[Gittarero]

Thanks for all your efforts. I really appreciate it as do many other people.

[death_au]

Damn. My computer at home has an AMD processor, but it's a Sempron 3300+, and it doesn't have the black screen issue. Meaning there's no way for me to search through the revisions for the problem until next Thursday... (next time I'm at my parents' place). Sorry guys.

[KTownEgghead]

Damn. My computer at home has an AMD processor, but it's a Sempron 3300+, and it doesn't have the black screen issue. Meaning there's no way for me to search through the revisions for the problem until next Thursday... (next time I'm at my parents' place). Sorry guys.

No problem, just keep moderating :) Congrats on that, BTW.

[Gittarero]

Damn. My computer at home has an AMD processor, but it's a Sempron 3300+, and it doesn't have the black screen issue. Meaning there's no way for me to search through the revisions for the problem until next Thursday... (next time I'm at my parents' place). Sorry guys.

I think the trend in common has been AMD ATHLON processors. Every post I've seen has said Athlon, as far as I remember.

[KTownEgghead]

I can vouch for this problem... I have an AMD Athlon x2 processor, and I don't know why it does it :P

[jstump91]

Since we now have a range of revisions where this issue might have been introduced, we need somebody who has the issue (and has some patience) to do a binary search.

(That means updating to the revision in the middle of the range and seeing whether the issue occurs so that it's possible to eliminate half of the possible range, and repeating this process until you get down to just the revision that introduced it.)

It certainly beats checking around haphazardly.

[death_au]

Since we now have a range of revisions where this issue might have been introduced, we need somebody who has the issue (and has some patience) to do a binary search.

(That means updating to the revision in the middle of the range and seeing whether the issue occurs so that it's possible to eliminate half of the possible range, and repeating this process until you get down to just the revision that introduced it.)

It certainly beats checking around haphazardly.

If no one does it by then, that's my current plan for next Thursday. Would be good if someone could do this in the meantime though.
If you want to try, but you've never run from source before, when you download the code from the SVN, I'd roll back to revision 1075 immediately, so you can tell if you have your python environment set up right (since we know that 3.100 final works fine)

[tibiazak]

don't know if this'll help, but i've got the same issue (have yet to try changing the .ini and/or putting it in a new folder - i extracted the archive over an old install of one of the betas - not sure which) and i do NOT have an AMD processor.

specs: intel core2duo 1.56 ghz
2 gb ram
GeForce 8600m gfx card
Windows 7.

like i said, dunno if it helps... gonna go try the .ini/moving folder stuff.

edit: that fixed the problem for me. i deleted the .ini and created a new folder (with a fresh extraction) for FoFiX. no problems now.

[Bruut]

Just got the issue myself here.

Installed on a spare computer at my parents. It is a 'clean' computer, just formated, only installed windows XP with updates and an antivirus (nod32). I use the 3.120 final from the installer. Computer is a Athlon XP 2100, G-Force 6600GT. Fullscreen doesn't help either, nor does changing the theme.

Odd thing is, I have an AMD X2 here as well, and that runs it perfectly..

Weird things happening.

P.S. issue still exists in rev 1905.