I am getting no movement on Balmorra. Tried deleting the settings file but it keeps puting this in, though i don't have any plugins. Code: <EnabledPlugins> <Value>Auto-Equip</Value> <Value>Use Lockboxes</Value> <Value>Relicious</Value> </EnabledPlugins> There is no errors in the log file, last line is Bot thread started. Edit: Clean install -> same issue
I experienced the same issue. It occurs if your target is more than one hop away (so nav server query). Currently I've reverted back to 397 until it's resolved.
Thanks! I m having lots of issues with 399 also, bot keeps calling stuck routine all the time, and I ve even gotten tells if I m lost, just lucky i was not afk.
I am going to try out new build see what happens. He is adding in checks in place for mounting. Just hang tight.
Confirmed this last buddywing update doesn't have any movement. Old build before this works great for me. I have been using it all day and I am so god damn happy since is Aevitas fearless
Yep r397 is working ok for me too at least in 1 Instance. Trying ISBoxer now for the 3189th time lol. I hate load heavy VMs.
I m still getting "Unstuck loops" without any apparent reason, seems to be often if there s z-axis movement in the hop. No mount involved just testing with questing profiles that used to work 2 days ago on Korriban. Code: [00:42:00.130 D] Generating path to TurnInQuestTag: Lord Samus for A Fighting Chance <-44.1836, 3.802763, -2.5856> [00:42:00.163 E] Got response from server, validating. [00:42:00.163 E] Response has 15 hops. Converting to vectors and path queue. [00:42:00.163 D] Nav Service path generated. [00:42:00.163 D] Generated path to <-44.1836, 3.802763, -2.5856> (TurnInQuestTag: Lord Samus for A Fighting Chance) with 15 hops. [00:42:02.539 D] Moving to next hop: <-25.6, 1.810849, 1.6>, T: None (TurnInQuestTag: Lord Samus for A Fighting Chance) D: 3.365854 [00:42:09.963 D] Moving to next hop: <-25.6, 1.809678, 1.6>, T: None (TurnInQuestTag: Lord Samus for A Fighting Chance) D: 0.009667635 [00:42:12.340 D] [Stuck Handler] We're stuck at <-25.6, 1.80001, 1.6> - kor_rebuild_test - 4000000106296B6D [00:42:16.443 D] Stuck handler, unsticking. [00:42:16.443 D] at Buddy.Navigation.ReactiveAntiStuck.Pulse() at Buddy.Navigation.DefaultNavigationProvider.(String ) at Buddy.Navigation.DefaultNavigationProvider.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast, Boolean straightLineWhileGenerating) at Buddy.Navigation.Navigator.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast, Boolean straightLineWhileGenerating) at Buddy.CommonBot.CommonBehaviors..(Object ) at Buddy.BehaviorTree.Action.RunAction(Object context) at Buddy.BehaviorTree.Action..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.Decorator..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.Decorator..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.Decorator..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.Common.HookExecutor.Run(Object context) at Buddy.BehaviorTree.Action.RunAction(Object context) at Buddy.BehaviorTree.Action..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.Common.HookExecutor.Run(Object context) at Buddy.BehaviorTree.Action.RunAction(Object context) at Buddy.BehaviorTree.Action..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.Decorator..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.CommonBot.BotMain.() [00:42:18.544 D] Generating path to TurnInQuestTag: Lord Samus for A Fighting Chance <-44.1836, 3.802763, -2.5856> [00:42:18.609 E] Contacting nav server for path. [00:42:18.690 D] Waiting for path request to finish... [00:42:18.757 D] Nav callback called. [00:42:20.787 D] Generating path to TurnInQuestTag: Lord Samus for A Fighting Chance <-44.1836, 3.802763, -2.5856> [00:42:20.821 E] Got response from server, validating. [00:42:20.821 E] Response has 14 hops. Converting to vectors and path queue. [00:42:20.821 D] Nav Service path generated. [00:42:20.821 D] Generated path to <-44.1836, 3.802763, -2.5856> (TurnInQuestTag: Lord Samus for A Fighting Chance) with 14 hops. [00:42:22.999 D] Moving to next hop: <-26.5, 1.809678, 1.875>, T: None (TurnInQuestTag: Lord Samus for A Fighting Chance) D: 1.039597 [00:42:25.308 D] Moving to next hop: <-26.625, 1.809678, 2>, T: None (TurnInQuestTag: Lord Samus for A Fighting Chance) D: 0.1770402 [00:42:27.387 D] [Stuck Handler] We're stuck at <-26.625, 1.800112, 2> - kor_rebuild_test - 4000000106296B6D [00:42:29.739 D] Start/Stop Button Clicked! [00:42:29.739 D] BotMain.Stop() called [00:42:29.739 N] Stopping the bot. [00:42:29.840 D] Sleeping while waiting on execution state to be available for BotMain.Stop() [00:42:31.491 D] Stuck handler, unsticking. [00:42:31.491 D] at Buddy.Navigation.ReactiveAntiStuck.Pulse() at Buddy.Navigation.DefaultNavigationProvider.(String ) at Buddy.Navigation.DefaultNavigationProvider.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast, Boolean straightLineWhileGenerating) at Buddy.Navigation.Navigator.MoveTo(Vector3 destination, String destinationName, Boolean useRaycast, Boolean straightLineWhileGenerating) at Buddy.CommonBot.CommonBehaviors..(Object ) at Buddy.BehaviorTree.Action.RunAction(Object context) at Buddy.BehaviorTree.Action..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.Decorator..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.Decorator..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.Decorator..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.Common.HookExecutor.Run(Object context) at Buddy.BehaviorTree.Action.RunAction(Object context) at Buddy.BehaviorTree.Action..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.Common.HookExecutor.Run(Object context) at Buddy.BehaviorTree.Action.RunAction(Object context) at Buddy.BehaviorTree.Action..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.Decorator..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.BehaviorTree.PrioritySelector..() at Buddy.BehaviorTree.Composite.Tick(Object context) at Buddy.CommonBot.BotMain.()
Seems like after combat a few times it won't start movment with mounts UGH. Was working great and so confused on whats going on. I even did fresh installs :s.
Mine is getting stuck as well, waiting between pulls. I've reverted back again until this is all sorted.
Yea I am so confused since it wasn't doing this before. I had it running perfect from the build he sent me. I even tested that build and now its doing this. What makes no sense is my guy mounts randomly and then won't. Scav nodes perfect and everything else. Combat is smooth as can be. God I love buddywing now!
Yea seem the checks for mounting isn't always calling the mount. So then it will not contact the nav server since you didn't mount. Very random indeed. If you are not on mount new update works fine yet. If you want mounts use 397 that Dev post back. Some times things don't always work out!
Newest update is not working without mount for me either. 397 has some but very few issues. Useitem gets stuck more often then before the last Swtor patch, some but not too many unnecesary unstuck calls. 397 is usable for me while not being optimal , i have to adjust several profiles removing quests that used to work before.
Yea fearless leader will look into this. I am gone most of today since of business. I wish every one luck!