Jump to content

eafa

Members
  • Posts

    65
  • Joined

  • Last visited

Bug Report Comments posted by eafa

  1. I messaged you a 4min video of how it happens from the launch, please watch it...

    I'm sure the problem isn't that big and you can fix it easily, just find out why it restarts all the time.

    Thank you in advance.

  2. I do it now but it took me a ton of time to figure out this problem and it was all good before July updates, you have changed something in all WR versions in late June-July and after this WR can't work properly with Proxycap.

    Proxycap is the best proxifying software so I will keep using it but now I have to avoid WR proxification then it works fine... 

    It's not normal anyway in my opinion. There shouldn't be such incompatibility between WR and Pcap.

  3. Logs are fine, no errors, they are similar to normal logs, I've updated 335 version today and same thing happens, it just crashes instantly after launch.

    one of the logs, others are just longer but there is no sign of any error

    [D] 17:31:00 - [Info] Log file created: 27 июл 2017 17H31.log.html
    [D] 17:31:00 - [Info] WRobot Version: 1.7.5 (34661) for wow: 3.3.5a_12340
    [D] 17:31:00 - [Info] Offical website: https://wrobot.eu/
    [D] 17:31:00 - [Info] Operating System Details: Microsoft Windows NT 6.2.9200.0
    [D] 17:31:00 - [Info] Lang: Русский (Россия)
    [F] 17:31:00 - [Memory] D3D9 found: 6A 20 B8 A9 78 63 69 E8 9E 97 
    [F] 17:31:00 - [Memory] D3D11 found: 8B FF 55 8B EC 83 EC 58 A1 14 
    [D] 17:31:00 - [Memory] D3D9 used

    previous versions work fine, problem is only with latest updates

     

  4. BSOD again, no driver module or anything, just this : 

    STOP: 0x000000F4

    Also there is big wow mouse pointer in the middle of the screen which means that wow was full screen 800*600 or 1024*768 - default setting, which happens exactly when I try to launch more than 1 wow instances at the same moment. Wow just goes default probably coz Config.wtf is busy at that moment.

     

  5. Sorry for the confusion, my problem was caused by a .dll plugin which was compiled with the previous version, all good without it.

    But ! I still have another problem - my PC may get BSOD and reboot accidently while running 3+ wrobot+wotlk instances, it also seems that it happens on mass relog/restart, for example when server goes down or works unstable, I've also noticed that relogger doesn't "lock" wow executable while loading, hbrelog does such thing and it lowers to minimum any loading collisions. Can you add a checkbox for "loading lock" to allow only 1 wow instance to load at once ?

  6. There is another issue now, when relogger is launching all profiles using "Start Checked" (8 atm) , 1 or more wow instances would load with default setttings (fullscreen, default graphics, etc) so a minor delay between launchs is needed, atleast 1 sec.

×
×
  • Create New...