search

matatk / agrip

AGRIP AudioQuake and Level Description Language (LDL)
http://agrip.org.uk
Other
16 stars 6 forks source link

AudioQuake.exe crashes on Windows 10 #40

Closed Finnboy94 closed 3 years ago

Finnboy94 commented 4 years ago

When I build with python build.py on Windows 10, the build is completed, but the AudioQuake.exe file in Dist says> Failed to start script AudioQuake.

matatk commented 4 years ago

Hi @Finnboy94 thanks for your bug report. Oddly I am not getting the same error—I was actually able to follow the current build instructions and can get both the launcher and the game running. This appears to be good news, in that it should be possible to get it working for you, but I'm not currently sure how to debug the built AudioQuake.exe file.

I found that PyInstaller offers a --debug option that causes the built exe file to output various infomration when it runs. However, after running PyInstaller manually with this option enabled (pyinstaller --debug all -y AudioQuake.spec) the behaaviour of the genereted exe file was not changed, so I must be missing something.

Does the error message you get have any more to it than "Failed to start script AudioQuake"?

Finnboy94 commented 4 years ago

No, the error is just that one sentence. I am using Python 3.8.1. I was unable to build with PyInstaller's normal version, so I downloaded and installed PyInstaller development version and am able to build, but the error persists. It seems that there might be some modules missing or something -- I can attach the Warning txt file when I get back to the computer where the build was done.

matatk commented 4 years ago

Thanks for the update. I'd be interested to hear about the problems had with using PyInstaller 3.4. I plan to move to the latest Python and PyInstaller soon, too. Currently I'm using Python 3.7.3.

I figured out how to request debugging info for the built AudioQuake.exe: in AudioQuake.spec, if you change the lines debug=False, to debug=True, and console=False, to console=True, you can then run dist\AudioQuake\AudioQuake.exe in the command prompt and it will output lots of debugging messages. They should identify what the problem is (if you're happy to paste them all in here then great, but they will include the path on your system to the AudioQuake folder, just so you know).

Finnboy94 commented 4 years ago

Actually, after changing Debug=True and Console=True, the program just exits when started from dist. I have attached the warning txt file from Build folder. warn-AudioQuake.txt

matatk commented 4 years ago

Thanks for your update. When you set Debug and Console to "True", are you running AudioQuake.exe in the Command Prompt? I would expect it to produce some output even if it crashes.

Thanks for sending the warnings file. Interestingly, the one generated when I run a build is similar but has far fewer things missing, and a cursory glance showed none from the standard library.

When I run the command python in a Command Prompt, it tells me that I'm using the 32-bit version of Python—I wonder if you are using the 64-bit one (if so, maybe that's the cause of the issue)?

matatk commented 3 years ago

Closing this for now, as I can't reproduce it, and hopefully the latest code fixes it. Feel free to re-open if it's still a problem; thanks for your bug report.