Thread

ts7 vray crashes

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 vray crashes // Bugs

1  |  

Post by bigL // Feb 17, 2006, 2:05pm

bigL
Total Posts: 16
hello to all truespace-users,


i have the following problem (and may be someone else, too):


when rendering a small scene (< 8000 vertices/faces) with vray options "transparent shadows enabled", "caustics enabled" with factor 200.000, photons 500 and distance 0.200 i got an microsoft visual c++ error after the precalculations before the real rendering starts. When using less photons like 200 everything works fine.


any ideas why this happens (and how to solve it) ??


and hopefully the reason is not my workstation:


WindowsXP SP2 (32bit)

Dual Xeon 3,6GHz

4GB Kingston RAM


regards,

bigL

Post by ProfessorKhaos // Feb 17, 2006, 3:10pm

ProfessorKhaos
Total Posts: 622
pic
Gave your scene a try. It took quite a while despite the simplicity (plane, cube & sphere). Probably due to all the internal reflections.


One thing you didn't specify (and I assumed) was that you're rendering single sided (TomG pointed out this setting for proper refraction/internal reflection effects for glass in VRay)


I also turn off multithreading for my renders though I don't know if that setting has an effect with VRay or not.


Here's the image.


Win XP SP2

Pentium IV, 3.2GHz, Hyperthreading

4GB DRAM

NVidia 6200

Post by bigL // Feb 18, 2006, 3:38am

bigL
Total Posts: 16
thank you for your action....and you are right. the amount of reflections causes this crashes....when using single sided rendering these scene uses only 670MB, but looks very different to double sided rendering, which always crashes at a memory usage of 1782MB (independent of using the /3GB switch in the boot.ini).

depending on the suggestions that there are to many reflections, i tried succesfully double sided rendering with setting the max-depth from 10 to 9 in the raytracing-options panel (which uses 1750MB without crashing) .


regards,

bigL

Post by Steinie // Feb 18, 2006, 5:46am

Steinie
Total Posts: 3667
pic
I found this statement on VRay.info listing top ten reasons VRay crashes:


"Most of the other crashes (probably 99%) are related to running out of memory; there is a page in the help index that gives some tips what to do in that case."


Just something to keep in mind when using the product. This had nothing to do with trueSpace so other applications crash too.

Post by Alien // Feb 18, 2006, 5:56am

Alien
Total Posts: 1231
pic
Hmmm - sounds like this might be a case for using 64bit v. of XP, assuming people can find the necessary drivers for all their hardware. IIRC, even on a 4GB system, 32bit XP only actually allows a maximum of 2GB for progs [the other 2 gets allocated for windows itself I think]. I know bigL said it only used up about 1700-ish MB, but he probably has a few other "little" things running, eg firewall, anti-virus, etc, which could be enough to make up the difference & cause Vray to run out of memory.


Disclaimer: this is just pure conjecture on my part, I have neither Vray nor XP64.

Post by bigL // Feb 18, 2006, 7:57am

bigL
Total Posts: 16
yes, yes...the memory-usage. alien, you are right with the maximum of 2GB for applications. using the boot.ini /3GB flag expands this to 3GB for applications and only 1GB for the system. But this does only work, when the application is specially compiled for this (with additional parameter-settings)......and ts7.exe seems not to be compiled this way....or may be the miscrosoft visual c++ dll which also belongs to the crash-message is running out of stack-size or something like that (it's also c-code, isn't it !). I also tried WinXP64, but truespace isn't a 64bit-application and so it is only working in a 64/32bit compatibility mode in WinXP64.....and crashes the same way.


regards,

bigL

Post by Alien // Feb 18, 2006, 12:11pm

Alien
Total Posts: 1231
pic
Oh. I thought 32bit stuff still got upto 2GB per app in XP64, so thought it might benefit from the extra 250-300MB. <shrug> Oh well, that's me out of ideas.


I know Roman's said that 64bit's not a high priority for Caligari at the moment, but in light of this memory issue, the increasing number of people with 64bit CPUs [sadly not me, yet], & the falling prices of memory, I really think Roman should consider making it a higher priority.

Post by roman // Feb 24, 2006, 9:41am

roman
Total Posts: 320
We certainly will be monitoring this issue.
Awportals.com is a privately held community resource website dedicated to Active Worlds.
Copyright (c) Mark Randall 2006 - 2024. All Rights Reserved.
Awportals.com   ·   ProLibraries Live   ·   Twitter   ·   LinkedIn