Jump to content

Donsch

Official Tester
  • Content Count

    16
  • Avg. Content Per Day

    0.1
  • Joined

  • Last visited

Community Reputation

2 Neutral

About Donsch

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Weird issues running multiple bots at the same time The symptom: The running bot seems to interact with all other windows, especially if background mode is checked. To be sure if this is your symptom, while running the bot in docked mode, the attached bot screen would constantly flicker between folded into the emulator and out to the side again. I couldn't use any other program while the bot was running, because the cursor was constantly being hijacked. However, in the end, the conflict was most likely a conflict with emulators. I suspect people experiencing this issue have installed many other emulators over a long period of time. The solution: (that worked for me) I also had Oracle's Virtualbox installed, so went to C:\Program Files\Oracle\VirtualBox from a command prompt and ran ".\vboxmanage list vms" which showed some VM's with an "unavailable" status. Then I ran .\virtualbox unregister [uuid] where uuid was each VM that showed to be unavailable from the previous command. A uuid looks like this: da298e62-d6f6-4e83-a8ca-918d5b9b6f00 At this point, my Memu VM's disappeared (but should have been unrelated to above), so now to get Memu's showing up again, go into C:\Program Files\Microvirt\MEmuHyperv and run MemuHyperV.exe This may be in another Memu folder, and if you don't have it, you can download it separately. Also known as MemuManager. From this utility, you select ADD Existing, and navigate to where the Memu VM's are stored, mine were at: "C:\Program Files\Microvirt\MEmu\MemuHyperv VMs" in folders named Menu, Memu_1, Memu_2, etc... After adding Memu VM's back, you need to log out of Windows and back in, a reboot was not required. The above steps removed what I believe was a conflict between Memu and Vbox, which probably stemmed from trying so many things in the past. I hope this helps someone else.
  2. Donsch

    Memu loses Wifi on a predictable pattern

    I finally got this fixed and it had nothing to do with the bot, but was probably caused by trying many versions of Menu and other emulators. I'm not sure if this will help, but here is what I did. I also had Oracle's Virtualbox installed, so went to C:\Program Files\Oracle\VirtualBox from a command prompt and ran ".\vboxmanage list vms" which showed some that were "unavailable" status. Then I ran .\virtualbox unregister [uuid] where uuid was each VM that showed to be unavailable. A uuid looks like this: da298e62-d6f6-4e83-a8ca-918d5b9b6f00 At this point, my Memu VM's disappeared, so now, go into C:\Program Files\Microvirt\MEmuHyperv and run MemuHyperV.exe This may be in another Memu folder, and if you don't have it, you can download it separately. Also known as MemuManager. From this utility, you navigate to where the Memu VM's are stored, mine were at: C:\Program Files\Microvirt\MEmu\MemuHyperv VMs in folders named Menu, Memu_1, Memu_2, etc... After added VM's back, you need to log out of Windows and back in, a reboot was not required. The above steps removed what I believe was a conflict between Memu and Vbox, which probably stemmed from trying so many things in the past. I hope this helps someone else.
  3. Memu loses Wifi on a predictable pattern First let me preface with, I'm not sure what is causing this. But I have observed a solid pattern and at least have something to report. Secondly, I never had this problem before the update, and third, I blew away all the Memu VM's and remade them from a known good backup that is several months old. Importing this master ova has fixed past problems with Memu, but nothing is working this time. Here is the pattern. The bot skips bases until it finds a target, it is after the target is found that some zooming operation happens and all of a sudden the flashing wifi bars appear on the screen. There is no recovery from this, the only way out is to stop the bot, close Memu, and restart the bot. It doesn't do it every time the bot finds a base to attack, but EVERYTIME this happens, the bot just found a base to attack. If I had to guess, I'd say the bot probably runs find for an hour or two before this happens, while I have it setup to switch between 2 or 3 accounts per bot. I actually blew away all the VM's a few times now thinking something is wrong with the VM, but with a solid pattern identified, I'm started to think the bot is causing this somehow. I also found a post about putting in a known good DNS entry instead of using AUTO, and I did that as well, which had no effect on the issue. Regards,
×