Whdload games to fast

[elessar84]

Hi. I am having trouble getting the correct speed when playing on my WHDLoad setup. I copied uae configuration and added two lines in whdload according to this tutorial, but the speed of the games is still a bit too fast. https://eab.abime.net/showthread.php?t=49744
executestartup=uae-configuration cachesize 0 cycle_exact true
executecleanup=uae configuration cachesize 8192 cycle_exact false
It only helps to exit to the emulator menu and disable the options cycle-exact (full). However, after loading the next game, this method must be repeated. My question: is there any command or way to prevent cycle-exact full from starting when the game starts?
Winuae latest beta
Whdload 18.6 OS 3.9
default amiga 4000 setings with zorro 3

[jotd]

you can use pre-start and post-quit options of whdload to set cycle exact or disable it using uae-config command.

Personally I try to fix games which are too fast (submit an issue to mantis.whdload.de for each game in that case), but I have such a setting to disable/enable JIT which is just too much for most games.

for cycle exact Retronerd gives the solution https://eab.abime.net/showpost.php?p=627878&postcount=3

[elessar84]

Thanks for the advice, however these two options only cause a winuae crash
ExecuteStartup = uae-configuration blitter_cycle_exact true
ExecuteCleanup = uae-configuration blitter_cycle_exact false

[Aardvark]

blitter_cycle_exact doesn't seem to do anything anymore, just use cycle_exact.

Where exactly you added these lines? If they are in WHDLoad-Startup and WHDLoad-Cleanup scripts, then exclude "ExecuteStartup/Cleanup = " part.

[elessar84]

At the end, in the whdload.prefs file.

[hexaae]

Every single game requires it's own settings unfortunately, even though most of them should work fine with these simple tooltypes in the WHDLoad game icon:
EXECUTESTARTUP=
EXECUTEPOSTDISK=uae-configuration cachesize 0 cpu_speed real cycle_exact true

Executepostdisk has the advantage to run the script/command after HD loading, right before the game starts.

[elessar84]

You're right, I tested a few games and had no problem with them. However, there are also a few that work badly on fast winuae configurations, such as Barbarian by Palace (to fast), Operation Wolf starts only once after adding the ExpChip command in the game icon, without it does not turn on at all (flashing screen). Heimdall 2 (my favorite Amiga 1200 game) displays some graphic artifacts on the map for selecting a location. It only helps to disable the cycle_exact (full) emulator configuration.

[Mixon]

Hi!

Babarian (Palace) will good works with it:

ExecuteStartup=UAE-Configuration Cachesize 0 cpu_speed real cycle_exact true cpu_multiplier 1

Mike

[Retro-Nerd]

Barbarian (Palace) runs too fast on my real A1200. Created a bug report some years ago on mantis.


http://mantis.whdload.de/view.php?id=2976

[elessar84]

@Mixon I tried on two systems: Os3.9 (A4000 setup) and BetterWorkbench (A1200 setup) and the command cpu_multiplier 1 exits winuae without any error.
I am using winuae 4.9, and whdload 18.7

[Mixon]

Crash when I start it from iGame but works when I starts it from icon.


Works on OS39 A1200 latest WinUAE for me.


With 68020 CPU good, but with 68040 or 68060 fast.

[Mixon]

This game is very sensitive for timing
You can also try on A4000 (68040/68060 cpu) emulations this:

ExecuteStartup=UAE-Configuration cachesize 0 CPU_Speed real CPU_Multiplier 1 CPU_Throttle -900.0
ExecuteCleanup=UAE-Configuration CPU_Speed max Cachesize 8192 CPU_Multiplier 4 CPU_Throttle 0

It’s also works for me.

[hexaae]

Just a hint:
use
EXECUTESTARTUP=
EXECUTEPOSTDISK=....

It is better than ExecuteStartup because changes will be applied only right before WHDLoad launching the game, instead of slowing down WB immediately 'till the game loads and gets launched... (yes, ExecuteStartup= left empty is required).

[stainy]

Originally Posted by hexaae

Just a hint:
use
EXECUTESTARTUP=
EXECUTEPOSTDISK=....

It is better than ExecuteStartup because changes will be applied only right before WHDLoad launching the game, instead of slowing down WB immediately 'till the game loads and gets launched... (yes, ExecuteStartup= left empty is required).

ok and would you just do a ExecuteCleanup line after those two? to bring everything back to how it was?
I have a global startup and cleanup in .prefs. I guess per game overrides that?

[elessar84]

Originally Posted by Mixon

This game is very sensitive for timing
You can also try on A4000 (68040/68060 cpu) emulations this:

ExecuteStartup=UAE-Configuration cachesize 0 CPU_Speed real CPU_Multiplier 1 CPU_Throttle -900.0
ExecuteCleanup=UAE-Configuration CPU_Speed max Cachesize 8192 CPU_Multiplier 4 CPU_Throttle 0

It’s also works for me.

Thanks to these settings, the game finally started to run much slower. I hope an official fix will come out someday to fix the speed of this game. I have one more question: is it possible to change the processor type, e.g. from 68040 to 68020, using the whdload command? I tried to enter cpu_model 68020 in ExecuteStartup = uae-configuration however, it either causes a system crash or a reset.

[Mixon]

You can't change CPU on working computer
It's will crash.



The simple and best solution:


Make 2 cycle-exact/no jit configuration with max compatibility:



One A600 (WB 2.0 or 2.1) config for old games (like Barbarian), and

One A1200 (WB 3.0 or 3.1) config for AGA fames.


You don't need UAE-Configuration, OS39, BestWB, etc...


Clean workbenches, only WHDLoad and TinyLauncher (with automatic start).


It's all.

[hexaae]

Originally Posted by stainy

ok and would you just do a ExecuteCleanup line after those two? to bring everything back to how it was?
I have a global startup and cleanup in .prefs. I guess per game overrides that?

General cleanup will be used (I use a script where I reset all WinUAE emu settings when exiting to WB from WHDLoad games), unless you specify a ExectueCleanup=...
In S:WHDLoad.prefs:
ExecuteCleanup=S:WHDLoad_Cleanup_script ;command to execute on WHDLoad exit

[Mixon]

I play Apydia on latest stable WinUAE with this:
ExecuteStartup=UAE-Configuration joyport1autofire normal

...but autofire not works.

Press F12 for go to the menu, and I see the autofire option is enabled.

I do nothing, just press cancel for go back to the emulation, and now the autofire works

Any idea?

[elessar84]

@Mixon I just like having everything in one place. Using uae-configuration commands I was able to fix almost all problems with games that did not want to work properly. Only Operation Wolf does not want to run on os 3.9. No matter what I set, I have a black screen and white stripes.

[Mixon]

not in 100% because some parts can't change when emulation is running (cpu, chipset, etc) and some games will not perfect (like barbarian)


now i can't enable the autofire with uae-configuration. try this please.