26 July 2005, 14:39 | #1 |
Registered User
Join Date: Aug 2002
Location: The Hague/Netherlands
Posts: 15
|
Fastest possible but maintain chipset timings
The speed option "Fastest possible but maintain chipset timings" works perfectly with JIT enabled, but doesn't seem to work with any other CPU option.
If I choose any cpu without JIT, this option gives exact the same speed as the A500 option. I checked this with the Sysspeed utility. The emulated system also 'feels' like A500 speed. Another indicator is the fact that WinUAE doesn't use all CPU power in even CPU intensive applications / non system games. The percentage stays at 75 for example. Could this be a bug, or am I doing something wrong? |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Fastest Amiga Games | Djay | Nostalgia & memories | 73 | 09 June 2016 21:42 |
Floppy drive timings and NTSC floppy unreliability | mark_k | support.WinUAE | 6 | 02 February 2013 22:03 |
V-Sync problems with Fastest possible, but maintain chipset timing. | cobhc | support.WinUAE | 2 | 28 March 2009 12:14 |
Fastest TCP/IP software | Smiley | support.Hardware | 7 | 14 March 2005 18:26 |
CPU emulation and timings....... | Bloodwych | support.WinUAE | 1 | 04 August 2003 16:00 |
|
|