FoFiX 3.120+ - black screen

Gittarero · Postby **Gittarero** » Fri Sep 25, 2009 3:22 pm

death_au wrote:
jstump91 wrote: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)

I'm gonna give this a go. I'm installing Python and allt he other stuff now. Fingers crossed!

slantyr · Postby **slantyr** » Fri Sep 25, 2009 5:38 pm

death au and i had a conversation that reminded me of something about the old amd processors

they were optimized for nvidia, amd was all about nvidia until ati bought the company right around the time the am2 came out

link

something like this would be worth a try (yes it should work with xp and vista)

i'm going to sniff around nvidias website a little bit

you guys should search for your specific cpu drivers and see what you come up with

Gittarero · Postby **Gittarero** » Fri Sep 25, 2009 9:52 pm

^-- Tried the suggested .reg system patch, didn;t change anything. No driver updates available for my processor, it just uses the generic ms one only.

Ok I got the compiler going and spent some time trying out different revisions. Here's where it gets wierd...

updated to r1075, compiled fine, ran fine.
updated to r1282, compiled fine, ran fine.
updated to r1317, compiled fine, crashed on loading the .exe. Cant remember what the .exe.log said but i saved the error it spat out to cmd line when run from source. It was more descriptive but it was basically saying it didnt like the line "self.useSoloMenu = Theme.use_solo_submenu" in MainMenu.py, line 116 (AttributeError: 'module' object has no attribute 'use_solo_submenu')
Now I decided to see if 1.320 final/r1905 would compile ok and run (in case r1317 was somehow a bad revision within the set) so I tried. It wouldn't compile, saying I was missing a ton of modules which I'm still not understanding. Then I tried running r1905 from source and it WORKED CORRECTLY, THE MAIN MENU WAS WORKING! I went into a song and all the missing graphics were there. THE WHOLE GAME WORKED FINE!

So that's as far as I've got with it. I checked my original copy of 1.320 which had the error and it still does, but when I run from source, it's working perfectly. I have some free time tomorrow so maybe we can solve this soon?

death_au · Postby **death_au** » Sat Sep 26, 2009 3:41 am

I doubt the crash is related to the problem at hand, but it is certainly very interesting that the latest version worked when you compiled it yourself. If this is the case, then when I start testing on my parents' machine, it's probably not going to help much because it will work fine.
...Perhaps this is a packaging issue and NOT a code issue after all?

slantyr · Postby **slantyr** » Sat Sep 26, 2009 7:19 am

look again he said he couldn't compile r1905.

edit:

using the 2.6 version, i just tried to compile r1905 everything seemed to go normally

when i started the .exe i got this error

guaranteed, all the themes have a notes.png

i installed the pyaudio module but it didn't change the error
just didn't see the warning

when trying to run from the source an error reporting that i'm missing MSVCR71.dll appeared, but fofix still worked after the error

edit 2 more testing
r1894 is the first one i can't compile and run

Gittarero · Postby **Gittarero** » Sat Sep 26, 2009 11:46 am

I spent a couple of hours trying things out today. When I said r1905 wouldn't compile, I meant it wouldn't compile and run. It creates the files but fofix.exe was bombing out.

When I said there was a message about missing modules I didnt realise it was saying it for every revision I tried to compile, working or not. This is what it says:

Spoiler:The following modules appear to be missing
['AppKit', 'Foundation', 'Pyrex.Compiler.Main', '_curses', '_imaging_gif', '_ima
gingagg', 'core.abs', 'core.max', 'core.min', 'core.round', 'ctypes', 'ctypes.ut
il', 'distutils.ccompiler', 'distutils.command', 'distutils.command.bdist_rpm',
'distutils.command.build', 'distutils.command.build_clib', 'distutils.command.bu
ild_ext', 'distutils.command.build_py', 'distutils.command.build_scripts', 'dist
utils.command.config', 'distutils.command.install', 'distutils.command.install_d
ata', 'distutils.command.install_headers', 'distutils.command.sdist', 'distutils
.core', 'distutils.dep_util', 'distutils.dir_util', 'distutils.dist', 'distutils
.errors', 'distutils.extension', 'distutils.fancy_getopt', 'distutils.file_util'
, 'distutils.log', 'distutils.msvccompiler', 'distutils.sysconfig', 'distutils.u
nixccompiler', 'distutils.util', 'distutils.version', 'email.Utils', 'fcompiler.
FCompiler', 'fcompiler.show_fcompilers', 'hashlib', 'lib.add_newdoc', 'nose', 'n
ose.plugins', 'nose.plugins.base', 'nose.plugins.builtin', 'nose.plugins.errorcl
ass', 'nose.tools', 'nose.util', 'numarray', 'numscons', 'numscons.core.utils',
'objc', 'pygame.movie', 'pygame.movieext', 'scipy', 'setuptools', 'setuptools.co
mmand', 'setuptools.command.bdist_rpm', 'setuptools.command.develop', 'setuptool
s.command.egg_info', 'setuptools.command.install', 'setuptools.command.sdist', '
sqlite3', 'testing.Tester', 'numpy.absolute', 'numpy.arccos', 'numpy.arccosh', '
numpy.arcsin', 'numpy.arcsinh', 'numpy.arctan', 'numpy.arctanh', 'numpy.bitwise_
and', 'numpy.bitwise_or', 'numpy.bitwise_xor', 'numpy.bool_', 'numpy.ceil', 'num
py.complex_', 'numpy.conjugate', 'numpy.core.add', 'numpy.core.cdouble', 'numpy.
core.complexfloating', 'numpy.core.conjugate', 'numpy.core.csingle', 'numpy.core
.double', 'numpy.core.float64', 'numpy.core.inexact', 'numpy.core.intc', 'numpy.
core.isfinite', 'numpy.core.isnan', 'numpy.core.maximum', 'numpy.core.multiply',
'numpy.core.single', 'numpy.core.sqrt', 'numpy.cosh', 'numpy.divide', 'numpy.fa
bs', 'numpy.float32', 'numpy.float_', 'numpy.floor', 'numpy.floor_divide', 'nump
y.fmod', 'numpy.greater', 'numpy.hypot', 'numpy.int_', 'numpy.invert', 'numpy.le
ft_shift', 'numpy.less', 'numpy.log', 'numpy.logical_and', 'numpy.logical_not',
'numpy.logical_or', 'numpy.logical_xor', 'numpy.maximum', 'numpy.minimum', 'nump
y.negative', 'numpy.not_equal', 'numpy.power', 'numpy.remainder', 'numpy.right_s
hift', 'numpy.sign', 'numpy.sinh', 'numpy.tan', 'numpy.tanh', 'numpy.true_divide
']

*** binary dependencies ***
Your executable(s) also depend on these dlls which are not included,
you may or may not need to distribute them.

Make sure you have the license if you distribute any of them, and
make sure you don't distribute files belonging to the operating system.

OLEAUT32.dll - C:\WINDOWS\system32\OLEAUT32.dll
USER32.dll - C:\WINDOWS\system32\USER32.dll
COMCTL32.dll - C:\WINDOWS\system32\COMCTL32.dll
SHELL32.dll - C:\WINDOWS\system32\SHELL32.dll
ole32.dll - C:\WINDOWS\system32\ole32.dll
WINMM.DLL - C:\WINDOWS\system32\WINMM.DLL
WSOCK32.dll - C:\WINDOWS\system32\WSOCK32.dll
comdlg32.dll - C:\WINDOWS\system32\comdlg32.dll
ADVAPI32.dll - C:\WINDOWS\system32\ADVAPI32.dll
msvcrt.dll - C:\WINDOWS\system32\msvcrt.dll
WS2_32.dll - C:\WINDOWS\system32\WS2_32.dll
GDI32.dll - C:\WINDOWS\system32\GDI32.dll
multiarray.pyd - H:\Python24\lib\site-packages\numpy\core\multiarray.pyd
VERSION.dll - C:\WINDOWS\system32\VERSION.dll
KERNEL32.dll - C:\WINDOWS\system32\KERNEL32.dll
OPENGL32.dll - C:\WINDOWS\system32\OPENGL32.dll
GLU32.dll - C:\WINDOWS\system32\GLU32.dll

With older releases the list of 'appears to be missing' modules is a lot shorter but it's still there. Is this normal?

I have the same problem with compiling and running r1905 as post above me...
fofix.log

fofix.exe.log

Then I tried to compile and run r1893 and it does work. Running from the fofix.exe r1893 the main menu shows, and the missing in game graphics are all there.
fofix.log

Spoiler:(D) Checking MIDI output ports for a wavetable or synth for sound generation...
(D) MIDI output port count = 2
(D) MIDI Output port 0 found: Creative Sound Blaster MPU-401
(D) MIDI Output port 1 found: Microsoft GS Wavetable SW Synth
(D) GameEngine class init (GameEngine.py)...
(D) FoFiX v4.0.0 development (r1893) 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.
(W) OpenGL extension ARB_shader_objects not supported - shaders disabled
(D) 1 joysticks found.
(D) 1 MIDI inputs found.
(W) Image not found: M:\Games\themes\MegaLight\star3
(W) Image not found: M:\Games\themes\MegaLight\star4
(W) Image not found: M:\Games\themes\MegaLight\starfc
(W) Image not found: M:\Games\themes\MegaLight\submenuselect
(W) MegaLight\sounds\ failsound.ogg not found -- using general failsound.ogg instead.
(W) MegaLight\sounds\starpowerready.ogg not found -- using starpower.ogg instead.
(W) MegaLight\sounds\crowdcheers.ogg not found -- using data\sounds\crowdcheers.ogg instead.
(W) MegaLight\sounds\staractivate.ogg not found -- using starpower.ogg instead.
(W) MegaLight\soundsattleused.ogg not found -- using starpower.ogg instead.
(W) MegaLight\sounds\stardeactivate.ogg not found -- sound disabled.
(W) MegaLight\sounds
escue.ogg not found -- using starpower.ogg instead.
(W) MegaLight\sounds\coopfail.ogg not found -- using out.ogg instead
(D) Default animated stage for MegaLight theme = Normal
(D) Ready.
(D) 6 guitscw sounds found in sounds: guitscw1.ogg - guitscw6.ogg
(W) Image not found: M:\Games\themes\MegaLight\menu\versiontag
(D) 6 bassscw sounds found in sounds: bassscw1.ogg - bassscw6.ogg
(D) 8 drumscw sounds found in sounds: drumscw1.ogg - drumscw8.ogg
(D) View: Push: LoadingScreen
(D) 6 guitscw sounds found in sounds: guitscw1.ogg - guitscw6.ogg
(D) View: Pop: LoadingScreen
(D) View: Push: MainMenu
(D) View: Push: Menu
(W) OpenGL extension ARB_shader_objects not supported - shaders disabled
(D) View: Pop: Menu
(D) View: Pop: MainMenu
(D) View: Pop: Menu

Also, I when I was trying to find a way to sort out the missing modules message, I uninstalled python and all the dependencies and put them onto the default c: drive. When I was installing the numpy superpack it said "target cpu does not support SSE2 and SSE3". I don't know if thats related to this or the shaders thing (meaning its irrelevant to this menu issue)?

---- EDIT ----

Not sure what else to do now. Let me know what else I can do... I hope this lot helps somehow!

death_au · Postby **death_au** » Sat Sep 26, 2009 6:43 pm

Gittarero wrote:Also, I when I was trying to find a way to sort out the missing modules message, I uninstalled python and all the dependencies and put them onto the default c: drive. When I was installing the numpy superpack it said "target cpu does not support SSE2 and SSE3". I don't know if thats related to this or the shaders thing (meaning its irrelevant to this menu issue)?

This is pure conjecture at the moment, but I think you may have hit onto something there. Presumably most CPUs support SSE2/3 and whoever has packaged the windows builds has a CPU that does, so compiled FoFiX with an SSE-enabled version of numpy. However if the AMD Athlon processors do not support SSE2/3, there is the possibility of errors occuring. Otherwise there would be no need for a "nosse" version of numpy.
So presumably, if we switched out numpy with the "nosse" version and repackaged it, this might clear up the problem.

DoctorM · Postby **DoctorM** » Sat Sep 26, 2009 6:49 pm

death_au wrote:
Gittarero wrote:Also, I when I was trying to find a way to sort out the missing modules message, I uninstalled python and all the dependencies and put them onto the default c: drive. When I was installing the numpy superpack it said "target cpu does not support SSE2 and SSE3". I don't know if thats related to this or the shaders thing (meaning its irrelevant to this menu issue)?

This is pure conjecture at the moment, but I think you may have hit onto something there. Presumably most CPUs support SSE2/3 and whoever has packaged the windows builds has a CPU that does, so compiled FoFiX with an SSE-enabled version of numpy. However if the AMD Athlon processors do not support SSE2/3, there is the possibility of errors occuring. Otherwise there would be no need for a "nosse" version of numpy.
So presumably, if we switched out numpy with the "nosse" version and repackaged it, this might clear up the problem.

This was suggested before. Athlon XP's have no SSE2 or 3. SSE2 was implemented in the Athlon64.

Gittarero · Postby **Gittarero** » Sat Sep 26, 2009 7:59 pm

death_au wrote:
Gittarero wrote:Also, I when I was trying to find a way to sort out the missing modules message, I uninstalled python and all the dependencies and put them onto the default c: drive. When I was installing the numpy superpack it said "target cpu does not support SSE2 and SSE3". I don't know if thats related to this or the shaders thing (meaning its irrelevant to this menu issue)?

This is pure conjecture at the moment, but I think you may have hit onto something there. Presumably most CPUs support SSE2/3 and whoever has packaged the windows builds has a CPU that does, so compiled FoFiX with an SSE-enabled version of numpy. However if the AMD Athlon processors do not support SSE2/3, there is the possibility of errors occuring. Otherwise there would be no need for a "nosse" version of numpy.
So presumably, if we switched out numpy with the "nosse" version and repackaged it, this might clear up the problem.

Yeah that totally makes sense.

I've been playing on r1893 and it's absolutely fine. I notice this release seems to run better on my crappy PC than previous versions but it's still bugging me why I can't compile r1905 or r1906 properly... It builds everything, but when I try to run fofix.exe, it bombs straight away:
fofix.exe.log

fofix.log

- None of the themes are missing the notes.png file.

Any idea how to fix that?

Bruut · Postby **Bruut** » Sun Sep 27, 2009 5:29 am

Ok, I installed all dependencies again, this time with the command line option "/arch nosse" on the numpy installer, so that would be:

numpy-1.3.0-win32-superpack-python2.6.exe /arch nosse

I ran from source and voila, menu is there.

I hope this works for everyone here.

max26199 · Postby **max26199** » Sun Sep 27, 2009 7:28 am

Gittarero wrote:Any idea how to fix that?

i missed something when implementing Issue941
does r1907 solve it?

slantyr · Postby **slantyr** » Sun Sep 27, 2009 2:23 pm

just tested r1909 and everything compiles and works again :)

luciuskarf · Postby **luciuskarf** » Mon Sep 28, 2009 3:44 pm

I just downloaded the Py2.4 and the modules, downloaded the revision 1909 and compiled, it works fine =)

Thanks people, this version runs extremely better than 3.100 Final ^^

death_au · Postby **death_au** » Mon Sep 28, 2009 7:42 pm

Now that people have it compiling properly, could someone who had the problem and now doesn't post their library.zip?
I want to try grabbing some things from it and see if I can get a fix for people who don't want to compile their own.

Gittarero · Postby **Gittarero** » Mon Sep 28, 2009 9:32 pm

death_au wrote:Now that people have it compiling properly, could someone who had the problem and now doesn't post their library.zip?
I want to try grabbing some things from it and see if I can get a fix for people who don't want to compile their own.

http://www.megaupload.com/?d=WN0BU7SU

FoFiX 3.120+ - black screen

Re: FoFiX 3.12beta 2 - black screen

Uncle Fester

Re: FoFiX 3.12beta 2 - black screen

Re: FoFiX 3.12beta 2 - black screen

Blue Heaven!

Re: FoFiX 3.12beta 2 - black screen

Uncle Fester

Re: FoFiX 3.12beta 2 - black screen

Re: FoFiX 3.12beta 2 - black screen

Blue Heaven!

Re: FoFiX 3.12beta 2 - black screen

Re: FoFiX 3.12beta 2 - black screen

Re: FoFiX 3.12beta 2 - black screen

Re: FoFiX 3.12beta 2 - black screen

Re: FoFiX 3.12beta 2 - black screen

Uncle Fester

Re: FoFiX 3.12beta 2 - black screen

Re: FoFiX 3.12beta 2 - black screen

Blue Heaven!

Re: FoFiX 3.12beta 2 - black screen

Re: FoFiX 3.12beta 2 - black screen

Who is online