ICE_rendering instantiate object

[eldee]

enable verbose logging (through the render options), and also enable file-logging (through the script editor preferences). My guess is that it's a memory allocation error due to your GI settings, but without an actual error or log, there's not much more to say about it.

[ThE_JacO]

Probably instantiating the wrong input or through the wrong node.
Post a description of the tree.

[DaVee]

eldee : hi, I did a log file,there (http://dg1.dave.free.fr/withGI.log)I hope this is enough to get a solution, I don't really know how to interpret this kind of informations, lack of knowledges. hope you'll find something. ;)

ThE_JacO: hi, This a screen capture of all things must be interesting: render tree, Ice tree, materiel manager, scene and explorer.

I did a really simple scene. The GI is set to default. Only one light (spot light).

http://dg1.dave.free.fr/cgtalkGIrender.jpg

So thanks for answers, if you want something else i forget to resolve this problem, please tell me. ;) I tried many things. I don't really know where to go now. I'm stuck.

DAvid.

[ThE_JacO]

If you're using set instance geometry then you should be fine.
The same setup works fine for me.

Turn on verbose logging like Eldee was suggesting and make sure you rendering settings aren't preventing instancing somehow.

[DaVee]

I did a log file. but I don't know how to interpret this.
May be you might help me.

Link of log file there. (http://dg1.dave.free.fr/withGI.log)

Thanks ahead. ;)

[DaVee]

An other log file. shorter ;)

Link to log file there (http://dg1.dave.free.fr/withGI03.log)

I did several render, I mean Tried to do some :). And I noticed the last line written in the file is:
' INFO : RCI 0.4 info : allocated 13 MB, max resident 13 MB

Maybe I should change something related to this. I'll try to find where.

If you have an idea you're welcome.

David. ;)

[eldee]

try reducing your photon depth.. with all of those instanced objects you're probably getting a ton of bounces and getting a memory-related crash. currently you have 10 reflection bounces per ray (and I can't tell what the falloff is on it, depends on the scale of your scene as well). Those are actual reflection bounces too, not just bounces off of reflective surfaces.. so any time a ray hits geometry, it will bounce. so you're getting tons of bounces, with a really high accuracy per bounce radius.

reduce your radius to something pretty low, and your bounces as well

edit: also- if it's just a test scene, maybe upload it somewhere and somebody can take a look at it. i've duplicated your scene visually and it works fine on my machine. how much RAM do you have? I'm using 7.5 w/ 8 gigs of RAM.

[CiaranM]

If you don't need shape animation on your instances, then try using the 'Set Instance Shape' node instead of the one you're using.

[DaVee]

eldee : ok i'll try some adjustments as you said. I already set the reflection and transparency to zero (good start :) ). I'll look at photons tuning.
Meanwhile i give the scene test there Scenes test 112Ko (http://dg1.dave.free.fr/Scenes.rar) .
And I'm using 7.5 too but only 2G RAM. {scratch head}, maybe i need some more.
Thanks for your help.

CiaranM : I did research for 'Set Instance Shape', but this node is not in the IceTree list. :shrug:

Thanks everyone.

DAvid.

EDIT POST (for CiaranM ). >> I was wrong about the Node name, I was looking for 'set instance shape' instead of 'Instance shape' . SO the last one is on the list, I'll try it right now. Thanks :applause:.

[toonafish]

Your scene kept crashing here too, after changing the "set instance geometry" node to "instance shape" it rendered fine.

[CiaranM]

EDIT POST (for CiaranM ). >> I was wrong about the Node name, I was looking for 'set instance shape' instead of 'Instance shape' . SO the last one is on the list, I'll try it right now. Thanks :applause:.

Yep, sorry, I was thinking of 'Set' because that's what it does. 'Set Instance Geometry' uses Mental Ray render archives, which might get you out of a jam if you need a billion instances, but often can be quite flakey.

[DaVee]

toonafish : Yes, ' instance shape' node works fine. :thumbsup:

CiaranM : 'Flakey' ??:eek: don't understand, ... whatever, I understood the essential of your sentence, that's the most important. ;)
And Thanks a lot for advices.

Thanks everyone, I hope this thread will help someone too ... one day ... in the future. ;)

[toonafish]

Maybe you should report it to AD tech support if you can, it smells like a bug to me. It's a very simple scene that should not give you any problems with ICE instances I think.

They are been very helpful and fast to respond.

http://subscription.autodesk.com

[Razorb]

How much memory do you have on your PC, one of the largest problems i see is low resources especially when it come to Raytracing, Instancing Geom, FG, GI. Softimage is hungry your setup renders fine on my machine with 8 gigs of DDR3 no problems at all, in making a planet explode and using instanced geom i have seen it crash on a 2 gig machine and render on the exact same machine with 4 gigs.

As with all 3d apps They love memory, most videos you watch (training that is) are done on machines with 8 gigs of ram minimum, since most of the high level math is done in memory big problems like tons of instanced Geom can cause extensive problems on low mem machines.

anyway your problem looks like that so i though i would throw it out there.

Peace!!!
The node really shouldnt matter if there is no animation on the objects anyway, but apparently it does.

[toonafish]

I tried it on a laptop with 2 gigs and xsi crashed with "instance geometry".

But I can't believe MR needs more then 2 gigs for a scene with 3 planes and a about 20 instanced cubes.

Instanced geometry is in need of some big optimizations anyhow. I've been trying to get some nice toony grass for some time now, with hair instances, ICE "instanced geometry" and "instance shape" nodes but so far no workable solution. All I get is unworkable rendertimes and lots of crashes.

When I do the same with Modo's new replicators it's no biggie, even with GI it's very fast.
Mental Images needs to step it up a notch.

[DaVee]

toonafish : Yes, I'll probably report this to AD support. thanks ;)

Razorb : 2 gigs on my machine as i said in a previous post ;) . I'll probably add 2 or more, It's not so expensive on LDLC.
Anyway, my scene Test is very small, GI values are set to default (almost), and models are really basics, 2gigs seems to be sufficient for this stuff. I changed one node and render worked fine and pretty fast. So,...
... it works.

EDIT: toonafish you post just before me. Yes, it seems instance geometry don't work properly and needs some improvements. but i'm not an expert. ;)

Peace, love, and flower pie. :D

David.

[CGTalk Moderation]

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.