-
Notifications
You must be signed in to change notification settings - Fork 414
Octoshock [PS1] movies require a cycle count for timing. #1878
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Oh right this was technically resolved... in a different younger tracker. |
Looks like it's not resolved completely because there's discrepancy between values reported by mednafen and beetle on one side and bizhawk on the other.
Since games can switch between 240p and 480i as they please, we can't use any constant fps value to determine the correct movie length once and for all. Then we have the core changing its fps on the fly, but that is resolved by audio sync in dumping, isn't it? |
Nymashock implements ICycleTiming and reports a cycle count and clock rate accordingly. |
Soft closing mainly due to the eventual, real existing dropping of Octoshock. |
This is something I've been talking recently with @vadosnaprimer about this due to how there could be a change on how we handle dumping the core.
The times are vastly different when AVISync is in play or not for an NTSC game, a simple calculation of just using the framerate into amount of frames isn't cutting it anymore and apparently using cycle timing would correct the issues we're facing.
Some information that I found on cycle counts was over at ngemu.
The text was updated successfully, but these errors were encountered: