Open natrius opened 3 years ago
Thanks for the report! This is a known problem for a few years already. Currently we have to start the game as a command line application because of some bugs in freepascal on some Windows installs where a third party libraries crashes when it tries to log to command line output.
Ah, i see, no problem. Could not find another issue with that libpng problem, thats the main issue i wrote, not because of the CMD itself. Guessed already its for some sort of debugging stuff.
The PNG message would be fixed by updating the SDL_image DLL to >= v2.0.3.
Probably dumb question, but do you guys have to do that or can i do that on my own? Downloading from https://www.libsdl.org/projects/SDL_image/ and copying the files into the usdx folder did not work at all, had to reinstall usdx after that. (my mistake for not making a backup).
You should be able to replace the dlls on your system. What exactly happened when you tried that? Any error message?
I have the exact same problem, I'm on Windows 10, @s09bQ5 when you say "replace the dlls on your system" do you mean Windows System or the USDX Installation? where exactly should I replace it? what is the directory path? I really would love to solve this.
@natrius @E-World333 there were some smaller API changes, thus just replacing the DLL won't work for the windows build. For now, I'd suggest you to just ignore that command line window in the background, it should not keep you from playing the game as usual. Those PNG messages can be ignored, too.
Actual behaviour
When starting the game on Windows 10 (Windows 7 as well) a CMD appears with
libpng warning: Interlace handling should be turned on when using png_read_image
multiple times written in it. Additional 3 lines of that warning appears when entering the song-choice. Reproduceable.On Windows 7 it seems to sometimes minimize the game to show the CMD. Bit annoying but it goes away sometime by reestarting sometimes and alt-tabbing. On Windows10 this does not seem to happen.
Its not critical or anything, more an annoyance. Tested on 3 different machines, 1x Windows 7, 2x Windows 10
Expected behaviour
No background CMD with errors.
Steps to reproduce
Details
Provide some additional information: