Just wondering if anyone else is still crashing after the update to fix the crashing?
I can't even stay in the game longer 10 minutes before a client crashes.
Printable View
Just wondering if anyone else is still crashing after the update to fix the crashing?
I can't even stay in the game longer 10 minutes before a client crashes.
Been having this issue this morning using ISBoxer. I did not have any crashes last night when I was playing solo and also when boxing a duo.
This morning trying to 5 box games keeps crashing each client one after each other, about 30 seconds between each client crashing.
Very bizarre
Yeah I don't see the crash while playing solo.
I totally uninstalled and installed my video drivers (again).
That had no effect, game still crashes.
Same here, i've been 5 boxing using ISBoxer happily all week, I logged in today and each client is crashing.
I thought it was just me, i'm relieved that others are experiencing the same.
Hope they sort it out soon.
same here. i can solo box the game but anytime try to use isboxer it crashes like crazy. put in a ticket have yet to hear any thing back yet. if i hear any thing that can help i'll post here about it
I'm 3-boxing across two computers right now without any problems (two characters on one computer, one character on another).
Same problem here.
Can't keep them logged in long enough to do much of anything, very irritating.
5-boxing with two computers also seem fine (3 on one, 2 on the other).
damn..glad its not just me but bummed I cant 5 box 8(
Smedbox, are you using ISBoxer? When I don't use ISBoxer it works fine. Well the games run fine that is.Quote:
Originally Posted by Smedbox
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.
So just logged in this morning and have the same issue. Both 5 boxing and also duo boxing. I have a laptop with an nVidia video card and my desktop with an ATI video card, both are crashing.
The bizarre part is that the laptop was fine on Friday night and then the following day was crashing. So somthing changed without a notification to cause this issue :(
Very frustrated right now
Someone on the ISBoxer forums pointed out that the magic time/number was around 15 minutes. I have run 4 tests so far and each time the first client crashes at 14/15 minutes from enter game world.
I guess we can rule out video card though. At first I thought it had to do with ATI cards. Guess not.
I did some research into the actual crash. Looking at the Event Log, the exception that is getting raised is a general access violation error. I just ran a test with the Rift client exe running as Admin along with ISBoxer. I still get the crash.
Well I am out ideas now.
Another point is that even single boxing with ISBoxer is causing a crash. Whereas single boxing without ISboxer the clients is stable.
I was thinking maybe it was related to an AFK timer, and that maybe if the client was not focused when that timer hit, the act of setting afk would cause a crash. But I have been setting in game solo (no ISBoxer) for almost 30 minutes and its been unfocused the whole time. Also I never went in AFK so, I guess that got ruled out.
I can't seem to reproduce a crash at all, without ISBoxer running the client.
Yeah, definitely an ISBoxer issue.Quote:
Originally Posted by Norrin
Quote:
Originally Posted by 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.
Quote:
Originally Posted by 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.
Yup, just a single client logged in and it still crashed :-(Quote:
Originally Posted by Norrin
As you can see in my post, each machine is running up to three characters.Quote:
Originally Posted by Norrin
Even so, for Crowdx and I, it doesn't matter how many we run, even just one it crashes.Quote:
Originally Posted by Smedbox
What are you running different that has it so you don't crash.
And by InputDirector, I assume you mean innerspace?
Same with my I duo box and keeping having random crashes. Playing solo nada.Quote:
Originally Posted by Norrin
Nope, InputDirector. Each machine has an NVIDIA GPU (but different ones) and both uses the 275.33 driver.Quote:
Originally Posted by Norrin
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.Quote:
Originally Posted by Smedbox
Edit: No still crashes.
My notebook has an nVidia card (GTX460M) and desktop has an ATI 6970. Both systems are intel based.Quote:
Originally Posted by Smedbox
Intel I7
12 gig
Radeon 5870
Lax mentioned he is looking into the problem.
Your setup is very similar to mine, same chipset and gpuQuote:
Originally Posted by Norrin
I'm using InnerSpace 1.11 (build 5469).
I am using IS 1.11 (build 5473)
I just upgraded to 5473 today though.
Quote:
Originally Posted by Norrin
Still on 1.11 build 5469
Ouch. When did this start happening? Was doing fine last week.
My setup: 1 main (first PC; NVidia GTX460; Win7 x64) + 4 alts (2nd PC; ATI 5750; Win7 x64). I'm running IS 1.11(5469) and ISBTK 39.1.818.1.
After 11 minutes by the in-game chat, 3 of my 4 alts and my main all crashed within 60 seconds of each other.
W. T. F.
Guess I'll go back to playing Dead Space until things are sorted out. :/
[edit] OK, so without ISBoxer running, the clients are still up (no crashes) after 30 minutes.
[edit2] Been playing (running quests) for 45 minutes now using Octopus and haven't had a single crash. Be interesting to see what Lax has to say about this.
[edit3] And wow...my FPS on my main went up from averaging 40fps to a smooth 55-60. /boggle
Have you guys tried with the NVIDIA 275.33 driver version? It could be that other driver versions don't like the combination of recent RIFT optimizations and IS hijacking all D3D calls to display the IS overlays.
Also, it could be interesting to see if you guys also have problems with FRAPS, since it does a similar D3D-hijacking as IS does?
Quote:
Originally Posted by Smedbox
I'm having the same problem on a laptop with a radeon 5800. Don't think its just a nvidia issue. The other 4 computers run just fine.
I've tried everything easy i can think of. Stuff like turning off addons, and removing the files in the interface folder. I was able to dupe the crash a few times by loading different interfaces.. ie /loadui 5box. It doesnt always crash when i mess with that though.
Not sure what else to do, the game runs fine when i don't launch with isboxer.
I am running an ATI Radeon 5870. So not NVidia here either.
I have not played with no Overlay, though I can't imagine that being an issue.
Yeah, it's not an NVIDIA-only issue, but that doesn't mean that it's not a graphics driver issue. It does make it much less likely, but there can be some bad interference between IS DirectX-hooks and the DirectX usage of the game, which certain driver versions could be more tolerant to than others.Quote:
Originally Posted by notole
When IS is enabled, all graphics drawing from the game is diverted from going straight to DirectX and the driver. Instead, all graphics function calls will go to IS, which then forwards the calls to DirectX and the driver. IS will modify some of these function calls and add it's own drawing at the end of every frame. FRAPS does this too.
Yeah I understand driver issues. Was only mentioning that I dont have NVidia.
Turned overlay stuff off and crash still happens. Not a big surprise there.
I have not tried Octopuss. Maybe I will try that until the issue with ISBoxer gets figured out.
See above with regards to NVidia vs ATI -- I have one box with each type of graphics card and are (with the exception of the disk subsystem) identical in CPU/motherboard/RAM/etc..Quote:
Originally Posted by Smedbox
Hmm...an interesting thought. I don't have fraps but I may download the trial version and see what it does.Quote:
Originally Posted by Smedbox
I'm working on tracking this down, but when I kill rifterrorhandler.exe and attach a debugger I'm not getting any crashes. And of course, the rift error handler won't share any of its information it will only send it to Trion and there doesn't seem to be a log of it.
So... if anyone wants to try killing the rifterrorhandler.exe processes (there is one per instance of rift.exe) and see if the crashes stop for them too... report back ;)
Quote:
Originally Posted by Lax
I will do that now. After my test with older ati drivers fails.
I'll give this a shot when I get home tonight.Quote:
Originally Posted by Lax