elishacloud
commented
8 months ago What game are you running with this issue? It looks like it may be a nullptr exception.
Closed SilentMRG closed 1 day ago
elishacloud
commented
8 months ago What game are you running with this issue? It looks like it may be a nullptr exception.
SilentMRG
commented
8 months ago The one in the title: State of Emergency =)
elishacloud
commented
8 months ago LOL. I thought you were saying that the crash was a state of emergency.
SilentMRG
commented
8 months ago I agree it's a pretty "peculiar" name for a game, hehehe. XD The real name of the error is "Memory Exception", and after this error the infamous "Appcrash" error occurs.
elishacloud
commented
4 days ago Can you try with the latest build? I fixed a number of errors that could have lead to a crash on exit.
SilentMRG
commented
4 days ago Elisha, I no longer had the game installed, so I installed it, played for 30 minutes and when I exited the same problem...
I am attaching my dxwrapper configuration with the log, so you can kindly take a look and tell me whether my configuration is ok or not, perhaps, I am the culprit in making an invalid configuration which is resulting in the error aforementioned. I should mention that no AppCrash errors occurred this time.
Thanks for pointing me to the new version!
SilentMRG
commented
4 days ago I was almost forgetting... I marked this: "HandleExceptions = 1" In the "ini" file. I think this line is used to deal with these "exceptions" errors; anyway, the game or I are out of luck. XD
elishacloud
commented
4 days ago I suspect that some interface is not getting released by the game until exiting causing this issue. I will need to look at this later.
SilentMRG
commented
4 days ago At the end of the log it says this:
"opened file SAVEGAMES\GLOBAL STATUS\DEFAULT.OPT"
Wouldn't it be the dxwrapper trying to access something it's not supposed to access or the game getting in the way of the dxwrapper and doing this? Accessing something that is not meant for him to access. I don't understand the subject, but this specific line caught my attention.
SilentMRG
commented
3 days ago Just for the record (maybe it helps), the folder is not called "SAVEGAMES", it is called "SaveGames", and the "GLOBAL STATUS" folder is called "Global status". You know, some programs differ in upper and lower case letters, I don't know if this is the case with dxwrapper. In the image below, you can see that there is another folder along with "Global status":
Inside the "0-mrg(Revolution)" folder there is a file "SAVEDGAME.DAT", and inside the "Global status" folder, two files: "DEFAULT.OPT" (mentioned in the log), and "GAMESAVE.DAT".
SilentMRG
commented
3 days ago I apologize for the consecutive posts, I took a look at the dxwrapper report and found these lines:
"844 22:48:15.960 d8_Direct3DCreate8 844 22:48:15.960 GetD3d9UnnamedOrdinal cannot find unnamed ordinal '18' in System32 d3d9.dll! 844 22:48:15.960 Direct3D9SetSwapEffectUpgradeShim Error: Failed to get address!"
Well, my system has DirectX 9 installed, it seems the report is saying otherwise?
elishacloud
commented
3 days ago The crash dump file you send does not show which module crashed. What OS are you using? Can you upload the full dxwrapper log file?
844 22:48:15.960 GetD3d9UnnamedOrdinal cannot find unnamed ordinal '18' in System32 d3d9.dll!
844 22:48:15.960 Direct3D9SetSwapEffectUpgradeShim Error: Failed to get address!This error means dxwrapper could not find the Direct3D9SetSwapEffectUpgradeShim function. Either you are using an OS that does not have that function or the fingerprint of that function is different on your OS or the d3d9.dll file is corrupt.
844 22:48:15.960 d8_Direct3DCreate8Since you are using d3d8to9, can you try the released version of d3d8to9 from here and see if you have the same issue? I want to see if it is an issue with dxwrapper or d3d8to9.
SilentMRG
commented
3 days ago I'm using Windows 7 64-bit, the same Windows and the same laptop that I've been using to test several old games with dxwrapper. And I don't remember this DX9 error in the other versions. Well, I'm going to reinstall DX9 here to see if that solves it.
Here is the log with the stub of your launch, notice that it is a dxwrapper log plus the error log mentioned above: log.zip
And here is just the error log: log (2).zip
Because with the dll "d3d8to9" no dxwrapper report was created.
Edit: I don't remember these lines...
"5924 16:32:45.785 Loaded library: winmm.dll 5924 16:32:45.815 Installing memory management hooks 5924 16:32:45.815 Installing messaging hooks 5924 16:32:45.815 Installing display mode hooks 5924 16:32:45.879 Installing registry hooks 5924 16:32:45.879 Installing Win32 hooks"
In previous versions of dxwrapper. In my ignorance winmm.dll does not communicate correctly with Windows 7, it seems to be a Windows 10 dll. Despite that, I was having an "Exception" error with cnc-ddraw here: https://github.com/FunkyFr3sh/cnc-ddraw/issues/152
Funky was able to fix it, the problem was that the dll was accessing the incorrect ".exe". Wouldn't that be the case here? I know it's about "ddraw", but you know... Sometimes incorrect paths are accessed.
elishacloud
commented
3 days ago I'm using Windows 7 64-bit, the same Windows and the same laptop that I've been using to test several old games with dxwrapper. And I don't remember this DX9 error in the other versions.
Ok, don't worry about the error message. That d3d9 function is not available on Windows 7, only Windows 10 and 11.
Here is the log with the stub of your launch, notice that it is a dxwrapper log plus the error log mentioned above:
That is a game log. I wanted to see the dxwrapper log. It should be called something like dxwrapper-game.log
In previous versions of dxwrapper. In my ignorance winmm.dll does not communicate correctly with Windows 7, it seems to be a Windows 10 dll.
That is weird. Maybe I am missing some functions in the dll. Are you still seeing that issue with this latest release? This could be the issue because the game could be calling a winmm function on exit that is missing from my stub. Can you try with a different stub? Maybe dsound.dll or dinput8.dll?
Funky was able to fix it, the problem was that the dll was accessing the incorrect ".exe". Wouldn't that be the case here?
I would need to know more details about this to say. Not sure why the dll is accessing an exe file in the fist place.
SilentMRG
commented
3 days ago That is a game log. I wanted to see the dxwrapper log. It should be called something like
dxwrapper-game.log
Where is this log created? No such log is created here, only the two logs I sent. In fact, in all versions of dxwrapper I never saw this log. On my side, it is always the sent log (of the game) that is created. And no, I did not disable log in the "ini" file settings.
That is weird. Maybe I am missing some functions in the dll. Are you still seeing that issue with this latest release? This could be the issue because the game could be calling a winmm function on exit that is missing from my stub. Can you try with a different stub? Maybe dsound.dll or dinput8.dll?
For the record, I installed the latest version of DX9 downloaded here: https://www.microsoft.com/en-us/download/details.aspx?id=8109
He updated some things and the error remains the same. Using any of these dlls results in the same error.
elishacloud
commented
3 days ago Where is this log created? No such log is created here, only the two logs I sent.
The log will be located in the same folder as the dxwrapper.dll file. The log file has been there since day 1. All releases of dxwrapper has the same log file. If there is no log file then it means that dxwrapper is not being loaded. What dxwrapper stub are you using? Maybe try a different dxwrapper stub?
SilentMRG
commented
3 days ago The log will be located in the same folder as the dxwrapper.dll file. The log file has been there since day 1. All releases of dxwrapper has the same log file. If there is no log file then it means that dxwrapper is not being loaded. What dxwrapper stub are you using? Maybe try a different dxwrapper stub?
Elisha, the first zip I uploaded just above has this file, it's called "dxwrapper-kaospc.log". I assume you didn't open it. I even eplaned "Here is the log with the stub of your launch, notice that it is a dxwrapper log plus the error mentioned log above:" Lol... now I don't understand anything. XD
SilentMRG
commented
3 days ago English is not my native language, so maybe I didn't express myself correctly. The "log (2).zip" file is just the same as what was posted in the main post. In this second test, I used "d3d8to9" from the link you provided, but the log "dxwrapper-kaospc.log" was not created.
And in "log.zip" there is the file "dxwrapper-kaospc.log", because in this first test I used the d3d8 dll of your version. The other dlls you mentioned worked, but presented the same error, so nothing worth mentioning.
elishacloud
commented
2 days ago The "log (2).zip" file is just the same as what was posted in the main post. In this second test, I used "d3d8to9" from the link you provided, but the log "dxwrapper-kaospc.log" was not created.
Sorry I missed that.
I see this line in the log file:
5924 16:32:46.058 CreateProcessWHandler C:\Windows\system32\rundll32.exe C:\Windows\system32\gameux.dll,GameUXShim {6a62c0b8-5137-4a10-a174-124952a9c068};D:\Mateus\State Of Emergency\KaosPC.exe;5920This is caused by the DisableGameUX. You could try adding this option to the ini file and disabling it.
Edit: I don't remember these lines...
These are new things I added into the latest release for the dd7to9 and d3d8to9 features. It helps with compatibility issues in these older games. Since the crash happens even in older version before I added that I don't think it is related to that.
elishacloud
commented
2 days ago BTW: Did you try the released version of d3d8to9 from here instead of dxwrapper? I just want to see if the issue is in d3d8to9 or in dxwrapper.
SilentMRG
commented
2 days ago This is caused by the
DisableGameUX. You could try adding this option to the ini file and disabling it.
I disabled DisableGameUX and the same error occurred, here is the log: dxwrapper-kaospc.zip However, I took a quick look and didn't see that line.
BTW: Did you try the released version of d3d8to9 from here instead of dxwrapper? I just want to see if the issue is in d3d8to9 or in dxwrapper.
I just did it with just d3d8to9 and nothing else, a log was created: log.zip
SilentMRG
commented
2 days ago The cause of the error is version 1.12.0 of d3d8to9. I just tested version v1.11.1 and the error did not occur! I would venture to say that many random games must be suffering from this version 1.12.0 exception error.
SilentMRG
commented
2 days ago Just to be sure, would it be possible for you to provide a d3d8 stub of version 1.11.1 so that I can test with dxwrapper?
Unfortunately, d3d8to9 does not work directly with dxwrapper, of course, because you made changes to the d3d8 stub that comes with dxwrapper to work with dxwrapper.
I thank!
elishacloud
commented
2 days ago Just to be sure, would it be possible for you to provide a d3d8 stub of version 1.11.1 so that I can test with dxwrapper?
Ok, good catch. If it is caused by 1.12.0 then this one should fix it. I just removed the check-in that likely has the issue: dxwrapper.zip
SilentMRG
commented
2 days ago All very well! Using this configuration: dxwrapper.zip
Elisha, thank you for all your help and patience! =)
elishacloud
commented
2 days ago @SilentMRG, can you try with this build? I put a proper fix in for this rather than just reverting the bad PR.
Edit: Please try this one instead: dxwrapper.zip
SilentMRG
commented
2 days ago Edit: Please try this one instead: dxwrapper.zip
Here is the log: dxwrapper-kaospc.log The latter presented the same error.
SilentMRG
commented
2 days ago I just want to take advantage of the topic and say that Freedom Fighters, the vanilla version and not the 2020 re-release, suffers from the same problem when exiting the game. I have the retail version and I just tested it, with the other version that didn't lock the State of Emergency, and with this last one.
Here are the logs: dxwrapper-freedom.log error.log
elishacloud
commented
2 days ago I was able to find and download State of Emergency, using a no-cd patch. I am not seeing the crash after starting a game and then exiting. Is there some special steps to do to get the crash?
Here is the build I am testing: dxwrapper.zip
SilentMRG
commented
2 days ago No steps, just the basics, get to the main menu and exit the game using the "Quit" option. Or load a game, enter the gameplay and then exit through the gameplay menu and then through the main menu.
What size No-CD are you using? Mine here is 1.97 MB (2,067,923 bytes), I don't know if that changes anything.
elishacloud
commented
2 days ago I am using the one from here.
SilentMRG
commented
2 days ago Try this: KaosPC.zip
SilentMRG
commented
2 days ago I was forgetting, I tested this last build and the same error occurred.
Maybe the problem is Windows 7? I mean, if you're optimizing things for Windows 10 and 11, eventually things will stop working on versions of Windows before 10.
elishacloud
commented
2 days ago Yes, I am testing with Windows 10. Could be something on Windows 7.
Edit: But since the one change worked then I need to figure out what is going on because it is a code change that fixed it.
SilentMRG
commented
2 days ago Just to be clear, the game never crashed when starting, it always crashes when exiting, with an exception error and sometimes an AppCrash.
SilentMRG
commented
2 days ago In fact, the same error occurs with Freedom Fighters when exiting, but in this case it is an AppCrash. With that other version it didn't crash. Look, I'm not programmer, but I'm thinking it might be a memory leak or something.
elishacloud
commented
2 days ago Ok, let me run some tests later when I have some time.
SilentMRG
commented
2 days ago Sometimes one of the dlls tries ferociously to eat memory while the game is running, and when it exits there is some kind of memory clogging or whatever, which ends up causing the game to freeze. Maybe there is a technical explanation for the nonsense I just said. XD
elishacloud
commented
1 day ago I tried Freedom Fighters also and I don't see any crashes on exit either. I used Windows 10 for both of the, I am installing Windows 7 to see if that makes a difference.
Here is what I am using to test: dxwrapper.zip
elishacloud
commented
1 day ago Ok, I can reproduce the crash on Windows 7. It does not seem to happen on Windows 10. Looking into it.
elishacloud
commented
1 day ago Ok, I believe this is the fix for the issue: dxwrapper.zip
Edit: I created a pull request for the fix here.
SilentMRG
commented
1 day ago Ok, I believe this is the fix for the issue: dxwrapper.zip
Edit: I created a pull request for the fix here.
It worked like a charm! Tested in State of Emergency and Freedom Fighters. =)
SilentMRG
commented
1 day ago I'm sure that all D3D8 games converted to D3D9 were facing this error in Windows 7. Strange that no one else reported this, maybe I'm the only crazy person in the world when using Windows 7 for games.
Edit: Just a side note... I remember using dxwrapper with Project Eden: https://www.gog.com/en/game/project_eden
It was a while ago, so maybe it's a false memory, but I remember it crashing when exiting with an exception error, and sometimes it would show a (rare) appcrash error when playing, anyway, I need to test the fix on it these days. Maybe this error was haunting me since that time, and due to lack of time I didn't report it here.
elishacloud
commented
1 day ago I don't know if it is certain patch levels in Windows 7 or what, but this issue should happen to most d3d8 games, if you have the right setup.
SilentMRG
commented
1 day ago Exactly... Well so far so good, I think I can close this, from what I understand it has been fixed. =D
Thanks man!
elishacloud
commented
1 day ago BTW: we did get another report of this issue here. Windows 7 64bit, crash on exit, everything is the same.
SilentMRG
commented
1 day ago Cowboy, you've discovered the mother of all fixes! This old leather has never seen anything like this before.
Hello...
Using your wrapper will cause a memory error or something like that every time I exit the game. In general, everything works fine, without problems or crashes, but when I exit the game this always happens:
Activate Shutdown via exit Music already stopped opened file SAVEGAMES\GLOBAL STATUS\DEFAULT.OPT
Note: Not using your wrapper will not cause this issue, however, I will be stuck with extremely fast animations among other appcrashes that are inherent to an older game. Using d3d8to9 only also causes the same problem.
Cheers! And thanks for your attention!