|
|
TS7.51 crashing on simply loading texture
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.
TS7.51 crashing on simply loading texture // Bugs
Post by weaveribm // Aug 9, 2007, 5:37am
|
weaveribm
Total Posts: 592
|
Hi Caligari Support I'm reporting a crash when creating a cube and rendering an image to the cube from the Vray Shaders panel. Simple cube UV
TS application memory space grows in system memory until there's a crash every time. To workaround this after saving the scene to a Library I create a new space, TS takes the usual 450MB and I can then continue to work. But if I then create anything or re-texture anything there's a TS7.51 application crash after TS7.51/Vray1.52 seizes >1.6GB system memory. For a cube. I size the cube as small as possible to minimise memory use. Village idiot joke :)
Thanks!
Peter |
Post by weaveribm // Aug 9, 2007, 6:05am
|
weaveribm
Total Posts: 592
|
Ah it's a simpler problem I think Caligari
It is the Inserting of the scene into the Library that is causing TS7.51 to grab all system memory. I have learned to save my work often and so when I create a simple object or retexture something I do a save (Workspace, created Library) right away - and this looks to be causing the crash. It's very ironic :)
But very frustrating too obviously... please help, maintaining stiff upper lip
Peter |
Post by weaveribm // Aug 9, 2007, 8:09am
|
weaveribm
Total Posts: 592
|
Very consistent now. TS7.51 is crashing and burning on saving the scene every single time, reason being (from Task Manager) that all available system memory is grabbed by the TS application in the (successful luckily!) save to a Library. Pre-save system RAM in use by TS7.51 is only 500MB
Peter |
Post by Shike // Aug 9, 2007, 11:34am
|
Shike
Total Posts: 511
|
Sounds weird... does that happen with all scenes/objects for you?
I'm actually using the same method, constantly saving scene and objects to my libraries... and currently it's a scene with 1million+ polygons and up to 3000x3000 textures.
And I havn't had any problems. :confused:
Should be noted: I work in Workspace and have turned off the Bridge.
(only turning it on if I absolutely have to use a Modeller function.) |
Post by weaveribm // Aug 9, 2007, 12:06pm
|
weaveribm
Total Posts: 592
|
I have only the one scene so far Shike :)
have turned off the Bridge.
(only turning it on if I absolutely have to use a Modeller function.)
That's a good idea thanks Shike! will try that. I am using Modeller quite a lot to experiment with glass created in both modes. I will turn the bridge off after I do something in Modeller thank you
currently it's a scene with 1million+ polygons and up to 3000x3000 textures
Whoah! That puts my problem into perspective :)
Peter |
Post by Shike // Aug 9, 2007, 9:52pm
|
Shike
Total Posts: 511
|
What size on the texture do you have (if you are using one).... one cube with a texture over the limit can cause irratic results.
Havn't tried yet what size trueSpace7.51 supports in Modeler/Workspace, Lightworks/Vray, Bridge On/Off...
( 3000 and below are pretty safe, higher than that might cause blank render, or fatal render error....but as I said... havn't tested in latest version.)
Also, what type of imagefile... jpg,bmp,png,tif,tga... havn't tested this myself, but think I've read in the forum that users have opinions on what format is best. I usually use jpg or png.
Another thing that can cause huge memory drainage is HDRI images, most of them are bigger than what is usually needed for light and reflection.
I tend to resize them to 1000px in photoshopCS2, and if I want it as a background, I use PS2 to cut out a piece from the original pic and save it as PNG or similar.
You could also test with some of the scenes that comes with truespace... just to check that your specific scenefile hasn't become corrupt. |
Post by weaveribm // Aug 10, 2007, 2:23am
|
weaveribm
Total Posts: 592
|
What size on the texture do you have (if you are using one).... one cube with a texture over the limit can cause irratic results
Thanks Shike - a standard 1600x1200 image. I'm working at a very basic TS level as I'm learning the ropes. Cables :) I'm pretty sure that the bug if it is a bug is connected with saving the scene rather than any logical error. 1600x1200x4bytes being less than 8MB. RAM grabbed is 1GB and climbing to the inevitable dissolution :)
I've had the same problem after dragging a Vray material to an object. Again as soon as I change something I do a Save As, RAM fills up and I naturally suspect that the crash is caused by what I did just last: dragged an icon to a Workspace object. But everything falls into place once the common malfunction :) rears its head. It's the saving of the scene that causes or at least is associated with the massive memory churning
what type of imagefile... jpg,bmp,png,tif,tga... havn't tested this myself, but think I've read in the forum that users have opinions on what format is best. I usually use jpg or png.
Thanks, I use a Targa file usually or a bitmap. Never jpg. I've only just discovered the png format which appears to be favoured over the bitmap format
You could also test with some of the scenes that comes with truespace... just to check that your specific scenefile hasn't become corrupt.
Ah that's a very good idea Shike. I will collect some complex scenes and try to reproduce the error. Yes I do suspect there's maybe something in the scene that's causing problems. Caligari team will be able to find something in the dumpfile hopefully but meanwhile I'll follow your helpful pointers thanks again!
There's another 'bug' report of mine nearby, I think at that time the crashing/RAM flooding happened in the same way but I found that if I did not drag a Vray Material icon to an object in Workspace but instead double-clicked on the Vray Material icon - the crash didn't happen. I've obviously found new ways to cause the memory hogging :)
Your 'turn off the bridge' advice I'll try this next session Shike. Switch to Modeller, turn the bridge on, do whatever. Turn off bridge, switch to Workspace, turn bridge on. It's a plan :)
I've found that I can work almost normally on the scene without saving, then when finishing up I do the save. See system RAM allocation climbing, 1.6GB any minute now it'll crash, quick do a New Space. TS memory in use drops (usually) to normal levels, I drop in the scene saved - off we go again undaunted :)
So this is the thing. When I load the scene in which I just created an object/textured an object etc (the same scene in which creating the object appeared to cause TS to crash) - TS is happily running. So I surmise that the object itself or the object's creation is not causing problems. Or else TS would crash perhaps with the new (suspected of crash-causing) object in there. It's only while scenes are being saved that the flooding system RAM error pops up... so far <gulp> :)
Peter |
Post by Shike // Aug 10, 2007, 3:53am
|
Shike
Total Posts: 511
|
Will be interesting to see how your tests works out because I'm getting confused...
I just tried replicating your situation.. tga image 1600x1200 in VRay material in library. Creating cube, dragging material from library to cube, testing with bridge off/auto/on, testing to save scene by insert in new workspace libraries and using saveAs in Model...still, memory doesn't go up much, maybe 1Mb..then down again...?
Edit: Since you actually seems to be able to save the scene...could you zip it and post it here for us to test? (Together with the texture...not sure if that's included in the rsscene file.)
Edit: Wonder if something went wrong when you updated to VRay 1.52? For example, a virus-scanner starting to mess up during installation?
Did you have any problems before the 1.52 update?
(shouldn't be the problem if update went without errors and you actually can do a VRay render.)
I know I had some problems (because of my extreme stupidity) when they released tS7.51... I upgraded tS, but failed to understand that there was a VRay1.51 also...
and tS7.51 + VRay1.5 wasn't a happy marriage ;) Crashed every time I right-clicked on the render icon :p |
Post by weaveribm // Aug 10, 2007, 5:36am
|
weaveribm
Total Posts: 592
|
The scene saves normally Shike. In the saving is when memory is seized without limit by TS but I only know this because I have Task Manager running and that warns me about when TS is about to throw a wobbly, which is at around 1.66GB. But thank goodness the scene is saved normally every time nothing is lost. The scene is attached to my trouble with Vray glass/lighting, the black edge of legend in the Bugs thread I think, sorry mate I'm leaving TS do its thing right now while the going's good :)
Switched to Vista now I have a better idea of what's happening. Imported the scene from the XP boot drive to a Vista-created Library, set up the ClothMotion flag animation and right now TS is running a 600 frame animation from Modelspace Vray at 30secs/frame. So something's happening :)
Wonder if something went wrong when you updated to VRay 1.52?
Good point Shike. I needed to update to Vray 1.52 on Vista earlier. This time switching around hasn't provoked anything nasty and I've done lots of saves to the Libraries. Very good the Libraries are too.
Crashed every time I right-clicked on the render icon
Ouch! We're a survivors group really :)
Peter |
|
