Topic by Noxxa

Posted: 2/8/2011 8:05 PM

Quote

Noxxa

They/Them

Moderator, Expert player (4139)

Joined: 8/14/2009
Posts: 4083
Location: The Netherlands

I think Wii input recording isn't done yet on Dolphin, so you're unable to rewatch non-replay runs yet.

http://www.youtube.com/Noxxa <dwangoAC> This is a TAS (...). Not suitable for all audiences. May cause undesirable side-effects. May contain emulator abuse. Emulator may be abusive. This product contains glitches known to the state of California to cause egg defects. <Masterjun> I'm just a guy arranging bits in a sequence which could potentially amuse other people looking at these bits <adelikat> In Oregon Trail, I sacrificed my own family to save time. In Star trek, I killed helpless comrades in escape pods to save time. Here, I kill my allies to save time. I think I need help.

Posted: 2/12/2011 8:48 AM

Quote

sgrunt

He/Him

Emulator Coder, Former player

Joined: 10/28/2007
Posts: 1360
Location: The dark horror in the back of your mind

Mothrayas wrote:

I think Wii input recording isn't done yet on Dolphin

It's implemented now!

Posted: 2/12/2011 9:49 AM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

Not quite :/ Unless I'm doing something wrong. The feature is there (and it even counts frames now) but it only works for Game Cube games. After recording and saving my inputs, it will never play them back for the Wii. Choosing "Play Recording" from the menu and selecting my .dtm only has the same effect as rebooting the .iso normally. Nothing plays back and it only accepts new input. Gamecube games work fine on the other hand. This was on Dolphin r7128.

Posted: 2/12/2011 9:50 AM

Quote

sonicpacker

Active player (420)

Joined: 9/21/2009
Posts: 1047
Location: California

You need the newest rev. But the Dolphin site's compiler is down at the moment. So you either have to compile it yourself, or wait a bit longer.

https://personalitygrowth.com/entp-myths-stereotypes-misconceptions-cliches-and-tropes-that-are-inaccurate/

Posted: 2/12/2011 10:38 AM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

sonicpacker wrote:

You need the newest rev. But the Dolphin site's compiler is down at the moment. So you either have to compile it yourself, or wait a bit longer.

Newer than r7128? Yeah I guess I'll just have to anxiously wait for the compiler

Posted: 2/13/2011 12:20 AM

Quote

sgrunt

He/Him

Emulator Coder, Former player

Joined: 10/28/2007
Posts: 1360
Location: The dark horror in the back of your mind

See e.g. here for a recent build (keep an eye on the forums there).

Posted: 2/15/2011 10:32 PM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

So is anyone else still having problems recording? Revision 7128 and less wouldn't record any Wii inputs, and everything after r7150 that I've tried just freezes. I'm now using r7177 and it still freezes when I try to play a recording. Has anyone successfully recorded and played back a Wii game?

Posted: 2/15/2011 10:34 PM

Quote

sgrunt

He/Him

Emulator Coder, Former player

Joined: 10/28/2007
Posts: 1360
Location: The dark horror in the back of your mind

I have. Make sure you disable GameCube controllers if you're trying to record input for Wii (the two don't play nice at this point in time).

Posted: 2/15/2011 11:10 PM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

Thank you. This nugget of information solved my problem. Now to commence speedrunning! :D

Posted: 2/22/2011 12:04 PM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

As of r7209, I can get my recorded Mega Man 10 .dtm's to playback, and everything is dandy... until I load a save state. After the frame I loaded my state, my inputs are out of sync and the end result is Mega Man running, jumping, and shooting haphazardly. Also, another possibly related issue I'm having is after loading a state, it takes about 3 in-game frames before Mega Man will obey my inputted commands. In fact, come to think of it, it ALWAYS takes about 3 frames to register my inputs. I've just adapted to that and account for it by entering commands 3 frames early. However, on the stable r7060 that I've been using, the saved states include the previously entered commands, so I can still pick up where I left off seamlessly. These new revisions do not carry over the previously entered commands into save states, so every loaded state begins with a few frames with my character idling. So to sum it up, my recorded .dtm's are out of sync, and my commands are registered a few frames after I input them. Does anyone have settings for a revision that does not have these two problems?

Posted: 2/22/2011 4:56 PM

Quote

sgrunt

He/Him

Emulator Coder, Former player

Joined: 10/28/2007
Posts: 1360
Location: The dark horror in the back of your mind

Make sure you turn off "Reconnect Wiimote on Load State". It causes exactly the problem you describe.

Posted: 2/22/2011 11:12 PM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

Wow, once again thank you! After that fix, and few more tinkerings, I am now able to re-record and playback on r7228. I had to disable dual core and idle skipping, and use LLE audio with audio output disabled. This obviously slows the game down, but it doesn't matter since I'm playing frame by frame. But every now and then the playback STILL becomes desynced. I'm not quite sure what specific event is causing it. I know using Last State caused some of the desyncs, so I stop using that feature. But sometimes I can go for 1000+ frames without a desync, and sometimes it's less than 100. Right now, just to be safe, I save the movie every so often and play it back, just to make sure it synced right. Usually its not synced somewhere down the line, so I save a state a little before the desync and continue recording. This is ok for now, while I'm still on the first level. But later on I'll have to sit through 20 minutes of video just to see if the last 20 seconds of input has synced properly. And if it does that Wii controller disconnect thing where Mega Man ignores all commands and just keep running, I have to stop, playback, and start from a save state again. Is this just where the Dolphin is at right now, or do you have another magical fix for me, sgrunt? :D

Posted: 2/23/2011 1:38 AM

Quote

Toad_King

Joined: 3/20/2009
Posts: 87

It seems that syncing with Wiimotes is still causing some problems on my end, even without using savestates. Since I never got to test Wiimote recording fully, I wasn't sure if they played back right, but now it seems it's not the case. Do you still have sync issues on Gamecube games?

Posted: 2/23/2011 1:39 AM

Quote

sgrunt

He/Him

Emulator Coder, Former player

Joined: 10/28/2007
Posts: 1360
Location: The dark horror in the back of your mind

diggidoyo, you're basically describing my current experience with Wii rerecording at this point. If that changes in the future, I'll let you know.

Posted: 4/28/2011 9:57 AM

Quote

DDRKhat

Player (36)

Joined: 9/9/2006
Posts: 388

Bump. I've hit a brick wall and cannot progress. My dolphin refuses to save new input into my input file and so I cannot get any further, I went back to further optimize a earlier screen and now I can't progress at all regardless of how far I rewind and try to record from. So sorry folks but it could be quite a while before I even manage to get to Tornado Man and beat him because of this issue and real life issues.

A whisper in the wind~~

Posted: 4/28/2011 9:58 AM

Quote

NrgSpoon

Joined: 6/14/2004
Posts: 646

Uh... you didn't accidentally make the movie file read-only or anything like that?

I like my "thank you"s in monetary form.

Posted: 4/28/2011 10:04 AM

Quote

DDRKhat

Player (36)

Joined: 9/9/2006
Posts: 388

NrgSpoon wrote:

Uh... you didn't accidentally make the movie file read-only or anything like that?

I've not done anything quite so daft, no. I and Administrator have FULL write access to the movie file, I've tried running dolphin as non-admin/admin. I tried doing my new input and saving it into a new file and recently tried (in pure abandon hope) that a copy-pasta would (somehow?!) fix it. The odd thing is that I didn't change ANYTHING to do with the file prior to it become "locked up", I didn't change it's location permissions or anything. Possibly related; As of recent it seems that DOWN or RIGHT and my "frame advance" button (B) seems to kill hotkeys, I can manually frame advance pressing the pause button but otherwise it just is completely unresponsive.

A whisper in the wind~~

Posted: 4/28/2011 3:21 PM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

I've had this exact same problem several times so far. The way I've been fixing it is to play back the input file, save a state way before the affected part, and continue recording from there. I know you mentioned you tried this, but when I say way back, I mean a lot further than usual. I'm not quite sure what's causing it, but I've always been able to somehow overcome it. As a matter of fact, I'm actually having this problem right now. I'll do what I usually do and see if I can pinpoint exactly what fixes the problem. Not sure about the other problem you mentioned. I'm using r7302 so I can't configure hotkeys. ~~~ Well, you're not gonna like my answer, but I ended up having to go back about 5000 frames before I was able to continue recording. I still have no clue as to what causes the problem. For some reason, the old inputs (the ones we are replaying) are being copied into the new export. Only fix for now is to get trying earlier and earlier save points until the problem dissapears.

Posted: 4/30/2011 8:14 AM

Quote

DDRKhat

Player (36)

Joined: 9/9/2006
Posts: 388

The hotkey issue is becoming prodominantly the problem, I am simply unable to do do anything because it's so awkward to press the PAUSE button with my mouse whilst trying to hold down the inputs. I've got no clue what is causing this, I might see if I can configure my PS2 pad to get around the issue.. As for not liking the answer your right, 5000 frames of input sets me ages back... Sigh. The info is helpful however, I'll try going back 5000 frames (I found a few optimizations I could have done ANYWAY so it gives me an excuse I suppose...) Edit: Tried going back over 5000 frames, nothing. Also during the whole attempt I found those optimizations weren't possible, I can't squeeze the 5 frames I need to make the jump to the platform (prior to the 2 sidewards moving bots in the area you suggested) I even tried hitbox exploiting (hitting an enemy seems to shrink it's hitbox) but unfortunately im already half-in those bots by the time I can land the shot through it's shield so I just can't get to full height without the cost of frames. I suppose I'm stuck waiting for a update to Dolphin to be able to continue or restart and I really don't fancy restarting without good reason. the small plus-side in this is I've found the source of the hotkey issue. Pressing the keyboard RIGHT or DOWN arrows seems to nuke hotkeys, they become completely unresponsive, it's associated to those keys in general and not just something in configuration because changing the D-pad's keys to anything else allows me to continue without any issues. This did however give me an excellent excuse to wire up my PS2 pad.

A whisper in the wind~~

Posted: 4/30/2011 10:16 AM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

Ah, now I see what you mean by the hotkey issue. Glad you found the fix, because I did the same thing. I don't think the keyboard can register more than 2 or 3 keypresses at the same time into the emulator. I configured my xbox controller. Also, I'd like to recommend a program called xpadder. It's only 10 bucks, and has been an enormous help in my emulation process. Basically, it allows you to program keyboard functions (F1, Shift F1, F10) etc, into the controller. There may be some free programs that let you do this, but xpadder has got to be the best tool for the job because of its layout and features. Since the MM9 and 10 only use about half of the buttons available, I put the pause button and several save/load state hotkeys on the controller. You can imagine how this speeds things up. Hmm, and you're right about the 5000 frames not working. I thought it did because it showed a different input, but when I tried to record further, it reverted back to the old inputs. I'll keep trying. I know there's a fix because I've done it before. I'll also post a thread on the Dolphin support forums.

Posted: 4/30/2011 12:05 PM

Quote

kuja_killer

Player (48)

Joined: 3/2/2007
Posts: 123
Location: Lake Havasu, Arizona

ah heh, it was pretty fustrating for me just to put my hands on a bunch of keys at once while trying to work in dolphin but i always was getting through though, just very uncomfortable i'd have my left hand on left side of keyboard for jump/shoot/weapons, my right hand fingers on arrow keys for moving, but the hardest part - put my mouse right up against the keyboard below it, and trying to get my right thumb to reach the mouse click buttons, to click the pause/unpause button from the top of the emulator for frame advance. it's a really screwed up feeling, but how i was getting through. so yea basically like the first setence from ddrhat. i dont have any wired controllers id be able to use to setup myself unfortanetely.

Posted: 4/30/2011 3:26 PM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

What I find weird, is that right after you mention the input file problem, I run into the same thing and can't fix it anymore. :( I'm at a standstill too until someone comes up with a fix. It really doesn't make any sense why the old inputs would carry over to the new input file.

Posted: 4/30/2011 3:43 PM

Quote

DDRKhat

Player (36)

Joined: 9/9/2006
Posts: 388

In regards to hotkey I personally use "Joy2Key" it turns my PS2 controllers inputs into Keyboard presses, and your right it's helpful MegaMan only uses 1 & 2. my setup is something like this; (Joy2Key) TRIANGLE to increment save-state (Joy2Key) L1 Un-pause (Joy2Key) R1 Toggle FrameAdvance (Joy2Key) L2 Load State (Joy2Key) R2 Save State U/D/L/R = U/D/L/R X = JUMP CIRCLE = SHOOT SEL = - START = +

A whisper in the wind~~

Posted: 5/1/2011 1:36 PM

Quote

diggidoyo

Experienced player (580)

Joined: 1/27/2011
Posts: 427
Location: Oregon

So, a little update: I was able to fix it. But I used a combination of several things so I don't know exactly what fixed the problem. You might have some luck if you try all or at least some of what I did. 1. Watch the replay. 2. Some time before the desync (I did 6000 frames since 5000 didn't work), pause the emulation and turn frame advance on. 3. Save a state 4. Advance 1 frame to initiate the state save. 5. Open another instance of Dolphin and load this save state. This is to ensure its not an "input locked" save state and you can still enter new input. If it's locked (Mega Man keeps running right, etc), repeat steps 3 and 4 in the original instance of Dolphin. Once you have a save state you can control, close the new instance of Dolphin. 6. Export the recording. 7. Delete, or at least move the old recordings out of the folder. 8. Close and re-open Dolphin 9. Watch the new replay. 10. Slightly before the end of the movie (I use the previous screen transition), pause the emulation and turn on frame advance 11. Save a state. 12. Advance one frame to initiate the state save. 13. Same as step 5. 14. Load this state and continue recording as usual. This should unlock the recording. You shouldn't have to do everything I've listed, but this is exactly what I did and it worked. Under normal circumstances, steps 1-8 can be discarded and it should rerecord just fine.

Posted: 5/2/2011 9:04 AM

Quote

DDRKhat

Player (36)

Joined: 9/9/2006
Posts: 388

I feel defeated inside. I tried all of this. (You realize you have to load the state and advance a frame to initiate to be able to export?) and went back WAY more than 5k frames just to make absolute certain.. No luck, it just ignores the input and cuts off where i've tried to do it. By step 13 you mean literally just do Step 5 right? Not go back to Step 5 and proceed (ignoring Step 13 this time).

A whisper in the wind~~