03 June 2012, 12:45 | #41 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
http://www.winuae.net/files/b/winuae_2420b4.zip
Beta 4: - Custom input event autofire wasn't always canceled when shortcut included qualifier(s). - Do not crash if 7zip unpacking fails because out of memory or process address space. (Big compressed CD images and 32-bit Windows) - Log also RDB dostype in text format. - Replaced misc panel checkboxes with scrolling checkbox list view. Now there is unlimited space for all kinds of on/off options that I previously refused to add because of lack of GUI space. - Added disable notification icon option. - Loading statefile using GUI now remembers statefile filename, allowing to save configuration files with statefile (running configuration file will automatically load the statefile). This required manual config file editing previously. Statefile path and checkbox that "forgets" stored path added to GUI. - Ignore vendor specific USB usage pages (Do not list for example some Logitech USB mouse/keyboard receiver dongles) - Z2 RTG + 68EC020 fixed, RTG requires memory mapping. (Memory mapping was originally JIT only and 68EC020 is not JIT compatible) |
03 June 2012, 13:36 | #42 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
Quote:
Something like "version x did this when running that but following version y does does this when running same program using same settings" is much better (but note that fastest possible = nothing is guaranteed, especially compatibility) Quote:
|
||
03 June 2012, 13:52 | #43 | ||
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
Quote:
Quote:
|
||
03 June 2012, 15:16 | #44 | |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
Quote:
With Beta 4, the issue is quite apparent. When running the WHDLoad demo "Big Time Sensuality" by Axis (started from a plain vanilla 3.1 workbench) in fastest possible mode -and- low latency vsync, then after some seconds of running, the demo quits back to workbench with the message "WHDLoad has detected that a previous call to 'resload_Diskload' has been interrupted. The actual call to 'resload_FlushCache' can therefore not been processed." If I run this demo with the exact same config, but only disable vsync, then it works without problems. Configs, logs and screenshot attached. |
|
08 June 2012, 11:07 | #45 |
Registered User
Join Date: Nov 2009
Location: UK
Posts: 497
|
As of beta 4 (perhaps some earlier betas too), almost all of the tearing issues on my hardware are gone. Only using HQ4X (software or D3D) has noticeable tearing, as well as some other D3D filters. (Does anyone else have any issues with D3D filters on this beta series?)
Software HQ3X is rock solid though, even at 1920x1080 (fullscreen and fullwindow) with fastest-possible JIT + no-buffer vsync. Windowed mode works well too (with Aero disabled). |
08 June 2012, 15:51 | #46 |
Supernormal
Join Date: Jul 2007
Location: Istanbul / Turkey
Age: 43
Posts: 1,411
|
I can't make WinUAE create winuaelog.txt by turning it on from the miscellaneous part of the gui.
Last edited by ancalimon; 08 June 2012 at 15:59. |
08 June 2012, 16:29 | #47 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
Quote:
Check winuaebootlog.txt for path information. |
|
08 June 2012, 17:07 | #48 |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
It might be, but I'm not fully sure yet.. I have some additional testresult. Running it with exact same config but instead of low latency vsync, use legacy vsync instead, the demo works.
So (with the config earlier attached, only changing between vsyncs): - Fastest possible without vsync: works - Fastest possible & legacy vsync: works - Fastest possible & low latency vsync: doesn't work It strikes me as a bit odd that that the first two work, and the third doesn't. If it's a timing issue than why is low latency vsync the only one suffering from it (even with having tried the various CPU throttle settings with it, which should also affect timing?) Any idea? |
08 June 2012, 17:29 | #49 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
Vsync can change how CPU time is "distributed" a lot and HD access runs in separate thread which can make HD access timing very different. (Error seems to have something to do with OS HD access)
Does it do the same when running from ram disk or hdf? (instead of directory) |
08 June 2012, 18:22 | #50 | |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
Quote:
I found something interesting additionally. Running the demo from floppy with the exact same fastest possible & low latency vsync config, the demo does work. There is a small bug though when running from floppy. In the beginning of the demo it doesn't show the zooming routine with the "Axis - Anno Domini 1994" text, but it only shows the text when the zoom finishes. (Same happens with A1200 cycle exact config.) Interestingly the end of this "non-working" zooming routing on the floppy version is also the exact same spot where the whdload version crashes: whdload does properly show the zooming, but at the end when the text is fully zoomed it quits back with the reported error. I think it's a safe bet to say that the whdload version has that zooming routine patched, possibly in a bit "hackerish" fashion, causing the demo to be very timing sensitive at that point? So I'm not sure if it explains it as truely being a whdload patch/timing issue (it could still coincide with e.g. a "load from disk" event), but it does seem to make it more probable..? |
|
09 June 2012, 22:24 | #51 |
Supernormal
Join Date: Jul 2007
Location: Istanbul / Turkey
Age: 43
Posts: 1,411
|
|
12 June 2012, 01:02 | #52 | |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
I've been testing some more and found that my earlier conclusion on the Axis demo compatibility in fastest possible and low latency vsync (see posts here and here) wasn't fully correct; the CPU Speed throttle does have influence. This would point to it plainly being a demo or slave timing issue, but hang on..
Using earlier attached A1200+fastestpossible+lowlatencyvsync config (see here), and varying CPU speed: CPU Speed set to -90%,-80%,-70%: demo works CPU Speed set to -60% or less: demo "crashes" with the earlier reported error. So adding to the earlier reported results:
Maybe it can be of help, so I've gone back to the 2.4.1 beta series (again using the same config) and found that with 2.4.1 beta 1 to beta 6 this demo did work in fastest possible mode at full speed and low latency vsync. Since 2.4.1 beta 7 and onwards it doesn't work anymore. Hopefully this provides a clue as to whether this is indeed a pure slave timing issue, or whether there's an identifiable issue with the current fastest possible low latency implementation, that keeps it from having the same level of compatibility as fastest possible mode with no vsync / legacy vsync. Quote:
Last edited by Dr.Venom; 12 June 2012 at 01:20. |
|
14 June 2012, 18:58 | #53 | |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
Interlaced frame type mismatch 1<>0
Quote:
I've been experimenting a bit with the shaders and having a scaled image on my LED screen, and noticed that the "integer scaling" option in filters only scales in steps of 2, i.e. 2,4,6,8. As such it's missing the 3X scaling, and I was wondering if you could add these to the integer scaling options? I'm asking because in my experience a 4x scaled image (or 2x with double line mode enabled), fills the whole 1080p height, but pixels look too pixelated/blocky. A 2x scaled image (or 1x with double line mode) looks closer to CRT, but the image on screen is too small (filling only half of the 1080p height). The sweetspot as such would be 3X scaling (or 1.5X with double line mode enabled), finding a good balance between filling enough screensize and pixels not becoming too blocky or pixelated. That way when applying a (modified) scanline/CRT filter makes it look closely to what a 14inch CRT is looking like. As such, hopefully it's possible to have the 3X and 1.5X scaling options added. (Or is there maybe something code-wise standing in the way it?) Lastly, when experimenting a bit with the WinUAE.fx shader code I noticed that the built-in bi-lineair filtering option in WinUAE seems to get applied after the shader filter has done its job. I was wondering if this could be the other way around, so have the filter shader manipulating the source image -after- it has been bi-lineair filtered, or maybe have a flag in the .fx file where you can set whether the filtering is coming before or after the shader? Hopefully something is possible here.. |
|
17 June 2012, 11:56 | #54 | ||||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
Quote:
Quote:
EDIT: winuae.zip updated, perhaps I "accidentally" fixed it Quote:
Quote:
Last edited by Toni Wilen; 17 June 2012 at 13:03. |
||||
18 June 2012, 18:49 | #55 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
http://www.winuae.net/files/b/winuae_2420b5.zip
Beta 5: - More custom input event fixes. - Replaced custom event single line string dialog with larger multiline dialog, increased allowed custom event string length. - Autoresolution didn't detect interlaced mode in some situations. - Added "Internal events" input device category. Currently it only contains two events: "CPU reset" and "Keyboard reset". It can be used to customize what happens when emulated Amiga is reset. For example: set CPU mode back to fastest possible, eject or insert disks, quit emulator, etc.. - Added 68020 prefetch CPU core. Emulates instruction prefetch without cycle-exact. "More compatible" option enables this mode (Previously it did nothing in 68020 mode) - A1200/CD32 Quickstart compatibility slider changed: cycle-exact/prefetch/fastest possible without JIT/JIT - ASPI support removed. |
22 June 2012, 12:07 | #56 | |||
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
Quote:
The bad news: it will not work in any configuration that uses LED 1080i as display output. It will always give the frame type mismatch. The good news: there is a specific configuration with CRT 574i in which interlace -always- seems to work. See the attached A500 configs and logs. The weird thing though is that: 1. A500.uae: this gives the frame type mismatch, always. Changing only -one- setting in above config, setting the default screenmode to start in 742x574i instead of 742x287: 2. A500-lace-(default refresh).uae: interlace will -always- work without any frame type mismatch Why does 2 work and 1 not? Does this still point to an issue with screenmode enumeration, or something? To make it even more confusing, setting the refresh rate to 25hz (instead of "default") in config 2, will cause it to break again and always result in the frame type mismatch. Unfortunately whatever I try to replicate this behaviour with LED 1080i doesn't work, there it will always give the frame type mismatch.... Quote:
Quote:
|
|||
22 June 2012, 12:49 | #57 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
Quote:
EDIT: for some reason calibration adjustement value is lost after mode is "remembered" again. Checking.. (Nothing wrong, it does not matter if minv=1) EDIT2: Do you mean it only "works" if you select screen mode that does not show "i" in calibration log message? Last edited by Toni Wilen; 22 June 2012 at 13:58. |
|
22 June 2012, 14:36 | #58 | ||
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
Quote:
What makes it tricky is that this mode easily results in a black screen. Currently it only seems to work when the screenmode is triggered from displaydata (like in earlier attached configs and quote below). 1. Removing the "gfx_interlace=true" in the first line will result in a black screen, or 2. Setting the gfx_refreshrate=0 in the first line to gfx_refreshrate=25 results in a black screen EDIT: 3. The default screenmode in WINUAE must also be set to 742x574 interlace in combination with the displaydata, otherwise the displaydata trigger will result in a black screen on switch to interlace Quote:
Last edited by Dr.Venom; 22 June 2012 at 14:45. |
||
22 June 2012, 15:04 | #59 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,534
|
Quote:
Quote:
|
||
22 June 2012, 15:39 | #60 | |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
See attached logs.
2. A500-lace-(default refresh).UAE --> interlace "WORKS" 1. Only changes default 742x574 interlace screenmode to 742x287 (displaydata untouched)--> mismatch 3. Only changes default 742x574 interlace "default refresh" to "25hz" (displaydata untouched) --> mismatch 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 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 |
|
|