Jump to content
This site uses cookies! Learn More

This site uses cookies!

By continuing to use this site, you agree to allow us to store cookies on your computer. :)

  • 3.3.5 Relogger bug


    pudge
    • Version: All Product: Relogger Type: Bug Status: Fixed

     When you press stop all or change wow path, the wow window will cause an error... old version wrobot work's fine

     




    User Feedback

    Recommended Comments

    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

     

    Share this comment


    Link to comment
    Share on other sites

    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.

     

     

    Share this comment


    Link to comment
    Share on other sites

    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

     

    Share this comment


    Link to comment
    Share on other sites
    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

    Share this comment


    Link to comment
    Share on other sites
    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 ❤️

    image.png

    Share this comment


    Link to comment
    Share on other sites
    5 hours ago, Froddzei said:

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

    Relogger > General settings

    Share this comment


    Link to comment
    Share on other sites


    Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Paste as plain text instead

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...