WinUAE 4.0.0 beta series - Page 2

AMIGASYSTEM · 09 April 2018, 15:37

Quote:

Originally Posted by Toni Wilen

Fixed in next beta.

Ok thank you Toni (tested last "winuae.7z", ClipBoard Sharing now it works perfectly), today i tried to create 2 monitors (RTG/PAL) and I noticed that the pointer can not be used simultaneously on the 2 screens, there is a way to do it?

Mclane · 09 April 2018, 16:38

Hi Toni,

Just tried the new beta and was keen to see what the lag free vsync was like but after setting full screen, cycle exact, selecting 60Hz and the monitor I want to use and start winuae becomes unresponsive, it does not fully crash but the only way to end it is with task manager.

Config was a default Winuae A500, no disk loaded (just to see if it was a disk or not), if I run but don't use the low vsync then Winuae works 100%

Logs provided....

Thank you..

ramon · 09 April 2018, 17:14

Black screen on various Amiga 1200/4000 config. F12 does nothing, must kill Winuae with task manager and therefor, no winuaelog.txt saved. Strangely, CD32 does work. Amiga 1000, 500, 600, 2500, 3000 and CDTV seems to work fine.

Toni Wilen · 09 April 2018, 17:53

Quote:

Originally Posted by ramon

Black screen on various Amiga 1200/4000 config. F12 does nothing, must kill Winuae with task manager and therefor, no winuaelog.txt saved. Strangely, CD32 does work. Amiga 1000, 500, 600, 2500, 3000 and CDTV seems to work fine.

Quote:

Originally Posted by Mclane

Hi Toni,

Just tried the new beta and was keen to see what the lag free vsync was like but after setting full screen, cycle exact, selecting 60Hz and the monitor I want to use and start winuae becomes unresponsive, it does not fully crash but the only way to end it is with task manager.

Config was a default Winuae A500, no disk loaded (just to see if it was a disk or not), if I run but don't use the low vsync then Winuae works 100%

Logs provided....

Thank you..

Step 1:

Run winuae with -logflush parameter, this should create log without missing data.

Step 2:

Right click winuae.exe in Task manager and select Create dump file. Attach the dump file.

White · 09 April 2018, 20:40

Hi Toni,
Thanks for the reply, at the moment I deleted all the configurations.
Creating a new configuration with winUAE 4 everything works well.
The crashes do not verify them.
If I add the old configurations again, winUAE 4 crashes.
I have this problem, the keyboard of my computer does not support F10 even having updating the BIOS of the Lenovo, and a long-known problem.
First ALT-TAB worked with version 3.6.1, now with winUAE 4 no
Now with winUAE 4 I have to press CTRL ALT CANC
in this way I can not reset the hot configurations
am I wrong?
Thanks again for your work and your patience and any suggestions.
Thanks again!

Steve · 09 April 2018, 21:05

Quote:

Originally Posted by Toni Wilen

Does F12 work identically?

Pressing F12 returns WinUAE to the desktop menu as normal.

Toni Wilen · 09 April 2018, 21:06

Quote:

Originally Posted by AMIGASYSTEM

I noticed that the pointer can not be used simultaneously on the 2 screens, there is a way to do it?

This is not emulation related but Amiga OS related (so offtopic here

), but no, normally you can't have active WB on multiple monitors.

Quote:

Originally Posted by Toni Wilen

Vertical centering seem to mess up partial updates..

Possibly fixed in winuae.7z now.

Retro-Nerd · 09 April 2018, 21:58

Confirmed. Black lines and tearing is gone now with centering -> vertical enabled.

Steve · 09 April 2018, 22:59

Quote:

Originally Posted by Retro-Nerd

Confirmed. Black lines and tearing is gone now with centering -> vertical enabled.

It doesn't fix it for me unfortunately. In fact I think the new version has introduced slightly more tearing at the top of the screen during scrolling.

Retro-Nerd · 09 April 2018, 23:01

Are you sure you got the correct beta zip version from 20:59?

Steve · 09 April 2018, 23:03

Quote:

Originally Posted by Retro-Nerd

Are you sure you got the correct beta zip version from 20:59?

Ah, I downloaded the 64 bit version. Is it not this one?

Retro-Nerd · 09 April 2018, 23:04

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

Maybe clear your browser cache before downloading it.

White · 09 April 2018, 23:14

Hi Toni,
I added AMD-RAMDISK again, it works perfectly.
Strangely with the second added configuration ALT-TAB works perfectly.
I hope it is useful.
Thank you! I'm always happy for a new version of winUAE :-)

mcbpete · 09 April 2018, 23:39

What's the difference between the two modes 'Low Latency VSync' and 'Low Latency VS, 50/60hz' ? The former seems to keep fluctuating wildly between 50 & 60 fps (mainly towards 60fps, even though it's set to PAL), but the latter maintains a rock solid 50fps.

I'd obviously prefer the rock solid frame rate but is that one actually running in the new 'Lagless VSync' mode? It doesn't seem to display those coloured 'debug' bars when pressing End+F9 so I'm thinking maybe not ...

Steve · 09 April 2018, 23:56

So with mine, using the latest exe I get no black lines on the display when using vertical centering. So that's the good news.

Unfortunately there is still some tearing at the top of the screen during gameplay.

Even more unfortunate, if I press F12 and change nothing, then return to the game it becomes extremely choppy with tearing all over the display during scrolling. LED's remain normal so it's not a CPU issue.

If I then switch to standard vsync display the scrolling image returns to normal.

If I switch back again (back to low-latency) the screen tears all over the place again during scrolling.

Retro-Nerd · 10 April 2018, 01:35

Do you use scaling? Most of the scaling methods acting weird for me with lagless Vsync. Try no scaling and select a horizontal/vertical x-size, e.g for 1080p in hires 2x/2x or lores 4x/4x.

Toni Wilen · 10 April 2018, 08:56

It sounds more like some power saving feature causing issues. Make sure GPU and CPU power saving settings are not too high. Temporarily try max power settings to confirm if it is power saving related. Do also separate test with sound emulation disabled.

Check END+F9 bars, they should be stable, topmost bar may flicker, remaining bars should be stable (slight jitter is normal, sometimes larger jump but never more than 1/2 total bar size)

50/60 means monitor refresh rate follows Amiga refresh rate. It should not make any difference if Amiga refresh rate does not change.

Does reducing number of bars (new value in display panel) help? 1 matches old low latency vsync (not really but close enough)

And as usual, attach your config and winuaelog.txt. Exit and re-enter fullscreen mode few times when logging. Include also photo that shows tearing if possible (with END+F9 bars visible).

Leandro Jardim · 10 April 2018, 11:37

Quote:

Originally Posted by Toni Wilen

Try selecting real resolution from the list, not "native", it seems "native" has some issues..
EDIT: Also make sure to select 50hz or 60hz refresh rate, don't select "default".

Confirmed. Thanks Toni!

Mclane · 10 April 2018, 12:58

Quote:

Originally Posted by Toni Wilen

Step 1:

Run winuae with -logflush parameter, this should create log without missing data.

Step 2:

Right click winuae.exe in Task manager and select Create dump file. Attach the dump file.

Here you go Toni,

Thanks for looking..

Would not allow me to upload the zipped dump file so external link to that..

http://www..com/file/cjz7j1n8o5drzlz/winuae.zip

DamienD · 10 April 2018, 13:06

Quote:

Originally Posted by Mclane

Would not allow me to upload the zipped dump file so external link to that..

http://www..com/file/cjz7j1n8o5drzlz/winuae.zip

Did you upload to Media Fire?

This gets stripped automaticcally by EAB...

So the link will need to be http://www.Media Fire.com/file/cjz7j1n8o5drzlz/winuae.zip (obviously remove the space).

09 April 2018, 20:40	#25
White Registered User Join Date: Sep 2016 Location: italy Posts: 1,480	Hi Toni, Thanks for the reply, at the moment I deleted all the configurations. Creating a new configuration with winUAE 4 everything works well. The crashes do not verify them. If I add the old configurations again, winUAE 4 crashes. I have this problem, the keyboard of my computer does not support F10 even having updating the BIOS of the Lenovo, and a long-known problem. First ALT-TAB worked with version 3.6.1, now with winUAE 4 no Now with winUAE 4 I have to press CTRL ALT CANC in this way I can not reset the hot configurations am I wrong? Thanks again for your work and your patience and any suggestions. Thanks again! Attached Thumbnails Last edited by White; 09 April 2018 at 20:45. Reason: error1

09 April 2018, 23:14	#33
White Registered User Join Date: Sep 2016 Location: italy Posts: 1,480	Hi Toni, I added AMD-RAMDISK again, it works perfectly. Strangely with the second added configuration ALT-TAB works perfectly. I hope it is useful. Thank you! I'm always happy for a new version of winUAE :-) 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

09 April 2018, 17:14	#23
ramon Registered User Join Date: Sep 2014 Location: Canada Posts: 12	Black screen on various Amiga 1200/4000 config. F12 does nothing, must kill Winuae with task manager and therefor, no winuaelog.txt saved. Strangely, CD32 does work. Amiga 1000, 500, 600, 2500, 3000 and CDTV seems to work fine.

09 April 2018, 21:58	#28
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,436	Confirmed. Black lines and tearing is gone now with centering -> vertical enabled.

09 April 2018, 23:01	#30
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,436	Are you sure you got the correct beta zip version from 20:59?

09 April 2018, 23:04	#32
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,436	http://www.winuae.net/files/b/winuae.7z Maybe clear your browser cache before downloading it.

09 April 2018, 23:39	#34
mcbpete Zone Friend Join Date: Oct 2004 Location: London, England Age: 41 Posts: 239	What's the difference between the two modes 'Low Latency VSync' and 'Low Latency VS, 50/60hz' ? The former seems to keep fluctuating wildly between 50 & 60 fps (mainly towards 60fps, even though it's set to PAL), but the latter maintains a rock solid 50fps. I'd obviously prefer the rock solid frame rate but is that one actually running in the new 'Lagless VSync' mode? It doesn't seem to display those coloured 'debug' bars when pressing End+F9 so I'm thinking maybe not ...

09 April 2018, 23:56	#35
Steve I Identify as an Ewok Join Date: Jul 2001 Location: North Lincolnshire Age: 45 Posts: 2,356	So with mine, using the latest exe I get no black lines on the display when using vertical centering. So that's the good news. Unfortunately there is still some tearing at the top of the screen during gameplay. Even more unfortunate, if I press F12 and change nothing, then return to the game it becomes extremely choppy with tearing all over the display during scrolling. LED's remain normal so it's not a CPU issue. If I then switch to standard vsync display the scrolling image returns to normal. If I switch back again (back to low-latency) the screen tears all over the place again during scrolling.

10 April 2018, 01:35	#36
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,436	Do you use scaling? Most of the scaling methods acting weird for me with lagless Vsync. Try no scaling and select a horizontal/vertical x-size, e.g for 1080p in hires 2x/2x or lores 4x/4x.

10 April 2018, 08:56	#37
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	It sounds more like some power saving feature causing issues. Make sure GPU and CPU power saving settings are not too high. Temporarily try max power settings to confirm if it is power saving related. Do also separate test with sound emulation disabled. Check END+F9 bars, they should be stable, topmost bar may flicker, remaining bars should be stable (slight jitter is normal, sometimes larger jump but never more than 1/2 total bar size) 50/60 means monitor refresh rate follows Amiga refresh rate. It should not make any difference if Amiga refresh rate does not change. Does reducing number of bars (new value in display panel) help? 1 matches old low latency vsync (not really but close enough) And as usual, attach your config and winuaelog.txt. Exit and re-enter fullscreen mode few times when logging. Include also photo that shows tearing if possible (with END+F9 bars visible).

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