FAQ  •  Register  •  Login

Directx 11 problems

Moderator: MiRai

<<

ehalvorson

Posts: 5

Joined: Sun Jul 08, 2012 5:12 am

Post Sun Jul 08, 2012 5:28 am

Directx 11 problems

I am having issues getting direct x 11 to work with WoW and ISBoxer/Inner Space 1.11 build 5642.
Video Card is ATI M7820.

I have tried adding the "-d3d11" main executable parameter to each of the game default profiles, I have tried enabling directx 11 under advanced options on each account etc and i always get the same result. The first slot opens up with the directx setting enabled under options, but the window ends up in 800x600 resolution, it does not expand to fill the top window layout position... and none of the other slots launch.

Ive even blown away all the config files, let iSBoxer recreate them with the export... and then just adding the -d3d11 setting to each of the game profiles under the inner Space configuration.

Anybody have a set of detailed steps for enabling directx 11 for WoW?
<<

MiRai

User avatar

Vibrant Videographer

Posts: 3010

Joined: Fri Nov 20, 2009 3:30 pm

Post Sun Jul 08, 2012 6:24 am

Re: Directx 11 problems

Can you open up WoW by itself and use DX11?
Are you trying to use multiple monitors or an external monitor for this?
Is the setting in WoW's video settings set to Primary for the monitor?

I've never dealt with a FirePro card before... Do they use special drivers?
<<

ehalvorson

Posts: 5

Joined: Sun Jul 08, 2012 5:12 am

Post Sun Jul 08, 2012 7:10 am

Re: Directx 11 problems

Yes I can use Direct x 11 if I open WoW by itself.
Single Monitor -> Laptop Screen
Yes Video Settings are set for Primary for the Monitor

There FirePro drivers seem like any other Catalyst Drivers.

I can load the individual slots, login and play, using direct x 11 one at a time. I can set them to windowed full, or windowed 1920x1200 etc ( i cant set them inside the game to the 1920x928 that ISBoxer sets them to for the window layout).
I have even tried logging into each of the slots one at a time, then going back into the config files and resetting the resolution to the 1920x928 setting. but when i try to launch the full character set... it opens the first one, but it never expands up into the main layout position, and never opens any of the other slots.

If I remove the -d3d11 parameter from the inner space game configuration profiles, and then go delete the 'SET gxApi "D3D11"' line from the WTF files that automatically gets added to them, i can relaunch the set just fine... but its back to dx9
<<

lax

User avatar

Site Admin

Posts: 7303

Joined: Tue Nov 17, 2009 9:32 pm

Post Sun Jul 08, 2012 7:49 am

Re: Directx 11 problems

The single most common reason for this exact post is from launching a single instance of the game through Inner Space, but without launching it through ISBoxer. (In which case the answer would be to use the ISBoxer Character Sets submenu or the ISBoxer Character Set Slots submenu to do the launching.)

From your post, I have no idea if you've had it working before, if it works in d3d9 mode but suddenly stops when you try the d3d11 mode, etc. I see from your account that you're not completely new so I'll take it as it stops in d3d11 mode..

In the Help menu in ISBoxer select "Diagnostics for game crashes" and follow the instructions to get me diagnostics from wow.exe. When it does the Copy for you, go to https://www.privatepaste.com, paste it there and after clicking Save Paste, give me the URL or the Paste ID. These diagnostics should help identify whatever is interfering (usually some other program that is also listed in the wow.exe process)
<<

ehalvorson

Posts: 5

Joined: Sun Jul 08, 2012 5:12 am

Post Sun Jul 08, 2012 9:16 am

Re: Directx 11 problems

Paste ID b16676b9df -> diagnostics for running the wow.exe directly
Paste ID 9d85390347 -> diagnostics for wow.exe being launched by trying to launch the Team/Character set thru inner Space.

Yes, I have had it working in D3D9 Mode for almost a year.
I always launch my teams by Right clicking the Inner Space Icon in the notification area -> Select ISBoxer Character Sets -> then select the Team I want.
I can switch back to D3D9 mode and it works just like it always has -> Awesome :D

if it helps this is the process i followed for each of the 5 game profiles to try to switch to D3D11 mode:
To use DirectX11 in World of Warcraft, there is a setting in Config.WTF but this setting would need to be applied to all of your virtual Config.WTF files. Until ISBoxer has this option built in for you, it is recommended that you use the command-line switch instead to select between DirectX11 and DirectX9. That is, you can add a -d3d11 or -d3d9 parameter to wow.exe through your Inner Space Game Configuration, as follows:
1. Right click the Inner Space icon in the system tray (notification area)
2. Select Configuration
3. Click the Game Configuration tab
4. Select World of Warcraft from the first drop-down box
5. Select World of Warcraft Default Profile (or your custom profile, whatever ISBoxer is configured to use per Character) from the second drop-down box
6. Make sure "Main executable filename" is wow.exe, NOT the WoW launcher. In the "Main executable parameters" box, put "-d3d11" with no quotes. To switch back later if needed, replace it with "-d3d9" with no quotes.
7. Click Apply to save your changes
8. Click Close Profile to back out of the Game Profile editing panel if you want, or just hide the Inner Space window; you're done.

Then launch my team by Right clicking the Inner Space Icon in the notification area -> Select ISBoxer Character Sets -> then select the Team I want.
The first character (instance of WoW launces, but it doesnt expand up into the upper window layout slot like normal, and the other instances don't launch either.

Also if it helps I have 7 copies of Wow. One copy that I use for Single Player mode, and one each for my 6 accounts. I used junctions so that the footprint would be smaller, and to minimize patching of both the game and addons.
I use the following at the command line when I have to redo my setup after a computer reload:

mklink /H /J "F:\Program Files (x86)\World of Warcraft 2\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 2\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 2\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 3\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 3\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 3\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 4\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 4\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 4\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 5\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 5\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 5\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 6\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 6\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 6\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 7\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 7\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 7\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"

and then i copy all the Base files (.exe, .dll etc from the main folder to the other 6)
<<

lax

User avatar

Site Admin

Posts: 7303

Joined: Tue Nov 17, 2009 9:32 pm

Post Sun Jul 08, 2012 9:57 am

Re: Directx 11 problems

Your non-IS diagnostics are in d3d9 mode and your IS diagnostics are in d3d11 mode. not that it makes a difference for this purpose ;)


Also if it helps I have 7 copies of Wow. One copy that I use for Single Player mode, and one each for my 6 accounts. I used junctions so that the footprint would be smaller, and to minimize patching of both the game and addons.
I use the following at the command line when I have to redo my setup after a computer reload:

mklink /H /J "F:\Program Files (x86)\World of Warcraft 2\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 2\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 2\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 3\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 3\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 3\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 4\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 4\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 4\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 5\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 5\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 5\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 6\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 6\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 6\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 7\Data" "F:\Program Files (x86)\World of Warcraft\Data"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 7\Interface" "F:\Program Files (x86)\World of Warcraft\Interface"
mklink /H /J "F:\Program Files (x86)\World of Warcraft 7\Cache" "F:\Program Files (x86)\World of Warcraft\Cache"

and then i copy all the Base files (.exe, .dll etc from the main folder to the other 6)

This part should be pretty much irrelevant other than that you're going through the pain in the butt of having 7 wow folders and doing extra work when you reboot. ;) With ISBoxer you only need one copy of WoW, though many people keep one separate for solo play and one for multiboxing. The only reason to use multiple WoW folders is to keep separate configuration (at the cost of performance), but with ISBoxer you get that automatically through Virtual Files.


A couple things that might be relevant to the issue though. :)
1. Catalyst Control Center may have application-specific profile switching enabled (formerly called Catalyst AI), and this can break Inner Space support. You can try killing the CCC.exe process prior to launching your ISBoxer Character Set to rule this out.

2. AVG could also potentially be breaking something in one mode but not the other. You can try temporarily disabling AVG, though this requires also shutting off its Services in the Windows Administrative Tools. I'm not expecting it to be AVG in this case since I would expect it to have the same effect whether you have wow set for d3d9 or d3d11.

Also I'm assuming that in the window that comes up, it looks like a normal WoW window with the normal window title and without an Inner Space FPS indicator... right? ;)
<<

ehalvorson

Posts: 5

Joined: Sun Jul 08, 2012 5:12 am

Post Sun Jul 08, 2012 12:13 pm

Re: Directx 11 problems

the non-IS diagnostic would be d3d9 in this case because the particular program folder WOW6 (for short) only ever gets launched by IS. the regular config.wtf still has the base settings. The IS diags have it because using the -d3d11 parameter is set within the IS Config for the WOW6 default profile which causes it to get injected into the character specific wtf files.

My single player copy is set to use d3d11 and to run in x64 mode... i can run diags on that one if you would like, or i can change the regular config file in WOW6 to use it. (Willing to try anything at this point)

And yeah the 7 copies of the game is overkill, its a left over habit from when I was using Keyclone. Main reason I used to do it was certain addons used to get quirky when the save data was opened by more than one character at a time. But yes now that i think about it, I can cut it down to two copies. I only had to set it up once per computer reload (as in reinstalling the OS and all software from scratch).

1. Tried killing Catalyst Control Center (CCC) Same result
2. Disabled all AVG services, rebooted, killed all AVG processes - still same result

And yes you would be correct, the window that comes up looks like a normal WoW window without the IS FPS indicator, or any of the IS functionality.

Anything else you can think of that I could try?
<<

lax

User avatar

Site Admin

Posts: 7303

Joined: Tue Nov 17, 2009 9:32 pm

Post Sun Jul 08, 2012 12:25 pm

Re: Directx 11 problems

The AVG Services will probably start again after rebooting? (especially if processes were running)

Otherwise no, I don't see why it wouldn't work in d3d11 at this point. It might be something specific to your video card + driver combination. Did you try newer drivers perhaps? :?
<<

ehalvorson

Posts: 5

Joined: Sun Jul 08, 2012 5:12 am

Post Sun Jul 08, 2012 1:33 pm

Re: Directx 11 problems

AVG services didnt restart after reboot, i disabled the service startups. The tray icon and one other thing that are called in the registry do start up, but when I kill the 2 processes they stay killed. Re-Killed CCC.exe, and tried killing MOM.exe also. Still same results.

I tried updating to the latest version of the driver released 6/20/2012 just before the first post.

I also tried dropping back to a total of 2 WoW folders... the original Program Files (x86)\World of Warcraft\ for single play and Program Files (x86)\World of Warcraft 2\ for multi-boxing -> no change
I tried deleting the 3 added files for 64bit -> WoW-64.exe, MovieProxy.exe, and Battle.net-64.dll from the World of Warcraft 2 folder -> no change

Tried dropping video settings to lowest - no change

Only real thing that I notice is that if I delete the config-character-server.wtf files, and re-export from ISBoxer and then launch the IS Character set, again the first slot opens with the d3d11 setting enabled, but the resolution is set to 800x600. Looking at the config files, only the first slots config file gets the changes (the SET gxApi "D3D11", but it shows the resolution setting in the config file to be gxResolution "1152x864"), the rest get left alone.

Config-Character-Realm.wtf as exported by ISBoxer (with privacy data xxxx ed out):
SET accountName "xxxxxxx@xxxxxxxxxxxxxxxx"
SET accountList "xxxxxxx|xxxxxxxx|xxxxxxx|xxxxxx|!xxxxxx|xxxxxx|"
SET gxWindow "1"
SET maxfps "0"
SET maxFPSBk "0"
SET readTOS "1"
SET readEULA "1"
SET readScanning "-1"
SET readContest "-1"
SET locale "enUS
SET showToolsUI "1"
SET accounttype "CT"
SET readTerminationWithoutNotice "-1"
SET installType "Retail"
SET enterWorld "1"
SET hwDetect "0"
SET videoOptionsVersion "4"
SET mouseSpeed "1"
SET Gamma "1.000000"
SET ChatMusicVolume "0.29999998211861"
SET ChatSoundVolume "0.39999997615814"
SET ChatAmbienceVolume "0.29999998211861"
SET VoiceActivationSensitivity "0.39999997615814"
SET Sound_MusicVolume "0.40000000596046"
SET Sound_AmbienceVolume "0.60000002384186"
SET farclip "185"
SET weatherDensity "0"
SET realmName "xxxxxx"
SET gameTip "45"
SET Sound_EnableSoftwareHRTF "1"
SET Sound_OutputDriverName "System Default"
SET playIntroMovie "4"
SET Sound_EnableAllSound "0"
SET timingTestError "0"
SET Sound_MasterVolume "1"
SET guildRecruitmentChannel "0"
SET minimapTrackedInfo "4104"
SET particleDensity "10"
SET rippleDetail "1"
SET reflectionMode "0"
SET environmentDetail "50"
SET checkAddonVersion "0"
SET baseMip "1"
SET textureFilteringMode "0"
SET gxResolution "1920x928"

Gets changed to this after launching the character set (again with privacy info crossed out):
SET accountName "xxxxxxx@xxxxxxxxxxxxxxxx"
SET accountList "xxxxxxx|xxxxxxxx|xxxxxxx|xxxxxx|!xxxxxx|xxxxxx|"
SET gxWindow "1"
SET maxfps "0"
SET maxFPSBk "0"
SET readTOS "1"
SET readEULA "1"
SET readScanning "-1"
SET readContest "-1"
SET locale "enUS"
SET showToolsUI "1"
SET accounttype "CT"
SET readTerminationWithoutNotice "-1"
SET installType "Retail"
SET enterWorld "1"
SET hwDetect "0"
SET videoOptionsVersion "4"
SET mouseSpeed "1"
SET Gamma "1.000000"
SET ChatMusicVolume "0.29999998211861"
SET ChatSoundVolume "0.39999997615814"
SET ChatAmbienceVolume "0.29999998211861"
SET VoiceActivationSensitivity "0.39999997615814"
SET Sound_MusicVolume "0.40000000596046"
SET Sound_AmbienceVolume "0.60000002384186"
SET farclip "185"
SET weatherDensity "0"
SET realmName "xxxxxx"
SET gameTip "46"
SET Sound_EnableSoftwareHRTF "1"
SET Sound_OutputDriverName "System Default"
SET playIntroMovie "4"
SET Sound_EnableAllSound "0"
SET timingTestError "0"
SET Sound_MasterVolume "1"
SET guildRecruitmentChannel "0"
SET minimapTrackedInfo "4104"
SET particleDensity "10"
SET rippleDetail "1"
SET reflectionMode "0"
SET environmentDetail "50"
SET checkAddonVersion "0"
SET baseMip "1"
SET textureFilteringMode "0"
SET gxResolution "1152x864"
SET gxApi "D3D11"

Return to World of Warcraft

Who is online

Users browsing this forum: No registered users and 5 guests