13 May 2021, 23:18 | #1 |
Registered User
Join Date: Mar 2013
Location: Leipzig/Germany
Posts: 466
|
Changes to default model configurations?
Since data cache emulation has been improved in recent WinUAE versions, it's probably a good idea to remove the default non-compatible config for the 030/040/060 CPUs:
https://github.com/FrodeSolheim/fs-u...ardware.c#L213 In addition, the new cpu_data_cacheshould be used. Could be like so: for accuracy=1: cpu_compatible=true cpu_data_cache=true for accuracy=0: cpu_compatible=true cpu_data_cache=false for accuracy=-1: cpu_compatible=false cpu_data_cache=false Also memory/blitter cycle exact mode should be availabe for the big box Amiga models. What about introducing a new accuracy=2 mode? (not to break compatibility with older configs) Edit: chipset_subpixel=trueshould be configurable too, so we can finally play WormsDC without glitches. :-) https://eab.abime.net/showthread.php?t=103212 Last edited by jbl007; 13 May 2021 at 23:37. Reason: Worms!!!!! |
15 May 2021, 11:30 | #2 |
FS-UAE Developer
Join Date: Dec 2011
Location: Førde, Norway
Age: 43
Posts: 4,043
|
I think your ideas make a lot of sense. This should definitively be considered for FS-UAE 4.0.
The original "accuracy" mechanism in FS-UAE is quite coarse, and with the plethora accuracy-related options (compatible cpu, cycle-exact cpu, chipset and/or memory, data caches, blitter-related options, etc), it is quite hard to boil this down a slider in one dimension. So another alternative to deprecated the accuracy option, make sure the default models are as good as possible for general use, introduce more official options to tweak it from there (*). (*) Note, it has always been possible to apply and override any UAE emulation-related by prefixing the option name as seen in WinUAE config files with uae_. But I also want to try keep the number of promoted options - the ones I put in the face of the user - distilled to a minimum while still being usable, because otherwise it can quickly become overwhelming. So I need to try to find the most important ones, or the most important combination of options. And the more obscure settings for rare cases can be hidden more away, or even just be available as custom options you need to type yourself. As another example of something that (maybe) needs considering is the default accuracy of the A1200 model, at least for WHDLoad games. Since the 68020 CPU isn't accurately emulated anyway, and since the WHDLoad games are often patched to be less dependent on the speed of the CPU, maybe using an "cycle-exact" A1200 model is just making it needlessly demanding to emulate. An Raspberry Pi 400 cannot in general run cycle-exact A1200 in FS-UAE, but with cycle-exact off, there is hope. So if cycle-exact is not important in this case, maybe it should default to off. I haven't run any extensive testing on this though. An in general, I have quite little information about how the real-world compatibility of games and software is affected by these options, especially with newer WinUAE releases (**). So, I will appreciate input in this matter, to help figure out the best default settings in 2021, and what the most useful compatibility options to tweak are (**) It probably makes sense to actually wait before making changes, until at least WinUAE 4.4 code is merged into FS-UAE. (@jbl007: PS: uae_chipset_subpixel=truemight work fine in FS-UAE 4.x already) |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
configuration default does not show model | amiga_Forever | support.FS-UAE | 2 | 19 October 2017 17:12 |
Default configurations tab in WinUAE | antonvaltaz | support.WinUAE | 7 | 18 July 2011 15:00 |
Configurations? | Worf | support.WinUAE | 12 | 02 March 2009 22:35 |
configurations | Unregistered | support.WinUAE | 3 | 29 August 2002 23:01 |
|
|