WinUAE 4.0.0 beta series - Page 22

vagrant · 10 June 2018, 05:22

Small issue introduced in beta 11;
Using D3D11 fullscreen mode, switching from winuae GUI (in desktop) back to emulation brings the windows mouse cursor to front, and needs a mouse click to resume.
Also if lagless vsync is used, switching back from GUI also create a black line at bottom of screen (see pic).

jotd · 10 June 2018, 10:15

latest beta: debugger command "breakpoint when PC is within a range"

Code:

f start_address end_address

doesn't work anymore.

mark_k · 10 June 2018, 15:48

Quote:

Originally Posted by ED-209

Also if lagless vsync is used, switching back from GUI also create a black line at bottom of screen (see pic).

Could that be the same issue I mentioned here? Is there any difference if you change vertical scaling, e.g. from 3× to 3.5×?

vagrant · 10 June 2018, 16:34

Quote:

Originally Posted by mark_k

Could that be the same issue I mentioned here? Is there any difference if you change vertical scaling, e.g. from 3× to 3.5×?

I think separate issue, I'm not using any scaling (720x576)

mark_k · 10 June 2018, 17:11

The issue I see isn't specific to scaling, though it seems to be worse if you open GUI, change scaling and continue emulation. It does happen on just opening GUI and returning to emulation. What exactly appears in the bottom lines might vary depending on graphics card driver, Windows version etc. I see "trash" rather than all black.

Toni Wilen · 10 June 2018, 17:19

Last line is not rendered by design in lagless mode (because it is very special case).
EDIT: I still can't duplicate any graphics garbage.

mark_k · 10 June 2018, 18:00

Run WinUAE, load config (with D3D9 or D3D11, full-screen lagless vsync), click Start: no problem.
Press F12 then click Cancel to continue emulation: that's when the problem happens.

Toni Wilen · 10 June 2018, 18:18

Nope. I have done that dozens of times already.

Toni Wilen · 10 June 2018, 19:14

Quote:

Originally Posted by jotd

latest beta: debugger command "breakpoint when PC is within a range"

Code:

f start_address end_address

doesn't work anymore.

Quote:

Originally Posted by ED-209

Small issue introduced in beta 11;
Using D3D11 fullscreen mode, switching from winuae GUI (in desktop) back to emulation brings the windows mouse cursor to front, and needs a mouse click to resume.

winuae.7z should fix both.

vagrant · 11 June 2018, 03:25

winuae.7z fixed mouse cursor issue, though black line at bottom remains.
I tried disabling the OSD to see if it was related, and it's as if the bottom 3 lines are 'stuck' on screen (see pic, does not happen prior to b11).

Toni Wilen · 11 June 2018, 08:45

Quote:

Originally Posted by ED-209

winuae.7z fixed mouse cursor issue, though black line at bottom remains.
I tried disabling the OSD to see if it was related, and it's as if the bottom 3 lines are 'stuck' on screen (see pic, does not happen prior to b11).

Make sure it happens in some "standard" resolution (1920x1080 or similar), in early startup screen (so that there is no unknown variables. If it does not happen in early startup -> point to exact disk image that is needed to duplicate it). Then attach config.

Does the last line glitch change if you alt-tab or enter and exit GUI?

vagrant · 11 June 2018, 09:35

I'm using CRT monitor, its default resolution is 1280x1024, the problem still happens no matter what resolution is used. Yes it happens on the early startup screen, it happens in any native amiga output situation.
ALT-TAB produces exactly the same problem.

Toni Wilen · 11 June 2018, 17:17

OSD garbage in last lines should be fixed now but last 2 dark/bright lines are not.

vagrant · 11 June 2018, 17:40

Yep confirmed, OSD garbage gone & 2 lines remain.

Toni Wilen · 11 June 2018, 17:48

Last line may be fixed (as in hidden again if lagless mode) now.
Did it only happen when using F12 to enter GUI? Not even using ALT-TAB?

vagrant · 12 June 2018, 01:19

It was happening under both situations, but looks to be fixed now

Kalamatee · 12 June 2018, 05:11

Hi Toni, I have one gripe with the current WinUAE - if I run it with the -log option it opens a window and displays the output there, but when I jump into the debugger the log window gets closed so I have to then go find the actual log file. Would it be possible to have it leave the log window open?

Toni Wilen · 12 June 2018, 09:14

Quote:

Originally Posted by Kalamatee

Hi Toni, I have one gripe with the current WinUAE - if I run it with the -log option it opens a window and displays the output there, but when I jump into the debugger the log window gets closed so I have to then go find the actual log file. Would it be possible to have it leave the log window open?

This thread is only for beta specific issues.. But switch to console debugger (xx command) and you get both (GUI version is unsupported).

mark_k · 12 June 2018, 13:15

Quote:

Originally Posted by Toni Wilen

Last line may be fixed (as in hidden again if lagless mode) now.

I don't see "trash" in the bottom lines any more, but it looks like the bottom two lines are blanked in lagless vsync mode, not just the bottom one. (Press End+F9 so border is non-black to see.)

Toni Wilen · 12 June 2018, 13:34

Quote:

Originally Posted by mark_k

I don't see "trash" in the bottom lines any more, but it looks like the bottom two lines are blanked in lagless vsync mode, not just the bottom one. (Press End+F9 so border is non-black to see.)

I meant single Amiga side line because number of visible lines depends on config.

10 June 2018, 05:22	#421
vagrant Registered User Join Date: Mar 2012 Location: Australia Age: 44 Posts: 1,126	Small issue introduced in beta 11; Using D3D11 fullscreen mode, switching from winuae GUI (in desktop) back to emulation brings the windows mouse cursor to front, and needs a mouse click to resume. Also if lagless vsync is used, switching back from GUI also create a black line at bottom of screen (see pic). Attached Thumbnails

10 June 2018, 10:15	#422
jotd This cat is no more Join Date: Dec 2004 Location: FRANCE Age: 52 Posts: 8,162	latest beta: debugger command "breakpoint when PC is within a range" Code: f start_address end_address doesn't work anymore.

11 June 2018, 03:25	#430
vagrant Registered User Join Date: Mar 2012 Location: Australia Age: 44 Posts: 1,126	winuae.7z fixed mouse cursor issue, though black line at bottom remains. I tried disabling the OSD to see if it was related, and it's as if the bottom 3 lines are 'stuck' on screen (see pic, does not happen prior to b11). Attached Thumbnails

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WinUAE 3.2.2 beta series	Toni Wilen	support.WinUAE	21	20 December 2015 17:35
WinUAE 3.1.0 beta series	Toni Wilen	support.WinUAE	305	06 June 2015 23:25
WinUAE 2.3.3 beta series	Toni Wilen	support.WinUAE	124	17 September 2011 15:48
WinUAE 2.0.0 beta series	Toni Wilen	support.WinUAE	445	13 December 2009 14:46
WinUAE 1.6.1 beta series	Toni Wilen	support.WinUAE	54	18 June 2009 11:05

10 June 2018, 17:11	#425
mark_k Registered User Join Date: Aug 2004 Location: Posts: 3,334	The issue I see isn't specific to scaling, though it seems to be worse if you open GUI, change scaling and continue emulation. It does happen on just opening GUI and returning to emulation. What exactly appears in the bottom lines might vary depending on graphics card driver, Windows version etc. I see "trash" rather than all black.

10 June 2018, 17:19	#426
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	Last line is not rendered by design in lagless mode (because it is very special case). EDIT: I still can't duplicate any graphics garbage.

10 June 2018, 18:00	#427
mark_k Registered User Join Date: Aug 2004 Location: Posts: 3,334	Run WinUAE, load config (with D3D9 or D3D11, full-screen lagless vsync), click Start: no problem. Press F12 then click Cancel to continue emulation: that's when the problem happens.

10 June 2018, 18:18	#428
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	Nope. I have done that dozens of times already.

11 June 2018, 17:17	#433
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	OSD garbage in last lines should be fixed now but last 2 dark/bright lines are not.

11 June 2018, 17:40	#434
vagrant Registered User Join Date: Mar 2012 Location: Australia Age: 44 Posts: 1,126	Yep confirmed, OSD garbage gone & 2 lines remain.

11 June 2018, 17:48	#435
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	Last line may be fixed (as in hidden again if lagless mode) now. Did it only happen when using F12 to enter GUI? Not even using ALT-TAB?

12 June 2018, 01:19	#436
vagrant Registered User Join Date: Mar 2012 Location: Australia Age: 44 Posts: 1,126	It was happening under both situations, but looks to be fixed now

12 June 2018, 05:11	#437
Kalamatee Registered User Join Date: May 2017 Location: Scotland Posts: 53	Hi Toni, I have one gripe with the current WinUAE - if I run it with the -log option it opens a window and displays the output there, but when I jump into the debugger the log window gets closed so I have to then go find the actual log file. Would it be possible to have it leave the log window open?

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