Crashing still occuring post update

[Smedbox]

Smedbox, are you using ISBoxer? When I don't use ISBoxer it works fine. Well the games run fine that is.
I don't think it is ISBoxer causing any problems. ISBoxer has not changed at all in the last few days. And before the update I had no problems at all.

I am running an ATI 5870 graphics card, and it powering 5 monitors. Not that I think that has anything to do with it either.
One thing I have not tried yet though is playing the games on the same crappy low setting that I normally box with. I was thinking maybe it was a conflict with ATI's Catalyst drivers. I did do a complete uninstall of the ATI drivers and reinstall them yesterday. That made no change.

Anyway will continue to play it with it today.

I'm running with ISBoxer and InputDirector with no problems. Haven't tried with more than three characters per machine, but I have zero problems. I've stood idle in Meridian for 15+ min, I've been in Runic Descent for 40 min, I've played PvP, no problems.

My two machines are using different OS (Win7 and Vista), but both are 64-bit. The only problems I'm having are that the summon friend dialog box won't go away until you hit /reloadui or re-log and that one machine doesn't get any voice overs even though it's enabled in the settings.

[Norrin]

I'm running with ISBoxer and InputDirector with no problems. Haven't tried with more than three characters per machine, but I have zero problems. I've stood idle in Meridian for 15+ min, I've been in Runic Descent for 40 min, I've played PvP, no problems.

My two machines are using different OS (Win7 and Vista), but both are 64-bit. The only problems I'm having are that the summon friend dialog box won't go away until you hit /reloadui or re-log and that one machine doesn't get any voice overs even though it's enabled in the settings.

You are on separate machines for each character. All mine are on the same machine.
Maybe that has something to do with it. However I think Crowdx has seen it crash with just one client running.

[crowdx]

You are on separate machines for each character. All mine are on the same machine.
Maybe that has something to do with it. However I think Crowdx has seen it crash with just one client running.

Yup, just a single client logged in and it still crashed :-(

[Smedbox]

You are on separate machines for each character. All mine are on the same machine.
Maybe that has something to do with it. However I think Crowdx has seen it crash with just one client running.

As you can see in my post, each machine is running up to three characters.

[Norrin]

As you can see in my post, each machine is running up to three characters.

Even so, for Crowdx and I, it doesn't matter how many we run, even just one it crashes.

What are you running different that has it so you don't crash.

And by InputDirector, I assume you mean innerspace?

[Smedbox]

Even so, for Crowdx and I, it doesn't matter how many we run, even just one it crashes.

What are you running different that has it so you don't crash.

And by InputDirector, I assume you mean innerspace?

Nope, InputDirector. Each machine has an NVIDIA GPU (but different ones) and both uses the 275.33 driver.

Time to dump your system specs and see what's common/different.

[Norrin]

Nope, InputDirector. Each machine has an NVIDIA GPU (but different ones) and both uses the 275.33 driver.

Time to dump your system specs and see what's common/different.

Are you running the Developer version of innerspace? I was not until now. I noticed that when I selected to use that, there was an update. I am testing my 5 man team right now. Would be very nice if that fixes it.

Edit: No still crashes.

[crowdx]

Nope, InputDirector. Each machine has an NVIDIA GPU (but different ones) and both uses the 275.33 driver.

Time to dump your system specs and see what's common/different.

My notebook has an nVidia card (GTX460M) and desktop has an ATI 6970. Both systems are intel based.

[Norrin]

Intel I7
12 gig
Radeon 5870

Lax mentioned he is looking into the problem.