WinUAE 3.6.0 beta series

[Toni Wilen]

Originally Posted by Amiga68k

Hope that helps... and perhaps the FPS counter remaining stable is the desired value compared to the value fluctuating? The quicker boot time was a nice side-effect though...

FPS going above normal usually means emulator expects vsync but display isn't doing that. It speeds up booting because any delay that uses timers runs much faster. (Most drivers have waits to guarantee hardware being ready. Which only wastes time in emulation..)

Originally Posted by DualC

I saw eirlier in the messages 16 bit mode should work?, i have tried in latest beta 12 and my screen is black then i try to start it up in 16 bit mode.

But it works in 32 bit.

Attach winuaelog.txt. I only tested it by forcing 16-bit internal texture and it did work. Screen mode is always 32-bit in D3D11.

[DualC]

Toni, here is the logfile u wanted.

[Toni Wilen]

Apparently 16-bit formats were completely removed from DX11 and partially restored in DX 11.1.

DXGI_FORMAT_B5G6R5_UNORM
DXGI_FORMAT_B5G5R5A1_UNORM
Requires DXGI 1.2 or later. DXGI 1.2 types are only supported on systems with Direct3D 11.1 or later.

https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx may help. (Or not.. "These provide partial functionality: Direct3D 11.1 DXGI 1.2")

[DualC]

Originally Posted by Toni Wilen

Apparently 16-bit formats were completely removed from DX11 and partially restored in DX 11.1.



https://msdn.microsoft.com/en-us/lib...(v=vs.85).aspx may help. (Or not.. "These provide partial functionality: Direct3D 11.1 DXGI 1.2")

Hmm, nah .. i already have this update on my computer.

[Toni Wilen]

Ok, so 16-bit textures/full DXGI 1.2 is Windows 8+ only. I guess I need to add fall back to DX9 if 16-bit is needed. (Fortunately it isn't really been needed for long time, except when hardware does not have 32-bit support or has slow 32-bit support)

[DualC]

Hmm. I got new problem now. Upgraded to Windows 10, and now it rolls back to d3d9 again in latest beta 12.

[Toni Wilen]

Originally Posted by DualC

Hmm. I got new problem now. Upgraded to Windows 10, and now it rolls back to d3d9 again in latest beta 12.

Attach log again, please. Don't attempt to fix it by installing some windows/driver updates, I want to know what goes wrong.

[DualC]

Here u got the logfile Toni.

[Toni Wilen]

DXGI_ERROR_NOT_CURRENTLY_AVAILABLE 0x887A0022

The resource or request is not currently available, but it might become available later.

MSDN says "If GetDisplayModeList is called from a Remote Desktop Services session (formerly Terminal Services session), DXGI_ERROR_NOT_CURRENTLY_AVAILABLE is returned."

Did you use some kind of remote connection?

It looks like I should enumerate screen modes only if fullscreen mode is requested to prevent this side-effect.

[DualC]

Originally Posted by Toni Wilen

MSDN says "If GetDisplayModeList is called from a Remote Desktop Services session (formerly Terminal Services session), DXGI_ERROR_NOT_CURRENTLY_AVAILABLE is returned."

Did you use some kind of remote connection?

It looks like I should enumerate screen modes only if fullscreen mode is requested to prevent this side-effect.

Hi.

Nah, no remote connection here, i only start up a command promt and use like "winuae.exe -log"

[Toni Wilen]

Include also winuaebootlog.txt, thanks. (It includes display mode enumeration list that does not use D3D)

[DualC]

Originally Posted by Toni Wilen

Include also winuaebootlog.txt, thanks. (It includes display mode enumeration list that does not use D3D)

Well i belive i cant help u with that cose i went back to Win7 again, Win10 messed up my comp and some program i use often didnt work.

Hope it's ok anyway and maybee some other got the same problem in the future.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3600b13.7z
http://www.winuae.net/files/b/winuae64_3600b13.7z

Beta 13:

- Memory cycle exact CPU speed slider scale fixed. (0 is max)
- D3D11: monitor bezel overlays supported.
- D3D11: RGB mask wrong colors fixed. (RGB<>BGR)
- D3D11: fall back to D3D9 if 16-bit mode is selected but it is not supported. 16-bit is not required format in D3D11.
- D3D11: minimum supported hardware level is now 9.1 (was 10.0).
- Added Evesham Micros Reference SCSI controller emulation.
- Kupke Golem HD3000 autoboot disabled option did nothing.
- It was not possible to override Z2 RAM board autoconfig data if board had built-in manufacturer/product ID defaults (for example any Z2 HD controller with Z2 RAM)

Evesham Micros Reference:
- Basic 5380 based PIO controller.
- Fake DMA, byte wide data port.
- Driver has filesystem relocator but it seems to be broken, for example PFS3 crashes because all relocations point to invalid addresses.
- "Evesham.device (Kemputa1/Evesham drive 13Mar93)", "(c)1993 Kemputa Systems,Pen-y-Gwaith,Ysbyty Ystwyth,Ystrad Meurig,Dyfed. UK"
- It has strange fast RAM configuration, RAM can be disabled with a jumper but it only clears autoconfig "add to free list" bit. If you want to replicate this (board's custom memory test utility only runs in this mode), tick RAM panel edit autoconfig data and clear bit 5 of first byte (for example E4 -> C4)

WARNING: Partial but non-working D3D11 mode custom shader support is included. It will either cause errors during .fx parsing or shows blank screens. Don't try to use any .fx files yet.

[vagrant]

Hey Toni, I think something have broken with display handling, last working beta is b10.
All my configs are set to low latency 50/60 & no buffering.
When I load the configs into the latest betas, it reverts settings to legacy vsync & double buffering. If I change the settings back and launch emulation - these changes are ignored and launches legacy/double buffer mode anyway..
I can only change buffer and vsync mode successfully after emulation has started, and saving a new config still reverts any settings to legacy/double buffer.
Attached log of trying to launch with low latency & no buffer.

[Amiga68k]

Since Beta 11 there are sound output issues with my particular setup (A4000 + Toccata) in D3D 11 mode.

When using EaglePlayer or DeliPlayer I always disable JIT:

uae-configuration cpu_speed real cachesize 0 cpu_throttle 2000.0

In D3D 11 mode there is a lot of noise/stuttering/slowdown going on since Beta 11. Using Beta 13 in D3D 9 mode slightly improves things, but not entirely. The sound plays correctly, but as soon as I move the mouse around it starts outputting noise. Post 194 contains logs from Beta 10 and 11, let me know if anything else is needed.

[Toni Wilen]

Originally Posted by Amiga68k

Since Beta 11 there are sound output issues with my particular setup (A4000 + Toccata) in D3D 11 mode.

When using EaglePlayer or DeliPlayer I always disable JIT:

uae-configuration cpu_speed real cachesize 0 cpu_throttle 2000.0

In D3D 11 mode there is a lot of noise/stuttering/slowdown going on since Beta 11. Using Beta 13 in D3D 9 mode slightly improves things, but not entirely. The sound plays correctly, but as soon as I move the mouse around it starts outputting noise. Post 194 contains logs from Beta 10 and 11, let me know if anything else is needed.

Does it also happen in native mode? (Not RTG). You sure it isn't some power saving feature? (It has happened many times that suddenly in some update power saving starts working differently, without any explanation..)

Originally Posted by ED-209

Hey Toni, I think something have broken with display handling, last working beta is b10.
All my configs are set to low latency 50/60 & no buffering.
When I load the configs into the latest betas, it reverts settings to legacy vsync & double buffering. If I change the settings back and launch emulation - these changes are ignored and launches legacy/double buffer mode anyway..
I can only change buffer and vsync mode successfully after emulation has started, and saving a new config still reverts any settings to legacy/double buffer.
Attached log of trying to launch with low latency & no buffer.

Attach config. Log does not show any reasons why opened display mode is normal vsync, there is not even any calibration messages until you manually changed it back.

[Amiga68k]

Originally Posted by Toni Wilen

Does it also happen in native mode? (Not RTG). You sure it isn't some power saving feature? (It has happened many times that suddenly in some update power saving starts working differently, without any explanation..)

There is no issue with Beta 13 when choosing a PAL High Res mode.

All power saving settings (on the host, mainly Intel Graphics Power Plan) are configured as "Maximum performance".

[vagrant]

Attached 2 configs

[vagrant]

Also, if load b11 / b12 / b13, select a quickstart config, change to low latency with no buffering, it still reverts to legacy / double buffer after launch.

[Toni Wilen]

Originally Posted by ED-209

Also, if load b11 / b12 / b13, select a quickstart config, change to low latency with no buffering, it still reverts to legacy / double buffer after launch.

I can't duplicate, your config also works fine, no buffer stays and log shows correct screen info. Any buffer size change would also add log message. Normal vsync forces at least 1 buffer and it won't add any messages so something causing normal vsync mode would partially explain it but normal vsync force would also add log message.

If you manually load the config, does GUI show correct vsync and buffer info?

D3D9Ex: PS=3.0 VS=3.0 720*576*50p FS VS=-1 B=0I 32-bit 0 (16384x16384)

(Your log shows VS=1: normal vsync and B=1I: 1 buffer)