Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DUKE3D.EXE freezes on DOSBox-X 2022.09.0 and 2022.12.26 in the main menu #3912

Open
2 tasks done
maltic42 opened this issue Dec 30, 2022 · 6 comments
Open
2 tasks done

Comments

@maltic42
Copy link

maltic42 commented Dec 30, 2022

Describe the bug

I am trying to get Duke Nukem 3D Atomic Edition from GOG running on DOSBox-X on an M1 MacBook Pro running on Mac OS Ventura 13.1. I tried several settings and tweaks, but it always freezes after entering the main menu.

Steps to reproduce the behaviour

Download Duke Nukem 3D Atomic Edition for Mac from gog.com. Open the file by choosing "Show package contents" in the Finder, navigate to Contents and Resources, open the contents of Duke Nukem 3D.boxer and copy everything from the folder C.harddisk to a folder of your choice. Start the Dosbox, mount the previously created folder with Duke Nukem as drive C and start DUKE3D.EXE. The game will freeze in the main menu.

Expected behavior

The game should not freeze.

What operating system(s) this bug have occurred on?

MacOS Ventura 13.1

What version(s) of DOSBox-X have this bug?

2022.09.0 and 2022.12.26

Used configuration

Default

Output log

Early LOG Init complete
DOSBox-X's working directory: /Applications/dosbox-x.app/Contents/MacOS
Logging init: beginning logging proper. This is the end of the early init logging
Logging: No logfile was given. All further logging will be discarded.
DOSBox-X version 2022.09.0 (macOS SDL1)
macOS EXE path: /Applications/dosbox-x.app/Contents/MacOS/dosbox-x
macOS Resource path: /Applications/dosbox-x.app/Contents/Resources
macOS: NSTouchBar support detected in system
Host keyboard layout is now us (US English)
Mapper keyboard layout is now us (US English)
SDL1 auto-detected desktop as 1680 x 1050
The default output for the video system: opengl
Configured windowposition: -
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
ISA BCLK: 8333333.333Hz (25000000/3)
monopal: green, 
Active save slot: 1 [Empty]
USING AVI+ZMBV
Max 3670016 sz 16384
Final 16384
MIDI:Opened device:coreaudio
Pentium CMPXCHG8B emulation is enabled
VOODOO LFB now at d0000000
Serial1: BASE 3f8h
Serial2: BASE 2f8h
Parallel1: BASE 378h
MPU-401 Registering I/O ports as if IBM PC MPU-401 at base 330h
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Allocated APM BIOS pm entry point at f000:ce40
Writing code to fce40
Writing code to fce60
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
ISA Plug & Play BIOS enabled
VGA ROM BIOS init callback
pixratio 1.000, dw false, dh false
Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
WARNING: No translation support (to host) for code page 0
   2649400 ERROR BIOS:Keyboard layout file auto not found
   2649400 ERROR BIOS:Keyboard layout file auto not found
XMS: 50 handles allocated for use by the DOS environment
EMS page frame at 0xe000-0xefff
COMMAND.COM env size:             720 bytes
COMMAND.COM environment block:    0x0701 sz=0x002d
COMMAND.COM main body (PSP):      0x072f sz=0x009a
COMMAND.COM stack:                0x0749
pixratio 1.350, dw false, dh false
Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Aspect ratio: 720 x 540  xToY=1.333 yToX=0.750
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Loaded language file: de_DE.lng
2604873043 ERROR BIOS:INT15:Unknown call ax=BFDE
2604873121 ERROR BIOS:INT15:Unknown call ax=BFDE
DOSBox-X has switched to max cycles, because of the setting: cycles=auto.
If the game runs too fast, try a fixed cycles amount in DOSBox-X's options.
2604883920 ERROR BIOS:INT15:Unknown call ax=BF01
pixratio 1.200, dw true, dh false
Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Loaded language file: de_DE.lng
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Aspect ratio: 640 x 480  xToY=1.333 yToX=0.750
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)
Screen report: Method 'CoreGraphics' (1680.000 x 1050.000 pixels) at (0.000 x 0.000) (286.389 x 178.993 mm) (11.275 x 7.047 in) (149.000 x 149.000 DPI)

Additional information

No response

Have you checked that no similar bug report(s) exist?

  • I have searched and didn't find any similar bug report.

Code of Conduct & Contributing Guidelines

  • I agree to follow the code of conduct and the contributing guidelines.
@maltic42 maltic42 added the bug label Dec 30, 2022
@maltic42 maltic42 changed the title DUKE3D.EXE freezes on DOSBox-X 2022.09.0 in the main menu DUKE3D.EXE freezes on DOSBox-X 2022.09.0 and 2022.12.26 in the main menu Dec 31, 2022
@Jeidoban
Copy link

Jeidoban commented Dec 31, 2022

I had this issue with duke3d as well as issues with BLOOD crashing on m2 macbook air. This only happens with the native ARM builds of dosbox-x, when running x86 dosbox through rosetta it works great

@digistorm79
Copy link

I have seen this behavior with a number of programs that use floating point math. This one could also be related with #3890

@superblobster
Copy link

Works fine in the Windows build.

@digistorm79
Copy link

Do you have an ARM or x86 windows system? This bug is known to happen on macs with M1 (so ARM64) builds. X86 is working fine on macs, so the bug is in the difference in code between ARM64 and x86

@joncampbell123
Copy link
Owner

This may have been resolved by the recent fixes to dynamic core regarding floating point (FPU) emulation.

If you are able to compile the latest commit to master and try it, go ahead. The fix should be in the latest upcoming release.

@maltic42
Copy link
Author

I´ll try this out once the build is ready - thanks!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants