Pudge

I also used the lua event handler trying to catch this bug, but it doesn't detect it.

4 hours ago, Droidz said:

if you can try with new update

Updated. Nothing has changed, the screen still turns black.
What could be the problem? DirectX? Game client? Did you do it as I showed in the video? Did you manage to reproduce the bug? I'm terribly interested.

@Droidz here is the fastest way to reproduce this bug: 

6 hours ago, Droidz said:

you are the first to report me this problem.

When you found bugged node blacklist zone.

FPS seems low, what return https://wowwiki.fandom.com/wiki/API_GetFramerate ? Maybe code like 

if GetFramerate() < 5 then ReloadUI() end

can resolve problem

It is very strange that I am the first, considering how often the screen "breaks" when a bot flies in places like Auchidon, Hellfire Citadel and similar "non-standard" textures (M2 and WMO). By the way, I also thought about checking the FPS, but the problem is that FPS does not always fall so low.

Still need a help

15 hours ago, Droidz said:

Hi, you have try to use option "Skip nodes in water" ? 

Yes!  But the bot sometimes just ignore this option...

SpellManager.GetCompanionInfo () always returns 0;

On 5/12/2017 at 4:45 PM, Droidz said:

GetFlyMountName() and GetFlyMountName() return random avalable Flying/ground mount name. Seem to works.

returns nothing

3.3.5a

But I would like to catch exactly the moment when the loading bar is visible on the screen

5 hours ago, Froddzei said:

Can someone tell me where to add this bot argument ? i can't find it.

Relogger > General settings

Interact.ClearTarget();

Works fine in latest version, thanks ❤️

@Droidz We need it, update pls

4 minutes ago, Droidz said:

I'll add this option

Thank you in advance! I look forward to it.

8 minutes ago, Droidz said:

new version use debugging by default to hook wow (with hardware breakpoint). When WRobot closing he remove all breakpoint (but he cannot do it when you kill process), he shoulds do it when relogger close bot (I need to check why relogger don't close correctly WRobot).

If your server don't detect directx hook you can in relogger general settings use wrobot arg:

-dx

 

 Seems it works! Many thanks ❤️

2 minutes ago, Droidz said:

new version use debugging by default to hook wow (with hardware breakpoint). When WRobot closing he remove all breakpoint (but he cannot do it when you kill process), he shoulds do it when relogger close bot (I need to check why relogger don't close correctly WRobot).

If your server don't detect directx hook you can in relogger general settings use wrobot arg:

-dx

 

Okay, will try it reight now

And I will correct, this is not relogger bug, this is wrobot bug.

And judging by the comments (more precisely by their absence), I only have this bug/error. PLEASE! Help me to understand why i get this error....

When i launch wrobot.exe by default way ( wrobot.exe shortcut ( with dx ) or from relogger ) - i have 100% wow crash when killing wrobot process. 
This is wow crash each time when wrobot process is forcedly terminated by relogger or task manager or this code System.Diagnostics.Process.GetCurrentProcess().Kill(); 
When i launch wrobot.exe no dx hook ( and from relogger with -nodx arg ) - i have no crashes.... what this mean?...

That might be the solution.... But when the bot starts with -nodx arg from the relogger, the graphics in WoW doesn't work and the bot doesn't work....

I also tried to delete d3dx libraries and installed SlimDX.... no effect, same error. Windows 7, windows 10 with all updates..... same error.

@Droidz Not planning to implement this? What do you think?

@Droidz please please please, do something like this for wotlk, that would be super wonderful.....

Default = true - this is for old profiles.

10 hours ago, Matenia said:

It's possible fairly easily, as the quest type already uses a grinder under the hood. But creating the path recorder is more complicated.
I suggest you record the path in the grinder product and just copy over the waypoints. WRobot's code basically creates a path between all hotspots using the pathfinder.

@Matenia Thanks for reply. I already tried to do that. Here is an example of how it works, the same path in the product grinder and kill and loot in the quester. Kill and Loot just stops at every point at low FPS and thinks he's stuck. Even at high FPS, it does not work as well as a grinder product.
 

This is how pathfinder create path in «Kill and loot» type with flying points. 
It generates for each point very strange «Air-to-Earth-Air» paths that look wildly suspiciously directly asking for a ban. It doesn't use «Long Move» and pauses between each point if the FPS is below 40, it works like these are ground points with type «None».

Does anyone have the same problem? I tried on different pc, and versions of windows, the same problem....

I asked my friends who do not use the robot to install the robot and check, also error

On 3/18/2020 at 10:31 AM, Droidz said:

Do you use last WRobot update?

@Droidz version 2.3.3 (32199), because newest versions are crashing wow window with 132 error when the wrobot.exe closes (at the moment when the relogger changes one 'Run' to another)

Lua.LuaDoString("ClearTarget()");
Lua.RunMacroText("/cleartarget");
Interact.ClearTarget();
None of this works.
There is also 
robotManager.Helpful.Keyboard.PressKey(wManager.Wow.Memory.WowMemory.Memory.WindowHandle, System.Windows.Forms.Keys.Escape) but this is savagery