Launch fails Wow unresponsiv

Hi,

Today for some reason isBoxer (innerSpace) freezes while launching the first client. Worked fine last night.

I can manually start WoW fine both in DX9 and DX11, using innerSpace single game launch menu option. And starting WoW without innerspace all together also works fine.
The Freeze happens just when normally the 2nd game window would launch. I can hear the game sound but the game window is unresponsive
Task manager tells me that wow is unresponsive but it utilizes alot of CPU and has alot of I/O read and writes going on.... ?

The console states:
| 22:56:23 ISBoxer: Preparing to launch Character Set 'New T
| 22:56:23 ISBoxer: Settings imported from ISBoxerToolkit.Ge
| 22:56:23 ISBoxer: Making sure Characters in Character Set
| 22:56:23 ISBoxer: Good!
| 22:56:23 ISBoxer: Launching Character Set 'New Test' ...
| 22:56:23 ISBoxer: Launching Slot 1 Character 'Tanakh-Al'Ak
Successfully executed '"C:\Program Files (x86)\World of Warc
Session launched (is1): "C:/Program Files (x86)/World of War
| 22:59:27 ISBoxer: Character from Set 'New Test' not fully
Select again to continue launching additional slots.
| 22:59:27 ISBoxer: Instructions completed.

Also tried clearing isBoxer config and make a new set using the Wizard to no success.

Any help would be appreciated,
Ztar

[lax]

This might be what has been reported as "black screen" since WoW 4.1, which will only happen when WoW is in Direct3D 11 mode and the window is moved (e.g. because of your ISBoxer window layout) even without ISBoxer. So, possible fix in the meantime is to switch it to d3d9.

Thanks for the suggestion..... the strangest thing...

Today, loading up isBoxer the xml settingsfile was empty.
I manage to load a old copy and adjusted the settings to run DX9... also before saving the config i deleted a hotkey i remember that i added before the trouble started yesterday. Now all the instances of the game starts, running DX9.

However i was a bit confused as it had been running fine in DX111 ever since 4.1 came out. Therefor i again set wow to load in DX11 and tried again. And now it works in DX11 as well ?!?!

However unlikely it might be - could a keybind cause the behavior? The keybind removed was for toggling Click to Move and had INS as hotkey. Does INS has some built in functionality that might interfere or do think i was some other random bug i was seeing?

Regards,
Ztar

[lax]

Nope, nothing special about Insert. Glad it's working now though