search

divyang4481 / bizhawk

Automatically exported from code.google.com/p/bizhawk
0 stars 0 forks source link

Unable to load savestates following movie playback #213

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Record a SNES movie in Compatibility mode
2.Playback the movie, stop playback and then save state
3.Reboot Bizhawk and attempt to load savestate

What is the expected output? What do you see instead?
Expect state to load normally, instead get "System.InvalidOperationException:  
You've attempted to load a savestate made using a different SNES profile than 
your current configuration.  We COULD automatically switch for you, but we 
haven't done that yet.  This error is to make sure you know that this isn't 
going to work right now."

What version of the product are you using? On what operating system?
Bizhawk 1.7.2

Please provide any additional information below.
Encountered after selecting "Tool-assisted Speedruns" as as a SNES profile.

Original issue reported on code.google.com by khazw...@gmail.com on 20 Jul 2014 at 10:22

GoogleCodeExporter commented 9 years ago 
Sounds like you didn't reboot the core after setting your profile.  Did you not 
notice the icon in the status bar?

I'm betting if you open the emulator again, now that everything is set, you 
will not be able to reproducet his.

Original comment by adeli...@tasvideos.org on 21 Jul 2014 at 12:50

GoogleCodeExporter commented 9 years ago 
I did reboot the core.  I also tested it twice before submitting the bug report 
and again just now.

Precise steps I just followed:
-Launch bizhawk, preset to compatibility mode and TAS profile
-Open rom:  Dragon View (U)
-Record movie from Power-on
-Record about 1500 frames of input.  Save and stop movie.
-Close and re-open Bizhawk
-Open rom, Play movie I just recorded.
-Playback a while then Stop movie.  Save a state sometime after stopping.
-Close and reopen Bizhawk
-Open rom and attempt to load state.

I have not been able to follow these steps without encountering the error and a 
subsequent crash.

Original comment by khazw...@gmail.com on 21 Jul 2014 at 1:00