• Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Endscene hook failed & no quest bot

    Discussion in 'Honorbuddy Support' started by clanstyles, Dec 9, 2012.

    Thread Status:
    Not open for further replies.
    1. clanstyles

      clanstyles Guest

      Honorbuddy v2.5.6597.518 started.
      Logging in...
      Error - Endscene hook failed: The type initializer for 'MainDev.RemoteASM.RemoteAsm' threw an exception.
      Attached to WoW with ID 6160
      New bot added!: ArchaeologyBuddy
      New bot added!: BGBuddy
      Honorbuddy v2.5.6597.518 started!
      Character is a level 1 BloodElf Warlock
      Current zone is Sunstrider Isle
      Please wait a few seconds while Honorbuddy initializes.
      [Singular] Starting Singular v3.0.0.1271
      [Singular] Installation: integrity verififed for 3.0.0.1271
      [Singular] Determining talent spec.
      [Singular] TalentManager - looks like a None
      [Singular] Current spec is None
      [Singular] Building method list
      [Singular] Initialization complete!
      Initialization complete.


      I have it set to direct x 9. I also tried dx11. Both same error. I also don't see any other bots besides the ones listed ArchaeologyBuddy and BGBuddy. Any reason why questbot isn't listed?
       
      Last edited by a moderator: Dec 9, 2012
    2. bambam922

      bambam922 Well-Known Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      6,071
      Likes Received:
      28
      Trophy Points:
      48
      Try using the latest beta build and tell me if it still happens.

      [Beta] Honorbuddy Beta Builds

      I am not sure if this will be a definite fix, but it's worth a try.
       
    3. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      make a new Hb installation from scratch

      make sure you are running both wow and Hb as admin
      also make a try using DX9
       
      Last edited: Dec 10, 2012
    4. clanstyles

      clanstyles Guest

      I've done this, same thing. I've resintalled it 2-3 times. I've also tried the betas, no luck, same error.
      I've tried both on DX11 and DX9 and of course they have admin rights.
       
    5. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      remove:
      - microsoft .net framework 4 client profile
      - microsoft .net framework 4 extended
      - microsoft visual c++ 2010 x86 redistributable

      restart your pc,
      download the installationwizard from here
      run it as administrator.
      after the wizard is done, run windows update. And install all updates for .net & c++
      restart
       
    6. clanstyles

      clanstyles Guest

    7. CodenameG

      CodenameG New Member

      Joined:
      Jan 15, 2010
      Messages:
      38,369
      Likes Received:
      231
      Trophy Points:
      0
      Last edited by a moderator: Dec 13, 2012
    8. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
    9. clanstyles

      clanstyles Guest

      I've tried this. Re-installing the C++ run time isn't the solution.

      I've gone ahead and did some research on this specific issue. It seems if you build something for .NET 2.0 you need to specifiy in the App.config that it supports .NET Runtime 4.0 or 4.5.

      https://www.dropbox.com/s/t2iyvbpklhczoy8/shot_121213_084252.png
       
    10. bambam922

      bambam922 Well-Known Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      6,071
      Likes Received:
      28
      Trophy Points:
      48
      Update to the latest version and if you still get the error, post a log.
       
    11. clanstyles

      clanstyles Guest

      Same thing. This is the latest log. I've reinstalled .NET.
       

      Attached Files:

    12. bambam922

      bambam922 Well-Known Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      6,071
      Likes Received:
      28
      Trophy Points:
      48
    13. clanstyles

      clanstyles Guest

      This is becoming irritating and useless. The last response wasn't helpful.
       
    14. bambam922

      bambam922 Well-Known Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      6,071
      Likes Received:
      28
      Trophy Points:
      48
      Sorry everything I'm trying to tell you is not working.
      You are in the severe minority when it comes to this issue and it hardly ever pops up.

      There is something missing on your PC, and I don't know what.
      The log said something about .NET 2. I gave you a link to it.
      Didnt work? Don't get angry.

      Let me set it up via teamviewer. PM me the info.
       
    15. clanstyles

      clanstyles Guest

    16. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      do you have a wow tunel installed or another tool for WoW or something?
       
    17. clanstyles

      clanstyles Guest

      No. Applications running daily are Azure Emulator, Steam, Skype and Visual Studio 2012 (.NET 4.5).
       
    18. Tony

      Tony "The Bee" Staff Member Moderator

      Joined:
      Jan 15, 2010
      Messages:
      128,834
      Likes Received:
      571
      Trophy Points:
      113
      create a new windows user (admin) and make a try from that user plz
       
    19. clanstyles

      clanstyles Guest

      I though I should update this.

      I've solved the issue. Nobody bothered to pay any attention to what I was actually saying.

      The fix is to modify the config file for the .NET application to enable legacy support. You can do this by creating a file named: Honorbuddy.exe.config

      In this file past the following XML.

      Code:
      <configuration>
        <startup useLegacyV2RuntimeActivationPolicy="true">
          <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0"/>
        </startup>
      </configuration>
      
      Your welcome.
       
    20. CodenameG

      CodenameG New Member

      Joined:
      Jan 15, 2010
      Messages:
      38,369
      Likes Received:
      231
      Trophy Points:
      0
      thank you, thats good to know, ill report it to our developers to see if we can get this changed by default or find another way to overcome this issue all together.
       
    Thread Status:
    Not open for further replies.

    Share This Page