Patch 8.1.5 DirectX [Archive]

MiRai

03-12-2019, 05:13 PM

As of patch 8.1.5, there is now a new version of DirectX 11 available in the game client: Legacy.

https://us.forums.blizzard.com/en/wow/t/world-of-warcraft-8-1-5-graphics-api-details/121541

In some brief testing, DX11 now performs sub-par for me, while DX12 and DX11 Legacy (DX11L) perform fine.

I just wanted to point this out to everyone in case you're experiencing issues, but in the case of ISBoxer users, you may be forcing DX11 through the Game Profile attached to your Characters. If you are, then you are using a version of DX11 that may now perform poorly for you, as it does for me (both with and without Inner Space).

So, ISBoxer users will want to update Inner Space to build 6423+ by simply restarting the program and clicking "patch these files," as well as update ISBoxer to build 42.10.0321.1 through the Help > About menu.

Other than that, you'll probably want to make sure you're using DX11 Legacy, either through the in-game setting, or through the new Game Profile (https://giant.gfycat.com/PoliteQuaintHedgehog.webm) which should now be available if you updated both programs.

Also, if you were/are using DX12, then nothing has changed.

Also, this patch, like others, has reset your video settings, and so, assuming your hardware is capable, your game clients are defaulting to DX12 (including W7 users (https://blogs.msdn.microsoft.com/directx/2019/03/12/world-of-warcraft-uses-directx-12-running-on-windows-7/)), which means you may also experience poor performance due to VRAM limitation.

Finally, if you're experiencing further issues, then please take a look on the Blizzard forums (https://us.forums.blizzard.com/en/wow/c/support/technical-support), because, more than likely, it's already been asked, seeing as there has been a flood of users with issues since the servers came up.

EDIT1: Working parameter found; instructions added.
EDIT2: Inner Space updated.
EDIT3: Further clarification.
EDIT4: Another update because Lax keeps changing things.

Ellay

03-12-2019, 10:59 PM

Thanks for posting this Mirai, just setting this up before even logging in helps me get the most out of my limited night without having to toy with issues.

MiRai

03-12-2019, 11:18 PM

Thanks for posting this Mirai, just setting this up before even logging in helps me get the most out of my limited night without having to toy with issues.
No problemo /Arnold

Lax also posted a, perhaps, more detailed set of instructions (including images) for adjusting some settings above, over on the ISBoxer forum.

http://isboxer.com/forum/viewtopic.php?p=46219#p46219

Onceprince

03-13-2019, 05:39 PM

Ughmahedhurtz

03-13-2019, 06:01 PM

I have 16gb or ram, and played with 10 wows easily, now i cant at all, 8 maximum. Are they increase ram per one wow or what? Do u have some similar problems, i did everything properly change also to my very low seting graphics etc.
Did you make sure you selected DX11 Legacy in your settings? Verify it in-game on the clients just to be sure.

MiRai

03-13-2019, 06:12 PM

I have 16gb or ram, and played with 10 wows easily, now i cant at all, 8 maximum. Are they increase ram per one wow or what?
Yes, some people who are running 16GB of RAM in their machine have been reporting problems with increased RAM usage.

Do u have some similar problems, i did everything properly change also to my very low seting graphics etc.
I don't normally track the RAM usage of the game client(s) because I have more than enough and will likely never have an issue with running out of it. So, unfortunately, I can't say whether or not I'm seeing increased RAM usage because I don't normally track it to begin with.

However, as Ugh pointed out, if you're using an API other than the Legacy option, then you can, most definitely, expect increased RAM usage (https://i.imgur.com/D3rzkar.png).

Onceprince

03-13-2019, 06:41 PM

how to swithc on legacy mode, do i need to change on wow advanced option also, coz there is opet to switch to dx11 legacy optin

I did in wow dx11 legacy option

MiRai

03-13-2019, 06:47 PM

how to swithc on legacy mode, do i need to change on wow advanced option also, coz there is opet to switch to dx11 legacy optin
The instructions are literally the first post of this thread.

CMKCot

03-13-2019, 08:01 PM

they made the dx12 mode even more resource hungry, im on a 2080ti (11gb vram) + 32gb ram + 7900x cpu and i get some weird freezes that make clients unplayable, they have to relaunched.

the screen gets stuck on a frame and doesn't recover. i can see that the client is still online cause the other clients can see him online, but cant recover. seems similar in a way to the bfa launch bug where innerspace would lose its "hooks" on a windows if it got the full screen transparency effect.

Lax

03-13-2019, 08:13 PM

For ISBoxer users, all you need to do is update Inner Space to build 6420, which is now available. Close and restart Inner Space and when it pops up and offers build 6420, click "Patch these files".

This build forces WoW to use the DirectX 11 Legacy mode instead of DirectX 11 (though it is still allowed to use DirectX 12). Once the new DirectX 11 mode is fully supported by Inner Space (without the reported crashes, missing things, etc), I will release another update to re-enable the new DirectX 11 mode.

MiRai

03-13-2019, 08:17 PM

CMKCot

03-13-2019, 10:21 PM

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.

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.

Boostab

03-13-2019, 10:34 PM

Thanks for the heads up I did what you had mention on the ISBoxer forum and got it up and running thanks again .

CMKCot

03-13-2019, 11:00 PM

small update, could it be that Innerspace is for some reason trying to hook into the gpu output of netflix?

look at this:

https://www.dual-boxing.com/attachment.php?attachmentid=2141&stc=1

this error popped up while trying to change tabs on firefox while chrome was open in the background.

Lax

03-13-2019, 11:13 PM

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

CMKCot

03-14-2019, 12:47 AM

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

(https://send.firefox.com/download/eb5b1d1ec3/#GL_PHYJsYUj1M7_GmbHoGg)
windows even take keyboard input as you can see.

Onceprince

03-14-2019, 03:27 AM

Does that mean i dont need to use anything that is explained in this post, i mean that MiRai explained?

For ISBoxer users, all you need to do is update Inner Space to build 6420, which is now available. Close and restart Inner Space and when it pops up and offers build 6420, click "Patch these files".

This build forces WoW to use the DirectX 11 Legacy mode instead of DirectX 11 (though it is still allowed to use DirectX 12). Once the new DirectX 11 mode is fully supported by Inner Space (without the reported crashes, missing things, etc), I will release another update to re-enable the new DirectX 11 mode.

Tanis Longbow

03-14-2019, 04:20 AM

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)?

WOWBOX40

03-14-2019, 05:10 AM

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.*

MiRai

03-14-2019, 12:36 PM

I've updated the instructions again after today's Inner Space update, and they should be easier to follow.

JohnGabriel

03-14-2019, 03:27 PM

In some brief testing, DX11 now performs sub-par for me, while DX12 and DX11 Legacy (DX11L) perform fine

I was using DX12 before the patch, should I switch to DX11L?

My computer was borderline able to perform before the patch. Now in order to stop the windows closing I had to lower my slaves video settings again. But everything seems to be working ok now. Main at 7, slaves at 2 with max 15 FPS in background.

I was planning on just waiting a couple more days to see if the after-patch hotfixes helped any.

MiRai

03-14-2019, 05:56 PM

I was using DX12 before the patch, should I switch to DX11L?
If you want to save on hardware resources, then DX11L is the way to go, otherwise nothing has changed with DX12 in respect to Inner Space.

JohnGabriel

03-14-2019, 11:07 PM

A green MVP in the tech support forums (https://us.forums.blizzard.com/en/wow/t/wow-increased-ram-usage-after-patch/122780/4) says

One thing I noticed with the reset was that “Triple Buffering” is set as enabled. I had mine set to disabled and this caught my eye. I did some experimenting. That setting jumped my total Ram usage by a good amount - around 500mb. Try disabling there.

Might be something for you to take a look at if you're still seeing problems in DX11L

Also for those like me who were waiting to switch, a blue poster in the tech support forums (https://us.forums.blizzard.com/en/wow/t/day-3-crashing-still/124326/2?u=shame-bleeding-hollow) while discussing crashes similar to those here said

Looking into this it appears the crash is related to a DirectX12 issue our developers are actively looking into resolving via a future patch or hotfix.

Its coming soon, but it doesn't seem a good idea to keep using DX12 right now. IsBoxer can't help us with a bug in the game.

MiRai

03-14-2019, 11:41 PM

Also for those like me who were waiting to switch, a blue poster in the tech support forums (https://us.forums.blizzard.com/en/wow/t/day-3-crashing-still/124326/2?u=shame-bleeding-hollow) while discussing crashes similar to those here said

Looking into this it appears the crash is related to a DirectX12 issue our developers are actively looking into resolving via a future patch or hotfix.

Its coming soon, but it doesn't seem a good idea to keep using DX12 right now. IsBoxer can't help us with a bug in the game.
That's a pretty specific crash for DX12 related to only those with AMD GPUs that aren't using updated drivers, and are still running an older version of Windows 10. Not only that, but, from their report, they weren't even able to start the game client, so... if you're experiencing such an extreme issue, then it's apparent right from the get-go that you have something to fix. Otherwise, if you were using DX12 before patch 8.1.5, and can still use it now, then I would expect that you're fine to continue using it.

Azzbringer

03-15-2019, 11:01 AM

Wizeowel

03-16-2019, 11:23 AM

For me the ram usage is more or less the same. I run 15 clients on 1 pc with 32gb ram.
But since the patch my gpu memory usage has gone from 60-70% to 100% despite using same settings on all clients. The results are same in DX11 and DX11 legacy.

I'm now experiencing short freezes on all clients every few minutes.

I was having this as well - Dedicated GPU memory was at 10GB and Shared GPU at 2GB. Random visual freeze, although the affected character would still follow and cast. I tried disabling Triple Buffering in the advanced settings. Everything seems fine, now back to 7.8GB dedicated GPU. I hope that's the solution.

Azzbringer

03-16-2019, 08:11 PM

I was having this as well - Dedicated GPU memory was at 10GB and Shared GPU at 2GB. Random visual freeze, although the affected character would still follow and cast. I tried disabling Triple Buffering in the advanced settings. Everything seems fine, now back to 7.8GB dedicated GPU. I hope that's the solution.
I think I did something similar, it's working better now. I played around with different settings so I can't tell for sure what worked.

This makes me wonder, does having 2gpus help out with vram in regards to how many games you can run?
Right now 8gb seems not to be enough any more to run more than 15 clients.

MiRai

03-16-2019, 09:41 PM

This makes me wonder, does having 2gpus help out with vram in regards to how many games you can run?
If you're using SLI, then no, VRAM is not pooled together, it is mirrored across the GPUs.

However, if you have multiple GPUs each hooked up to their own display with a custom Window Layout to avoid cross-GPU "contamination," then yes.

Azzbringer

03-17-2019, 04:12 AM

If you're using SLI, then no, VRAM is not pooled together, it is mirrored across the GPUs.

However, if you have multiple GPUs each hooked up to their own display with a custom Window Layout to avoid cross-GPU "contamination," then yes.
So the GPUs would still be on the same motherboard, just not connected to one another?

MiRai

03-17-2019, 12:48 PM

So the GPUs would still be on the same motherboard, just not connected to one another?
Assuming you're running a single-PC setup, yes, but we're getting a bit off topic here. If you wish to know more about "splitting the load," then there is an entry on the ISBoxer Wiki (http://isboxer.com/wiki/GPU_Management) (which could probably be slightly updated at this point), or, if you would like to discuss this further, then please create a new thread in the appropriate sub-forum.

omegared

03-17-2019, 01:04 PM

DX11L is great for my old pc! Very annoying Blizz keep changing the settings, but at least i can run around Boralus Harbor again.

Azzbringer

03-17-2019, 08:53 PM

Assuming you're running a single-PC setup, yes, but we're getting a bit off topic here. If you wish to know more about "splitting the load," then there is an entry on the ISBoxer Wiki (http://isboxer.com/wiki/GPU_Management) (which could probably be slightly updated at this point), or, if you would like to discuss this further, then please create a new thread in the appropriate sub-forum.

Apologies, there's just so much to learn about the whole multiboxing subject. I get too excited. 😌
I will check out the Wiki. Thank you.

Altsoba

03-22-2019, 10:46 AM

MiRai

03-22-2019, 12:15 PM

Do I need to manually revert something?

Anyone having the same issue?
Any idea on how to solve it?
Any additional info I can provide for a better help?
The main focus of this thread was to inform people about the change to DirectX, so the obvious question is:

Which version of DirectX do you have the game set to use?

WOWBOX40

03-22-2019, 01:37 PM

Hello everyone.

When Mirai (thank you) posted this link - http://isboxer.com/forum/viewtopic.php?p=46219#p46219 - I followed the instructions and was just perfect.

Today I updated ISBoxer and patched InnerSpace and the animation is staggered (to a non-playable point) on the 5 clients (running 4 on graphic quality 1 and 1 in graphic quality 10) .
I changed nothing else on the settings.

Do I need to manually revert something?

Anyone having the same issue?
Any idea on how to solve it?
Any additional info I can provide for a better help?

Thank you very much.
A.

1.
Start innerspace.
Rightclick the red taskbar ikon...configuration....game configuration....choose the game from the drop down menu arrow.....click profiles for wow at the botton...choose the dx11legacy one...make sure it says -d3d11legacy at the main executable parameters. If it didnt, edit it and then close the profile...then choose apply...

2.
Launch the character set.

Dont log on.

Doublecheck manually each game: change as needed back to dx11legacy and lower / adjust the gfx settings. Disable everything you can on the advanced page, can help.

Exit the games and relaunch the characterset.
Repeat as needed to get all saved.

3.
Enter isboxer and under each character, select the dx11legacy game profile.
Export...

Sorted... most likly.

Altsoba

03-25-2019, 01:30 PM

Hello everyone and first of all, thank you.

WOWBOX40, your step by step solved it.

Cheers.
A.

lilithwalker

03-27-2019, 08:17 AM

want to say something about the ram now, since that patch i found my 6 clients eating my 16gb, 2gb each of them, but after 30 minutes or so, they get to 700mb, don't know what is causing this or anything, but they work great, i'm usually in the same spot, so maybe thats why, but even going to orgrimar doesnt get the ram past 1.2gb each, my videocard is always full, so i will try that triple buffering later today, i registered since a lot of stuff here is helping me a lot.