New game client DirectX crashes (not positive if Miqo related)

[LukaribroParticipant]

Ever since the last update to Miqobot, both of my systems I’m running her on have been getting crashes related to DirectX. Usually I’d think it was the game itself, but this is where I’m questioning Miqo’s recent involvement.

I have four clients of the game going at all times, two on two computers. Each computer has one client dedicated to running Miqobot and one client running my own bots made with AHK. I’ve been running this setup for close to a year, with no major changes to my own program, without any issues.

Yet ever since what seems to coincide with the last update to Miqobot with the 5.3 patch, I’ll get one DirectX related crash only for the client with Miqo attached (that my own bot doesn’t touch at all). I’ll note the exact error message if this isn’t a known issue already, but it’s a very ambiguous, almost useless message like “DirectX has encountered an error” and then the frozen client will close when I click OK.

Some specifics:
The Miqo executable was downloaded separately on each machine, so it’s unlikely shared corruption from a single download.
One system runs Windows 7, the other Windows 10.
No similar errors occurred before this started on both machines with the new Miqo version.
Every occurrence of the crash has been while running a typical, very basic crafting scenario of mine. But the crash point itself seems to be either at the very start of a craft, or in the middle of waiting for macro steps to complete (yes, I use wait commas like a pleb)

Overall it’s infrequent enough to leave Miqo still usable, but frequent enough that it’s a huge headache. I didn’t see any post about a known issue introduced with the last update, but since it’s affecting multiple of my computers, two that are very different, maybe it’s not so isolated.

• This topic was modified 4 years, 2 months ago by  Lukaribro.

[LukaribroParticipant]

Update: The error message itself is “A fatal directx error has occurred (11000002)” which at least was a common error back around 4.3 as well.

It’s really weird that it’s affecting both of my clients yet doesn’t seem to be a newly widely reported error in the ffxiv community lately.

It could be that the error causing shared behavior between the two clients isn’t that they run Miqobot, but that they craft a lot. Maybe I’m getting this error at such a high frequency (it’s been a rare twice in the past 2 hours now…) because I’m just triggering a crafting related bug.

So if that’s the case, has anyone been managing to use Miqo to craft a ton and /not/ been getting errors lately?

[LyfoxParticipant]

Yea ive been crafting tons of stuff since the last update. No crashes here. Though im not running multiple clients with AHK bots and im using solver instead. Try removing one of those things from the equation and see if it changes anything.

[LukaribroParticipant]

Damn. While I’m glad yours is working for you, sounds like this is going to be a pain for me to isolate. Not running my own bots for long enough to wait for the seemingly random error to occur would be rather costly, so trying to figure out what, if anything, changed between versions comes first.

Since I’ve been running the same AHK version with luckily no updates lately, it’d be good to hear from the Miqo devs if they changed anything functionally under the hood with the last update that was different than the usual patch memory address updates and new scenario functions.

[MiqobotKeymaster]

No, there has been no changes to Miqobot source code besides the standard procedures following every game patch. The current Miqobot version uses the same game interaction methods as before.

This issue is indeed unique. We haven’t received any reports that would describe a similar behavior.
We sincerely apologize that we can not resolve your problem.

[LukaribroParticipant]

Cool, thanks for clarifying. At least that means the nuclear option of wiping and reinstalling everything, or replacing those cheap botting computers should fix it.

[Author]

Posts