visual C++ Runtime library error
visual C++ Runtime library error
i am receiving a file specific error for indigo 07 test 3 in which when i try to load the scene indigo freezes at node 47/64 and then pops up the microsoft visual C++ library error. does anybody know what this could be either in the scene or a bug?
a shiny monkey is a happy monkey
Were you monitoring the free RAM with the Task Manager or similar tool ? I bet the mesh was too big, or too many triangles at the end... Dividing the big mesh in smallest shapes may help here... or it's a bug maybe (dunno, still using the same test scene for materials in 0.7t3).
(Optional) geometry caching wanted back, Ono, pleaaase !
(Optional) geometry caching wanted back, Ono, pleaaase !
i am not sure what was wrong, but i re-exported it from blender and it worked. i have 1gb of ram and the scene at most used 600mb of ram so that at any moment i had about 800 mb of ram being used. only problem now with the new scene is that all my models using sss (newest format) are invisible!
a shiny monkey is a happy monkey
As far as I can remember I get this error message when Indigo needs to much RAM...
(Try to render the Lucy 3D scan from Stanford with 28.000.000 triangles and you get it too
)
This Crash happens before the full RAM is used...
Make sure to set your "super_sample_factor" to 1, because 2 takes much more RAM!
(Try to render the Lucy 3D scan from Stanford with 28.000.000 triangles and you get it too

This Crash happens before the full RAM is used...
Make sure to set your "super_sample_factor" to 1, because 2 takes much more RAM!
polygonmanufaktur.de
- VictorJapi
- Posts: 58
- Joined: Sun Jan 21, 2007 1:27 am
- Location: Zamora - Algeciras || España
In the inifile.txt:
It's the very last entry------Miscellaneous settings-----
"halt_time" "-1"
"logging" "true" --write to log.txt?
"display_period" "20.0" --number of seconds between display of the render in preview window.
"image_save_period" "20.0" --number of seconds between saves of the render to PNG and EXR.
"save_tonemapped_exr" "true" --Write .exr tonemapped render as well as normal PNG?
"save_untonemapped_exr" "true" --Write .exr untonemapped render as well as normal PNG?
"num_threads" "1"
"cache_trees" "true" --TEMP TEMP TEMP
"polarisation" "true"
"super_sample_factor" "2" --a higher value takes more RAM but may reduce aliasing.
thank you but, i look at my inifile but there's no super sample factor..
watch :
------File loading settings------
"scenefilepath" "testscenes\ior_test.xml"
--Scene xml file to load. Relative to working directory (e.g. indigo.exe path)
--Alternatively, this path can be an absolute path, eg c:\indigo_scenes\testscene.xml
------Output image dimensions------
"width" "600" --Note that the ratio of these should match the camera aspect ratio defined
"height" "450" -- in the scene xml file.
------Metropolis light transport settings------
"metropolis" "true" --if true, use MLT, if false, use pathtracer
"large_mutation_prob" "0.4" --Probability of using fresh random numbers.
"max_change" "0.02" --max mutation size, must be in range [min_change, 1)
"max_num_consec_rejections" "200"
------General tracing parameters------
--"russian_roulette_live_prob" "0.8" --0.7
"max_depth" "1000" --max ray bounce depth.
"bidirectional" "true"
------Path tracer settings------
"strata_width" "5" --number of samples per pixel = strata_width*strata_width
------Network rendering settings-----
"frame_upload_period" "20.0" --number of seconds between uploads of image to network master
------Miscellaneous settings-----
"halt_time" "-1"
"logging" "true" --write to log.txt?
"image_save_period" "40.0" --number of seconds between saves of the render to PNG and EXR.
"save_tonemapped_exr" "false" --Write .exr tonemapped render as well as normal PNG?
"save_untonemapped_exr" "false" --Write .exr untonemapped render as well as normal PNG?
"num_threads" "1"
"cache_trees" "true"
that's all...
i use the release n.6
today i have another runtime error...
watch :
------File loading settings------
"scenefilepath" "testscenes\ior_test.xml"
--Scene xml file to load. Relative to working directory (e.g. indigo.exe path)
--Alternatively, this path can be an absolute path, eg c:\indigo_scenes\testscene.xml
------Output image dimensions------
"width" "600" --Note that the ratio of these should match the camera aspect ratio defined
"height" "450" -- in the scene xml file.
------Metropolis light transport settings------
"metropolis" "true" --if true, use MLT, if false, use pathtracer
"large_mutation_prob" "0.4" --Probability of using fresh random numbers.
"max_change" "0.02" --max mutation size, must be in range [min_change, 1)
"max_num_consec_rejections" "200"
------General tracing parameters------
--"russian_roulette_live_prob" "0.8" --0.7
"max_depth" "1000" --max ray bounce depth.
"bidirectional" "true"
------Path tracer settings------
"strata_width" "5" --number of samples per pixel = strata_width*strata_width
------Network rendering settings-----
"frame_upload_period" "20.0" --number of seconds between uploads of image to network master
------Miscellaneous settings-----
"halt_time" "-1"
"logging" "true" --write to log.txt?
"image_save_period" "40.0" --number of seconds between saves of the render to PNG and EXR.
"save_tonemapped_exr" "false" --Write .exr tonemapped render as well as normal PNG?
"save_untonemapped_exr" "false" --Write .exr untonemapped render as well as normal PNG?
"num_threads" "1"
"cache_trees" "true"
that's all...
i use the release n.6
today i have another runtime error...

Sorry Lady,isabelp1 wrote:today i have another runtime error...
because of your poor 512 MB Ram Rig you will see this message often

Indigo takes a lot of RAM to work..... try to avoid HDR lightning,
Perhaps Instancing in Indigo 0.7tx may safe some RAM too for you.
At last try to close as much running processes of your system as possible before starting Indigo... good luck!
polygonmanufaktur.de
Who is online
Users browsing this forum: No registered users and 8 guests