-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AmigaOS4 build for SDL2 tend to freezes #55
Comments
Perhaps and SDL2 bug? @capehill |
Will try sdl1 version, but if i remember well sdl1 version luck some functionality in devolution, like window mode, scaling, etc ? And issue start to happen only with load/save changes, before all was good with the same sdl1. But will check with sdl1 as well |
Mean in last phrase sdl2 of course, just cant edit post from phone |
Hmm, okay. |
My test build is based on this commit 9f83bdd (24th of Dec). I'm using the latest SDL2 build we have and I don't see anything special in window/fullscreen mode, game starts. Edit: after rebasing, it still works for me. I have a slightly hacked build, with SDL_Mixer disabled. I noticed a problem if you start with -f parameter, the engine seems to call SDL_GetTicks before SDL_Init. With the latest AmigaOS 4 SDL2 implementation it simply crashes and I should probably make it more robust, but I think it's still a mistake on the application side. After all, SDL_GetTicks is supposed to return the counter value since the library initialization. |
@kas1e Any news from you? Can you try a clean build? Can you provide a test build with all SDL serial logs on? Which commit you are based on? |
@capehill |
Build today's version of devolution over SDL2, and when I just run it in fullscreen mode it shows me intro "blizzard" animation, and once I hit "ESC" it just freezes. No crash log, nothing. CPU loading 0%, the whole system still operational.
Also setting the "fullscreen" option in .ini file didn't take into account, the game runs in full screen anyway. Like .ini didn't parse correctly anymore. I checked via snoopdos, and .ini file surely opened.
I can't say when it start to be broken, but it was ok a few months ago.
The text was updated successfully, but these errors were encountered: