Yuri's Revenge: Invisible mouse in pause menu; crash on exit

[jimfranke]

As soon as I enter the pause menu in Yuri's Revenge the mouse cursor disappears forcing me to kill the process through the Windows Task Manager. This happens with both the distributed version of cnc-ddraw through CnCNet, as well with the latest version downloaded from this repo. The older ts-ddraw however doesn't seem to have this problem.

Besides this issue the game seems to freeze upon exiting the game though the menu's, hanging the "battle control terminated" voice line, crashing the process and making it necessary to reboot Windows. Again, not happening in ts-ddraw.

Running Windows 11 Pro with latest updates applied. Tried different combinations of renderers, fullscreen/windowed etc as well as other options through the config exe.

[FunkyFr3sh]

This is not a cnc-ddraw bug, it's a bug with the cncnet client you're using. It does overwrite your ddrraw.ini with a older incompatible one (you can open ddraw.ini after the game start and compare it with the original one from cnc-ddraw.zip and you will see)

[jimfranke]

Ah that explains thanks! I will try modifying the INI to read-only and see what happens :)

Perhaps it's possible to copy cnc-ddraw to the Resources/ subfolder from where CNCNet copies its files to the game root directory. I'll post an update here later for future reference.

[LuKeSt0rm]

Perhaps it's possible to copy cnc-ddraw to the Resources/ subfolder from where CNCNet copies its files to the game root

This works as long as you don't update through CnCNet. (tested for function of my RA2/YR R2P launcher )

[jimfranke]

@LuKeSt0rm Thanks! I can also confirm this workaround fixes the issues I was having :)

[jimfranke]

@LuKeSt0rm @FunkyFr3sh Any idea if the crashes that sometimes happen on exiting the game through the pause menu have something to do with cnc-ddraw? Mouse issues are resolved and I have verified that ddraw.dll and ddraw.ini are unchanges by CnCNet.

[FunkyFr3sh]

I haven't heard about such an issue with YR yet, but you could try a test run with the debug build: #44