Are you trying to change your video settings when the client freezes? What you describe is what happens to many after trying to change the video settings while using DX12.Originally Posted by CMKCot
Are you trying to change your video settings when the client freezes? What you describe is what happens to many after trying to change the video settings while using DX12.
Do not send me a PM if what you want to talk about isn't absolutely private.
Ask your questions on the forum where others can also benefit from the information.
Author of the almost unknown and heavily neglected blog: Multiboxology
yeah, i used to have that happen when changing video settings, but now im just playing regularly. (and if i change vid settings i use notepad)
i have it narrowed down to when im running Netflix and its damn DRM riddled player does its black magic. seems that the player does something to the GPU, akin to a resolution change, and Innerspace craps itself.
tried using a 1080 and it works fine when watching and seeking video on netflix, plug in the 2080ti and its a disaster.
to anyone reading this, stay away from the 2080ti, worst purchase ever. had to clock my main screen from 100mhz down to 60 because it would BSOD or kill the second monitor, has weird screenflashes when rendering webpages (second RMA, so its a thing with the GPU, not a problem.) and RTX is the dumbest feature since hairworks. and with this last dx12 update 5 clients @1440p eat so much vram im using up most of the 11gb on the card.
im having to pirate movies and series again so i can watch them on VLC and not have Netflix give me cancer.
sorry for the rant, good to see the legacy DX gets support, will try it once the support is there.
Thanks for the heads up I did what you had mention on the ISBoxer forum and got it up and running thanks again .
small update, could it be that Innerspace is for some reason trying to hook into the gpu output of netflix?
look at this:
this error popped up while trying to change tabs on firefox while chrome was open in the background.
Uh, are you launching chrome and/or firefox via Inner Space? It only loads into processes that it launches, and processes launched by those that it launches.
So the question is what is launching chrome.exe, that was launched by Inner Space? ... and why
nope, only wow is being run. btw of all the crashes its the first time i see that msg about chrome.
been testing some more and it seems to be triggered even if i don't have a window running netflix. all i have to do is heartstone or use a portal and some screen will randomly crash. (lower change with only the games running, but its still there)
the game keeps running, for example if use another character to summon a mount with a vendor and i hover the mouse on the crashed window over the spot where the vendor would be, i see the icon change and if i click i hear the gfx of the vendor window. so the game is not interrupted, the frame seems to get frozen and overlays the actuall game screen. its similar to the bug at the start of BFA, where the screen would glitch similarly and at the same time innerspace would lose control of the window.
i managed to crap it all up by trying to run OBS, heres the video:
https://send.firefox.com/download/eb5b1d1ec3/#GL_PHYJsYUj1M7_GmbHoGg
windows even take keyboard input as you can see.
Last edited by CMKCot : 03-14-2019 at 12:51 AM
Does that mean i dont need to use anything that is explained in this post, i mean that MiRai explained?
I have updated my Innerspace to 6420, created a new team (3 boxing). When I log in and check the settings all clients are running DX12 and not DX11 Legacy?
I tried the work around yesterday (d3d11legacy or something similar) and was running fine, after the Innerspace update this morning struggling to get 3 box team to work.
If the new Innerspace update 'forces' my clients to use DX11 Legacy, is there something overriding it setting it back to DX12 which I should be changing (within the game possibly)?
After patching isboxer, you have to manually doublecheck if the settings under "configuration" etc is set to legacy, then also go into isboxer and change it to dx11 on each and every character, then export the settings.
http://isboxer.com/forum/viewtopic.php?p=46219#p46219
Then, after you have launched all the games, you have to manually enter each and every game (no need to actually enter passwords and then enter the game with the character), change to dx11legacy as needed and lower settings from 7 to 1 etcetcetc to your liking.
Close down the games and relaunch the character set, multiple times, untill all gets the new settings are stored and working.
With all at settings 1, dx11legacy and the nice macro switch so the slaves get much lower grafix, 5 games = uses 14gb RAM (when stationary in a calm zone with no other players in sight). This seems to be 1 gb or so more than last patch. If you have 16 gb RAM and doing something intense, it might increase the RAM so it goes up to your max, if you have 16 gb. This may be the reason games can suddenly freeze or just "go away / close it self down with no warning".
If you run 5 games, everything on lowest possible settings and dx11legacy: get atleast 32 gb RAM from now on, just in case.
10 games = 33 gb RAM in use, when stationary in a calm zone with no other players in sight.*
Last edited by WOWBOX40 : 03-14-2019 at 05:20 AM
I've updated the instructions again after today's Inner Space update, and they should be easier to follow.
Do not send me a PM if what you want to talk about isn't absolutely private.
Ask your questions on the forum where others can also benefit from the information.
Author of the almost unknown and heavily neglected blog: Multiboxology
Posting Rules
Reply With Quote
Connect With Us