I installed hearthbuddy just as directions said. Did everything by the book. I have diagnosed the problem i am having in every way i can imagine and hope you all have a solution i've missed. Everytime my character plays a card through the buddy, the card lags when placed and framerate freezes where it's at even if its high. When my opponent plays there is no lag or spike and also there is none if i turn the bot off.. The animations right after a play is where it usually freezes making multiple attacks hard to get in with lots of cards to use without the time running out,It is not smooth in this aspect.. I attached my latest log but im not sure it will be much help. Used the trial version, if we can fix this i'll buy a forever copy!!
Also, i would like to add that the specs from my computer are not contributing to this short freeze. Again, I can play at over 100 FPS solid without the buddy with my computers hardware.
This is currently by design, and will be something that changes in the near future. When the AI "updates", it updates while we hold the current game frame. If we were to update the AI outside of the current frame, the freeze would disappear, since the game is no longer waiting for the next frame to render. However, to separate it properly, the actual part of the AI that updates based on current client information has to be done inside our frame lock, and then the game simulations that take place need to be done outside.
That makes perfect sense Pushedx, thanks for the response. I hope it is something that gets fixed. I am not worried about it other than the fact that if I have a lot of cards on board to play sometimes the bot cannot play them all before time expiring..... other than that its not a huge issue. When is an expected change in delay and is there anything I can do in meantime to help make it better?
No, and the reason is talked about here why it's an issue in the first place. It's a complex issue for our bot, whereas it's something most humans don't even have to think about.
The next Beta version contains a few changes to try and address the issue from an API standpoint. SF calcs will be done outside of frame, and some caching was added to avoid the issue of the same data being requested multiple times each frame. There's still room for improvement, but hopefully it should be somewhat better.
