Why do we have autosave as a default setting? I think it should be turned off and you turn it on if you want.
Why do we have safety bags in every car? I think it should be absent, and you put it there after you crash if you want survive.
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.
Joined: 4/7/2015
Posts: 330
Location: Porto Alegre, RS, Brazil
ruadath wrote:
Why do we have autosave as a default setting? I think it should be turned off and you turn it on if you want.
You can turn it off if you want.
More than this, I think BizHawk should always be recording a movie no matter what, just like in Lsnes, in order to not lose stuff when you're casually researching. And of course, this being toggleable.
Games are basically math with a visual representation of this math, that's why I make the scripts, to re-see games as math.
My things:
YouTube, GitHub, Pastebin, Twitter
That's not going to happen. A lot of things in bizhawk shift modes and behaviours when movies are recording. That's a compromise between the differing needs of studying/playing and tasing. We had that idea a long time ago (mostly so we could repro bugs automatically from the contents of savestates), but that was early on and before the tasing tools got more serious.
You're automatically always recording a movie if you use tastudio. Which, judging by the topic title, you are expected to do :P
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'm not sure if I'm the only one, but as of late, old versions of BizHawk's tasproj files for GBA at least don't seem to open in new versions of BizHawk. For instance, when I create a tasproj file using 2.0, it seems to give me an error in 2.1. Same applies if I made a tasproj in say, 1.11.3 then open it in 2.0.
The only way for me to migate this is to make a new tasproj file on the version I want, then copy-paste the input file from the old tasporj file to the new one. Is there a way to make it auto do that if the tasproj file fails to load?
Virtual Boy and TAStudio
1. TAStudio > metadata > savestate history settings doesn't gets saved.
Workaround:
a. edit default savestate history
b. close tastudio, close bizhawk
2. The default savestate history is 512mb / 512mb / 512mb / 4 (savestate every 16 frames) while the savestate is 1.26 mb, so there's only 810 states which is enough for a 810*16 frames long TAS (12960 frames = 216 seconds = 3.6 minutes) after this you have to reseek from the beginning if you are going back from 3.6+ minutes
edit: what is the difference between project save capacity and disk capacity? if both of them set to 512mb, wouldn't it be the same available num states?
3. There's an unrequired "Memory consistency check" that fails if you change anything in the "sync settings" like the drawing color which has nothing to do with a TAS.
edit: for whatever reason, sometimes I can start the TAS, then I go to one of the savestates and the error dialog pops up until TAStudio is closed
PhD in TASing 🎓 speedrun enthusiast ❤🚷🔥 white hat hacker ▓ black box tester ░ censorships and rules...
3. There's an unrequired "Memory consistency check" that fails if you change anything in the "sync settings" like the drawing color which has nothing to do with a TAS.
Ehh... I could do something about this, but it's non-trivial to fix and it's honestly not something that should be an issue. The non-sync settings really don't affect sync, even though they're in savestates, so there won't be any issue with the published movie since it's not savestate anchored (if it is, never do that ever; it's a bad idea for many reasons).
Ehh... I could do something about this, but it's non-trivial to fix and it's honestly not something that should be an issue. The non-sync settings really don't affect sync, even though they're in savestates, so there won't be any issue with the published movie since it's not savestate anchored (if it is, never do that ever; it's a bad idea for many reasons).
But the issue is that I'm forced to stay in the same non-sync setting otherwise the dialog pops up until there is no savestate with previous non-sync setting.
1. Make a 5 minute TAS in virtual boy
2. Open TAStudio, stay at the 5 minute mark
3. Close TAStudio, change 3D color, open TAStudio
For every frames that have a savestate (per 16 frames default) and it wasn't seeked from start will throw the dialog error that's impossible to avoid/close/skip. The only way to get back to a correct state is
1. Open tasproj, edit sync setting that applies to all savestates stored
2. Seek it right from the beginning or from a series of savestate without different sync setting
3. Save tasproj after seeked, save, close tastudio
I've already had crashes 3 times, which corrupts my movie and it's backup movie.
PhD in TASing 🎓 speedrun enthusiast ❤🚷🔥 white hat hacker ▓ black box tester ░ censorships and rules...
But the issue is that I'm forced to stay in the same non-sync setting otherwise the dialog pops up until there is no savestate with previous non-sync setting.
.
Right. That's what you said the first time. And I'm not unsympathetic to it, but there's clearly a workaround that you can use: Don't change those settings.
As far as the dialog goes, we're going to change it so that aborts/bails the TASStudio session. Until that happens, you can use CTRL+ALT+DEL and force close the application for the same effect.
I know. If you're using TAStudio to play test a hack you're making, always go back to frame 0 then save the .tasproj file. Close the ROM then Re-open it if you made changes to the ROM.
For some reason after upgrading from BizHawk v1.11.9.1 to v2.1 I kept getting nothing but Unhandled exceptions then after a few open and closes they stopped.
My main problem is that when I upgraded I kept experiencing audio and framerate issues. When I play what I have worked on; the audio clips, slows down and generally goes down several pitches throughout the entirety of what i have worked on. I then found out that having TAStudio open causes this slow down in Bizhawk.
Next, I deleted all files, unzipped all, and ran v2 prereqs again. now when i play it the audio no longer changes pitch but now the framerate is locked at 50fps causing the game to be slower playing with all the controls nothing worked, again TAStudio being open causes slow down. I downgraded to Bizhawk v2 and that outright crashed when I opened the project in TAStudio.
Finally I downgraded to Bizhawk v1.13.1 and that like v1.11.9.1 had no issues.
After upgrading from bizhawk 1.11.9.1 you lost your choice of display method which is apparently the only right one for your system. Change config > display > display method until the performance resembles 1.11.9.1
Upgrade or downgrade your GPU drivers. They seem not to work well in 64bits programs. If you're using a laptop, make sure you've forced activating the discrete gpu when running bizhawk
Desktop, All my graphics are up to date and I would rather not have to uninstall and reinstall my graphics to find out if the problem lies there.
But I do get a Uhandeled Exception everytime I close TAStudio.
In the meantime I will use v1.13. since it does not have any notable problems (although it does have some occasional slow downs).
Well I wish I could help some further way or atleast make this easier on you somehow but i don't know. (remember I'm a newbie, still learning stuff, please be patient.)
I did try downgrading graphics but that did not help either and the Unhandled Exception i mentioned earlier did not show up.
When you first said update or downgrade the graphics, I had a thought of a rather unfortunate case scenario of my graphics card overall needs to be replaced (3years old no significant problems). My computer sometimes doesn't want to work right when i need it to.
Well I wish I could help some further way or atleast make this easier on you somehow but i don't know. (remember I'm a newbie, still learning stuff, please be patient.)
1. Post the full log of unhandled exception error message you get next time (when the window pops up)
2. I have a somewhat slow laptop, so I can easily spot slower stuffs like opening just ram watch with a few values also slows down everything just like TAStudio (despite the processing volume differences). If you write down your FPS (view > display FPS) and the steps you do (or record a video) while getting into a much slower state, we can help (and investigate) the issue
PhD in TASing 🎓 speedrun enthusiast ❤🚷🔥 white hat hacker ▓ black box tester ░ censorships and rules...
Alright, I had hoped that i would get Unhandled Exception between now and then so i could post it here but I never got one.
New release of Bizhawk v2.1.1 has given me the answer to the problem that has been happening.
I have found an interesting quirk with TAStudio that questionably is happening and is the main source of the problem that I have been experiencing.
Apparently the window size of TAStudio is causing the slowdowns; I've checked Bizhawk v2.1 to make sure and it is the window size of only TAStudio that causes this problem, having Bizhawk full screen or half Screen has no issues.
Please post a full screen screenshot so I can replicate it.
Rendering ever changing variables is not a simple task and requires processing power. TAStudio changes the actual frame's row color and input while doing the usual stuffs. What I had success in the past was moving the processor intensive windows out of sight but I don't know if this still works.
Also please write down the FPS value you have between the two states, like "everything shown full size" and the one you say half size.
PhD in TASing 🎓 speedrun enthusiast ❤🚷🔥 white hat hacker ▓ black box tester ░ censorships and rules...
Alright, here are the images, each image has FPS and on it.
1: http://imgur.com/hQIURC3
2: http://imgur.com/RJE5pO7
3: http://imgur.com/Su5yMzH
Image 3 is the style of how i have been doing my TAS thus far. But after v2 slowdows have occured.
4: http://imgur.com/U0NPqfG
Image 4 Split across 2 monitors (Would never use this style might help you some.)
Since I use windows 10 I normally press the Windows Key & the left/right arrow key to have this window placement or I drag the window to the edge of the screen and drop.[/submission]
How is the pattern not obvious to you? A large tastudio window is slow. That's how it's always been in every version. If newer bizhawks are slower than you have less overhead because your system is weak and 64bits is slower, or because your GPU driver is bugged, or because youve changed your config > display > display method somehow, or because the core you're using runs slower savestates than it used to in older versions.
But large tastudio windows can soak up the CPU on even a beefy system.
There's probably nothing you can do about this.
To be clear:
1. 64bits is slower
2. GPGX in 64bits may be slower
3. Everything is operating normally
In fact, the thing that changed in 2.0 is state size of Genesis. It was 144KB, now it's around 800KB of core data. State gap became bigger, previously it was 1 frame (resulting in states every other frame. Now it's 12, with state every 13th frame. The time it takes to save each state is likely what causes your slowdown.
To skip unnecessary input roll updates, you can turn on turbo seek and turn off follow cursor. And make the emu window smaller. I'd be interested in how much each of these changes helps you.
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.
All of what you suggested did work Feos. Although for a matter of convenience i would prefer to have the Follow Cursor Checked instead of having to check & uncheck it when I make an adjustment so I'll have a smaller window like in this image http://imgur.com/hQIURC3 for the time being. Thank you all for your assistance plenty of workarounds and hope that this is not an isolated event.
Have some other issues but I'll put them in the Bugs only Forum.
