Notice how I try to seek to frame 294, but it only seeks to 255, which is at the same position in the window after it scrolls up to where the current frame was. This means everything works as intended if Follow Cursor is off.You shouldn't need a degree in computer science to get into this hobby.
Cause a fatal error: [...]
1.11.7's TAStudio undo feature appears rather broken. It works fine for a while, but eventually it makes an entire line of input all the way to the beginning for some reason. All I did was add lines of "A" "B" at discrete parts of the movie using the piano roll if it helps. Edit: Also, pressing "Undo" after loading a tasproj file then advancing past said movie seems to immediately hop to frame 0, even if I added no other input.
1.11.7's TAStudio undo feature appears rather broken. It works fine for a while, but eventually it makes an entire line of input all the way to the beginning for some reason. All I did was add lines of "A" "B" at discrete parts of the movie using the piano roll if it helps. Edit: Also, pressing "Undo" after loading a tasproj file then advancing past said movie seems to immediately hop to frame 0, even if I added no other input.
I reported these already and foes already fixed them. :)
Use interim.
Thanks. Somewhat related, but can the interim build link be posted somewhere more noticeable? It's rather obscure at the moment. feos, are you able to edit the first post/contact some mod who can?
You shouldn't need a degree in computer science to get into this hobby.
It oddly works fine before this error first appears however. After it appears though, it seems the only way to fix undo is closed TAStudios and reopen.
Edit: http://pastebin.com/Gg15ALXA The error expanded.On the interim, every now and then, it appears "undo" gets bugged, and gives this everytime: http://i.imgur.com/8aJBAh5.png It oddly works fine before this error first appears however. After it appears though, it seems the only way to fix undo is closed TAStudios and reopen. Edit: http://pastebin.com/Gg15ALXA The error expanded.
Please fix this: TAStudio does not execute joypad input from lua script, tough the input appear in the TAStudio window... The script works fine if launched without TAStudio engaged.
Can't help without repro steps.
Using the 1.11.7 official release, deleting a frame in TAStudio and undoing it with Ctrl+Z consistently deletes all savestates in the greenzone.
Use interim.
1. Open any game (I used GBA) 2. Wait for like 200 frames 3. Open RAM Watch 4. Add any new watch; doesn't matter the value 5. Open TAStudios under "Tools" 6. When asked to save Ram Watch, click "Cancel" 7. The movie now looks like this http://imgur.com/Is23ejZ Tried on interim + 1.11.7
I managed to trigger it just now. Seems like this: 1. Open TAStudios. The movie can be default.tasproj; doesn't matter 2. Make some input that goes "beyond" the current movie. So, say if the movie's length is 1, make some input at frame 5. 3. Frame advance beyond that point from step 2. In this example, that means play to frame 6+ 4. Press undo twice. In this example, the first undo gets rid of the input from frame 5. The 2nd undo gives the error. I hope this helps.
I was also getting some crashes where BizHawk would stop responding and close without prompting me to save the project. Has this been fixed in the latest interm as well?
Although, it takes a second or two for the undo feature to restore deleted frames, which iirc was instant before.
Note: It's not that I don't trust you or anything, considering some people experience bugs (example, I don't experience slow down on undo nor crashes) that I don't, but can someone please explain like I'm 5 how come even using bytecode (C# in this case) still somehow has underlying bugs that are OS-dependent? I thought byte code gets rid of that?
Although, it takes a second or two for the undo feature to restore deleted frames, which iirc was instant before.
