WinUAE 3.6.1 beta series - Page 5

White · 15 February 2018, 11:59

Hi Toni,
it works perfectly the x64 version, thanks
I have encountered this problem.
This only happened the first time I used beta4 x64
Now it does not happen anymore.
Thanks for the beta4 and your work

Thank you.

Toni Wilen · 15 February 2018, 17:20

Quote:

Originally Posted by White

Hi Toni,
it works perfectly the x64 version, thanks
I have encountered this problem.
This only happened the first time I used beta4 x64
Now it does not happen anymore.
Thanks for the beta4 and your work

Thanks, it seems A2065 tried to read past its internal RAM space, this is now fixed. (This shouldn't happen unless A2065 driver is confused so there may be something else too..)

Toni Wilen · 15 February 2018, 17:23

Quote:

Originally Posted by Retro-Nerd

Alt+Tab is broken for me since 3.6.1 beta 1. Alt+Tab works first, but when you try to return to WinUAE it crashes the emulator. No crash dump though inside my folder (portable ticked). Are logs enough?

edit: Argh, it's a shader issue again. Without a guest CRT shader WinUAE doesn't crash.

Can anyone else duplicate this? (It may be AMD only)

Config and required file here: http://eab.abime.net/showpost.php?p=...6&postcount=63

It still can be bug in D3D11 resource freeing/allocation but unfortunately D3D11 debug mode don't detect anything.

Retroplay · 15 February 2018, 18:28

Yes, same crash here on Nvidia GTX1080, also no crash dump.

Code:

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	winuae64.exe
  Application Version:	3.6.1.0
  Application Timestamp:	5a84801b
  Fault Module Name:	D3D11.dll
  Fault Module Version:	6.2.9200.16699
  Fault Module Timestamp:	5216eaa8
  Exception Code:	c0000005
  Exception Offset:	00000000000d6f09
  OS Version:	6.1.7601.2.1.0.256.1
  Locale ID:	2057
  Additional Information 1:	4d84
  Additional Information 2:	4d846379910cb553623bc8bf47ffd65e
  Additional Information 3:	6fe5
  Additional Information 4:	6fe5765be5e9f85c28d819e19bf60227

Toni Wilen · 15 February 2018, 18:40

It probably is Windows version specific or something because I can't duplicate it (win 10 + 1080Ti)

White · 15 February 2018, 20:50

Hi Toni,
thank you,
I'm very happy seriously
now I'm also trying RTL, ethernet.device works fine,
I really appreciate your work I have no other word to use.
I hope later to be able to contribute to the time you dedicate to this project.
I start using the system as I've always wanted to do.
And I'm sorry if sometimes I ask strange questions, but I continuously experiment.
Thanks again. :-)

Zandig · 15 February 2018, 23:23

Quote:

Originally Posted by Toni Wilen

Can anyone else duplicate this? (It may be AMD only)

Config and required file here: http://eab.abime.net/showpost.php?p=...6&postcount=63

It still can be bug in D3D11 resource freeing/allocation but unfortunately D3D11 debug mode don't detect anything.

Yes crash using Direct3D 11.
Direct3D 9 works fine.
Using Nvidia GTX 1080 - Windows 10 64 bit (1709 / 16299.248)

Toni Wilen · 17 February 2018, 10:29

Quote:

Originally Posted by Zandig

Yes crash using Direct3D 11.
Direct3D 9 works fine.
Using Nvidia GTX 1080 - Windows 10 64 bit (1709 / 16299.248)

Does it happen in all resolutions?

Zandig · 17 February 2018, 14:42

Quote:

Originally Posted by Toni Wilen

Does it happen in all resolutions?

Yes - same crash. Tried many different resolutions and various refresh rates. It shows this on screen when crashing...

Toni Wilen · 18 February 2018, 13:10

winuae.7z updated. It should fix all remaining D3D11 fullscreen<>windowed mode crashes. I managed to duplicate and debug it with older laptop. (D3D11 Present() call can internally run window event loop and things can get messy if event loop handler changes D3D11 mode.. Oddly enough this never happened on my main PC)

DamienD · 18 February 2018, 13:11

Nice work Toni

...I really need to try out D3D11 some day soon.

Retro-Nerd · 18 February 2018, 13:27

Quote:

Originally Posted by Toni Wilen

winuae.7z updated. It should fix all remaining D3D11 fullscreen<>windowed mode crashes. I managed to duplicate and debug it with older laptop. (D3D11 Present() call can internally run window event loop and things can get messy if event loop handler changes D3D11 mode.. Oddly enough this never happened on my main PC)

Still get a crash with Alt+Tab and return to WinUAE. This time with a dmp file.

Toni Wilen · 18 February 2018, 13:52

Redownload and create new dump file (as always, dumps are useless unless I still have matching separate debug symbol file, normally only happens with official betas)

Retro-Nerd · 18 February 2018, 14:08

Done.

Toni Wilen · 18 February 2018, 14:27

Another update. Still crashing?

Retro-Nerd · 18 February 2018, 14:31

No, seems you've fixed it.

Steve · 18 February 2018, 14:43

I still get the Alt-Tab 'force closing' issue using the latest beta. I enter fullscreen mode using DX11 hardware and the program exits on Alt-tab.

The 32 bit version just gives me the DOS window output like before.

Toni Wilen · 18 February 2018, 14:49

64-bit is never updated except when official beta gets released.

Zandig · 18 February 2018, 16:06

Toni,

A bit strange behavior with your latest beta winuae.7z (2018-02-18) and the ALT-TAB issue:

It has indeed fixed the ALT-TAB crash with Direct3D 11. However I have to ALT-TAB back to winuae twice to get the picture onscreen.

The first time I ALT-TAB back to winuae it displays a black screen. If then I ALT-TAB back to windows and then back to winuae again the picture appears.

As before, Directed3D 9 is working properly with ALT-TAB

Toni Wilen · 18 February 2018, 16:14

Quote:

Originally Posted by Zandig

Toni,

A bit strange behavior with your latest beta winuae.7z (2018-02-18) and the ALT-TAB issue:

It has indeed fixed the ALT-TAB crash with Direct3D 11. However I have to ALT-TAB back to winuae twice to get the picture onscreen.

The first time I ALT-TAB back to winuae it displays a black screen. If then I ALT-TAB back to windows and then back to winuae again the picture appears.

As before, Directed3D 9 is working properly with ALT-TAB

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

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WinUAE 2.8.0 beta series (Was 2.7.1)	Toni Wilen	support.WinUAE	214	01 May 2014 11:28
WinUAE 2.4.0 beta series	Toni Wilen	support.WinUAE	342	29 March 2012 09:02
WinUAE 2.3.0 beta series (was 2.2.1)	Toni Wilen	support.WinUAE	229	22 September 2010 19:20
WinUAE 2.0.1 beta series	Toni Wilen	support.WinUAE	14	22 December 2009 18:46
WinUAE 1.5.1 beta series	Toni Wilen	support.WinUAE	242	12 August 2008 12:42

15 February 2018, 18:40	#85
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	It probably is Windows version specific or something because I can't duplicate it (win 10 + 1080Ti)

15 February 2018, 20:50	#86
White Registered User Join Date: Sep 2016 Location: italy Posts: 1,480	Hi Toni, thank you, I'm very happy seriously now I'm also trying RTL, ethernet.device works fine, I really appreciate your work I have no other word to use. I hope later to be able to contribute to the time you dedicate to this project. I start using the system as I've always wanted to do. And I'm sorry if sometimes I ask strange questions, but I continuously experiment. Thanks again. :-)

18 February 2018, 13:10	#90
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	winuae.7z updated. It should fix all remaining D3D11 fullscreen<>windowed mode crashes. I managed to duplicate and debug it with older laptop. (D3D11 Present() call can internally run window event loop and things can get messy if event loop handler changes D3D11 mode.. Oddly enough this never happened on my main PC)

18 February 2018, 13:11	#91
DamienD Banned Join Date: Aug 2005 Location: London / Sydney Age: 47 Posts: 20,420	Nice work Toni ...I really need to try out D3D11 some day soon.

18 February 2018, 13:52	#93
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	Redownload and create new dump file (as always, dumps are useless unless I still have matching separate debug symbol file, normally only happens with official betas)

18 February 2018, 14:27	#95
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	Another update. Still crashing?

18 February 2018, 14:31	#96
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,438	No, seems you've fixed it.

18 February 2018, 14:49	#98
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	64-bit is never updated except when official beta gets released.

18 February 2018, 16:06	#99
Zandig Registered User Join Date: May 2009 Location: NY / USA Posts: 266	Toni, A bit strange behavior with your latest beta winuae.7z (2018-02-18) and the ALT-TAB issue: It has indeed fixed the ALT-TAB crash with Direct3D 11. However I have to ALT-TAB back to winuae twice to get the picture onscreen. The first time I ALT-TAB back to winuae it displays a black screen. If then I ALT-TAB back to windows and then back to winuae again the picture appears. As before, Directed3D 9 is working properly with ALT-TAB

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)