Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
A silly mistake. Reuploaded.
Addressing Hetfield90's request to set mem capacity above 1024, it's capped so for x86 systems, and can go eightfold for x64.
TASeditor wrote:
feos wrote:
The way taseditor does it is this: if the green arrow is in greenzone, it won't pause there, otherwise it will. That way AnS worked around my problems by adding some real logic: if I'm editing, I need it to stop at the last frame after each edit, so that I could evaluate the outcome; and if I'm just watching, to evaluate the fashion, it won't pause there to not break the real-time pace.
This is what TAS Editor only does with middle-mouse, but not with pause button or hotkey. TAStudio does it with all three of them.
Fixed, not uploading yet.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Another marker request: When you delete a frame in TAStudio with a marker also on the same frame, can it please not delete the marker and instead make the next frame be that marker (unless there's nothing left in front)?
Another marker request: When you delete a frame in TAStudio with a marker also on the same frame, can it please not delete the marker and instead make the next frame be that marker (unless there's nothing left in front)?
Only if you unbind markers from input.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
And I use some of the stuff in TAS Editor/TAStudio that can't change hotkeys too. I'd like to be able to change some of these though.
Like which?
Some for editing need better places for me: Cloning, deleting, selection courser up/down.
I'd like to put them somewhere near my left hand, so I don't need to move my hand from mouse or my other one all over the keyboard, they should be single key. Copy/paste/paste-insert/cut are already on the left, but multi-key.
I need a full list of those that you want to be hotkeys.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
I need a full list of those that you want to be hotkeys.
The best would be to make these costumazible.
Clone: c
Delete: d
Clear: x
Cancel actions: Esc (stops seeking, exit analog editing)
Rewind: q
Enter Analog edit and cycle through: e (Pressing e causes entering editing the analog input for the first visible analog column for the current selection, if multiple frames are selected edit input for all selected frames. If already in analog edit mode go to the next analog column when e is pressed once more)
Toggle auto-restore: s
Restore last position: a
That's quite a list. Updated the interim before I touch these.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
So far using the latest build with auto-save disabled I've gotten the more common error only 2 or 3 times after a couple hours of TASing(the one that previously consistently happened every 5-10 minutes), and the other errors are yet to occur.
This won't be necessary unless the other error that wipes all savestates and branches clean starts occurring again, but would it be possible to add an option that automatically creates a backup .tasproj upon saving? The reason I ask is because when you get a fatal exception and it prompts you if you want to save or not, you don't know if it's the type of error that erases branches and savestates or not until after you save. That way you could not lose progress if states remain intact, or use the backup that still has savestates if they get erased to avoid having to watch the TAS from the beginning.
Also would it be possible to add an option so that the greenzone tail never runs out, but adds additional tiers of larger intervals between savestates to the end of it?
would it be possible to add an option that automatically creates a backup .tasproj upon saving?
But I added an option to autosave to filename.backup, for tasproj and bk2, whichever you prefer.
Hetfield90 wrote:
Also would it be possible to add an option so that the greenzone tail never runs out, but adds additional tiers of larger intervals between savestates to the end of it?
This will eventually be done, but doesn't look like soon, since it requires touching the most dangerous part of tastudio - tas state manager.
Otherwise, how does putting markers as keys work? Does it reliably keep the states that are before markers after greenzone tail runs past it?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Otherwise, how does putting markers as keys work? Does it reliably keep the states that are before markers after greenzone tail runs past it?
So far it has worked all but one time, although I haven't tested it that much yet.
feos wrote:
But I added an option to autosave to filename.backup, for tasproj and bk2, whichever you prefer.
I see the check boxes for "Autosave As Bk2" and "Append 'backup' to Filename" but but it doesn't seem like they do anything? Is there somewhere that I can change the destination folder or file type? Checking them and saving doesn't put any backup file in my Movies folder.
They refer to autosaved files. And autosave happens if the interval is above zero. The folder is the same as your project's. I might add an option to fire backup per usual save too, but what would be the difference, if it gets corrupted at that step, they will be both corrupted.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
They get corrupted if you save when it asks you if you want to save as BizHawk is crashing(provided it was caused by a certain error). I don't think it's ever happened on a manual save or auto save before an actual crash.
So far using the latest build with auto-save disabled I've gotten the more common error only 2 or 3 times after a couple hours of TASing(the one that previously consistently happened every 5-10 minutes), and the other errors are yet to occur.
I doubt it's related to my updates. I'll need a repro method, can't see clearly what goes wrong from the call stack. Another reliable way would be if you install some free version of VS and have it running in a debug mode. So when it crashes, you could just printscreen the most recent functions from the callstack :D
Hetfield90 wrote:
They get corrupted if you save when it asks you if you want to save as BizHawk is crashing(provided it was caused by a certain error). I don't think it's ever happened on a manual save or auto save before an actual crash.
I see. But have you tried autosave itself, or you can't still get it working?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
They get corrupted if you save when it asks you if you want to save as BizHawk is crashing(provided it was caused by a certain error). I don't think it's ever happened on a manual save or auto save before an actual crash.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Clone: c Delete: d Clear: x -- Done, along with Insert. Configure in hotkeys.
Cancel actions: Esc (stops seeking, exit analog editing) -- Analog editing was already canceled by Esc. Added cancel seeking.
Rewind: q -- Global rewind now works
Enter Analog edit and cycle through: e (Pressing e causes entering editing the analog input for the first visible analog column for the current selection, if multiple frames are selected edit input for all selected frames. If already in analog edit mode go to the next analog column when e is pressed once more) -- Whenever I'm totally free.
Toggle auto-restore: s -- Done for all 3. Configure in hotkeys.
Restore last position: a -- Middle-click
Update the build!
Next:
- option to fire restore after mousedown -- Done, doesn't affect rerecords at all.
- esoteric frame 203000 problem
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
I fixed one case leading to this back then, do you have the repro steps?
Updating or loading branches seems to cause this problem (removal of states because of state gap). I haven't figured out how to fire it consitently though.
I have no idea how it happened, but when I loaded a tasproj file this suddenly appeared:
http://pastebin.com/jKV9gjAb
I cannot reproduce it yet, but I'll post again if it happens. This appeared for the dropbox version Feos linked.
Edit: Feos, was the seeking feature removed? Currently for some reason the latest dropbox link still has "Turbo seek" option, but it does not seem to do anything.
http://imgur.com/kJk179r
Edit2:
Anyone else experiencing this bug with feo's revision? In case no one knows what is going on, right clicking sometimes makes a different marker get selected.
Bind Markers To Input is a per movie setting. Its purpose is to shift markers along with input on frame removals/insertions/copypasting.
jlun2 wrote:
Feos, was the seeking feature removed? Currently for some reason the latest dropbox link still has "Turbo seek" option, but it does not seem to do anything.
Works perfectly for me.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
On the interim build by feos, pressing insert while TAStudio does not exist gives this error
System.NullReferenceException: Object reference not set to an instance of an object.
at BizHawk.Client.EmuHawk.TAStudio.InsertFrameMenuItem_Click(Object sender, EventArgs e)
at BizHawk.Client.EmuHawk.TAStudio.InsertFrameExternal()
at BizHawk.Client.EmuHawk.MainForm.CheckHotkey(String trigger)
at BizHawk.Client.EmuHawk.MainForm.<ProcessInput>b__1e(Boolean current, String trigger)
at System.Linq.Enumerable.Aggregate[TSource,TAccumulate](IEnumerable`1 source, TAccumulate seed, Func`3 func)
at BizHawk.Client.EmuHawk.MainForm.ProcessInput()
at BizHawk.Client.EmuHawk.MainForm.ProgramRunLoop()
at BizHawk.Client.EmuHawk.Program.SubMain(String[] args)
That's a common bug for tools hotkeys... Fixed/updated.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
I wasn't running into any of these issues while TASing a SNES game, but in a PSX game I'm having a lot more issues with the greenzone.
It's leaving a bunch of older savestates up with inconsistent spacing in between them, and my immediate greenzone tail only lasts for 1 savestate. I tried deleting the greenzone file and playing the run from the start, but it starts behaving the same way again after creating enough savestates.
Also,
feos wrote:
Otherwise, how does putting markers as keys work? Does it reliably keep the states that are before markers after greenzone tail runs past it?
This works as intended until the greenzone capacity gets limited by the aforementioned bug, then the marker state gets erased as well.
Exception Details
I tried it a bit starting a fresh PSX project (that I saved, loaded, edited), and it behaved normally. But I observed something like this with N64 before. Can you figure out the exact repro steps for PSX?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Can someone please try feos branch and do the following in order?
1. TAS using TAStudios for a GBA game, any type
2. Without stopping the movie, play another .bk2 file of the same game for a bit
3. Stop that movie, try to open a tasproj file, then open up tastudios?
I keep getting
every now and then when I do the above steps. It happens inconsistently, but I know it seems to always happen only for feo's branches but not the main 1.11.6 (including the latest one in July 12th.
Edit: And this erases my recent files list and some settings such as when to autosave for some reason.
http://pastebin.com/jKV9gjAb
I cannot reproduce it yet, but I'll post again if it happens. This appeared for the dropbox version Feos linked.
Edit: Feos, was the seeking feature removed? Currently for some reason the latest dropbox link still has "Turbo seek" option, but it does not seem to do anything.
http://imgur.com/kJk179r
Edit2:
Anyone else experiencing this bug with feo's revision? In case no one knows what is going on, right clicking sometimes makes a different marker get selected.
every now and then when I do the above steps. It happens inconsistently, but I know it seems to always happen only for feo's branches but not the main 1.11.6 (including the latest one in July 12th.
Edit: And this erases my recent files list and some settings such as when to autosave for some reason.
