Droid Engineer Archive
Thread: I *may* not last too much longer...
Page 1 of 3
TheRealTK421
Mon Jan 10, 2005 9:04 pm
#1
The CTDs are just getting more and more out of control.
I went down like 5 times in about 20 min. or so tonight (not to mention the anaylizing, reconstruction, optomization and files downloaded again). /sigh
Just a quick head's up that if you suddenly stop hearing from me (for like...err....ever), you'll know why.
/bow
Respectfully,
I went down like 5 times in about 20 min. or so tonight (not to mention the anaylizing, reconstruction, optomization and files downloaded again). /sigh
Just a quick head's up that if you suddenly stop hearing from me (for like...err....ever), you'll know why.
/bow
Respectfully,
ARC_Casper
Mon Jan 10, 2005 9:18 pm
#2
=/ /comfort. We need a new CTD module to prevent them from happening hehe.
TheRealTK421
Mon Jan 10, 2005 9:20 pm
#3
Please.....don't say that. You know that a lot of DE stuff comes out busted.
/bow
Respectfully,
/bow
Respectfully,
Straker_Atrella
Mon Jan 10, 2005 9:36 pm
#4
Odd, it doesnt happen to me that often, I go nights without it happening.
My Dancer gets it a lot more though. There are theories now linking the CTD to the activation of Lightsabers inthe area, have you been around Jedi a lot?
Ohh yea mna, hang in there. The rough days will be gone soon, we will be moving into the golden days of SWG soon.
Message Edited by Straker_Atrella on 01-10-2005 08:36 PM
TheRealTK421
Mon Jan 10, 2005 9:40 pm
#5
Tonight I was getting it out in the wilds of Tat (south of Mos Taike...looking for the farmer).
It probably occurred cause I had like 9 waypoints active and was toggling the planet map a lot.
Once you get one...boy, they just keep coming. On Sat. I could only get them solve by a 100% clean reinstall of SWG.
I don't intend to be trying to shoe-horn my way past all the problems for too much longer.
It probably occurred cause I had like 9 waypoints active and was toggling the planet map a lot.
Once you get one...boy, they just keep coming. On Sat. I could only get them solve by a 100% clean reinstall of SWG.
I don't intend to be trying to shoe-horn my way past all the problems for too much longer.
Even my patience has its end.
/bow
Respectfully,
/bow
Respectfully,
TheOrb
Mon Jan 10, 2005 11:01 pm
#6
TheRealTK421 wrote:
Please.....don't say that. You know that a lot of DE stuff comes out busted.
/bow
Respectfully,
lmmfao
Starcloud
Tue Jan 11, 2005 12:36 am
#7
The CtD's, pretty much, seem to be the result of a memory leak having to do with the new textures that were put into the game concurrent with JtL. The more times you load up a set of graphics, the more the memory seems to leak.
It may be a flaw with DirectX 9.0c, it may be a flaw with the graphics code still using 9.0a functions that don't work quite the same way now.
But there's one *sure* way to get the CtD's to stop, and that's to log out and reboot your computer when your first CtD happens.
Capt
Tue Jan 11, 2005 3:54 am
#8
quick question: what GFX card you on?
I know that I've never had a single CTD and I'm on a Geforce.
People I've heard of crashing seem to be on ATIs
Another posted that he got rid of CTDs by downgrading his catalysts to 4.11 and they stopped.
Just in case this helps/applies
I know that I've never had a single CTD and I'm on a Geforce.
People I've heard of crashing seem to be on ATIs
Another posted that he got rid of CTDs by downgrading his catalysts to 4.11 and they stopped.
Just in case this helps/applies
ASHRID
Tue Jan 11, 2005 4:34 am
#9
To continue what Capt was saying I've never had this issue and I'm not aware of any of my friends (all5 of them) having it either - We all run GeForce cards (I'm also still on WinME but I know some of the guys are running XP). Since I'm the only IT one among us I'd expect to have heard about it by now if any of them were having problems
(lets just say they dont generally need to be asked if they are having problems.....)
JavelinCatcher
Tue Jan 11, 2005 6:15 am
#10
JC:
Guards! Make sure TheRealTK421 doesn't leavethe game until I say so.
GUARD:
GUARD:
Not to leave the game even if you say so.
JC:
JC:
No, no. Until I say so.
GUARD:
GUARD:
Until you say so, we're not to leave the game.
JC:
JC:
No, no. No. You stay here and make sure he doesn't leave.
GUARD:
And until you'll say so.
JC:
GUARD:
And until you'll say so.
JC:
Right.
GUARD:
GUARD:
We don't need to do anything apart from just stop him from crashing to the desktop.
JC:
JC:
No, no. Leaving the game.
GUARD:
GUARD:
Leaving the room. Yes.
JC:
JC:
All right?
GUARD:
GUARD:
Right.
JC:
Right.
GUARD:
Oh, if-- if-- if, uhh-- if-- if-- w-- ehh-- i-- if-- if we--
JC:
Yes? What is it?
GUARD:
Oh, i-- if-- i-- oh--
JC:
Look, it's quite simple.
GUARD:
Uh...
JC:
You just stay here and make sure 'e doesn't leave the game. All right? Right.
GUARD:
Oh, I remember. Uhh, can he leave the game with us?
JC:
N-- no, no. No. You just keep him in here and make sure he--
GUARD:
Oh, yes. We'll keep him in here, obviously, but if he had to leave and we were with him--
JC:
No, no, no, no. Just keep him in here--
GUARD :
Until you or anyone else--
JC:
No, not anyone else. Just me.
GUARD:
Just you.
JC:
All right?
GUARD:
Right. We'll stay here until you get back.
JC:
And, uh, make sure he doesn't leave.
GUARD:
What?
JC:
Make sure 'e doesn't leave.
GUARD :
TheRealTK421?
JC:
Yes. Make sure 'e doesn't leave.
GUARD:
Oh, yes, of course.
JC:
Is that clear?
GUARD:
Oh, quite clear. No problems.
JC:
Right. Where are you going?
GUARD :
I'm coming with you.
JC:
No, no. I want you to stay here and make sure 'e doesn't leave.
GUARD :
Oh, I see. Right.
JC:
Right.
GUARD:
Oh, if-- if-- if, uhh-- if-- if-- w-- ehh-- i-- if-- if we--
JC:
Yes? What is it?
GUARD:
Oh, i-- if-- i-- oh--
JC:
Look, it's quite simple.
GUARD:
Uh...
JC:
You just stay here and make sure 'e doesn't leave the game. All right? Right.
GUARD:
Oh, I remember. Uhh, can he leave the game with us?
JC:
N-- no, no. No. You just keep him in here and make sure he--
GUARD:
Oh, yes. We'll keep him in here, obviously, but if he had to leave and we were with him--
JC:
No, no, no, no. Just keep him in here--
GUARD :
Until you or anyone else--
JC:
No, not anyone else. Just me.
GUARD:
Just you.
JC:
All right?
GUARD:
Right. We'll stay here until you get back.
JC:
And, uh, make sure he doesn't leave.
GUARD:
What?
JC:
Make sure 'e doesn't leave.
GUARD :
TheRealTK421?
JC:
Yes. Make sure 'e doesn't leave.
GUARD:
Oh, yes, of course.
JC:
Is that clear?
GUARD:
Oh, quite clear. No problems.
JC:
Right. Where are you going?
GUARD :
I'm coming with you.
JC:
No, no. I want you to stay here and make sure 'e doesn't leave.
GUARD :
Oh, I see. Right.
TheRealTK421
Tue Jan 11, 2005 6:51 am
#11
OMG!!!!!@@!
Okay....that totally made my morning.
Thanks, JC. I feel much better.
"No you're not...youll be stone dead in a minute."
/bow
Respectfully,
/bow
Respectfully,
TheRealTK421
Tue Jan 11, 2005 6:54 am
#12
/bow
Capt wrote:
quick question: what GFX card you on? ATI Radeon 9800 Pro
I know that I've never had a single CTD and I'm on a Geforce. I used to run a GForce but...err...I stopped.
People I've heard of crashing seem to be on ATIs Hmmmm...
Another posted that he got rid of CTDs by downgrading his catalysts to 4.11 and they stopped.
Just in case this helps/applies
Thanks...I'll look into this. One of the CSRs thinks my Profiles might be bunk (specificially some bad Datapad info). So, I'll be whacking that and seeing what happens from there.
Respectfully,
TheOrb
Tue Jan 11, 2005 10:42 am
#13
Starcloud wrote:
The CtD's, pretty much, seem to be the result of a memory leak having to do with the new textures that were put into the game concurrent with JtL. The more times you load up a set of graphics, the more the memory seems to leak.
It may be a flaw with DirectX 9.0c, it may be a flaw with the graphics code still using 9.0a functions that don't work quite the same way now.
But there's one *sure* way to get the CtD's to stop, and that's to log out and reboot your computer when your first CtD happens.
Would this command possibly help keep you in game a little longer?
/flushgraphicsResources fullReset
Page 1 of 3