WinUAE 3.6.1 beta series

[Zandig]

Originally Posted by Toni Wilen

Include log, please. Is it 100% repeatable or does it sometimes work?

Yes it is 100% repeatable.

Log attached..

[Toni Wilen]

Does it only happen with this config?

Remove all unneeded: all harddrives, shader files, masks.. Does it still happen? (the usual: remove all unknown variables)

EDIT: Does F12 and then exit GUI work or does it also cause blank screens?

EDIT even more: Did it always crash previously? I mean, did you ever manage to test this situation with previous official betas? Just wondering if this is actually unrelated problem.. Does same happen if you select some normal refresh rate (instead of "default")?

[Zandig]

Originally Posted by Toni Wilen

Does it only happen with this config?

Remove all unneeded: all harddrives, shader files, masks.. Does it still happen? (the usual: remove all unknown variables)

EDIT: Does F12 and then exit GUI work or does it also cause blank screens?

EDIT even more: Did it always crash previously? I mean, did you ever manage to test this situation with previous official betas? Just wondering if this is actually unrelated problem.. Does same happen if you select some normal refresh rate (instead of "default&quot?

It happens with various configs I tried.

Removing hard drives, shader files and masks - the problem still happens.

Various refresh rates and problem is still there.

F12 and exit GUI works properly, as does the middle mouse button.
Just ALT-TAB with the problem.

Sorry I have only tried your last few Betas on this problem, aside from the 3.6.0 release.

[Toni Wilen]

I suddenly managed to duplicate it but it didn't happen every time. For some reason Windows sent "window went inactive" message but still restored the hidden fullscreen window. WinUAE kept waiting for activation message..

I did some Window message handling adjustments and now I can't duplicate it anymore. (which probably won't mean anything..)

Anyway, winuae.7z updated.

[Zandig]

Originally Posted by Toni Wilen

I suddenly managed to duplicate it but it didn't happen every time. For some reason Windows sent "window went inactive" message but still restored the hidden fullscreen window. WinUAE kept waiting for activation message..

I did some Window message handling adjustments and now I can't duplicate it anymore. (which probably won't mean anything..)

Anyway, winuae.7z updated.

Yes the ALT-TAB issue is now fixed using Direct3D 11

However now if using Direct3D 11 and you right click on the WinUAE icon on the Windows taskbar and select "Close Window" it takes you back into the Amiga screen instead of closing the program.

Using Direct3D 9 works as intended by closing WinUAE.

[DamienD]

Originally Posted by Toni Wilen

I suddenly managed to duplicate it but it didn't happen every time. For some reason Windows sent "window went inactive" message but still restored the hidden fullscreen window. WinUAE kept waiting for activation message..

I did some Window message handling adjustments and now I can't duplicate it anymore. (which probably won't mean anything..)

Anyway, winuae.7z updated.

Don't you hate those super intermittent bugs that happen 1% of the time and are dependant on countless variables such as OS / drivers / settings / blah...

You're doing a sterling job master Wilen

You can solve / fix anything Amiga --> Windows related.

[rbm]

This is not a beta 3.6.1 related problem but a 3.6.0.

The latest working beta for the attached config is the 3.6.0 beta 16. The beta 17 crashes with a Microsoft Visual C++ Runtime Library Error.

Also attached the beta 3.6.0 beta 16 and beta 17 logs.

[Toni Wilen]

Originally Posted by rbm

This is not a beta 3.6.1 related problem but a 3.6.0.

The latest working beta for the attached config is the 3.6.0 beta 16. The beta 17 crashes with a Microsoft Visual C++ Runtime Library Error.

Also attached the beta 3.6.0 beta 16 and beta 17 logs.

Disable JIT direct. It had stupid change that allowed JIT direct which didn't really make sense..

[Toni Wilen]

Originally Posted by Zandig

However now if using Direct3D 11 and you right click on the WinUAE icon on the Windows taskbar and select "Close Window" it takes you back into the Amiga screen instead of closing the program.

Works for me, quits normally. Attach new logs.

[Toni Wilen]

http://www.winuae.net/files/b/winuae_3610b5.7z
http://www.winuae.net/files/b/winuae64_3610b5.7z

Beta 5: (1-2 weeks to go if D3D11 issues are really fixed..)

- Creating new file with "DOS" name (for example AUX) to directory filesystem drive returned error (got broken in 3.6.0, it added special handling for reading existing special named files in case if filesystem accepts them without mangling but creating new files was missed..)
- Autoscale ignored small vertical display areas in very top of display in some situations.
- A600/A1200/A4000 IDE missed doubler supported flag. (3.5.0+ only shows ports 2 and 3 if device is confirmed supporting IDE doubler)
- Virtual RDB is now supported with dynamic (VHD) hardfiles. (Virtual RDB: if partition hardfile is mounted to any hardware emulated IDE or SCSI controller, virtual RDB is automatically added. This enables to boot/mount partition hardfiles even when using hardware emulated HD controllers)
- Virtual RDB now also includes FSHD and LSEG blocks if hardfile FileSys path is non-empty. (Makes filesystem compatibility testing much faster and easier when using non-UAE controllers)
- If D3D11 mode shader/mask loading failed (for example missing mask image file), not all allocated data was freed.
- Remaining D3D11 alt-tab/F12 fullscreen<>windowed mode crashes should be fixed.
- D3D11 fullscreen mode restore after alt-tab sometimes only showed blank screen.
- Reverted 3.6.0b17 allow JIT direct in CSPPC mode. PPC can't boot without JIT-direct incompatible memory mapping. If you want JIT Direct with CSPPC and don't need PPC: Use CSMK3.

[DamienD]

Nice, off to test

[Zandig]

Originally Posted by Toni Wilen

Works for me, quits normally. Attach new logs.

Logs attached.

Also a pic of my bottom taskbar so you can see the icon I'm referring to..

[bagpipes]

Thank you, Toni! Now Arabian Nights with automatic scaling works like a charm.

[DamienD]

Originally Posted by bagpipes

Thank you, Toni! Now Arabian Nights with automatic scaling works like a charm.

...just tested Shadow Warriors using ransom1122's settings i.e. automatic scaling but unfortunately the top part is still cut off

I've attached his configuration file for you Toni.

[Toni Wilen]

Originally Posted by DamienD

...just tested Shadow Warriors using ransom1122's settings i.e. automatic scaling but unfortunately the top part is still cut off

I've attached his configuration file for you Toni.

Screenshot required!

[DamienD]

What the configuration file isn't enough?

Ok then:



Again, please note this is not my issue as I don't ever use "automatic scaling"...

[Steve]

Originally Posted by Zandig

Yes the ALT-TAB issue is now fixed using Direct3D 11

However now if using Direct3D 11 and you right click on the WinUAE icon on the Windows taskbar and select "Close Window" it takes you back into the Amiga screen instead of closing the program.

Using Direct3D 9 works as intended by closing WinUAE.

I can confirm the Alt-Tab issue is now fixed! Excellent work Toni, thank you.

I am also unable to duplicate the 'close window' issue from the taskbar. I tested this and it worked as expected.

[bagpipes]

Originally Posted by DamienD

...just tested Shadow Warriors using ransom1122's settings i.e. automatic scaling but unfortunately the top part is still cut off

I've attached his configuration file for you Toni.

Your config is wrong - with automatic scaling on the game runs perfectly.

[DamienD]

Originally Posted by bagpipes

Your config is wrong - with automatic scaling on the game runs perfectly.

AGAIN!!! IT'S NOT MY CONFIGURATION FILE, it's ransom1122's

I'm just helping him out with an issue he's mentioned to me numerous times (as he's probably still asleep in Australia).

[bagpipes]

Originally Posted by DamienD

AGAIN!!! IT'S NOT MY CONFIGURATION FILE, it's ransom1122's

I'm just helping him out with an issue he's mentioned to me numerous times (as he's probably still asleep in Australia).

Roger that!