- --
Viewing Issue Advanced Details
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
04261 | Save/Restore | Major | Always | Feb 26, 2011, 15:04 | Feb 26, 2011, 17:09 |
Tester | moa | View Status | Public | Platform | MAME (Unofficial Binary) |
Assigned To | Resolution | Invalid report | OS | Windows Vista/7 (64-bit) | |
Status [?] | Closed | Driver | |||
Version | 0.141u2 | Fixed in Version | Build | 64-bit | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 04261: save state don't restore CPU clock correctly using cheat | ||||
Description |
Hello. I've noticed that If you overlclock CPU of ddragon (using cheat) and then save state when you restore the save, the game is as slow as default CPU clock despite the sliders control tab says it's overclocked Tested on ddragon for easy check but I suspect it concerns all drivers Of course my Pc spec are fast enough to run it overclocked save state added Thank you |
||||
Steps To Reproduce |
- run ddragon with cheats enabled -press TAB and go to sliders controls, overclock to 200% main and sub CPU (yes this game is slow) - Check the attract mode when lots of sprites running (ffw with DEL) - reset with F3 & save state - Quit the game - Relaunch game - Load save state - Check the attract mode when lots of sprites running (ffw with DEL) |
||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | |||||
Attached Files
|
1.zip (29,038 bytes) Feb 26, 2011, 15:05 Uploaded by moa | ||||
Relationships
There are no relationship linked to this issue. |
Notes
2
No.07264
Tafoid Administrator
Feb 26, 2011, 16:14
|
Save States, as far as I'm aware, were never designed to save those options. They save the game data, not the preset clock speeds which should be stable. This sounds more like a feature request than an bug in save states. |
---|---|
No.07265
Fujix Administrator
Feb 26, 2011, 17:09
|
As Tafoid says, this is regarded as a feature request. It could cause a stability issue by restoring optional clock values from a cfg file, but I'm not sure. |