United3dArtists Archive

splinters · Post by **splinters** » 04 Apr 2010, 02:27

So, I am revisting some old scenes for a client; all done using tS 7 (various versions) and Vray. Problem is, despite having all the scenes and assets on a local disk, many of the scenes are crashing out tS...usually the more complex ones.

So, I uninstalled everything and reinstalled tS7.6 and Vray 1.53.....same problem.

Now the client wants some renders but I am worrying that I will not be able to get them.
Only difference is that this new laptop is on Windows 7 64 bit while I made them all on a Vista 32 bit desktop. Like the desktop this laptop has dual core, 4GB ram and a decent graphics card.

I am a bit rusty with Vray, am I doing something wrong here, any know issues or workarounds?

Thanks in advance for any help...getting pretty desperate now.

nigec · Post by **nigec** » 04 Apr 2010, 07:29

Does the dual core have AMD CPU's? if it does try turning off multi thread rendering, its a problem that's plagued me for the last 2 years, the CPU's timers aren't quite matched for some reason

splinters · Post by **splinters** » 04 Apr 2010, 09:46

Yup, AMD here.

Gave the multithreading a try and it still crashed after 20 secs or so after hitting the render to screen button.

If I have bridge turned on, one particular scene (which crashes every time) crashes upon loading the scene!!

marcel · Post by **marcel** » 04 Apr 2010, 11:32

when you load a scene with nurbs on the model side, TS crash if the bridge is on (with all os: win7, vista and xp). Even if you don't switch to workspace, the scene is loaded on both interface. another problem can be the new directx on win7 64 bits or the video ram on your new card.
you need to purge all info on the workspace to have a stable scene on model side when you use complex scenes. first start a new scene to erase all data on both side, erase all history, turn bridge off, then open your scene. never change the setting of the bridge or go to workspace during your work with these complex scenes.
I had scene (model side) with big problem. I saw this scene had another old scene on the workspace! (bug?). The file was huge on the hard disk. after the purge, the scene was 10 time small and had no problem to work.
It is possible your problem is different but difficult to know without the scene to try.

splinters · Post by **splinters** » 04 Apr 2010, 12:23

Cheers marcel, its definitely something in the scene as I deleted everything except the lights and settings and it rendered. Also several Vray scenes are rendering OK...I just need to isolate the problem....

EDIT: I took a few large models out of the scene and it renders so that reinforces my theory....time to investigate further.

splinters · Post by **splinters** » 04 Apr 2010, 12:48

Marcel, you are a genius. I had a flag in the scene which was a Nurb plane. I converted it to a poly and voila...renders fine now.

Thanks so much for the help...

trueBlue · Post by **trueBlue** » 04 Apr 2010, 14:04

Sounds like a script would help here.
This script runs Model's covert to Poly command on all selected objects.
If you run this in Workspace the Bridge must be On.

splinters · Post by **splinters** » 04 Apr 2010, 15:44

Cheers trueblue, I will give it a go but I work with bridge off normally.

marcel · Post by **marcel** » 04 Apr 2010, 16:30

splinters wrote:Marcel, you are a genius. I had a flag in the scene which was a Nurb plane. I converted it to a poly and voila...renders fine now.

Thanks so much for the help...

That is one of the thing i thougth.
I know other bug that crash TS. i give a name for these bug

- The invisible object: a scene crash. when you see the size of the file, it look too big.
What you need to do: save your work as separate object (model, light, cam, etc...) then create a new scene and import all the object. erase the bad scene. the new scene is smaller and good.
- the indestructible object : an object is locked and you can't do anything. Impossible to edit.
What you need to do: export a .obj of the bad object. copy all the objects that are on the same layer than the bad object to another layer. erase the layer with the bad object. import the .obj.

I think it would be interesting to do a list of resolved bugs like this. They are not in the manual.
we live best when we know our faults.

United3dArtists Archive

vray crashes...can you help?

vray crashes...can you help?

Re: vray crashes...can you help?

Re: vray crashes...can you help?

Re: vray crashes...can you help?

Re: vray crashes...can you help?

Re: vray crashes...can you help?

Re: vray crashes...can you help?

Re: vray crashes...can you help?

Re: vray crashes...can you help?