If you can compile the source, pull the latest commit. Some fixes have been made for dynamic core (also to fix another issue tracker item regarding Quake).

Thank you for the fix. I cannot do a compile due to the missing C++ components from my VS installation so I can check it in the next release.

I want to clarify I think the latest commit fixes it. It does fix another issue reported with Quake and dynamic core though.

@koszeggy The latest release is available.

@joncampbell123: Today I checked it again and the issues are still the same with the Windows x64 version. The mingw-win64 build is somewhat different than before: with that the Dos Navigator Real version freezes in a strange way: the mouse cursor is moving but neither mouse clicks, nor the keystrokes are working.

It crashes here using the SDL2 based 0.83.18 (Win/x64) with "Normal" core.

DOS Navigator still crashes using the Open Source version from http://www.dnosp.com/e_index.php
and DosBox-X 0.83.23.

It works as it should on DOSBox 0.74-3

How can it be reproduce?
It works for me.

This bug report should have closed some time ago.

It consistently fails as seen in the first screenshot when using a "normal" cpu core with the fpu option set to "true" in the configuration.
It launches fine on the same "normal" cpu core when fpu is set to "false".

If it fails with fpu=true and works with fpu=false it may be that your using the Windows VisualStudio (VS) build? If so, try the MinGW build instead.

The VisualStudio build only has 64bit precision for the FPU emulation, which is a VisualStudio limitation. While the MinGW build has the full 80bit FPU precision.

If it fails with fpu=true and works with fpu=false it may be that your using the Windows VisualStudio (VS) build? If so, try the MinGW build instead.

The VisualStudio build only has 64bit precision for the FPU emulation, which is a VisualStudio limitation. While the MinGW build has the full 80bit FPU precision.

I'm using the VisualStudio version, as I've stated previously.
I'll try your suggestion. Thanks for the tip. :)

Ok. As per rderooy's suggestion, I can confirm this happens only on the VisualStudio build.
The MinGW build works well.

Since the VisualStudio build causes at least one program to fail, should it even be included in the dosbox-x distribution at this point?

This issue still exists in the latest version 2024.03.01 (Visual Studio/64bit).
This version doesn't seem to include a 64bit MinGW version in the installer...