So sad

[Kgon]

Hi there guys. I 'm totally new at this Indigo render engine and i'm having some problems with it and i'don't know what to do to solve them. I really wanted to master this software but i can not even to start the rendering.
the problem is a MEMORY ALLOCATION FAILURE and ...other one that says something about too many triangles and a tree..not really sure.
I'm a Sketchup user and i have a house that wanted to render ,the file size is 1.8 mb, 2 displaced materials , 1 bump material default camera settings and 1600x727 output ( tried to decrease to 800x400 but no luck) mi pc specs are : Win XP 32 BITS , AMD ATLON X2 dual core PROCESSOR , 3-4 gb ram, ENVIDIA GEFORCE 7000M video card...is this enough for simple 1.8 mb scene??

Thanks in advance.
Regards

[Soup]

It'll be those displacement textures. The subdivision level is probably too high, your running out of memory because of it

[CTZn]

About the second error, see http://www.indigorenderer.com/forum/vie ... =17&t=9945 for a couple hints.

[Whaat]

Hi,

Your mesh subdivision settings are probably too high for your particular scene. I wrote a tutorial about the subdivision settings and how to optimize them for a given scene. It is located in this thread:
http://www.indigorenderer.com/forum/vie ... =19&t=6829

For now, try just lowering the max subdivision setting for the displaced materials until you don't get the errors any more.

[Kgon]

THANK YOU SO MUCH!!! problem solved...the error was very high displacement settings..but i'm still a bit worried about my pc spects...honestly ..what can i spect from Indigo with a machine like mine ??it's enough for any file size ....i mean i only need to pay attention to the material's displacement settings to succed with Indigo??...what you guys think?

[zeitmeister]

It would be great if we knew a little more specs of your PC... processor, and mainly RAM.
Do you use a 64bit system?
Besides displacement, aperture diffraction consumpts memory, too.

[Zom-B]

A Dual Core with 4 GB of RAM without aGPU that could speed up rendering... thats just like the iMac I sit in front of ^^

You can render with this rig! The limited 32bit system is quite a issue since more then 2GB of RAM usage will crash Indigo (and mostly all other 32bit apps ^^).

Rendertimes may be quite long (even if your 2core is fast), but you for sure know the deal in rendering business: more is better, every Mhz will be used!

you also can try to link various Computers via network rendering together to help you render images, maybe this is a option.
if you keep your images small, even via internet based network connection render help can be provided.

here are some tips to keep RAM usage small:
- don't use SuperSampling (blows internal render resolution to avoid AA)
- keep away from postPro aperture diffraction (needs quite a bunch of RAM if activated!)
- avoid to much LightLayers (each LL is raising IGI filesize and RAM usage of this by +100%)
- render via indigo_console (saves you the RAM usage of showing the image you are rendering)
- dont use excessive EnvMaps regarding MB size (EnvMap analysis during startup can cost a lot of RAM, even if its free after done again!)
- keep your SubDiv multi low and use viewDependency with pixeltreshold of at least 1 to save unneeded SubDiv.

[Kgon]

Thank you guys ...i'll keep all this in mind next time ...it seems i need to save some money to get a better pc.
Regards