WinUAE 3.4.0 beta series

[Toni Wilen]

Originally Posted by emufan

hmm, it is about the window size. Display -> Windowed
when i start with 800x600 OpalVision works.
when i resize the window ro maybe 814x616 OpalVision loosing its colors.
if i reduce the window size again, OpalVision is colored again.
can you reproduce that?

No, it is your filter setting. Just disable it already.

EDIT: It is known problem, opalvision control line is located in the very first visible line. (which is normally always invisible in overscan)

EDIT2: Also note that on the fly changes won't work with opalvision. OV's VRAM is usually only updated once at startup, not continuously.

[emufan]

Originally Posted by Toni Wilen

No, it is your filter setting. Just disable it already.

hehe, ok ok. i've done that. so many flags and options to set, sometimes you dont know where to look first.
i now know where to switch things to get the OpalVision to work.
alot of cool things you have added lately, thanks for that


-------------------------------------------------------------------------


beta 11 is missing the "SND xyz%" value in the window status bar, next to CPU, HD and so on. 3.3.0 does display the SND status.

[Toni Wilen]

beta 11 is missing the "SND xyz%" value in the window status bar, next to CPU, HD and so on. 3.3.0 does display the SND status.

It is by design. WASAPI pull mode can't report it. DirectSound still supports it.

[arti]

Is it only me but since Windows 10 I can't close Crash window.

[Toni Wilen]

Originally Posted by arti

Is it only me but since Windows 10 I can't close Crash window.

Probably and I don't think this is 3.4 beta specific anyway..

EDIT: in other words: not enough information! And it isn't that important anyway, crash is more important.

[thomas]

Originally Posted by arti

Is it only me but since Windows 10 I can't close Crash window.

It's not only you and it is neither related to Win10 nor to 3.4, you can never close the crash window if the crash occurs while WinUAE catches all input. In fullscreen mode you won't even see the crash window.

[arti]

But why I can't select it with Alt+Tab and press Close?

Instead I have to Alt+Ctrl+Del and kill WinUae.
Not very convenient.

[Dr.Venom]

When running Amiga interlaced screens on a PC host interlace screen, with "interlaced line mode" set to " double,fields" in WinUAE it will continuously run interlace frame type mismatch in the log.

15-319 [2869 000-000]: Interlaced frame type mismatch 1<>0 (149,-1)
15-400 [2873 000-000]: Interlaced frame type mismatch 1<>0 (-1,1119)
15-486 [2878 000=000]: Interlaced frame type mismatch 0<>1 (185,133)
15-567 [2882 000=000]: Interlaced frame type mismatch 0<>1 (-1,1119)
etc...

It does this only when WASAPI mode is selected. When DSOUND is selected the issue does not occur.

To replicate: run WinUAE with Wasapi mode on PC host interlace screen, with interlaced line mode set to " double, fields" and run a demo or game with interlaced screen in it (Lionheart options screen at start of game for example or Hardwired demo).

Please see attached logs and config. Toni, the config is a testcase one to make it easy to use on LCD screen, but for some reason the interlaced screen is reported as 15Hz (30i)... Anyway it serves to illustrate the issue. It's the same as on my CRT with 50i.

[emufan]

Originally Posted by arti

But why I can't select it with Alt+Tab and press Close?

Instead I have to Alt+Ctrl+Del and kill WinUae.
Not very convenient.

it's the same with win7 - have to use taskmanager and kill winuae this way

[Toni Wilen]

Originally Posted by emufan

it's the same with win7 - have to use taskmanager and kill winuae this way

I can try to uncapture the mouse before dialog appears but it does not guarantee anything. (also ctrl+alt+del and then esc and mouse should be force-uncaptured by Windows)

Originally Posted by Dr.Venom

When running Amiga interlaced screens on a PC host interlace screen, with "interlaced line mode" set to " double,fields" in WinUAE it will continuously run interlace frame type mismatch in the log.

15-319 [2869 000-000]: Interlaced frame type mismatch 1<>0 (149,-1)
15-400 [2873 000-000]: Interlaced frame type mismatch 1<>0 (-1,1119)
15-486 [2878 000=000]: Interlaced frame type mismatch 0<>1 (185,133)
15-567 [2882 000=000]: Interlaced frame type mismatch 0<>1 (-1,1119)
etc...

It does this only when WASAPI mode is selected. When DSOUND is selected the issue does not occur.

To replicate: run WinUAE with Wasapi mode on PC host interlace screen, with interlaced line mode set to " double, fields" and run a demo or game with interlaced screen in it (Lionheart options screen at start of game for example or Hardwired demo).

Please see attached logs and config. Toni, the config is a testcase one to make it easy to use on LCD screen, but for some reason the interlaced screen is reported as 15Hz (30i)... Anyway it serves to illustrate the issue. It's the same as on my CRT with 50i.

You forgot to mention when it started.

[Dr.Venom]

Originally Posted by Toni Wilen

You forgot to mention when it started.

The interlace frame type mismatch problem (when using Wasapi) was introduced with 3400 beta 6. Beta 5 is OK.

[Toni Wilen]

Originally Posted by Dr.Venom

The interlace frame type mismatch problem (when using Wasapi) was introduced with 3400 beta 6. Beta 5 is OK.

I don't see any difference between 5 and 6. Both have same problem, it is just
random if it starts quickly or later.

[Dr.Venom]

Originally Posted by Toni Wilen

I don't see any difference between 5 and 6. Both have same problem, it is just
random if it starts quickly or later.

I noticed something similar just now, when it "works" if I then press F12 and return to the screen the problem is there again. I will try to test some other WinUAE versions later on..

[emufan]

Originally Posted by Toni Wilen

I can try to uncapture the mouse before dialog appears but it does not guarantee anything. (also ctrl+alt+del and then esc and mouse should be force-uncaptured by Windows)

worth a try

[Toni Wilen]

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

Beta 12:

- If genlock is active, mode is not "-" and new genlock alpha option is checked, screenshots and avioutput videos include alpha-channel generated from genlock transparency data. Only works in 32-bit mode and may not work if capture before filtering is not set.
- Added genlock video input events: restart, pause/unpause, next and previous frame.
- WASAPI shared mode uses lower latency mode introduced in Windows 10 that allows sub-10ms latencies in shared mode (if sound driver supports it). Buffers larger than 10ms and non-Windows 10 systems use "old" method.
- "Min" (WASAPI only) sound buffer setting added. Selects smallest buffer size that driver supports.
- WASAPI sound buffer size adjusted. All buffer size values now allocate smaller buffer than previously, pull (event) mode is much more stable than previously used push mode, there is no need for very large buffer sizes anymore.
- WASAPI sound automatically switches to default device if current device disappears (for example unplugged USB sound card/headset)
- Added RTL8019 9346 EEPROM emulation.
- Ariadne II NIC emulation. RTL8019AS based. (9346 contents are not correct but driver does not seem to care)
- X-Surf NIC emulation, also RTL8019AS based. (Including ISA PNP emulation that driver needs...) No IDE support.
- X-Surf 100 (Z2 and Z3) NIC emulation, uses RTL8019AS "compatible" chip. Does not emulate any AX88796B extra features (=only works if driver assumes chip only supports NE2000/RTL8019AS features. Official driver does not seem to use any extra features.)
- Ariadne II and X-Surfs are currently SLIRP-only, no configuration available. Multiple enabled NICs are still also not supported.
- Disable horizontal/vertical filter configured blanking if display port adapter is active that needs RGBI control lines.
- Try to uncapture mouse before showing crash report dialog.

[emufan]

Originally Posted by Toni Wilen

- Added genlock video input events: restart, pause/unpause, next and previous frame.

one of the geek'iest features ever, even considered as useless, great work

- Try to uncapture mouse before showing crash report dialog.

tried to provoke a crash, no luck so far

[mritter0]

With b12 WinUAE crashes and closes at the pink boot stage. Same config I've been using for months.

[Toni Wilen]

Originally Posted by mritter0

With b12 WinUAE crashes and closes at the pink boot stage. Same config I've been using for months.

Does it stop crashing if you (temporarily) disable NE2000 PCI card?

[mritter0]

I don't have the NE2000 card enabled. I do have the Realtek 8029 enabled.

Disabling that, it does boot successfully.

[Toni Wilen]

Originally Posted by mritter0

I don't have the NE2000 card enabled. I do have the Realtek 8029 enabled.

It is same thing. 8019 (designed for ISA bus) and 8029 (designed for PCI) is NE2000 compatible (plus some extra realtek-only features that most drivers ignore)

Disabling that, it does boot successfully.

Great, it will be fixed in next beta.