WinUAE 4.0.0 beam racing with Wine/CrossoverMac

[bloodline]

I know running WinUAE on Wine is always going to have issues, but when I attempted to use the beam racing mode, the emulator is able to draw a single frame then crashes.

-edit- This happens using any number of slices.

[Toni Wilen]

Probably too difficult to debug but at least check if wine complains anything in its own log and also check winuae's log too.

[bloodline]

Originally Posted by Toni Wilen

Probably too difficult to debug but at least check if wine complains anything in its own log and also check winuae's log too.

Will do, cheers

[bloodline]

The Wine Log is 200meg... and doesn't really mean much to me (It's a lot of system calls and I have no Windows coding experience).

I've attached the WinUAE dump file and log file...

-Edit- Should I be looking for anything in particular in the Wine error log? Is the beam racing doing anything different from normal?

[DamienD]

Originally Posted by bloodline

The Wine Log is 200meg... and doesn't really mean much to me (It's a lot of system calls and I have no Windows coding experience).

Then compress / zip the Wine log and upload to a file hosting site for Toni to look at

[Toni Wilen]

Crash is division by zero so probably some display parameter query API returns invalid zero value for screen height or refresh rate or something. Dump is isn't really telling anything else, I guess it isn't fully compatible.

winuaelog.txt is also missing. Use -logflush command line parameter (not sure if it helps under wine)

[bloodline]

Originally Posted by DamienD

Then compress / zip the Wine log and upload to a file hosting site for Toni to look at

I think Toni has better thinge to do than look through 200meg of my Winlog
I will upload it though if anyone does want to have a look through, I'll also try and get WinUAE to produce a proper log file for Toni, which may be more helpful.

I would guess that he is correct about Wine returning some screen parameter as 0... I will submit this as a bug to the Wine team too (I wanted to get Toni's take on it first).

[DamienD]

Originally Posted by bloodline

I think Toni has better hing to do than look through 200meg of my Winlog

Well, I think Toni has better things to do than try to fix issues for people running WinUAE on MACs; using any means possible

Originally Posted by bloodline

I will submit this as a bug to the Wine team too (I wanted to get Toni's take on it first).

That should have been your first starting point really

[bloodline]

Originally Posted by DamienD

Well, I think Toni has better things to do than try to fix issues for people running WinUAE on MACs; using any means possible

True

Well WinUAE runs pretty much faultlessly on Wine... it's just the new new beamracing mode which causes issue.

That should have been your first starting point really

Beamracing is such a new feature, I thought it might be best to give Toni a heads up first.

Attached the winuaelog.

And the wine log (for the brave)
https://drive.google.com/open?id=1bs...Y8D67QAf90cbib

[Toni Wilen]

Selected display mode does not have adapter data!

This is the problem. I think I can prevent the crash and generate close enough values.

[bloodline]

Originally Posted by Toni Wilen

This is the problem. I think I can prevent the crash and generate close enough values.

Cheers Toni!

[Toni Wilen]

http://www.winuae.net/files/b/winuae.7z should fix the crash.

[alpine9000]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.7z should fix the crash.

I tried current wine devel today and I get crashes (including with the above version) if I used D3D11. Works great with D3D9. Surprised how great it works actually. Only thing I couldn't really use was video recording.

Added the dump and logs if you're interested. I am fine with using D3D9 however.

D3D11 free start
D3D11 freed3d start
D3D11 freed3d end
D3D11 free end
Max hardware surface size: 16384x16384
Mon 0 allocated draw temp buffer (1600*1280*32) = 07DD2020
D3D11 init start. (720*568) (720*568) RTG=0 Depth=32.
CheckFeatureSupport(DXGI_FEATURE_PRESENT_ALLOW_TEARING) = 80004001 0
IDXGIOutput QueryInterface 80004002
ExceptionFilter Trap: 00000000 C0000000 00000000
Access violation! (68KPC=00000000 HOSTADDR=00000000)

[bloodline]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.7z should fix the crash.

Thanks, will test when I get home tonight.

[Toni Wilen]

Originally Posted by alpine9000

IDXGIOutput QueryInterface 80004002

Winuae does not seem to implement IDXGIOutput1 (which is part of DXGI 1.2 that WinUAE requires).

Crash fixed (=fallback to D3D9)

[bloodline]

Originally Posted by Toni Wilen

http://www.winuae.net/files/b/winuae.7z should fix the crash.

Yes, this beta does work with Wine/CrossoverMac! Excellent, this works without fault.

[alpine9000]

Confirming beta 2 fixes this for me also.

[bloodline]

Beam racing is an interesting feature!

Testing with Lemmings using compatible A500 (1.2 Kick) settings; the game executes very slightly faster than a normal PAL A500, and at times I can get the mouse pointer to tear if I move it around the screen fast enough (the frame rate can get a bit jerky randomly, I assume if the CPU gets bogged down)... but the input latency is completely eliminated (or at least imperceptible to me).

I'm amazed it works so well! It makes DPaint a joy to use