|
|
The Crashing Blues
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.
The Crashing Blues // Archive: Tech Forum
Post by Dragneye // Jul 25, 2007, 9:42pm
|
Dragneye
Total Posts: 602
|
Maybe this thread can be helpful to other newcomers in this field who have little technical computer knowledge, but LOVE to see their art come to life, regardless.
Question 1: What causes the dang crashing?!
I try to let it finish a task before I ask the program to do something else - I don't run other apps ( other than somtimes music) when I use tS to avoid 'overworking' the puter - I have found that bad geometry causes some of the crashing - so far, that's all I can think of to help this program do its job. It usually crashes when I try to render, but does it other times also.
Any and ALL other comments and insights would be VASTLY appreciated.
Question 2: what can I clear/do to have it run better, avoiding the crashes?
Does tS store files that add up and make it crash? (like temp. or bak. files. I cleanse my puter often of these types of files)
(My background info) - Presently, I have 48 gigs of memory left out of a total of 145 on drive C. - Processor speed= Pentium 4 @ 3Ghz - memory(RAM) capacity = 1Ghz - video card= Radeon x300 - (don't know what other info to give to help in your reply)
Thank you all in advance for ANY insight. |
Post by Jack Edwards // Jul 26, 2007, 4:33am
|
Jack Edwards
Total Posts: 4062
|
Dragoneye,
It may help to have Taskmanager open to see if you're running out of memory when rendering. 1GB is on low side if you're using VRay with Caustics, Lightmaps, or HDRI.
-Jack. |
Post by spacekdet // Jul 26, 2007, 5:00am
|
spacekdet
Total Posts: 1360
|
Some common causes for crashing:
Old video card drivers. Also, new video card drivers. If you find a version of your driver that works well, stick with it.
Enormous textures (above, say 4000 pixels in size)
Layers and layers of shaders - Shaderlab on top of Simbiont on top of Shadermagic is generally not a good plan. Try to refrain from mixing shader apps on the same object.
Deeply nested hierarchies; If you have a complex object made up of many sub-parts, try to slim them down by booleaning the whole shebang into one or just a few objects. Naturally, save a copy of the thing first in case you need to break it down into it's components in the future.
Delete the file named 'truespace.cfg' if things get really flaky- this sometimes gets corrupted during a crash. tS will recreate it on startup and it'll be all new and pink and shiny.
Crashing during renders might be an out of memory issue...try to defrag your hard drives; and use the Task Manager to see what's invisibly running in the background. You are on the right track by running a clean machine.
Lighting conflicts- creating a scene using mapped shadows on skylights, volumetric area light arrays, and 14 IBL lights in a scene will chew up your computer...start simple and try to take it easy on the poor machine.
Squeezing every single tsx you own into the plugin toolbar. Try to run this with a minimum of tsx's as they also get loaded up every time tS starts. Add your favorites, but don't go overboard.
Read this: HERE (http://forums1.caligari.com/truespace/showthread.php?t=2632)
Also, what version of tS are you running?Happy Hunting! |
Post by Dragneye // Jul 27, 2007, 1:19pm
|
Dragneye
Total Posts: 602
|
Jack - I'll try that (never have). Maybe it's that simple
Spacekdet - don't know abt drivers. I'm sure that the video card is just a basic one, not necessarily 'pro' stuff for 'hi energy' graphics, but all the art I've done on the puter [a few pieces larger than 1000x1000] have never given me a "x needs to shut down. Please save..." message)
* will have to figure out how to check for the size of a texture (the last time it shut down WAS during a preview render of a specific texture)
* rarely have gotten to adding layers since its crashed before I've even gotten that far.
* Have avoided creating "objects with many sub-parts" ( I am VERY polycount sensitive, knowing that that is one large headache for a programs workload, which tends to cause... more crashes! lol), and have only recently tried hierarchies in my ongoing 'Elegant swans' video. Have also tried to 'hide' objects to maybe help tS do its job better.
* will try to find .cfg
* defrag quite often
* My plugin toolbar is quite simple and bare. Just the basics that came with tS
* I'm running tS 6.6, which from the posts I've read here in forums is quite stable, and for the record I think is a Great program and competes quite handily with the 'big boys'. AND, IMHO, they are 'fraid, cuz Roman and his team are doin' a great job at competing at a reasonable rate, (compared to the 'big boys'). You show me 'perfect', and I'll show you a liar; this is a dang good program, my only complaint may be that it offers me TOO many ways to get my vision done! lol
*PS: Spacekdet... I like when you say 'Happy Hunting'; though sometimes it feels like I'm hunting in a minefield, being cautious so it doesn't ... Crash/boom! :D |
Post by 3dvisuals dude // Jul 28, 2007, 1:48pm
|
3dvisuals dude
Total Posts: 1703
|
Delete the file named 'truespace.cfg' if things get really flaky- this sometimes gets corrupted during a crash. tS will recreate it on startup and it'll be all new and pink and shiny.
http://bestsmileys.com/signs13/20.gif
- 3dvisuals dude |
Post by W!ZARD // Jul 29, 2007, 5:30am
|
W!ZARD
Total Posts: 2603
|
I've always found tS to be quite robust - yes you can crash it but there are obvious ways to minimise this. The biggest two culprits are boolean operations and deep heirarchy structures. I always save the scene before any booleann operation and nothing in my experience stabilises a big scene better than tidying up the hierarchies.
With tidy heirarchy structures and ensuring that you're not simply pushing buttons to quickly for the prog to respond most of your crashes should go away. |
|
