Process out of Sync & Illidan problem

[tvsian]

I'm having two separate issues with the Alpha, both should be reflected in the attached logs.

Problem #1 - frequently when a match is loading, I'll get "Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired" and the bot will stop during the load screen, and I'll have to start it again when the match actually starts. I'm using it in a VM on a Mac so the loading is a bit slow, but once I restart it it works fine. I have seen the same issue on a PC running it natively when matches take too long to start.

Problem #2 - when the bot is playing as Illidan, it will hearth back, the log will say it's waiting for health regen, then it'll just stop moving. If I manually run over to a fight it'll start combat and I'll see it use abilities, but after it's done it won't move again. I'm wondering if it's waiting for mana to regen and having issues because he's not a mana user. I don't have any other non-mana users to test with at the moment.

 

[Apoc]

Thanks for the heads up!

I think I fixed the issue spamming your log in 2 different places. 1 is related to how we calculate the retreat position for certain abilities. I've changed it to use the raw client data, rather than our old generated info (which is rarely used now).

Units now also have "100%" energy, if they don't actually use energy, which will solve the bug with it running back to town for no good reason. (Somehow this one slipped through the cra cks, could have sworn we tested it though)

Unfortunately, our current "in-dev" build is not ready to be released just yet, so you'll have to wait until tomorrow probably for a new build which fixes these issues. We're working hard on map-specific objectives and in the process, breaking some things while we fix others.

Temporarily, please use a different hero

As for your issue with the "injection never finished", do you have a log of that? It doesn't appear in either of your logs attached. It's possible that this just stems from the VM locking up the process too long, and the bot just saying "we couldn't get things done in a timely fashion, bailing". Does the bot stop entirely? Or does it eventually pick itsef back up?

 

[tvsian]

Here's a log with the process out of sync. It cuts off because HotS crashed during the match, but it did run fine for a little bit before that.

Basically, it'll have a few lines of "Current game is loading... waiting....", then sometimes "Pulse Monitor detected very long pulse time of 00:00:10.0303966. Restarting the bot in case of deadlocks."

If it loads right after that it's fine. If it's still loading I get the process out of sync error and the bot stops itself. I can click Start after the match loads and it works fine from there, but if I'm not watching it to catch that it stopped it'll just AFK.

I've seen it happen on my PC where I'm not running in a VM, but it's a lot less common. It only seems to happen when HotS takes an extra long time to load the match.

 

[Apoc]

Here's a log with the process out of sync. It cuts off because HotS crashed during the match, but it did run fine for a little bit before that.

Basically, it'll have a few lines of "Current game is loading... waiting....", then sometimes "Pulse Monitor detected very long pulse time of 00:00:10.0303966. Restarting the bot in case of deadlocks."

If it loads right after that it's fine. If it's still loading I get the process out of sync error and the bot stops itself. I can click Start after the match loads and it works fine from there, but if I'm not watching it to catch that it stopped it'll just AFK.

I've seen it happen on my PC where I'm not running in a VM, but it's a lot less common. It only seems to happen when HotS takes an extra long time to load the match.

If this happens consistently during the loading screen, it seems to me that the game is "locked" basically. Unfortunately, it's quite difficult to detect when this happens, outside of changing some frame drop times during the loading screen (which I'll probably do just for this specific case)

Thanks for the heads up, and sorry for the issue

Most games won't lock the DirectX render thread from still running while it's loading things. But I guess Blizz went a different route with this game engine for some reason.