Hey look buddy, I'm an engineer. That means I solve problems. Not problems like "What is software," because that would fall within the purview of your conundrums of philosophy. I solve practical problems. For instance, how am I gonna stop some high-wattage thread-ripping monster of a CPU dead in its tracks? The answer: use code. And if that don't work? Use more code.
tastudio.addbranch(int index, , [string message = nil])tastudio.savebranch()tastudio.removebranch(int index)While we do already have the ability to load a branch and edit the current branch's text label via lua, it would be nice to have the ability to add/save/remove branches in TAStudio using lua functions.. While the savestate.saveslot() function does work for adding/saving the first 10 branches, it is limited to the 10 savestates. Would it be possible to add some lua functions something along the lines of the following so that a greater number of branches can be created/manipulated via lua?
- add an indexed branch (optionally with the provided name)
tastudio.addbranch(int index, , [string message = nil])- to save the current branch
tastudio.savebranch()- to remove a specific indexed branch
tastudio.removebranch(int index)
tastudio.add_branch([string text = nil])tastudio.update_branch(string branch_id)tastudio.remove_branch(string branch_idHey look buddy, I'm an engineer. That means I solve problems. Not problems like "What is software," because that would fall within the purview of your conundrums of philosophy. I solve practical problems. For instance, how am I gonna stop some high-wattage thread-ripping monster of a CPU dead in its tracks? The answer: use code. And if that don't work? Use more code.
"Count errors" controller reading test ROM's are now broken,. These were previously console verified.
5: (NES / AV Famicom only) The "put"/"halt" cycles of the DMC DMA should be able to clock the controller if the DMA occurs during a read from $4016. The LDA instruction should clock the controller again after the DMC DMA's "get" cycle.
4: Controllers should not be strobed when the CPU transitions from a "put" cycle to a "get" cycle.
BizHawk is a multi-platform emulator with rerecording tools written in C# * Github Project * Downloads, Release notes, and old versions
I'm using the latest dev version of BizHawk for optimal Linux compatibility (as linked here: https://nightly.link/TASEmulators/BizHawk/workflows/ci/master/BizHawk-dev-linux.zip) and I notice it isn't compatible with RetroAchievements. When signing in, the emulator immediately crashes, and it is never able to start up with it enabled.
I have seen an odd behavior two times in the past 2-3 weeks. The window for Bizhawk 2.11 would suddenly go to position (-32000, -32000). This time it happened when I selected a recent ROM (.hdd) to load, then set another window on focus to do something else, then looked at Bizhawk and couldn't find the window... The config file would say "MainWindowPosition": "-32000, -32000", and I have to set it to (0, 0) to fix it.
Hey look buddy, I'm an engineer. That means I solve problems. Not problems like "What is software," because that would fall within the purview of your conundrums of philosophy. I solve practical problems. For instance, how am I gonna stop some high-wattage thread-ripping monster of a CPU dead in its tracks? The answer: use code. And if that don't work? Use more code.
First I wanted to ask if there was a way to maintain static window sizes across all emulators to prevent constant window size changes
N64
More on functionality, has there been any developments for MAME/FBAlpha/Arcade games being more streamlined to use?
I've seen discussions about PPSSPP, Dolphin, and PCSX2 support floating around the forums, so I won't ask about those, but they'd be very cool to have too.
is there any plans to implement netplay features to Bizhawk?
Hey look buddy, I'm an engineer. That means I solve problems. Not problems like "What is software," because that would fall within the purview of your conundrums of philosophy. I solve practical problems. For instance, how am I gonna stop some high-wattage thread-ripping monster of a CPU dead in its tracks? The answer: use code. And if that don't work? Use more code.
