View Single Post
Old 15 October 2016, 11:27   #330
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 42
Posts: 19,517
Quote:
Originally Posted by emufan View Post
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)

Quote:
Originally Posted by Dr.Venom View Post
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.
Toni Wilen is online now  
 
Page generated in 0.05251 seconds with 9 queries