BW buffes up and then nothing more happens In the buttom of BW I get this message: "Poi: Type: Non|Stopped" Class: Bounty Hunter Profile: Mizzless Grind 16-20 LOG: [14:53:08.250 D] Start/Stop Button Clicked! [14:53:08.250 D] BotMain.Start() called [14:53:08.250 D] Forcing profile reload. -- Temporary fix for behavior cache issues during start/stop. [14:53:08.554 D] [Trace] Element Grind is not supported yet! [14:53:08.554 N] Current bot set to Grind Bot [14:53:08.555 N] Loaded profile [E]Balmorra 16-20 grind [14:53:08.555 D] Starting bot Grind Bot [14:53:08.555 D] Added new hook [RoutineCombat] f17eacca-f13f-45b0-8666-0df58ee0de45 [14:53:08.556 D] Added new hook [HotspotPoi] f8f9eca4-4f33-41f8-91ac-a7b6a6057dfb [14:53:08.556 D] Added new hook [SellVendorPoi] e504d1b3-86e8-4c3a-8297-ba788d129187 [14:53:08.556 D] Added new hook [SetLootPoi] bb58be47-7aa1-4ff1-ac65-563804c739b5 [14:53:08.556 D] Added new hook [SetCombatPoi] 431b193c-debf-4ea5-b2f5-2a0f290523d4 [14:53:08.556 D] Added new hook [SetVendorPoi] f8143685-992a-46e4-9a60-4cad69ea51ca [14:53:08.556 D] Added new hook [SetHotspotPoi] 12fe078a-92f5-4f35-8695-25eab5652209 [14:53:08.556 D] Added new hook [SelectPoiType] 41c70ecc-4f84-45a5-ba83-e1d41b0f1ca4 [14:53:08.556 D] Spooling up bot thread. [14:53:08.556 D] Bot thread started. [14:53:51.882 D] Start/Stop Button Clicked! [14:53:51.882 D] BotMain.Stop() called [14:53:51.882 N] Stopping the bot. [14:53:51.911 N] Bot Thread Ended. Was this requested? [14:53:51.982 D] Sleeping while waiting on execution state to be available for BotMain.Stop()
Your log has been seriously truncated at the beginning. From the fragment provided, it looks like you've pressed the "Start" button, then pressed the "Stop" button before Buddywing was finished initializing. Toss the full log next time it happens, and we'll have another look. cheers, chinajade
so the load time is more than 5min? I pressed the stop button by a error so I started agen and let it be for 5min then stopped it
Hi, CooyDK, Thanks for this log. It clearly demonstrates the problem here: [17:21:12.420 N] [AutoEquip] Equipping companion! [17:21:12.420 D] [AutoEquip] Currently equiped EquipDroidUtility slot's score is: -1 [17:21:12.425 D] [AutoEquip] Currently equiped EquipHumanEar slot's score is: 88 [17:21:12.425 D] [AutoEquip] Currently equiped EquipHumanImplant slot's score is: -1 [17:21:12.425 D] [AutoEquip] Currently equiped EquipHumanRelic slot's score is: -1 [17:26:36.261 D] Start/Stop Button Clicked! Something fundamental is definitely amiss. The first thing I would try is to make sure your Windows, .NET runtime, and C++ are up-to-date. The second thing could be a bug in DefaultCombat. I see a very small issue in DefaultCombat's Mercenary/Arsenal combat that shouldn't be a problem, but disturbs me. I'd suggest seeing if you can get any further using WingIt, or JoeBrewski's http://www.thebuddyforum.com/buddy-...pyrotech-bodyguard-commando-combat-medic.html (although, I'm not sure it supports the Arsenal spec at the moment). The third thing I would try is a fresh install. If you do, please put Buddywing in C:/Games/Buddywing/--not on your desktop, and don't use a path that has 'spaces or 'periods' in it (e.g., .../BuddyWing 1.0.946.339/...). If none of these remedies work, I'd crank the log level to max, produce another and let us have another look. Alternatively, you can contact Tony using the Honorbuddy Service, and see if he can speed you to a solution. cheers & let us know how it goes, chinajade
View attachment 2012-11-13 20.20.txt New install, running latest C++ & Framework 1.1 & 4.0 I disabeled Auto Equip, still the bot aint moving.
Hi, CooyDK, The log doesn't reflect any of the things you were asked to try (e.g., use of WingIt, place the new install in a C:/Games/Buddywing/ directory, log-level set to max, etc.). So basically, no new information is available to analyze. One other thing to check--is your toon on planet-side Balmorra (not on your ship)? I'm going to leave you to get with Tony at this point. cheers, chinajade
I cant make the program give you any more info. This is a 10 min log, how much longer should it be? And yes iem on Balmorra. But 1. I installed WingIt in a new place 2. Tryed diffrent routines 3. Delite C++ & Framework and re-installed it 4. Ran a regristry cleaning Anything more I should try? Also it seems that after I press start there is a long period befor the logging starts / the bot starts up. This can range from a few sec to a few minuts.
To which we responded in post #7: and in post #9: You're most welcome, and good luck with your problem. cheers, chinajade
running buddy from the folder on your desktop containing its version number is a bad thing ? That is where an how I run mine :/ Is there a post somewhere that has all these small but important things I am unaware of, I also just found a post about core affinity also.
Hi, Deadlybot, This is just stuff we "figure out over time". The fault lies largely with Windoze for this list. Some versions of Windoze afford more 'protections', or treat differently, items placed in certain folders--Desktop, and "Program Files" are two good examples. Some versions of Windoze have problems with 'spaces' or 'periods' in a directory component of a pathname. It all depends on which version of Windoze you're using (and maybe the patch level). The behavior may change whether you've UAC turned on or off, "advanced sharing" on or off, whether your underlying file system is FAT32 or NTFS, and a myriad other Windoze configuration items. (By the way, we always recommend UAC 'on'--'off' is just irresponsible and welcomes getting your Windoze system rooted or infected). We've been recommending the list above for several years. We noticed the same problems with Honorbuddy. These recommendations are largely defensive. We know that certain versions or configurations of Windoze have problems with the things we describe, but not all. They may fix your problem, they may not. I would say the recommendations fixed Honorbuddy user problems about 70% of the time they were recommended. Similarly, the recommendations have help a number of our Buddywing community members repair their problems. Good troubleshooting practices require we removing potential problems caused by Windoze first, then we move forward to other areas. You have to recall that a bot (as a Windoze application) is very very different than almost any other Windoze application (except perhaps for writing a debugger). Most normal applications just launch and are off-and-away. On the other hand, when a bot launches, the first thing it must do is attach to another process and start peeking and poking at it, and try to synchronize with the other process using conventional and unconventional techniques. This makes the nature of a bot program significantly different than any other application you run on Windoze. And consequently, a bot program is more sensitive to Windoze quirks and additional 'protections' than most other programs. cheers, chinajade
Thanks for the concise explanation, I will remember to put the new version in its own folder in the root directory on my pc. I am very methodical in getting things to work so this is one more thing I can try to get my buddywing to perform better for longer. As of now getting it to run longer seems to be my only problem.
Ok now I seem to get a new error after I completly deleted BW and c++ and the reinstall everything. When I start BW I get a error: View attachment 2012-11-19 15.39.txt
