easy rendering for Rhino in Windows
fault message
Hi,
I get the following fault message when starting up a renbdering in nXt:
"call to start raytracing failed returning codde 0, render cancelled.
It does not make me happy. Can I do do anything about it or is it time to buy a new computer?
thanks
Lex
Replies to This Discussion
-
Permalink Reply by Scott Davidson on -
This normally means that there is an error with the render setup. Here are some things to try:
Does Flamingo render a simple scene?
Will Flamingo render this scene at a low resoluton?
Do you have many trees, chairs or large bitmaps in the scene?
In Rhino, if you run the Analyze pulldown > Diagnostics > Select Bad objects, what does the command line report?
-
Permalink Reply by Lex Verheus on -
dear Scott,
the answer to your question is;
It does render the scene at a low resolution and size.
It is a relatively simple scene in volving a boat in water. No sails. It is a dull gray naval vessel. see attached file.
No trees. no chairs, two machine guns and two seachlights with lenses.
I had the bad objects removed.
I am using; AMD Athlon 64 X2dual 3800+, clockspeed 2.01GHz, 3.25Gb
File size is about 70Mb.
regards, Lex
- Attachments:
-
-
FTT-20m-PL3.jpg, 769 KB
-
-
Permalink Reply by Erik Tukker on
-
Dear Scott,
I have the same problem.
- All bad objects deleted or hided;
- No, rendering on a low resolution also does not work;
- No trees, chairs or large bitmaps present;
- A new model of a small filesize will be rendered without complications;
- My model has a filesize of approx. 290 mb.
I am starting to run out of options and become more and more frustrated. What can I do? Please help!
Workstation specs: Intel i5-2500 CPU @ 3.3 Ghz, 3.24 GB RAM, NVIDIA Quadro 2000
Software: Rhino 4 SR9, Flamingo nXt build: 10 July 2012
Regards,
Erik
-
Permalink Reply by Scott Davidson on
-
We need to decide if it is running out of memory, or there is an error in the model. If you turn off half the layers does it render?
We can test the model here. The best way to do this is to type this command in: "FlamingoNXtWriteDebugModel" This will create a model on the harddrive which you can send to us. The caommandline will report the fie name of the debug file. I recommend zipping it and using this form to send it to us:
http://www2.mcneel.com/upload/Upload.aspx
The file size is limited to 120 MB. Is the zipped file larger then that?
-
-
Hi Scott, Thanks for the reply.
I turned off about 50% of the layers and the result was good. It finally started a rendering without errors or problems. So I guess this could be a memory problem.
I checked some figures in the taskmanager:
- Model opened without further actions: 596 MB RAM usage
- Model during rendering process (error message appeard): 1467 MB RAM usage!!!
I have attached some screenshots of the taskmanager. Is this normal behaviour of nXt?
I have a 32 bit machine. Perhaps the 3GB settings in the boot.ini file could help me out?
Regards, Erik
- Attachments:
-
Permalink Reply by Scott Davidson on
-
The model may be too big, the 3 GB switch is worth a try:
http://wiki.mcneel.com/rhino/memoryincrease
A more likely problem are the mesh settings. Tools pulldown > Options > Mesh. I normally like to see Custom set to this:
Density (new in Rhino 4) 0.0
Maximum angle 0.0
Maximum aspect ratio 0.0
Maximum edge length 0.0
Maximum distance edge to surface (0.25 inches or 4 mm to start)
Minimum initial grid quads 16Maximum distance edge to surface is the key setting. Smaller values will lead to a smoother mesh, but more memory usage.
More information on meshing can be found here:
-
-
I have been checking my model and found a lot of custom mesh settings. Aperently I have been rebuilding more meshes then I thought I did. Rendering runs without any problems now so I guess that was the problem.
Thank very much for you help!
The 3GB setting will (hopefully) enabled by our ICT departement. This will give me some more buffer.
© 2013 Created by Scott Davidson.
