Emulator Issues #8316
closedDisable changing Emulated CPU Clock Override in Netplay
0%
Description
Over the past 24 hours, I've realized that I shouldn't have trusted users to use this feature correctly.
Updated by JosJuice over 9 years ago
Why? If it's about desyncs happening, the setting could just be synced. Or do we not want users to be able to force a clock override on other users? In that case, the clock override could be disabled unless all users set it to the same value, so that there still is some way to use it if everyone actually wants to.
Updated by JMC4789 over 9 years ago
Sure, but I didn't know if anyone would want to go through that much trouble. That's obviously a good idea, but I just wanted to make sure people couldn't cause desyncs with it.
Updated by JosJuice over 9 years ago
- Status changed from New to Accepted
- Milestone set to Current
- Relates to usability set to Yes
- Category set to netplay
Updated by JMC4789 over 9 years ago
Here I was assuming people would think it was too much work to sync it properly.
Updated by JosJuice over 9 years ago
I would still consider the issue fixed if it just is disabled. After all, everything is in sync if the setting always is set to the same value :P
Netplay already syncs some settings, right? I don't know exactly what the code is like, but it shouldn't be too hard to add another setting then. The last suggestion I had is more complex, but that's not really necessary.
Updated by JMC4789 over 9 years ago
The problem is that you can change this setting as the game runs. On/Off being synced would be really easy and nice. Even just a synchronization at startup would be better than current. Problem is, you can turn it on during netplay and people don't realize "Hey, this could cause a desync."
Updated by rukariosake over 9 years ago
#7 could be something to do for issue 8315.
Updated by JMC4789 over 9 years ago
It's already synced apparently. Never noticed.
Updated by JMC4789 over 9 years ago
- Milestone deleted (
Current)
Because it's synced at startup at least, the only time this would be a problem is if users were actually actively trying to mess things up or even more inept than usual.