Can't start the bot anymore

[esk213]

I kept getting memory errors which I was able to prevent when I forced the game to start with dx9, but now I can't start the bot anymore. It keeps telling me there is no process to attach and says there is a similar process (that shows the exact same version/hash). So, is there something I can do on my end or does the bot just not run with Wildstar dx9 instead of 11?

I just realized, the first time I try to start the bot when I just started the game the window just won't even appear giving me these logs:

2015-04-06 02:21:13,317 [1] INFO MainWindow - Logging in...
2015-04-06 02:21:13,701 [1] INFO MainWindow - T: 5247324855160942397 H: 1988898556
2015-04-06 02:21:14,184 [1] DEBUG ProcessWrapper - Mutex.TryOpenExisting on PID 7828
2015-04-06 02:21:14,229 [1] DEBUG ProcessWrapper - Mutex.TryOpenExisting on PID 7828
2015-04-06 02:21:14,570 [1] DEBUG MainWindow - Game Process Hook Type: Standard D3D11 64-bit #1 [Push 4]
2015-04-06 02:21:14,572 [1] INFO GameEngine - Attached to game: [7828] WildStar64 (Hash: 5051AAF9)
2015-04-06 02:21:14,584 [1] DEBUG Hotkeys - Initialized hotkeys to window handle + 1008E0
2015-04-06 02:21:14,613 [1] DEBUG GameManager - Base Addr 13FFE0000
2015-04-06 02:21:14,630 [1] INFO MainWindow - Local Player is a level 50 Chua Engineer Soldier
2015-04-06 02:21:29,666 [1] FATAL MainWindow - System.Exception: Process must have frozen or gotten out of sync: InjectionFinishedEvent_was_never_fired
bei GreyMagic.Executor.WaitForInjection(Int32 timeout)
bei GreyMagic.Executor.ExecuteInternal(Boolean inject, Int32 timeout)
bei GreyMagic.Executor.Execute(Byte[] bytes)
bei GreyMagic.CachedCall.CallInjected64[T](IntPtr address, Object[] args)
bei GreyMagic.ExternalProcessMemory.CallInjected64[T](IntPtr address, Object[] args)
bei Buddy.Wildstar.Game.DataTable`1.GetRecord(Int32 id)
bei Buddy.Wildstar.Game.GameManager.get_CurrentMapName()
bei Buddy.Wildstar.MainWindow.<AttachProcess>d__1c.MoveNext()
2015-04-06 02:21:34,087 [4] ERROR MainWindow - Game Process has exited. Shutting down!

 

[Deathdisguise]

This log looks similar to one where the fullscreen was enabled and it wasn't able to inject properly, ensure it's fullscreen windowed or windowed?

 

[esk213]

Yep only had it in windowed mode. They thing I don't understand is, I didn't change anything about either Wildstar or the bot. Both had no updates or anything changed at all and for some odd reason it just doesn't work anymore. I tried repairing Wildstar but that didn't seem to help. For some reason, that is probably not connected to the bot at all I started getting these Memory read errors in Wildstar (without the bot running), but as far as I can remember they only started after I started the bot this evening. Since then the game keeps crashing without even trying to start the bot (it only works properly with DirectX9 for some strange reasons, which again doesn't seem to like the bot).
So I am sitting here, not having changed a thing about both these programs and yet I can't seem to use them anymore.

Things that happen:
1. I start the game, log in and load in.
2. I start the bot, no window shows up, nothing happens and I get the posted log.
3. If I try to start the Bot again, which I did at first since there wasn't a window showing, it tells me there are too many sessions so I go kill the session.
4. Now I try starting the bot a third time and it cannot attach to the game anymore, probably because the first instance of the bot already tried and failed or something like that.

No idea if that helps but I thought I'd mention it.

 

[Deathdisguise]

Run Task Manager (CTRL + ALT + DEL) and see if there's a stray Wildbuddy in the processes you can murder.

 

[esk213]

Yeah already did that.

Problem is, if there was still an instance of Wildbuddy running, I wouldn't be able to properly start the bot at all with the previously mentioned session error anyway. I am able to start the bot without this error but I'll get the other error about not being able to attach the bot to a running process. So whatever I do I keep getting either of these errors, even when killing both the process and the session on buddyauth. I tried everything that came to my mind, I probably could just "reinstall" Wildbuddy aswell but I am not sure if that would change anything since I never changed anything about that anyway. Would be the last thing I could still try.
So if anyone got any other ideas I'd be grateful to read those

(Also tried disabling my protective software, didn't seem to help.)

 

[esk213]

I just managed to start the game with DirectX11 for a few minutes and that bot worked just when. Seems to be an issue with DirectX9, at least that'd be my guess.

 

[Deathdisguise]

It's been so long, who are you again? xD

 

[esk213]

It's been so long, who are you again? xD

Just a Wildbuddy user, or I am just not understanding what you are trying to imply.

 

[Deathdisguise]

Hahaha, I was attempting a tease about how you've been unable to bot for so long that we've all forgotten. =P

 

[esk213]

Oh, I see xD

Anyway, to sum it all up, I can start Wildstar with Dx11 again after a clean install without any addons (which might have caused the issues in the first place). Didn't try to bot yet, but I think the Dx9 thing still stands. Either it's plain obvious and I just don't understand it or the bot doesn't work with Dx9. Could be considered a bug in that case. Anyway, I'll try to run the bot now.

Edit: Carbine is plotting against me, servers are down.

Edit2: Issue seems to be fixed and realizing my mistake I feel dumber than ever before. Apparently the game only crashed because I dragged the Wildstar window on my third monitor that happened to be connected to my motherboard instead of my GPU. Therefore the drivers weren't update since I only ever updated my GPU drivers and Wildstar crashed cause the drivers are older than the game itself. At least I know that I need to run the game in Dx11 mode to be able to bot.

 

[giodzho]

Hi! I've done probably a mistake when I gor new key 3 hours ago, and because of my Noob experience of using Honorbuddy, I tried to install everything correctly, but at one moment i tried to press everything that can help me to authorise my wow account with new account in Honorbuddy. so I go to website to my profile... to sessions - and KILLED my the only one - that I had bought 3 hours ago... F***
Now I cant even launch Honorbuddy i enter my key in window - it starts, but then close...
Help me plz. Who can help me. Sorry for that newbie move...

 

[Deathdisguise]

Hi giodzho! Consider making a new thread instead of posting on the end of another (it'll get more attention), and move over to the honorbuddy support forum, this is wildbuddy.