Reply to Re: FreeDink V109.6 Crash to desktop
If you don't have an account, just leave the password field blank.
Hmm, perhaps, but at the same time, the fact that it doesn't crash in V108.4 or the OG game makes me think it's probably not the DMOD's fault.
Looking at the Free Dink changelog, it seems a lot has been rewritten...
The main things that stick out to me are:
- Move from C to C++ : this could have accidentally introduced some obscure bug somewhere I suppose?
- Rewrite graphics/sounds/inputs against SDL2 : this seems like another possible major change that can have some obscure unforeseen consequences related to loading/unloading screens
I kind of want to dig into it myself, but I'm but a poor .NET programmer and I am unfamiliar with compiling big projects with complicated dependencies... And building for Windows seems especially tricky with it. I messed with it for a few hours and didn't even manage to resolve the SDL dependencies.
Although, a thought just occurred to me right now. I had the same issue manifest under Ubuntu, so I should just try building it for Ubuntu in the first place, since I might have less issues with that. Then I can start poking around the code and see what happens... There's a 99.9% chance it will take me forever to understand how the engine works and I'll just give up, but hey, at the very least it could be an interesting learning experience.
Looking at the Free Dink changelog, it seems a lot has been rewritten...
The main things that stick out to me are:
- Move from C to C++ : this could have accidentally introduced some obscure bug somewhere I suppose?
- Rewrite graphics/sounds/inputs against SDL2 : this seems like another possible major change that can have some obscure unforeseen consequences related to loading/unloading screens
I kind of want to dig into it myself, but I'm but a poor .NET programmer and I am unfamiliar with compiling big projects with complicated dependencies... And building for Windows seems especially tricky with it. I messed with it for a few hours and didn't even manage to resolve the SDL dependencies.
Although, a thought just occurred to me right now. I had the same issue manifest under Ubuntu, so I should just try building it for Ubuntu in the first place, since I might have less issues with that. Then I can start poking around the code and see what happens... There's a 99.9% chance it will take me forever to understand how the engine works and I'll just give up, but hey, at the very least it could be an interesting learning experience.
