Resolved: Abnormal Speed/fps seen with latest Dev Builds

[Melchior]

I am using the latest Dev builds
v1.5.0-dev-1088-g0477e03  [Jonathan L]   2016-08-05 01:04:39
 


I have seen an abnormal Speedup of 200% and 120 fps.
The last build I was using is v1.5.0-1065, and it was over speed too...
While I normally have the safe speed hacks on, I tried with them disabled and found it was still over speeding...

my test case is Final Fantasy 12 (I load a save state to find it over speeding,  the initial Video animation that plays when the DvD image is loaded plays at the normal 100% Speed and 60 fps)

I tried loading the in-game save method instead of the save state and found it played at the normal frame-rate 100%/60fps
I overwrote my savestate with a fresh one and loaded it after to find it playing normally...
so I guess this bug report is invalid or can be closed...

   

what ever else is needed for this bug report let me know  and I will update this post with it.


My system Specs are in my Signature below:

[vsub]

I read your post 3 times but I couldn't understand what's wrong
The percentage never stay solid at 100/200% all the time and that's normal.Accidentally pressing Tab will switch to Turbo mode.
Encountering problems whole loading save states created but different version are to be expected

Or you mean that when you set it to 200%(which is set by default),it always runs at little above 120fps

[Melchior]

I noted the speed issue after loading a save state.... it seems to fine now that I did a fresh savestate...

[ssakash]

This is a recent issue due to the change on counters code. The NTSC double speed issue should be resolved by #1491 so moving this to resolved.

However there still might be some speed related problems when loading an older save state on a newer version of PCSX2. To resolve such issues, avoid using any older save states (or) wait for any future SYSCALL events of SetGsCrt()

For further information, feel free to look at the linked pull requests

---

Thank you for your report.
This bug report has now been marked as Resolved since it has been fixed on our code base.

This thread will now be closed and moved to the resolved bug reports subforum.