Guys I come from the DidyKnogRacist communite, and you are all wrong, tihs is the run of the mileniun and everyone who says otherwise dosnt know any bater! I found this run vary ease to masturbate too!!!! Don't fuck with me, I know this game so that mean I'm always right!StupedfackincommunityTASVideoz!!!!!!
Arc wrote:
I enjoyed this movie in which hands firmly gripping a shaft lead to balls deep in multiple holes.
natt wrote:
I don't want to get involved in this discussion, but as a point of fact C# is literally the first goddamn thing on that fucking page you linked did you even fucking read it
Cooljay wrote:
Mayor Haggar and Cody are such nice people for the community. Metro City's hospitals reached an all time new record of incoming patients due to their great efforts :P
it gives an error every time you load a state (turn off panic handlers)
What error are you getting, by the way, and in which game? I'm not seeing this in WW, at least when loading savestates made in the same version.
If you're seeing an error that says "Warning: You loaded a save whose movie mismatches", don't ignore that, it means you loaded a savestate incorrectly and it's trying to warn you about the desync that's going to cause if you don't fix it.
it gives an error every time you load a state (turn off panic handlers)
What error are you getting, by the way, and in which game? I'm not seeing this in WW, at least when loading savestates made in the same version.
If you're seeing an error that says "Warning: You loaded a save whose movie mismatches", don't ignore that, it means you loaded a savestate incorrectly and it's trying to warn you about the desync that's going to cause if you don't fix it.
It's fixed in 235. I believe the error was something like that, but it was a lie, and synced fine regardless of errors (which occurred every single time a state was loaded for me, in muramasa)
edit: actually it's not fixed, just got it in 235.
edit: actually it's not fixed, just got it in 235.
What's the actual error message (and are you seeing it even when loading saves that were created in 235)? If it's the same one I mentioned, it might be your fault for loading savestates incorrectly. Here is an example of what I mean (these steps should cause the error message if you follow them):
start or continue recording a movie
save state 1
run the game for a little while, pressing some buttons in the game
save state 2
load state 1 (not in read-only mode. still recording.)
run the game for a little while again but this time don't press the same buttons
also, run the game a bit longer than you did last time
switch to read-only mode
load state 2 <— brings up error message because you're not supposed to do it
This is a sequence of events you should avoid doing while actually TASing. This goes for other re-recording emulators as well. The warning that pops up is to make sure you don't accidentally do it without realizing it.
EDIT: I just noticed your posts in the other thread which give more details. I think there's an actual bug happening, though it could be several different things (for example, my error check code might be detecting the result of a bug in the DTM saving or loading code). In any case, I think the steps I posted above of "what not to do" could be informative for someone, even if that's not what you're doing in this case.
The error message was exactly what you stated, and included which byte the files differed at. I've also never attempted to load a save state from a previous version (except once, and when it crashed dolphin, i assumed it would never work).
It was happening every single time i loaded a save state in 234 (including if i saved a state, then immediately loaded it, regardless of whether read only was on or off). In 235, now it looks like it just happens if i load a save state after the current frame, such as:
1. start recording
2. save state 1
3. stop recording
4. play back recording with read only
5. load state 1 before reaching it.
I have definitely never done anything of the sort that would actually cause a desync.
Ok, i've got a problem in 235 that is completely breaking my movies. A new header is being randomly made in the middle of my .dtm files, causing a desync. Deleting the extra header does not make it sync. I have no idea what causes it. I uploaded a .dtm with an example of it, in case it's useful to anyone in figuring it out.
http://www.mediafire.com/?t5fvo2i42pugg6s
edit: Entire first 0x1000 bytes are duplicated. Deleting that however still does not make it sync.
Ok, i've got a problem in 235 that is completely breaking my movies. A new header is being randomly made in the middle of my .dtm files, causing a desync. Deleting the extra header does not make it sync. I have no idea what causes it. I uploaded a .dtm with an example of it, in case it's useful to anyone in figuring it out.
http://www.mediafire.com/?t5fvo2i42pugg6s
edit: Entire first 0x1000 bytes are duplicated. Deleting that however still does not make it sync.
I noticed this error, but not on dtms I record. If I go to the "savestates" folder the dtms there have the extra headers.
It appears to be caused by loading a save state in read only mode. So it seems like the problem should always fix itself, when you then save over the save stated you used. The only time it should actually cause a problem is if you playback a movie, load a state, then continue recording without reloading a save state from before you last closed dolphin.
Maybe it's fixed (as of 3.0-276)? I saw it before too, but I can't get the byte 0x1000 bug to happen anymore, nor do I see the error message appear (I think it was appearing because it was correctly detecting the junk at 0x1000 as a potential source of desync). It might have been caused by memory corruption in unrelated savestate code (which I hopefully fixed). But let me know if you find any steps that still make it happen.
By the way, I really don't recommend anyone to turn off panic handlers. If you do turn them off, you should be extra careful and periodically check your movie from the beginning for desyncs (a little more than usual, I mean), because there won't be any warning if something goes wrong.
I don't think 267 had my changes. Try 3.0-291. Note that builds I create might run slower than builds someone else makes of the same revision, and I don't have a 64-bit version.
Yeah, i saw that last night, it works great. And thanks for all the recent fixes.
CoolKirby wrote:
Why are the new Dolphin releases on EmuCR and not the Dolphin-Emulator Download page?
EmuCR appears to be a third party site that just compiles every new version of various emulators. Not sure why team dolphin doesn't always post the newest revisions.
Can't turn on read only while a game is paused, in 291 =x
Try going to Options > Hotkey Settings and setting a hotkey for "Read-only mode". Then you can press it when the game window is active to toggle read-only. That should always work even when emulation is paused.
Can't turn on read only while a game is paused, in 291 =x
Try going to Options > Hotkey Settings and setting a hotkey for "Read-only mode". Then you can press it when the game window is active to toggle read-only. That should always work even when emulation is paused.
Can't turn on read only while a game is paused, in 291 =x
Try going to Options > Hotkey Settings and setting a hotkey for "Read-only mode". Then you can press it when the game window is active to toggle read-only. That should always work even when emulation is paused.
Try going to Options > Hotkey Settings and setting a hotkey for "Read-only mode". Then you can press it when the game window is active to toggle read-only. That should always work even when emulation is paused.
It doesn't.
But the hotkey works when emulation isn't paused? Does the window title change when you press it or not?
