Printable View
Anyone else having random clients close on them without notice? They just go boom randomly, no error message, nothing. Running 5 clients with 8GB RAM and i5 2500k, low quality renderer. CPU is running at 100% (all cores), but that shouldn't be the problem imo. Been able to 5-box WoW at high to ultra settings without any trouble.
ya i have had this happen am not sure what it was doing. but its not done it in a long time don't know what i did change.
then i think a alt might of had a key binding to alt+f4. not sure now.
Though your ram is a little low am eating a good 12gb it likes to eat a lot of ram this game.
About 1 GB per client, am at 5.7GB used while running 5. Should be enough. And nope, no alt+f4 keybinds. :)
Edit: Well, had another 8GB RAM and installed em real quick. Same result, clients randomly crashing.
try removing the first lot of RAM and see if it is faulty chips (that was an issue I had a while back).
Did a memory test already. Got no other (windows, other games/applications) crashes at all, its just while boxing Rift. No problems while soloing Rift either.
There seems to be something amiss right now. I too am having some issues with cores being nearly maxed out. And while on mumble last night, was involved in trying to help diagnose 4, yes 4 other peoples SAME issue. (non-boxers). I have 32GB of 1600 RAM and running a gen 2 i7 OC'd, with (3) 550Ti GPUs in SLI mode. There is no reason I should have either maxed cores let alone fps issues... like I had last night.
I also noted there were 2 hot fixes
If you're "crashing" with no crash report, then the only other place that's going to hold any details is the Event Viewer (Windows / Applications). If nothing is showing up there, my money's on an ALT+F4 key binding.
Already taken a look at the OS events this afternoon, several Service Control Manager error messages.
Am going to try to box with HKN tomorrow (tried for about 15 minutes without any crashes today, but had to stop cause of RL). Been reading ISBoxer had some trouble back in 2011, maybe Keyclone (the software I've always used to box) has the same issues with Rift.
::Looks at the calendar::Quote:
Originally Posted by Klesh
Obviously, there are many people using IS/ISBoxer to multibox RIFT and you are the only person currently reporting that your clients are disappearing into thin air. If you want help tracking the problem down then you should probably post this on the ISBoxer forum since it sounds like it's not a normal error, but if you don't care to resolve the issue, then... I guess you'll be forced to move to another program. /shrug
I feel the need to clarify my previous post. I did not mean to imply mine crashed too. I was simply commenting upon the level of "intensity" of hardware RIFT's new patch going F2P seems to possibly be related. I.e. Even non boxers have mentioned seeing hardware requirement increases.
Perhaps the i5 youre using isnt able to keep up. Perhaps the video card is not cooling as well as it was when you first bought it. Perhaps your computer has more bloat on it now than when you started, and requiring more RAM resources. Perhaps the amt of RAM used now, is insufficient.
(Note: I also am using close to 12GB for 5 instances at a fps of 30)
Either way, all the "perhaps's" are indicative there is more investigating into the PC rather than pointing at the software.
/agree with Mirai
Keyclone != ISBoxer, you know. Never said am using ISBoxer, but well.....................Quote:
Originally Posted by MiRai
Well, the clients crashed pre 2.3 too (tried boxing Rift a couple of days ago), and they are crashing with 16GB RAM too, as already mentioned. Rift is the only application with such issues, so I highly doubt its my machine.Quote:
Originally Posted by Apps
Haha TouchéQuote:
Originally Posted by Klesh
well i had this prob on isboxer so. mien just stop after a bit of time maybe try a re install of the game check drivers as well is a good start i did a lot and it just stopped massing up.
I don't suppose you had the Raptr client running, that was crashing me.Quote:
Originally Posted by Klesh
Nope, never used Raptr. 1 account with Rift + Storm Legion and 4 trial (now free to play) accounts.
Well, 14 instant adventures and a total of 1 hour playtime with HKN, no crashes at all. Think it's safe to say Keyclone was causing the crashes, probably the same issues ISBoxer had back in the days.
Glad you got it working!
Spur of the moment I created 2 accounts and fired up 'ol keyclone. About 2-5 mins after logging on with both characters, joining group, starting to create macros......one client crashed.....about 2 min later the other crashed.
Did this about 3 times in a row before i decided to check on the forums for a solution.
Gonna have to test HKN(never tried it).
It's not gonna be a Keyclone problem.
My money is that you're on a laptop and something is getting maxed out. I'd suggest loading every box with the low quality renderer and going from there.
No, on a normal pc. I finally figured out the basics of hkn and got that working fine. At least now, if a rift window closes unexpectedly, I get a rift error message. It only completely disappears with no explanation with keyclone.
Wow... It IS a Keyclone problem, probably the same problems ISBoxer had back in the days (don't know what Lax had to change)...Quote:
Originally Posted by Ughmahedhurtz
Quote:
Originally Posted by cmeche
I read that as it's failing with keyclone and HKN, the only difference is that due to the differences in UI hooking between the two, the crash either displays an error or does not. The root cause of the problem is not keyclone or HKN. I'd bet money on it.Quote:
Originally Posted by Klesh
If you'd read the complete thread, you'd see I've had random clients crashing every couple minute. Switching to HKN stopped my crashes completely.
Ya, the reason for the crashes is probably the way Keyclone is sending the keystrokes to each window. As mentioned before, ISBoxer had such crashing problems too back in 2011 or so (which got fixed by Lax).
Doh. Missed the one post that had the relevant info in it. :P Correction acknowledged. In that case, yes, you're probably on the right track with regards to root cause.Quote:
Originally Posted by Klesh