WinUAE 2.4.0 beta series - Page 11

mingle · 12 February 2012, 13:07

Hi Toni... Sorry, I knew there was something I forgot to attach!

I tried the latest public Beta 16 and it's still dog-slow...

Mike.

Toni Wilen · 12 February 2012, 13:58

Quote:

Originally Posted by mingle

Hi Toni... Sorry, I knew there was something I forgot to attach!

I tried the latest public Beta 16 and it's still dog-slow...

Mike.

Attach also winuaelog.txt (remember to enable logging in misc panel). Does it also run slowly if you select Direct3D mode?
RTG mode only?

FreakyDan · 12 February 2012, 15:40

Quote:

Originally Posted by Dr.Venom

@ FreakyDan, I tested this with the latest unofficial Beta http://www.winuae.net/files/b/winuae.zip (exe dated 11-feb 17:47) . Could you try that one?

I've tried that version and now the tearing is gone, but I still get that crazy interlaced screen, using both kick3.0 and kick3.1.

Toni Wilen · 12 February 2012, 16:04

Quote:

Originally Posted by FreakyDan

I've tried that version and now the tearing is gone, but I still get that crazy interlaced screen, using both kick3.0 and kick3.1.

You really sure you have correct ROM? Works fine here with 3.0, looks weird (and lots of logging) with 3.1.

Toni Wilen · 12 February 2012, 16:22

Quote:

Originally Posted by mingle

All intuition-based tests seemed to crawl on 2400B16.

Redownload winuae.zip and test again, thanks.

FreakyDan · 12 February 2012, 17:02

Quote:

Originally Posted by Toni Wilen

You really sure you have correct ROM? Works fine here with 3.0, looks weird (and lots of logging) with 3.1.

Yes, I'm sure I have the correct roms.
But it seems to be a problem with one of my workbench setups (BetterWB) that causes the phenomena under 3.0, If i launch the demo from workbench it's weird. But if I boot without startup-sequence and launch it from CLI it runs fine.

Retro-Nerd · 12 February 2012, 19:43

The tearing with low latency Vsync without buffer is still there. I need at least "double buffer" to fix it.

Toni Wilen · 12 February 2012, 19:48

Quote:

Originally Posted by Retro-Nerd

The tearing with low latency Vsync without buffer is still there. I need at least "double buffer" to fix it.

(If this happened in 2.3.3 too): Not all drivers support D3D flush GPU queue NOW but delay it for later causing the tearing.

Double buffering mode is nearly as good as no buffer now.

Retro-Nerd · 12 February 2012, 19:54

WinUAE 2.3.3 was fine. It is one of the newer betas that causes the tearing again.

Quote:

Double buffering mode is nearly as good as no buffer now.

Good to know. I will test it with some pinball games.

mingle · 13 February 2012, 00:05

Hi Toni,

I tried the latest 2.4.0.0 b16 public Beta and it was even slower - SysInfo gave the same speed as an unexpanded A1200 :-)

I tried Direct3d and DirectDraw modes, with no discernible difference in speed.

Native and RTG modes are both slow - Native even slower than RTG.

I've attached log files for both 2.3.3.0 and 2.4.0.0.b16 - in both cases I booted into my ClassicWB config, opened the System disk, then the Tools drawer, the SysInfo drawer, then ran SysInfo and performed the "Speed" tests, then quit (F12) WinUAE.

I can see you're a busy man - hopefully we're not making you tear your hair out with these issues!

Cheers,

Mike.

Quote:

Originally Posted by Toni Wilen

Attach also winuaelog.txt (remember to enable logging in misc panel). Does it also run slowly if you select Direct3D mode?
RTG mode only?

Toni Wilen · 13 February 2012, 15:49

Quote:

Originally Posted by mingle

I tried Direct3d and DirectDraw modes, with no discernible difference in speed.

Native and RTG modes are both slow - Native even slower than RTG.

Redownload winuae.zip and try again, it should be faster again. I hope..

Toni Wilen · 13 February 2012, 16:06

Quote:

Originally Posted by Retro-Nerd

The tearing with low latency Vsync without buffer is still there. I need at least "double buffer" to fix it.

Does today's winuae.zip still have same problem? Is this fastest possible CPU or not? Both DD and D3D? (questions that always needs answering when topic is vsync)

Retro-Nerd · 13 February 2012, 18:19

Only in D3D, DD is fine. No, todays beta doesn't fix it, no matter what CPU Emulation speed is set.

mingle · 14 February 2012, 02:33

Much better - D3D also feels 'snappier' than DD mode, which is also shown in the SysSpeed results - see the two right-most columns for the tests I performed today using the latest beta (2400B16-DD & 2400B16-D3D).

Interestingly WinUAE 2.3.3.0 is still the champion (speed-wise!)

Cheers,

Mike.

Quote:

Originally Posted by Toni Wilen

Redownload winuae.zip and try again, it should be faster again. I hope..

mingle · 14 February 2012, 02:38

Just revisiting the screen-center issue I mentioned previously.

During the testing of the various betas I noticed that the issue (of the native-mode screens appearing on the left side of my display) only happens in DirectDraw mode.

When I switch to Direct3D, the native screens appear correctly in the middle of the display.

Cheers,

Mike.

Quote:

Originally Posted by Toni Wilen

But it is centered in the attached image?

I can't duplicate, works fine here.

Do not talk about centering before reading all other similar thread

It isn't that simple at all. Autoscale settings attempt to do that.

EDIT: Logs also needed. ~10-20% speed loss in fastest/JIT vsync modes is usually normal, there isn't any easy ways around it.

Toni Wilen · 14 February 2012, 15:53

Quote:

Originally Posted by mingle

Much better - D3D also feels 'snappier' than DD mode, which is also shown in the SysSpeed results - see the two right-most columns for the tests I performed today using the latest beta (2400B16-DD & 2400B16-D3D).

Perfect

Quote:

Interestingly WinUAE 2.3.3.0 is still the champion (speed-wise!)

Unofficial betas do not have full optimization enabled which could explain the difference.

Toni Wilen · 14 February 2012, 15:54

Quote:

Originally Posted by mingle

Just revisiting the screen-center issue I mentioned previously.

During the testing of the various betas I noticed that the issue (of the native-mode screens appearing on the left side of my display) only happens in DirectDraw mode.

When I switch to Direct3D, the native screens appear correctly in the middle of the display.

It is normal. DirectDraw can't handle all positioning situations, especially when using large resolutions, "can't do" position is top/left position. Previously this caused totally blank screen..

mingle · 14 February 2012, 22:05

Ah, okay... My Windows screen-mode is 1920x1080x32, makes sense now.

Also looking forward to the fully-optimised v2.4.0.0 :-)

Cheers,

Mike.

Quote:

Originally Posted by Toni Wilen

It is normal. DirectDraw can't handle all positioning situations, especially when using large resolutions, "can't do" position is top/left position. Previously this caused totally blank screen..

Retroplay · 14 February 2012, 22:29

Raw input seems to broken with XBCD drivers in beta 15 & 16.
Up/down and left/right have the same input in the test panel.
Last working version was b14.

Toni Wilen · 15 February 2012, 19:33

http://www.winuae.net/files/b/winuae_2400b17.zip

Beta 17:

- Fixed b16 low latency vsync issues.
- Possible fix for no buffer vsync tearing in D3D mode on some systems.
- Tweaked b4 too fast cpu audio hack, it broke routines that start playing empty sample (with length=1) and then near immediately reset audio pointer to correct sample. Hack detected this as a bad behavior and "fixed" it causing corrupt sound. (Game Solid 2 AGA)
- Release keys before pausing, stuck Alt if Alt-Tab pressed and emulation was set to pause when inactive.
- Magic mouse triggered window activation/deactivation didn't handle inactive pause or sound correctly.
- UAE controller mounted RDB hardfiles support bootable and do not mount checkboxes. "Do not mount" ticked = ignore all RDB hardfile partitions, "Bootable" unticked = do not boot from any RDB hardfile partition. Other boot priority values are ignored.
- Execute drive diagnostics IDE command should also set interrupt state (if enabled)
- Enable null filter if none and low latency vsync selected. It can't work with "none" filter.
- gfx_contrast/gfx_luminance/gfx_gamma didn't work on the fly using uae-configuration.
- Interlace mode detection rewritten. This should improve interlace emulation of weird programs doing weird things with interlace... Do not simply mirror BPLCON0 LACE bit but also check that LOF bit toggles correctly.
- Only enable vblank waits in non-vsync modes if triple buffering is enabled. I always forget that it is bad idea because on some systems it works fine, on some others it causes huge slowdowns.
- Some Advanced Chipset panel settings were not overridden if compatible settings was enabled. This could have caused strange compatibility problems even in Quickstart modes if default.uae had modified advanced chipset config entries.
- On the fly RTG vsync mode switch does not freeze the emulation anymore.
- Fixed A1000 Quickstart ROM missing message.
- KS 1.2 or older: map Z2 FastRAM as a non-autoconfig memory board.
- HID joystick negative axis values broke in b15.

14 February 2012, 22:29	#219
Retroplay Lemon Curry ? Join Date: Sep 2004 Location: Denmark Age: 49 Posts: 4,079	Raw input seems to broken with XBCD drivers in beta 15 & 16. Up/down and left/right have the same input in the test panel. Last working version was b14. Last edited by prowler; 10 September 2016 at 23:10. Reason: Removed attachments.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
WinUAE 2.5.1 beta series	Toni Wilen	support.WinUAE	69	22 December 2012 10:22
WinUAE 2.3.3 beta series	Toni Wilen	support.WinUAE	124	17 September 2011 15:48
WinUAE 2.3.2 beta series	Toni Wilen	support.WinUAE	79	31 May 2011 19:39
WinUAE 2.3.0 beta series (was 2.2.1)	Toni Wilen	support.WinUAE	229	22 September 2010 19:20

12 February 2012, 19:43	#207
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,435	The tearing with low latency Vsync without buffer is still there. I need at least "double buffer" to fix it.

13 February 2012, 18:19	#213
Retro-Nerd Missile Command Champion Join Date: Aug 2005 Location: Germany Age: 52 Posts: 12,435	Only in D3D, DD is fine. No, todays beta doesn't fix it, no matter what CPU Emulation speed is set.

15 February 2012, 19:33	#220
Toni Wilen WinUAE developer Join Date: Aug 2001 Location: Hämeenlinna/Finland Age: 49 Posts: 26,505	http://www.winuae.net/files/b/winuae_2400b17.zip Beta 17: - Fixed b16 low latency vsync issues. - Possible fix for no buffer vsync tearing in D3D mode on some systems. - Tweaked b4 too fast cpu audio hack, it broke routines that start playing empty sample (with length=1) and then near immediately reset audio pointer to correct sample. Hack detected this as a bad behavior and "fixed" it causing corrupt sound. (Game Solid 2 AGA) - Release keys before pausing, stuck Alt if Alt-Tab pressed and emulation was set to pause when inactive. - Magic mouse triggered window activation/deactivation didn't handle inactive pause or sound correctly. - UAE controller mounted RDB hardfiles support bootable and do not mount checkboxes. "Do not mount" ticked = ignore all RDB hardfile partitions, "Bootable" unticked = do not boot from any RDB hardfile partition. Other boot priority values are ignored. - Execute drive diagnostics IDE command should also set interrupt state (if enabled) - Enable null filter if none and low latency vsync selected. It can't work with "none" filter. - gfx_contrast/gfx_luminance/gfx_gamma didn't work on the fly using uae-configuration. - Interlace mode detection rewritten. This should improve interlace emulation of weird programs doing weird things with interlace... Do not simply mirror BPLCON0 LACE bit but also check that LOF bit toggles correctly. - Only enable vblank waits in non-vsync modes if triple buffering is enabled. I always forget that it is bad idea because on some systems it works fine, on some others it causes huge slowdowns. - Some Advanced Chipset panel settings were not overridden if compatible settings was enabled. This could have caused strange compatibility problems even in Quickstart modes if default.uae had modified advanced chipset config entries. - On the fly RTG vsync mode switch does not freeze the emulation anymore. - Fixed A1000 Quickstart ROM missing message. - KS 1.2 or older: map Z2 FastRAM as a non-autoconfig memory board. - HID joystick negative axis values broke in b15.

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