And yet another two builds to test: this and this. The first one is just 1.8.10 which I built by myself and the second is the last intermediate build not tested yet.
_mental_ wrote:And yet another two builds to test: this and this. The first one is just 1.8.10 which I built by myself and the second is the last intermediate build not tested yet.
We are getting close. Here is a build from the 1.9 maintenance branch with the offending changes reverted. I want to make sure that the crash is gone. Still need to figure out how to fix it properly.
_mental_ wrote:We are getting close. Here is a build from the 1.9 maintenance branch with the offending changes reverted. I want to make sure that the crash is gone. Still need to figure out how to fix it properly.
The mentioned crash is caused by this commit, the manifest changes in particular. I have no Windows 10 nor the needed hardware, so it may take a while to fix it properly.
As clearly stated in a previous topic there is no good solution for this crash.
I coded a small tool to update executable file's manifest, so GZDoom will not crash on Intel's integrated video. Run it from command line with path to executable to "fix" as a parameter.
P.S. I think this topic can be moved to Closed Bugs.
_mental_ wrote:As clearly stated in a previous topic there is no good solution for this crash.
I coded a small tool to update executable file's manifest, so GZDoom will not crash on Intel's integrated video. Run it from command line with path to executable to "fix" as a parameter.
P.S. I think this topic can be moved to Closed Bugs.
Thanks, the small tool works great, I can run Gzdoom 1.9 and even 2.1 now.
When I launch the program nothing happens, I tried to launch it from Command line with or without Admin and it's only say:
"Usage: C:\Users\*****\Downloads\wtfi.exe <file.exe> <...>", the problem is still there.