FeralChild64

Well, the debugger window is completely frozen for me, it does not react on keypresses at all. I can’t type HELP there. If I start moving windows around, debugger window...

AFAIK this is an emulation issue.

I don’t remember right now - did you set `machine = svga_s3trio64` in DOSBox-X?

The demo definitely used to work correctly on my home PC in mid 90’s, equipped with Phoenix S3 Trio 64 card - but I definitely had older drivers, as v1.70.04...

Tried the Critical Mass demo once again on: - DOSBox X (current GIT), machine type s3trio64 - DOSBox Staging (current GIT) - 86Box v4.1.1, emulating Phoenix S3 Trio 64 Guest...

One more observation: switching DOSBox X to machine `svga_s3trio64v+` fixes the problem with Critical Mass game demo and Trio 32/64 driver v1.70.04.

I suppose the values are the same as the "modeline" values we used to calculate on Linux to get custom resolutions back in the CRT days. There are online calculators...

@johnnovak Just one custom resolution is probably OK, but IMHO `vesa_custom_resolution` should also accept explicit resolution values. In _Quake_ you just select the resolution from the list, but in _Duke...

I confirm, I can reproduce the problem on Windows 11, with Intel Arc A770 card. It’s possible this is SDL library problem - when I copy SDL2.DLL which was shipped...

If I’m not mistaken, the crash happens within the `SDL_SetRelativeMouseMode(true);` call in `GFX_SetMouseCapture` function. [edit] And this only happens if we call `SDL_SetHintWithPriority(SDL_HINT_MOUSE_RELATIVE_MODE_WARP, "1");` to disable raw mouse input.