|
|
trueSpace slowdown and crashing
About Truespace Archives
These pages are a copy of the official truespace forums prior to their removal somewhere around 2011.
They are retained here for archive purposes only.
trueSpace slowdown and crashing // New Users
Post by TomG // Apr 15, 2009, 10:45am
|
TomG
Total Posts: 3397
|
Hmm, you said "I have the built in NVIDA GeForce Go6150....you should not update this Driver with HP computers ! " That to me meant that updating the driver would cause problems, meaning that the hardware itself is not free of problems and has as much chance of a driver problem as an external GPU.
Anyway, I am not sure what point you are making, nor why you seem to be irate, nor what it is you are irate about. I thought you were saying onboard GPUs never crash tS and external cards do, which would not be accurate and I wanted to make sure people were aware that external GPUs were just fine, and no more prone to problems than onboard GPUs.
HTH!
Tom |
Post by Mr. 3d // Apr 15, 2009, 11:42am
|
Mr. 3d
Total Posts: 747
|
TOM...you are lost.
You are the one that created an issue out of thin air. Maybe you need to read the Threads and posts more closely berfore you start making the wrong conclusions and wrongly pointing fingers. |
Post by TomG // Apr 15, 2009, 11:45am
|
TomG
Total Posts: 3397
|
But no-one has pointed fingers at anyone - no-one has accused anyone of anything, no fingers have been pointed.
HTH!
Tom |
Post by Mr. 3d // Apr 15, 2009, 11:51am
|
Mr. 3d
Total Posts: 747
|
I started out trying to help Shadow106 with the trueSpaqce issue. Jack chimed in about the Drivers. I acknowledged him with proven Display Driver issues. You then turned this whole Thread around as to trying to help me with a problem that does not exist. Then you twist the whole story around and include me in the middle.
You are misdirecting the main problem...trueSpace crashes. |
Post by TomG // Apr 15, 2009, 12:01pm
|
TomG
Total Posts: 3397
|
I never said you had a problem - you commented on the drivers, and I replied to that. You stated your machine is stable. Your comments did say to me "onboard graphics are more stable than external cards", whether you meant that or not, so to avoid anyone else being confused, I made sure no-one was worried that they have an external card, and also that no-one would think they ought to choose a machine with onboard in preference to outboard graphics.
And that was all. I haven't turned any issue around, said you had a problem, or tried to put you in the middle of anything, sorry you feel that way. I just want to make sure new users reading this do not think "Ah, better choose this new laptop with onboard graphics in that case, and I was going to buy one with a non-motherboard GPU!" as in most cases that would be a mistake for them, and I didn't want them to go away with that information.
Nothing more than that, no-one accused of anything there :)
HTH!
Tom |
Post by Mr. 3d // Apr 15, 2009, 12:09pm
|
Mr. 3d
Total Posts: 747
|
Alrighty then....your miscomunication then...and don't let it happen again:D LOL!!! |
Post by TomG // Apr 15, 2009, 12:20pm
|
TomG
Total Posts: 3397
|
Sure won't! Sorry you felt you were being accused of something, not my intent.
On the problem, got the scene, and having a look. Will be emailing Shadow directly, but posting here for everyone to know something about the cause.
There is an oddity in the hierarchy. All objects are single objects at the scene level (hood, body, and front of grill). However, one object GrillBorder (as you would expect, the edging around the grill) looks to be encapsulated with nothing. This means the top level object is not a geometry object. Going inside it finds the regular geometry object.
Now, I didn't get a crash, but I did get this - if I went to Modeler, and started Point Edit mode on this GrillBorder, then exited point edit mode (no actual editing done) and then went back to workspace, all seemed well. But when I save and load the scene - everything disappears except the GrillBorder object.
So clearly this is making tS uncomfortable with things, and at some point in working with it, it will crash. Something somewhere in the hierarchy is corrupted.
I fixed this as follows - entered the non-geometry GrillBorder object, selected the geometry object in there, saved it as object to workspace libraries, went back to scene level and deleted the GrillBorder object, and readded the one I saved. This one is just the geomtery with no encapsulation.
I could now go to Model, Point Edit the object, return to workspace, save, load, and all objects were intact. My guess is that this version of the scene will no longer crash. I will send it to Shadow to see.
I think the encapsulated object has been created using Encapsulate rather than Encapsulate in 3D. This creates a kind of object unique to the workspace, something that the Model side can't really understand. Somewhere along the way in crossing the bridge - eg to do a test render, use an old tool, or maybe just the bridge itself preparing things in case you go to the Model side, caused things to go out of synch, with the Model side confused about what this object was.
I do notice it keeps trying to load gradient.bmp too when I load the scene, will try repainting all the objects before sending it to Shadow see if I can get it to stop doing that.
So with luck this may be the problem! An object that had Encapsulate used on it rather than Encapsulate In 3D, and then had geometric operations performed on it.
Will see how Shadow gets on with the modified scene!
HTH!
Tom |
Post by Jack Edwards // Apr 15, 2009, 1:22pm
|
Jack Edwards
Total Posts: 4062
|
BTW, if anyone needs to update their drivers for the HP w/ nVidia 6150, the 179.32 drivers were the ones I ended up using. |
Post by Mr. 3d // Apr 15, 2009, 1:54pm
|
Mr. 3d
Total Posts: 747
|
Where's the link Jack ?
This is not an HP Display Driver is it ?
Why would I even consider replacing a perfectly good Display Driver with one that is not "officially" made for this computer ?
The problem that exists is that the HP update for the NVIDIA GeForce Driver is not specifically designed for the prior models. It sounds like your sister updated the GeForce Driver, had problems, called you, and instead of reloading the original factory sent Display Driver (which would have solved the problem), you searched the web with a trial and error effort until you finally found a compatible substitution ? |
Post by Jack Edwards // Apr 15, 2009, 2:06pm
|
Jack Edwards
Total Posts: 4062
|
Nope, I upgraded her laptop and re-installed Windows after the harddrive failed. ;)
Yup it's an HP specific driver:
http://www.laptopvideo2go.com/forum/index.php?showtopic=22782
Back up your old one before trying it, though. And I agree, if you're not having any problems with the current one there's no need to update it except for performance or compatibility reasons. :cool:
Keep in mind that nVidia uses a different driver model than other companies. Their drivers use a universal architecture so that the one driver works on all their cards. The updates generally include performance improvements and compatibility fixes in the software. |
Post by Mr. 3d // Apr 15, 2009, 2:14pm
|
Mr. 3d
Total Posts: 747
|
No wonder I don't recognize it...its 32bit:)
I'm running 64bit, and I'm not sure if the same update issue arises with the 32bit ? |
Post by Jack Edwards // Apr 15, 2009, 2:17pm
|
Jack Edwards
Total Posts: 4062
|
Here's the 64-bit one:
http://www.laptopvideo2go.com/forum/index.php?showtopic=22783
nVidia's 64-bit drivers that shipped with the computers back when Vista first came out were notoriously awful. So you might see significant performance improvement by updating. Though on a 6150.... even the best performance would still be rather poor... :(
Not much you can do about that in a laptop though, except buy a new one with a dedicated GFX card. |
Post by Mr. 3d // Apr 15, 2009, 2:38pm
|
Mr. 3d
Total Posts: 747
|
I know this update Jack. This update will worsen my computer's Display performance. I have EXCEPTIONAL perforfmance with my original factory sent NVDIA GeForce Go6150 Driver. If it's not broken, why fix it.;) |
Post by Jack Edwards // Apr 15, 2009, 3:08pm
|
Jack Edwards
Total Posts: 4062
|
Yup, go with the one that works best. :)
No sense in updating just to update, especially if it degrades performance. Though there were some issues with defective components and overheating with the HP nVidia laptops from around that time period, so it's possible that the update is to address that. *shrug* lol Laptops are always a special case. :rolleyes: |
Post by Shadow106 // Apr 15, 2009, 9:52pm
|
Shadow106
Total Posts: 49
|
Well for me the latest drivers have improved my system performance greatly and Tom seems to have found the issue with the scene although I am completely at a loss as to how it has happened with me not even knowing the Encapsulate tool existed lol |
|
