11 October 2016, 19:46 | #321 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,506
|
Quote:
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. Last edited by Toni Wilen; 11 October 2016 at 20:25. |
|
11 October 2016, 21:45 | #322 |
Registered User
Join Date: Feb 2012
Location: #DrainTheSwamp
Posts: 4,545
|
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. Last edited by emufan; 12 October 2016 at 09:07. |
12 October 2016, 20:39 | #323 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,506
|
Quote:
|
|
14 October 2016, 19:59 | #324 |
Registered User
Join Date: Jul 2008
Location: Poland
Posts: 662
|
Is it only me but since Windows 10 I can't close Crash window.
|
14 October 2016, 20:08 | #325 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,506
|
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. Last edited by Toni Wilen; 14 October 2016 at 20:23. |
14 October 2016, 20:34 | #326 |
Registered User
Join Date: Jan 2002
Location: Germany
Posts: 6,985
|
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.
|
14 October 2016, 20:38 | #327 |
Registered User
Join Date: Jul 2008
Location: Poland
Posts: 662
|
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. |
15 October 2016, 00:14 | #328 |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
Interlace frame type mismatch in Wasapi mode
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. |
15 October 2016, 02:01 | #329 |
Registered User
Join Date: Feb 2012
Location: #DrainTheSwamp
Posts: 4,545
|
|
15 October 2016, 11:27 | #330 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,506
|
Quote:
Quote:
|
||
15 October 2016, 15:34 | #331 |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
|
15 October 2016, 16:01 | #332 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,506
|
|
15 October 2016, 16:13 | #333 |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
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..
|
15 October 2016, 16:25 | #334 |
Registered User
Join Date: Feb 2012
Location: #DrainTheSwamp
Posts: 4,545
|
|
15 October 2016, 19:25 | #335 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,506
|
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. |
15 October 2016, 23:24 | #336 | ||
Registered User
Join Date: Feb 2012
Location: #DrainTheSwamp
Posts: 4,545
|
Quote:
Quote:
|
||
16 October 2016, 01:23 | #337 |
Registered User
Join Date: Sep 2013
Location: Bettendorf, IA, USA
Age: 52
Posts: 204
|
With b12 WinUAE crashes and closes at the pink boot stage. Same config I've been using for months.
|
16 October 2016, 12:44 | #338 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,506
|
|
16 October 2016, 20:37 | #339 |
Registered User
Join Date: Sep 2013
Location: Bettendorf, IA, USA
Age: 52
Posts: 204
|
I don't have the NE2000 card enabled. I do have the Realtek 8029 enabled.
Disabling that, it does boot successfully. |
16 October 2016, 21:12 | #340 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,506
|
Quote:
Quote:
|
||
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
WinUAE 3.0.0 beta series (was 2.8.2/2.9.0) | Toni Wilen | support.WinUAE | 1010 | 15 December 2014 13:41 |
WinUAE 2.7.0 beta series | Toni Wilen | support.WinUAE | 326 | 03 December 2013 23:37 |
WinUAE 2.5.0 Beta series (Was 2.4.2) | Toni Wilen | support.WinUAE | 310 | 01 December 2012 18:02 |
WinUAE 2.3.3 beta series | Toni Wilen | support.WinUAE | 124 | 17 September 2011 15:48 |
WinUAE 1.5.3 beta series | Toni Wilen | support.WinUAE | 58 | 09 November 2008 13:46 |
|
|