Closed gammaleak closed 3 years ago
I wondered if maybe your changes on Oct 7 to add frameskipping may have introduced this problem, so I downloaded the code as it existed eod Oct 6. Unfortunately, this problem still persisted.
So, you'll need to make sure that the AutoHotKey is running as Administrator as well, but the stranger part is the error message you're seeing, because it implies that the skillchain lib object is actually a boolean somehow. Can you post your skillchains lua? (addons/xivcrossbar/libs/skillchani/skillchains.lua)
@gammaleak ^
I uninstalled it back in November when I first tried and it didn't work. Just tried a re-install using the latest code and got the exact same results. I cannot tell if Autohotkey is running in Administrator mode or not. If I just try to "run Autohotkey" it just brings up a Help page and tells me I tried to run it without a script and that doesn't work (sorry, I have zero experience with AHK).
Ah, ok. Basically, you have to go to windower/addons/xivcrossbar, then right-click on ffxi_directinput.ahk and select "Run as Administrator", then do the same to ffxi_xinput.ahk. The addon should automatically start them for you, but this will help us nail down exactly where the problem is coming from.
With all that said, I'm still really confused as to how you're getting this runtime error. How are you starting the addon? Have you tried waiting until you're completely logged into a character before starting it up?
Here's what I'm doing:
And that's it. Tonight I can try to start both those scripts before launching the game and see if that changes anything.
One other note: I don't have Gearswap installed as I'm pretty newb at the game and don't have any jobs at iLvl119, so it seems sort of unnecessary at this point. But maybe that's a hidden dependency here?
Yeah, it looks like the skillchains lib doesn't like being loaded before the player's character is logged in. I've pushed an update, which I think will work for you.
It does seem that I have to manually launch both of those AHK scripts, but your fix got rid of the runtime error. Thank you!
Attempted a first-time install. As soon as Windower loaded the addon it began spewing lua runtime errors on two lines:
The initial setup dialog also did not recognize any of my button presses (Windower was launched as Administrator), however, I thought that this might just be due to the lua scripts failing.