WinUAE 4.0.0 beta series

[Toni Wilen]

Originally Posted by Rotareneg

Fixed the crashing by clearing the HKEY_CURRENT_USER\Software\Arabuusimiehet\WinUAE\AVConfiguration registry key. That config file still opens to 640x480 though.

"Native" not working was already mentioned. Output crashed if "capture before filtering" is set.

[vagrant]

Using winuae.7z and -busywait, as soon as I start emulation I get black screen then program quits, with both D3D9 & D3D11

[mark_k]

Regarding the "much too fast with 2 slices" issue I mentioned (probably same/related to ED-209's issue)... I discovered that it doesn't happen when Windows' power plan is set to Balanced. The problem occurs when power plan is set to High performance.

[Toni Wilen]

Originally Posted by ED-209

Using winuae.7z and -busywait, as soon as I start emulation I get black screen then program quits, with both D3D9 & D3D11

Does it still work in normal windowed/fullscreen modes?
Use -logflush command line, last 1-3 lines probably got lost when it crashed (fullscreen mode crash usually looks like quit)

Originally Posted by mark_k

Regarding the "much too fast with 2 slices" issue I mentioned (probably same/related to ED-209's issue)... I discovered that it doesn't happen when Windows' power plan is set to Balanced. The problem occurs when power plan is set to High performance.

I still can't duplicate but perhaps it is now fixed?

[mark_k]

Originally Posted by Toni Wilen

I still can't duplicate but perhaps it is now fixed?

Just tested today's winuae.exe 2018-04-13 20:11 and yes, that seems to have fixed it.

[vagrant]

Originally Posted by Toni Wilen

Does it still work in normal windowed/fullscreen modes?
Use -logflush command line, last 1-3 lines probably got lost when it crashed

winuae.7z & winuae2.7z both crash at startup, whether -busywait is set or not. I don't think logfile has changed. Yes, normal windowed/fullscreen modes still work fine.

[DamienD]

Originally Posted by Toni Wilen

Yes, set all config values before starting emulation, official beta 1.

Sorry for the delay Toni, here you go: https://www.sendspace.com/file/jxgbgn

[Toni Wilen]

Originally Posted by DamienD

Sorry for the delay Toni, here you go: https://www.sendspace.com/file/jxgbgn

It seems to hang in D3DKMTGetScanLine(). So looks like driver problem.. Mclane's hang problem seems to be exact same.

So the question is: is there something common in both? (EDIT: At least not GPU, Intel vs NVidia)

Does it also hang in full-window mode? (use same low latency config, only change to fullscreen to full-window). (Note that if it does not hang, speed is most likely wrong)

Does winuae.exe show full CPU core CPU usage or does it appear as using 0% of CPU when it hangs?

[DamienD]

Originally Posted by Toni Wilen

It seems to hang in D3DKMTGetScanLine(). So looks like driver problem.. Mclane's hang problem seems to be exact same.

So the question is: is there something common in both?

It's no problem up update both my "Intel HD Graphics 3000" and "NVidia GeForce GT 540M" drivers.

Originally Posted by Toni Wilen

Does it also hang in full-window mode? (use same low latency config, only change to fullscreen to full-window). (Note that if it does not hang, speed is most likely wrong)

Does winuae.exe show full CPU core CPU usage or does it appear as using 0% of CPU when it hangs?

Get back to you shortly; thanks Toni

[Toni Wilen]

Originally Posted by DamienD

It's no problem up update both my "Intel HD Graphics 3000" and "NVidia GeForce GT 540M" drivers.

Do you mean you have laptop that has both? It can work strangely and cause side-effects.

[DamienD]

Yes, both video cards mentioned inside the laptop.

Haven't had issues, strange effects with any emulators etc. over the past 7 years but get this new mode is different / techical.

[Toni Wilen]

Originally Posted by DamienD

Yes, both video cards mentioned inside the laptop.

Haven't had issues, strange effects with any emulators etc. over the past 7 years but get this new mode is different / techical.

It is quite different. Does it work if you force nvidia only or intel only?

[Toni Wilen]

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

Beta 2:

- New low latency vsync tweaks and updates.
- If low latency vsync polling takes longer than 2 vblanks, exit immediately to prevent total hang if scanline reads return unexpected and weird values.
- Display panel "native" resolution returned non-existing mode which got fixed to smallest supported resolution.
- Fixed clipboard sharing.
- Fixed graphics corruption (black lines/tearing) in new low latency mode with Vertical centering enabled.
- Added overlay led support. Led overlays must have same resolution as main overlay file, fully transparent color except location of led. Name must be <original name>_x_led.png where x = power,df0,df1,df2,df3,hd,cd,md,net (md = flash/eeprom access, for example cd32 nvram) Currently D3D11 only.
- MMU emulation works again (at least 68030 was broken)
- If low latency vsync and DSOUND: switch to WASAPI. New low latency vsync needs "pull" mode audio driver.
- Added new misc panel option, asks for confirmation when trying to close emulation window using close button or ALT+F4/CTRL+F11.
- Fixed Output panel crash if capture before filtering was set.

[mcbpete]

I can't seem to work out how to get the 'Low Latency VSync' mode to run at 50fps, it always seems to be locked at 60 (or will fluctuate around 60 if slices are set to '4', as the CPU led seems to randomly fly around 95% to 115% !). 'Low Latency VS 50/60Hz' is fine though and is a rock solid 50fps with the CPU led hitting around 15% tops (frequently it idles around 0-2%)

[DamienD]

Originally Posted by Toni Wilen

Does it also hang in full-window mode? (use same low latency config, only change to fullscreen to full-window). (Note that if it does not hang, speed is most likely wrong)

Does winuae.exe show full CPU core CPU usage or does it appear as using 0% of CPU when it hangs?

Yes, also hangs in full-window mode.

I have LEDs on, I do see 0% of CPU and none of the other LEDs are active. The game doesn't even start for a second, immediate hang after starting emulation.

Originally Posted by Toni Wilen

It is quite different. Does it work if you force nvidia only or intel only?

NVIDIA is forced. Removed this so the Intel is being used but same issue unfortunately.

[Toni Wilen]

Originally Posted by mcbpete

I can't seem to work out how to get the 'Low Latency VSync' mode to run at 50fps, it always seems to be locked at 60 (or will fluctuate around 60 if slices are set to '4', as the CPU led seems to randomly fly around 95% to 115% !). 'Low Latency VS 50/60Hz' is fine though and is a rock solid 50fps with the CPU led hitting around 15% tops (frequently it idles around 0-2%)

Did you manually select 50Hz? 50/60 = automatically select host 50Hz/60Hz matching Amiga refresh rate. "Normal" = sync to whatever mode user selected. (Display panel "default" refresh rate is not going to work very well)

[mcbpete]

Oddly it doesn't appear offer that - I have the following (unless I'm looking in the wrong section, which is likely !):

[DamienD]

You have the same video card as me mcbpete.

Just tried beta 2; I know you haven't fixed anything with my issue. Still major problems for me when using Low latency Vsynce but sometimes can see the LEDs changing value. I also see the screen update extremely slowly in "3rd of the screen" bars from black, then grey and then white as the display is being drawn (but that's when using warp mode and the process takes 20+ seconds). This is first power on sequence that the should take 3 seconds.

I can however press <F12> and <Ctrl> + <F11> to quit.

[Toni Wilen]

Originally Posted by DamienD

You have the same video card as me mcbpete.

Just tried beta 2; I know you haven't fixed anything with my issue. Still major problems for me when using Low latency Vsynce but sometimes can see the LEDs changing value. I also see the screen update extremely slowly in "3rd of the screen" bars from black, then grey and then white as the display is being drawn (but that's when using warp mode and the process takes 20+ seconds). This is first power on sequence that the should take 3 seconds.

I can however press <F12> and <Ctrl> + <F11> to quit.

Nothing is fixed, b2 only detects hung situation to prevent full hang. It also becomes really slow in this situation but it is better than hang

Originally Posted by mcbpete

Oddly it doesn't appear offer that - I have the following (unless I'm looking in the wrong section, which is likely !):

Attach winuaebootlog.txt, thanks.

Do you also have intel/nvidia dual GPU system?

[mcbpete]

Sure thing, find attached below. The only GPU I have on this laptop is the onboard Geforce 540m