Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
After the release of BizHawk 2.4.2, I was no longer able to use a lua script that had been working on 2.4.
With the release of 2.5, I had hoped that it would have been resolved...but it appears that I have a unique situation.
Any clue as to what is going on?
Just to add, I am testing these new version with a single instance; however, with 2.4...I am running multiple instances.
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
This specific issue you mention is known and documented in this ticket. You can check there for progress, if any.
In general, Lua is a tricky thing, and I find interactions with TAStudio to have problems. Hopefully that will be resolved in the future.
Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
RetroEdit wrote:
This specific issue you mention is known and documented in this ticket. You can check there for progress, if any.
In general, Lua is a tricky thing, and I find interactions with TAStudio to have problems. Hopefully that will be resolved in the future.
Thank you.
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
RetroEdit wrote:
This specific issue you mention is known and documented in this ticket. You can check there for progress, if any.
In general, Lua is a tricky thing, and I find interactions with TAStudio to have problems. Hopefully that will be resolved in the future.
The sad thing is, the changes to the cores in BizHawk 2.4.2 have amazing speed increases for ones that I use. This lua error showed up at the same time as those updates. I'm so anxious to make use of them.
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
Yeah, I'm starting to realize this issue is significantly higher priority than I originally though it was when I encountered it a few months ago. It breaks certain TAStudio-specific Lua functions, and it's just arbitrary that it's broken for certain things.
My workaround is to generally avoid TAStudio when scripting and take advantage of the speed boost when TAStudio is closed. I do stuff TAStudio is good at while I'm not using my scripts.
But that doesn't make sense for certain scripts, so I sympathize.
Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
RetroEdit wrote:
My workaround is to generally avoid TAStudio when scripting and take advantage of the speed boost when TAStudio is closed. I do stuff TAStudio is good at while I'm not using my scripts.
I wish, in this case, I could. I'm actually using TASStudio in a unique way to develop inputs that are used by my lua. If this were not the case, I would absolutely love to eliminate that for more of a speed increase. This is now giving me the push to move over to converting this to APIHawk.
RetroEdit wrote:
But that doesn't make sense for certain scripts, so I sympathize.
Thanks. The work done on this application is appreciated. In the meantime, I will be sticking to BizHawk 2.4 until it has been resolved.
I have tried to debug this myself, but the BizHawk sln has an architecture that will take me some time to figure out. At this moment, I don't have spare time to dedicate development to this app. Hopefully soon.
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
I have tried to debug this myself, but the BizHawk sln has an architecture that will take me some time to figure out. At this moment, I don't have spare time to dedicate development to this app. Hopefully soon.
Yeah, I've been contributions to BizHawk recently so I'm going to look into it now, and I should be able to find the code that raises the error. Solving it may be another matter entirely, though.
Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
RetroEdit wrote:
nymx wrote:
I have tried to debug this myself, but the BizHawk sln has an architecture that will take me some time to figure out. At this moment, I don't have spare time to dedicate development to this app. Hopefully soon.
Yeah, I've been contributions to BizHawk recently so I'm going to look into it now, and I should be able to find the code that raises the error. Solving it may be another matter entirely, though.
Huh...just curious, but if you happen to find a answer, do you suppose a binary file could be copied over to the existing 2.5 release? That way we wouldn't have to wait for another full publish?
Nevermind...If you find an answer...I can just publish locally.
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
I have tried to debug this myself, but the BizHawk sln has an architecture that will take me some time to figure out. At this moment, I don't have spare time to dedicate development to this app. Hopefully soon.
Yeah, I've been contributions to BizHawk recently so I'm going to look into it now, and I should be able to find the code that raises the error. Solving it may be another matter entirely, though.
Huh...just curious, but if you happen to find a answer, do you suppose a binary file could be copied over to the existing 2.5 release? That way we wouldn't have to wait for another full publish?
Nevermind...If you find an answer...I can just publish locally.
Dev builds are regularly released, so you can grab one of those. If you want to cherry-pick commits for some reason, you can build it yourself.
Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
RetroEdit wrote:
Dev builds are regularly released, so you can grab one of those. If you want to cherry-pick commits for some reason, you can build it yourself.
Sounds good, can't wait to see what you find. Thanks!
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
Just curious if there is any discoveries on this issue.
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
This is no longer an issue. Thank you guys. Bizhawk 2.5.2 is now allowing me to run my lua scripts.
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
Joined: 11/14/2014
Posts: 813
Location: South Pole, True Land Down Under
Hmmmm....very interesting. This error is still here (sorta), but it can be circumvented.
Not sure if any focus should be given to fixing it, but here is how to get around the problem.
When the message shows up (which comes up after running more than one emulator instance), just excuse the error. Go back to the lua console and play the script again. it will function as normal.
I recently discovered that if you haven't reached a level of frustration with TASing any game, then you haven't done your due diligence.
----
SOYZA: Are you playing a game?
NYMX: I'm not playing a game, I'm TASing.
SOYZA: Oh...so its not a game...Its for real?
----
Anybody got a Quantum computer I can borrow for 20 minutes?
Nevermind...eien's 64 core machine will do. :)
----
BOTing will be the end of all games. --NYMX
Any clue as to what is going on?
Just to add, I am testing these new version with a single instance; however, with 2.4...I am running multiple instances.
