I had problems with Innerspace in combination with MQ2 from the start. Temporary solutions like using version 1.15 for Win7 and 1.16 r6308 for Win10 seized to work properly since some months. So I lived with constant crashes on Win7 when logging out. Since about 3-4 MQ2-Patches it has gone completely nuts. Constant crashes while logging out was standard. So I researched and found that the "always" problematic plugin "/autologin" seemed the cause. I disabled it since then. But after the last patches this didn't helped either (whatever changed in MQ2). I read that there was an issue with Innerspace and MQ2 solved - so I updated Innerspace to the latest version - that was perhaps a fault. I simply gave up to send in bug reports - out of pure resignation.
While Innerspace network capability is completely unreliable, I switched all boxes mostly back to EQBC (1.3, Emule version) which has its own issues (1 out of 31 at logging gets wrong name "LOGIN_"). All other EQBC-Versions I tested so far are so unreliable in heavy use that I quit using them (I am talking about raid configs over 3 computer systems with 18-31 toons, they seems stable with 3-6 toons, but at a certain data flow somethings borks easily - Emules Version can handle it but still has the login-issue if about 31 toons login at once with the usual keybinding).
Now logging in simply crashes about 3 of 9 toons. Disabling MQ2 and enabling after logged in solved that part. But sometimes the system "quits" EQ2-tasks at random (!) while simply standing in the guild hall. No crash dingdong, no message for reason, simply vanished while loading missing toons (even on the second system under Win10, while loading on Win7).
Logging in with EQ (without MQ2/Innerspace): works without problems
What in gods name did change the last 3-4 patches at MQ2 - perhaps in combination of Innerspace?
Or did DGB install a check for MQ2 now to kick the tasks?
Today I need 3 complete tries on one system (9 toons) to get the box running.
Addon: I checked the hardware/software (4 different antivirus/trojan checkers, Win7-updates, NvidiaGTX-updates, kick of unnecessary tasks in the background/minimal config, hardwarechecks 24h ramtest, heattest, stabilitytest - everything was ok, like usual for a 24/7 rendering system - using of course SSD/Samsung, 24GB Ram, Nvidia680GTX, Asus Extreme MBP, 4/8-Core Intel, all watercooled and freezing -> rockstable config renders a complete week multiple tasks without problems).
While Innerspace network capability is completely unreliable, I switched all boxes mostly back to EQBC (1.3, Emule version) which has its own issues (1 out of 31 at logging gets wrong name "LOGIN_"). All other EQBC-Versions I tested so far are so unreliable in heavy use that I quit using them (I am talking about raid configs over 3 computer systems with 18-31 toons, they seems stable with 3-6 toons, but at a certain data flow somethings borks easily - Emules Version can handle it but still has the login-issue if about 31 toons login at once with the usual keybinding).
Now logging in simply crashes about 3 of 9 toons. Disabling MQ2 and enabling after logged in solved that part. But sometimes the system "quits" EQ2-tasks at random (!) while simply standing in the guild hall. No crash dingdong, no message for reason, simply vanished while loading missing toons (even on the second system under Win10, while loading on Win7).
Logging in with EQ (without MQ2/Innerspace): works without problems
What in gods name did change the last 3-4 patches at MQ2 - perhaps in combination of Innerspace?
Or did DGB install a check for MQ2 now to kick the tasks?
Today I need 3 complete tries on one system (9 toons) to get the box running.
Addon: I checked the hardware/software (4 different antivirus/trojan checkers, Win7-updates, NvidiaGTX-updates, kick of unnecessary tasks in the background/minimal config, hardwarechecks 24h ramtest, heattest, stabilitytest - everything was ok, like usual for a 24/7 rendering system - using of course SSD/Samsung, 24GB Ram, Nvidia680GTX, Asus Extreme MBP, 4/8-Core Intel, all watercooled and freezing -> rockstable config renders a complete week multiple tasks without problems).