If Utawarerumono is running too fast

Posted in

#1 by hko2006
2014-07-06 at 19:05
< report >Utawarerumono runs extremely fast with computers with multiple core CPU. Too fast that you can't see the damage and combo.

I found that Cheat Engine can be used to slow down the game.

1. Launch the game and Cheat Engine.
2. Click on the Select Process button at the top-left
3. Select the game, click Open.
4. Check the Enable Speedhack option on the right.
5. Change the Speed from 1.0 to 0.5 and click apply.
6. Play at normal speed!
#2 by dk382
2014-07-06 at 20:43
< report >If multicore processors are the problem, it may also be possible to fix this by starting up the game, opening Windows' task manager, right clicking the game process in the list, selecting Set Affinity, and assigning it only one core.Last modified on 2014-07-06 at 20:44
#3 by shokatsu
2014-07-06 at 21:09
< report >I remember this, my game was running fine but sometimes during combos the game would randomly speed up and entirely screw up my timing, this made the game much harder than it had to be.

Still greatly enjoyed it though.
#4 by pendelhaven
2014-07-07 at 10:02
< report >iirc this only happens on AMD 5200+ processors and similar (AM2 series iirc). should work fine in win7, but if you're in winXP, AMD has a fix in their site.

Didn't play Utawarerumono on Intel socket 775 series. can't say for sure.
#5 by mrducky
2016-02-22 at 07:54
< report >#2
Battles are too fast despite affinity change, but CE works.
#6 by alexff37
2016-02-23 at 21:53
< report >Just turn on vsync in videocard options.

Or use RivaTuner Statistics Server you can cap game fps without turning vsync on (vsync may delay input)Last modified on 2016-02-23 at 21:59
#7 by gimble-a
2021-01-10 at 18:14
< report >Setting VSync, capping max frames in Nvidia Control Panel, changing processor affinity didn't work for me (new ryzen).

I didn't want to grab Cheat Engine so ended up using Battle Encoder Shirase to slow the process. Great results with 60% limit / 25ms wake cycle.


You must be logged in to reply to this thread.