Nav server issues

[alien98]

Bots are not working, movement is nonexistent, possibly a move every 10 minutes but then its only 3 or 4 steps. Been like this all day and there are other threads about it, and no mention of support for it other than direction to post here, so here goes.

Same results after a reboot, after restarting swtor and buddywing.
Same results with default combat
Same results with Wing-it
Same results with Fight at joes
Same results after a fresh install of buddy wing and trying each routine one at a time

 

[Developer]

Your post must have done the trick. Logs now indicate that the navigation server is restarting, so 30+ minutes until all is well.

Cheers,
-D

 

[Jests]

Mine still isn't goin anywhere.

 

[CodenameG]

[22:42:09.737 N] Unhandled exception during init: System.Exception: Failed to ReadProcessMemory
   at GreyMagic.ExternalProcessMemory.ReadBytes(IntPtr address, Int32 count, Boolean relative)
   at GreyMagic.MemoryBase.ReadString(IntPtr address, Encoding encoding, Int32 maxLength, Boolean relative)
   at ..
()
   at ..
[
](Boolean , String , Object[] )
   at Buddy.Swtor.Objects.TorObject.CallScript[T](Boolean hasReturnValue, String function, Object[] args)
   at Buddy.Swtor.Objects.TorPlayer.GetSkillPointsSpentInTree(SkillTreeId tree)
   at DefaultCombat.SpecHandler.calculateSpec(SkillTreeId tree1, SkillTreeId tree2, SkillTreeId tree3) in e:\Buddywing\Routines\DefaultCombat\SpecHandler.cs:line 152
   at DefaultCombat.SpecHandler.GetSpec() in e:\Buddywing\Routines\DefaultCombat\SpecHandler.cs:line 26
   at DefaultCombat.DefaultCombat.Initialize() in e:\Buddywing\Routines\DefaultCombat\Routines\Joes\DefaultCombat.cs:line 54
   at Buddy.CommonBot.RoutineManager.set_Current(ICombat value)
   at Buddy.CommonBot.BotMain.SetCurrentCombatRoutine()
   at Buddywing.MainWindow.DoInitialization()

the log you posted isnt showing anything wrong with movement, the only error in the log is related to buddywing not being able to read from the process.

make sure you uploaded the correct log.

 

[alien98]

Unhandled exception during init: System.Exception: Failed to ReadProcessMemory I get a buddgwing popup for this error nonstop when closing the bot and sometimes when loading it,
so does everyone else who uses the bot. It has been mentioned many many times. It sometimes takes more than 30min to get the bot going because of this error.
You start the bot and get the error, then you have to cntrl alt delete to close the bot because it locks up.
Then you have to go to the buddywing auth portal site and close the process because you reboot your computer and relaunch swtor then relauch buddywing only to have it say,
you did not shut down buddy wing properly, well no shit sherlock. Then I usually delete the buddywing folder, re-download it, re logout my process from the auth portal, reboot and try again.
It is honestly a real pain in the ass.

I have a fresh install of windows 7 64bit
Fresh install of net framework 4
Fresh install of the c libraries
I use 3 folders for 3 full copies of buddywing each with its own routines because sometimes the bot will start with one routine installed but not the other.
I do fresh re download of the bot for each of my 3 folders and re download the routines fresh every time as well. I am not keeping any config files either,
I completely delete all three buddy wing folders every-time there is an update. I have exausted every option I can to make this error stop and it still plagues me nearly every time I attempt to use it.
I know for a fact I am not alone with this error. I also have this error on all three of the computers I use at my house. One is an AMD the other two are core i5 intels.
All three computers have 8 gig of ram, all three have ssd drives with windows 7 64bit. I have Geforce 9800gt in the older amd, a geforce gtx260 in one and a geforce gtx 560ti in the other.
This is all the info I can think of that may be helpful if there is anything else you want to know just ask, I would love to see you squash this bug and am glad to help in any way I can.


As for the movement errors, that is the correct log file, the movement errors were present even though they were not logged.
I have not noticed movement errors showing up in the log since last update of buddywing at all but the nav server has crashed a couple of times for sure and was brough back up and the bot ran fine.

 

[Jests]

That would make sense, it's been acting wonky for me again today.

 

[Tony]

you still got issues?

 

[Jests]

Not certain, I'm at work, but I'll post here in 2 hours when I am off work.

 

[Developer]

Hi Jests,

From my own experience setting up an optimal build for this game, I would recommend running it in Win 7 x86. I had far too many issues when trying to run it on a 64 bit OS, especially if using a VM.

Per the Unhandled Exception During Init error, I get this almost every time I start the bot, on all computers, but it only happens once. In my case, fixing it just requires me to close the window, wait a few seconds, and restart it again. Again, this might simply be because of the operating system.

Good luck,
-D

 

[Jests]

Hi Jests,

From my own experience setting up an optimal build for this game, I would recommend running it in Win 7 x86. I had far too many issues when trying to run it on a 64 bit OS, especially if using a VM.

Per the Unhandled Exception During Init error, I get this almost every time I start the bot, on all computers, but it only happens once. In my case, fixing it just requires me to close the window, wait a few seconds, and restart it again. Again, this might simply be because of the operating system.

Good luck,
-D

Thanks for the tips! Now that I've set my affinities like mentioned in another thread the bot works relatively well. Of course... if the nav servers haven't been dodgy ever since Sunday morning then I've likely got a problem, because my bot has been unstable. It could be the profile I'm running or maybe I'm having a new problem. I'll check it out when I get home.

*edit*
Well, my Commando isn't working. Let me try my Operative.

*edit*
Oh snap... My operative works! Must be something wrong with my commando profile. Funny, this while time I just assumed the server was down.