What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal
RebornBuddy Forums

Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Wildbuddy in Virtual Machine

M

mfaiola

New Member
Joined
Aug 28, 2015
Messages
18
I can't get this to work inside a virtual machine at all, is it not possible?
This is the error I receive and it says the direct X cant be wrapped if it already is.
Perhaps I should try to update the Nvidia Drivers within the virtual machines?

Is there any way we can get a version that will attach to a process that is already wrapped?

Trying to make use of all the keys that I purchased.
Thanks!


2015-10-22 05:38:42,797 [1] INFO MainWindowViewModel - WildbuddyBETA 0.1.589.288 starting...
2015-10-22 05:38:42,797 [1] INFO MainWindowViewModel - CPU Architecture: x64
2015-10-22 05:38:42,798 [1] INFO MainWindowViewModel - Process Architecture: x64
2015-10-22 05:38:42,798 [1] INFO MainWindowViewModel - OS: Windows 7 Ultimate x64
2015-10-22 05:38:42,798 [1] INFO MainWindowViewModel - OS Version: Microsoft Windows NT 6.1.7601 Service Pack 1
2015-10-22 05:38:42,798 [1] INFO MainWindowViewModel - .NET Runtime Version: 4.0.30319.17929
2015-10-22 05:38:42,798 [1] INFO MainWindowViewModel - System Memory: 1.62 GB Available
2015-10-22 05:38:42,798 [1] INFO MainWindowViewModel - CPU Cores: 1
2015-10-22 05:38:42,798 [1] INFO MainWindowViewModel - Application Uri: C:\Users\<User>\Desktop\WB FOR VM
2015-10-22 05:39:00,466 [1] INFO MainWindow - Logging in...
2015-10-22 05:39:06,195 [1] INFO MainWindow - T: 5247496909840980740 H: 2065382179
2015-10-22 05:39:06,203 [1] INFO MainWindow - Region: na
2015-10-22 05:39:07,096 [1] DEBUG ProcessWrapper - Mutex.TryOpenExisting on PID 620
2015-10-22 05:39:07,322 [1] DEBUG ProcessWrapper - Mutex.TryOpenExisting on PID 620
2015-10-22 05:39:10,216 [1] FATAL ProcessWrapper - Could not find DX11 in process!
GreyMagic.DirectXNotFoundException: Could not find DX11 in process!
at GreyMagic.DirectX..ctor(MemoryBase mem, Boolean dx9)
at GreyMagic.ExternalProcessMemory.Init(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm, IntPtr hookFunc, Boolean defaultCacheValue, Int32 copyBytes, Boolean veh)
at GreyMagic.ExternalProcessMemory..ctor(Process p, Boolean startupExecutor, Boolean dx9, Boolean startupRasm)
at Buddy.Wildstar.Engine.ProcessWrapper..ctor(Process proc, Boolean readOnly, Boolean dx11)
2015-10-22 05:39:11,505 [1] WARN MainWindow - Could not find DX11 in process!
2015-10-22 05:39:11,505 [1] WARN MainWindow - Attempting DirectX 9...
2015-10-22 05:39:23,702 [1] ERROR Application - UNHANDLED DISPATCHER EXCEPTION
2015-10-22 05:39:23,702 [1] ERROR Application - System.InvalidOperationException: Cannot create a process wrapper to a process that is already wrapped. [Mutex was not created]
at Buddy.Wildstar.Engine.ProcessWrapper..ctor(Process proc, Boolean readOnly, Boolean dx11)
at Buddy.Wildstar.MainWindow.<AttachProcess>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Buddy.Wildstar.MainWindow.<HandleProcessSelectorRefresh>d__13.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__0(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
2015-10-22 05:39:41,627 [1] INFO MainWindow - Selected new bot: Profile Bot v0.0.0.1 by Bossland GmbH
2015-10-22 05:39:48,840 [Pulsator Thread] FATAL Pulsator - Can not start! No combat routine is selected!
2015-10-22 05:39:48,841 [Pulsator Thread] DEBUG Pulsator - System.Exception: Can not start! No combat routine is selected!
at Buddy.ProfileBot.ProfileBot.OnStart()
at Buddy.Wildstar.Engine.Pulsator.()
2015-10-22 05:39:48,849 [Pulsator Thread] ERROR Application - UNHANDLED DOMAIN EXCEPTION
2015-10-22 05:39:48,849 [Pulsator Thread] ERROR Application - System.NullReferenceException: Object reference not set to an instance of an object.
at Buddy.ProfileBot.ProfileBot.OnStop()
at Buddy.Wildstar.Engine.Pulsator.()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()
 
Last edited:
If anyone has any experience attempting to run WB in VMWare 10 please feel free to chime in.
I've ran other types of bots within virtual machines so I was assuming this is an error generated from the WildBuddy core code and could possibly have a some modifications to allow attempting to connect to a process that is already wrapped.

I suppose I will pull out some old hardware for now and run another physical machine, but I was looking to buy even more licenses and run them within virtual machines.

Thanks again Apoc and friends! :D
 
Last edited:
Seems to be an issue with using directx 9 possibly. Forwarded a post to the BETA thread.
 
You must log in or register to reply here.
Back
Top