D3 patch 2.1.2 InnerSpace crashes

Constantly crashing now. Lag while playing 4 games where no lag occured before this last patch. Now innerSpace wont stay on.

Anyone else having an issue with D3? I havent changed anything on my end and have used ISBoxer for almost 2 years. Suggestions please

I haven't played much yet in the new patch so I am not sure about lag or random crashing, but I am also experiencing a crashing issue in the latest patch.

Every time I try to cycle to a different window using the Next Window hotkey Innerspace crashes.

[bob]

Perhaps this applies.

http://www.tomshardware.co.uk/lag-diabl ... 49601.html

http://us.battle.net/d3/en/forum/topic/15699486389#1

And the many posts on the forum, re; LAG
http://us.battle.net/d3/en/forum/5386227/

[lax]

I haven't played much yet in the new patch so I am not sure about lag or random crashing, but I am also experiencing a crashing issue in the latest patch.

Every time I try to cycle to a different window using the Next Window hotkey Innerspace crashes.

This issue should be fixed as of Inner Space build 6056; re-launch Inner Space to let it patch up

Well it seems my window layout was partly to blame. I had always on top set for my slot 1 which was causing swapping issues. Now my Next window key will swap properly and cycles all the way through my windows and it wraps back around, so it goes slot1 -> slot 2 -> slot 3 -> slot 4 -> slot 1 again.

I am still having crashing issues with my previous window hotkey though. It doesn't seem to crash every time though and the key is setup exactly like the next key except for the key combo used and the direction it is supposed to cycle. Since Next works I am just using that for now and I just took the keybinds off my gamepad for Previous. I don't cycle between characters enough to fool with figuring it out. I only swap when managing a lot of inventory or crafting on individual characters.

[lax]

I am still having crashing issues with my previous window hotkey though. It doesn't seem to crash every time though and the key is setup exactly like the next key except for the key combo used and the direction it is supposed to cycle. Since Next works I am just using that for now and I just took the keybinds off my gamepad for Previous. I don't cycle between characters enough to fool with figuring it out. I only swap when managing a lot of inventory or crafting on individual characters.

I've fixed the crash with Previous window in Inner Space build 6060. Re-launch Inner Space to let it patch up

Yeah well it worked fine yesterday, and today I can't launch Diablo III on either of my machines.

I mean, I can run a single instance of D3, but multiboxing crashes the game windows at startup in 6060 build. On both my machines.

The game crashes when I try to login, to be more precise. Game windows properly open, but whenever I enter my password and hit enter, all the windows crash.

OK I uninstalled the bundle, re-installed without the automatic download of beta patches so I'm back in build 6040 and it works.

HOWEVER, for some reason it seems that the uninstaller deleted my .xml file with all the work on the DxNothing layers, and I have no copy. BUT it's still in Innerspace. Is there any way to export back the file in IsBoxer, or save it from InnerSpace ?

[MiRai]

OK I uninstalled the bundle, re-installed without the automatic download of beta patches so I'm back in build 6040 and it works.

HOWEVER, for some reason it seems that the uninstaller deleted my .xml file with all the work on the DxNothing layers, and I have no copy. BUT it's still in Innerspace. Is there any way to export back the file in IsBoxer, or save it from InnerSpace ?

I don't know what the uninstaller actually does, but for future reference you could have: A) just unchecked the dev patch option in Inner Space, then shut it down, and it would have patched itself back to the stable build, or B) re-installed the ISBoxer download bundle right over the top of your current install without any negative impact.

As for a missing XML file...

If we're talking about VideoFX that were saved through the in-game control panel, then they'd be in your /Scripts/ folder. If you created a new Character Set that wasn't named the exact same to the old Character Set, then the VideoFX will not show up until you rename the XML file(s) to match your new Character Set.

If we're talking about your actual ISBoxer profile, then you could open up the one that ends in LastExported to retrieve your prior configuration.

just unchecked the dev patch option in Inner Space, then shut it down, and it would have patched itself back to the stable build

Heh, I'll do that next time.

As for a missing XML file (...)

I noticed that the "bits" of xml file still were in a subdirectory (DxNothing mini-maps layers and characters profiles). I needed the general configuration file, which the uninistall apparently ate (I didn't delete anything manually), and I don't have any LastExported file anywhere.

Fortunately I still have all the x,y locations, width and heigth of the DxNothing windows written on some scribbled piece of paper, so it won't take too long to re-build it.

Also, you need to know that this morning, when I woke up and couldn't multibox Diablo, I almost murdered my chinese girlfriend while she was still sleeping, because yesterday evening she installed plenty of chinese programs on computer #2. But since I couldn't multibox on computer #1 either, I found out that build 6060 was guilty, and not her