01-17-2011, 11:38 AM
01-17-2011, 01:08 PM
Almost got it. It's between 6156 and 6158. 3 possibilities.
Here are all of my notes, in one scrolling code box:
6158 is the first one that freezes up after loading state, and it's been doing it ever since. Consistently, I believe.
6156 Seems stable.
I could use this one, and just use the old wii remote when I need to target stuff on the screen, where the joystick and mouse / keyboard inputs both work at the same time. Then if I need to push the nunchuk forward, for like shield thrust, use the new, incomplete plugin.
Or else figure out a way to get a fully working new wii remote plugin to work with this version.
Quote:Changelog for r6158
- Fixed TimeBase and Decrementer registers so that they are updated only when needed
- Fixed RTC for GC homebrews
Changelog for r6157
Fixed some race conditions with PPC exceptions and external interrupts.
This may help fixing issues related to video interrupts handling.
Changelog for r6156
fix for my last commit
Changelog for r6155
some fixes for dlist, now is configurable in the video config section, still not in the gui,
disabled by default till a fix for segfaults in linux and geometry problems in some games
Here are all of my notes, in one scrolling code box:
Code:
6000 and 6119
can't emulate wii remote with both keyboard and joystic. kAnd it's messed up in other ways. It says it's incomplete.
saves and loads states in the same game, but not after you close the game and start a new one, at the beginning. It will load state after you get the game all started, from the game save file.
6201
Still remote says incomplete. Still a conflict. Can't use joystick and keyboard / mouse, at the same time. But you can tinker with your wii remote settings while you're playing.
Can not load state while in the same game.
Can not load state after starting a new game and getting into it.
6167
Loads state immediatly after save.
Then freezes up.
Can't load state on introduction screen of zelda. "ERROR: Trying to compile at 0. LR=802e823c"
Can load state once a new game is fully started.
But the wiiremote conflict makes it unplayable, after that load state.
6184
btw http://www.dolphin-emu.org/download.html?log=6184
http://www.dolphin-emu.org/download.html?ver=6184&arch=64
these kind of links work with all these versions...
Crashed when I tried to close the game window.
Can save and load state immediatly in game, but freezes up after leaving and coming back to game window.
Can load state after new game is fully started, but unplayable.
When state is loaded, and it's playable, it freezes up after about 10 seconds of playing.
Tried loading state on quest log screen, and got this crash error: "Unknown pointer address prefix 38, report this to devs: 0x38A00040
Continue?"
As if! lol
loaded states, but unplayable. But it didn't freeze. Saved and loaded again, still unplayable, froze after 10 seconds.
6191
Saves / loads state immediatly, but then freezes up after.
Loads state after fully starting a new game, but Link's still out of control, inspite of my attempts to fix the controller plugin. I suppose it would work on the old controller. Maybe I should try that.
Thought unplayable, it's not freezing up.
Won't even load state, at all with the old wii remote! What does this mean??? No error msg, just crash.
Now I try to save state in game, with old remote, then load it and crashes with this message:
"Unknown pointer address prefix 3E, report this to devs:
0x3E723F20
Continue?"
Switching back to new remote.
Tried to load state saved with old remote, and got this crash msg:
"ERROR: Trying to compile at 0. LR-00000000"
Will save and load state with new remote. But will freeze up after about 15 - 20 seconds. It doesn't crash. You can load state again and play again for another 15 seconds. And it's not unplayable.
Switches between states fine.
Loads after a full game restart, and once again, Link has a mind of his own...
6201
again...
Can save and load state immedatly, but freezes up.
Fully loaded a game, and it loaded state from last game, but unplayable. What did I do wrong? And it doesn't freeze up, just unplayable.
6224
saves and loads state, playable with new remote, then freezes up after 2 seconds.
it doesn't crash. You can load the same state again.
which I did, then froze up after about 90 seconds
switch to old remote
saved and loaded, but froze after 2 seconds
loaded same state again and moved around for about 10 seconds
loaded same state again and didn't move. froze after 2 seconds
loaded same state again and moved around for about 40 seconds. entered a new scene. Turned around to look at the same wall I just looked at, and then it froze and this message came up:
"Unknown pointer address prefix 38, report this to the devs:
0x3860000
Continue?"
Push either button and it crashes.
Maybe something isn't getting saved, having to do with the cache for remapping textures, or something like that.
As soon as I looked around to look at the same thing again, it froze up.
If you load the state, and keep moving forward, it won't freeze up for a long time. This time it froze up running toward a net I'm supposed to climb.
r6860
back to the future....
Saved and loaded state. worked. froze up after 2 seconds. didn't crash
loaded same state again, still playing after 60 seconds. Then it freezes up after about 90 seconds.
And I thought I was looking for the one that didn't load state at all. Could have saved some time.
Fully started the game, and loaded state, but now it's unplayable again!!!! Link ran in circles, and now he's beating his head agains the wall.
I know exactly how you feel, Link...
6119
again.
fully started new game, loads state from old game, but I get the "Communications with the Wii Remote have been interrupted." message.
But after that, you can keep loading state, and it keeps working.
6145
saved state and loaded
ran around a bit. tried to load same state, and crash.
Started new game, loaded state, and Link is out of control
OK. Started new game, and loaded state. Wii remote message.
No problem after that.
Got on Epona, hit her and saved state.
Loaded state from before, got the same wii remote message.
Loaded Epona state, no wii remote message, but it's unplayable.
Tried to save and switch states.. crash.
New game. Loaded all states with the wii remote message, except the one I saved before it crashed. Bad state I guess....
1st state loads with wii remote message
2nd state loads. no message, but epona is out of control.
3rd state load with message.
saved on 1st state while moving. but it loaded and worked fine with no message
loaded 2nd state. message. hook up the remote, and now it works.
I can't explain any of this.
6155
saved and loaded fine
played ok
tried to save and switch state, and crashed. I could have done that slower, i guess.
new game
1st state will load, but 2nd one wont.
Better change remotes.
crashed trying to load state from other remote. Not surpised.
Started new game. loaded good state, but unplayable.
I was on Epona
New game
Got on epona. saved state. got off . saved state. Can switch between states, and play fine.
saved again during combat. That state won't load, but the others will. All I get is music. no video. no sound effects if I slash or anything.
Tried again. same thing
Found a yellow rupee, and it made a big deal of it. Saved during that screen, and that state will load fine. Can switch between all 3 good states and it doesn't freeze.
Wait . default graphics was openGL. trying direct3d9, which used to be the default.
won't load state from other graphics plugin. Not surprised.
Saved and loaded.
New game . loaded 1st state, but out of control.
New game . saved and loaded states in the same game works fine.
Glad I didn't have to test all those again with a different graphics plugin.
So I guess I'm looking for the one that freezes up after loading.
6161
This one froze up after about 90 seconds. direct3d9
Did the same thing again. abot 90 seconds.
Switching graphics.
I just loaded the game. not a saved state. Now i can't control the guy. Pressing up makes him go down. Checked the settings. they are fine. Restarted, and now it works. Wierd.
save and load state, freezes up after 2-10 seconds. that's with openGL
6158
OpenGL freezes up after about 10 seconds
Direct3d9 . same
6157
saves and loads. hasn't froze up yet. But I get a crash that says "CompiledBlock - shouldn't be here!" when I tried to save the 3rd state and switch back to the 1st.
New game. Loaded state from other game. no message, link out of control on 2 states, 3rd one won't load, but it doesn't crash it. I can load the other ones.
New game.
Saved. tried to to load that state while coming out of a tunnel, and got this crash: "Unknown pointer address prefix 3E, report this to devs:
0x3EC7FEC0
Continue?"
As if continuing is really an option. I liked the more honest message that says: "Dolphin will likely hang or crash. Enjoy." lol.
New game. Want to know if it freezes up.
Saved and loaded right at the start, with a bunch of water. Hasn't froze yet.
saved 3 times. After came out of that tunnel, and was in the clear, I tried to go back to the first save, and got the same crash, but with "0x3E2BB020"
New game. I'll just avoid that tunnel.
Saved in the water again. Saved again on land. can switch between states np.
Been playing for a few minutes. It's not crashing.
Conclusion
6158 is the first one where it freezes after load state, and it's been doing it ever since.
6156
Seems pretty stable...6158 is the first one that freezes up after loading state, and it's been doing it ever since. Consistently, I believe.
6156 Seems stable.
I could use this one, and just use the old wii remote when I need to target stuff on the screen, where the joystick and mouse / keyboard inputs both work at the same time. Then if I need to push the nunchuk forward, for like shield thrust, use the new, incomplete plugin.
Or else figure out a way to get a fully working new wii remote plugin to work with this version.
01-17-2011, 04:05 PM
(01-17-2011, 11:13 AM)NaturalViolence Wrote: [ -> ]Why would a save sate need to capture the state of the audio backend, gui, wiimote/input, or dsp threads? I would think the only two needed would be cpu and video.
I dunno how to explain it. It just does. Have you noticed how many games error out with a "disconnected wiimote" message after a save state is loaded? That's because the wiimote thread is out of sync.
01-17-2011, 04:26 PM
Metroid Prime in GC saves and loads states fine, so far, in r6868
01-18-2011, 02:18 PM
You'll eventually run into problems trust me.
Please try and figure out whether 6157 or 6158 caused it.
Please try and figure out whether 6157 or 6158 caused it.
01-18-2011, 04:44 PM
(01-17-2011, 04:05 PM)skid Wrote: [ -> ](01-17-2011, 11:13 AM)NaturalViolence Wrote: [ -> ]Why would a save sate need to capture the state of the audio backend, gui, wiimote/input, or dsp threads? I would think the only two needed would be cpu and video.
I dunno how to explain it. It just does. Have you noticed how many games error out with a "disconnected wiimote" message after a save state is loaded? That's because the wiimote thread is out of sync.
because timing is everything.
01-18-2011, 08:00 PM
6158 is the first one that freezes up after load state.
6157 did not freeze up.
I posted the changelogs.
6157 did not freeze up.
I posted the changelogs.
01-19-2011, 07:37 AM
Thank you. Now we just need some others to confirm it and the devs will probably revert the changes.
01-19-2011, 03:54 PM
Quote:the devs will probably revert the changes.
no they won't.
SaveState is secondary as a function. If it breaks; tough shit until it gets fixed.
01-19-2011, 06:15 PM
(01-18-2011, 08:00 PM)hypnotoad Wrote: [ -> ]6158 is the first one that freezes up after load state.
6157 did not freeze up.
I posted the changelogs.
Good job in tracking down the revision where the save states went downhill.
I've made a change in r6880 that should fix this - I did not find any other bugs in r6158. Let me know if r6880 works or not.