As I understand the cache folder must be separate and cannot be shared by your Clones. You must have own cache folder on each Virtual machine. That s why u link all files except cache folder.
ok, adding anohter core seemed to work better, so i'm using the win7 lite iso, 1 cpu 2 cores, but i shaliuno said 1 and 1 works the best, how are you achieving this with no lag? i'm running a i7-3770k 3.5ghz cpu with 16gb of memory
How much RAM per VM do you guys set? Anyone here able to run with 1.5Gb as guide suggests? Blank windows install takes about 300 mb, diablo 1Gb+ and demonbuddy takes 100+. However with 2Gb per VM I get constant low memory warnings and then game crashes. I can turn these warnings off by editing the registry but wouldnt this just make crashes silent?
Use the information here http://www.thebuddyforum.com/demonb...d3-crashing-common-causes-possible-fixes.html to lower the graphics of d3 more to warrant only 1gb of ram per vm.
Ya this is puzzling with VM im currently on mac with VM for db and when adding a core mine goes haywire and tells me my display driver stopped. This and occasional d3 crash associated with it, with 1 core and max the fudging ram the process goes to 90% threshold lol
Hey, I have been using this guide and the iso above to set up my only account on vmware workstation. Everything have went fine, i got the diablo 3 + buddy working... but always just for about 10 minutes. The issue i noticed is that when the bot goes to Tower Of The Cursed Level 1 (ALWAYS AT BEGINNING when he meets the first mobs), then diablo 3 client gets fixtures bugs and then it crashes within 5 seconds. I have already reinstalled diablo 3 (fresh installation from battle.net), modified the d3prefs.txt to lowest as possible and the same thing happens. I appreciate any ideas causing this nasty issue, thanks.
Amazing guide, running 3x bots easy peasy, thanks! I do have 1 question though, my only available internet option is wireless and sometimes I get disconnected for 1-5 minutes whenever my roommates microwave something. I would very much like to get a relogger since everything straight up crashes to desktop whenever this happens. Are there any working reloggers with vmware? The ones I tried won't allow me to enter into the d3 locatino field and I'm not computer savvy enough to figure out a solution.
I'ts running extremely slow, what stats is everybody using for their hardware? mine is Memory: 1 gig Processors: 1 core Asumming i'll have to add another core and bump up the ram
what is really wierd is the following. Im running 2 VMs with one bot each + a bot on the host on a Phenom II @ 3.6ghz with 12gb of ram. My Cpu was close to maxed out with that setup with an average of 90%. Now i lowered the ram of the VMs from 2.3gb to 2048 (which is a usual 2gb stick) and my cpu usage dropped to a steady 60-70%
I find it odd that everyone's reporting that their CPU is ramping up, I seem to have the opposite problem. I wasn't able to get the guide working for me (followed all the steps but when D3 goes to launch it takes a good 2 minutes just to get to the login screen, and it doesn't fare too well after that) I've got each VM with 1 Processor and 2 cores as well a 2gb ram but it still was just not wanting to work for me (and believe me, I tried following the guide several painstaking times). So as it is now i've had to just bite the bullet and make a 15-20gb VM for each bot with it's own copy of D3 and DB. With 3 VMs running my CPU usually is fine (20% tops) but my ram gets eaten up to about 8/12gb. Maybe i'm just too out of touch with the process. But I was wondering, is the whole idea that each VM has 2 Ethernet Adapters? 1 to connect to the internet and one to connect to the "Host Only" network to access the Diablo and DB files off your Main PC?
same for me, no way with only 1 core, demonbuddy eats to much CPU power now. But I think you could run 2 bots on 1 CPU 2 cores which makes 8 bots in total on i7-3770k, gonna try this now
Ok finally figured it out. If you want to run on one core you have to increase the priority of d3 to high/above normal. Theres a tool called prio saver to to that (though that did not work for me i just set it to high within yet another relogger). What seems to help too is enabling virtualisation within your bios! Im down to 30-40% CPU usage from 90%+! Guess its time to add another bot ;D Maybe add those points to the initial post?
Im stuck on step 6 on the virtual machine it doesnt show a Z: drive a little help pls.. P.S i have enabled to see hiden files and folders etc.