OTOY Forums

TBFX wrote:Are you manually instancing them? Have you checked that the shape node has movable proxy on? Everything working great on my system?

T.

yes- manual instance, movable proxy off ( if i switch that on - all the instances disappear in the render )

OK - i have instancing working but - doesn't work with groups...( i had tried it with single objects but i thought the objects weren't instances because the surfaces weren't highlighting in unison like instance surfaces often do etc. ) Even though i switched movable proxy on, on the original object, that didn't affect the objects already made and it made them disappear in the render.

YUP - very fast voxelizing and no memory increase - sweet. I didn't realise that instancing wouldn't work with groups.

jmfowler wrote:YUP - very fast voxelizing and no memory increase - sweet. I didn't realise that instancing wouldn't work with groups.

Yeah I had to combine my trees, had forgotten to mention Hierarchical instancing didn't work to JimStar but Slimshader has already done that for us in the last versions thread.

T.

TBFX wrote:

jmfowler wrote:YUP - very fast voxelizing and no memory increase - sweet. I didn't realise that instancing wouldn't work with groups.

Yeah I had to combine my trees, had forgotten to mention Hierarchical instancing didn't work to JimStar but Slimshader has already done that for us in the last versions thread.

T.

thanks for the help T, one thing I did learn is just how bad things can get when you max out your system ram, I may have 4gb v.ram but voxelising geometry to fill it becomes a nightmare once you're in swap......going to take the new machine all the way up to its 32gb limit ( and then add an ssd for swap like jimstar if i need it )

I did nod optimized the instancing speed so far, I worked with particles in these versions. I will check it about instances, why it takes so long in jmfowler's case... It would be good if jmfowler may give some scene in which he has the speed problems.
Don't worry, I will optimize all aspects step by step...

PS. More RAM - more speed when big particle- and instance- systems. As I'm adding the caching algorythms for speedup the things...

JimStar wrote:I did nod optimized the instancing speed so far, I worked with particles in these versions. I will check it about instances, why it takes so long in jmfowler's case... It would be good if jmfowler may give some scene in which he has the speed problems.
Don't worry, I will optimize all aspects step by step...

PS. More RAM - more speed when big particle- and instance- systems. As I'm adding the caching algorythms for speedup the things...

because i was using a group with a heavy mesh ( without movable proxy switched on ) and then instancing that.

- you can try it with a sphere 90 polygons ( movable proxy off) , put it inside a group by itself and then instance that group 900 times , now hit IPR. you will see.

Thank you for update Jim!
Bugs that I found in 3.03c:
-Sometimes Opacity for octaneGlossyMaterial is resetting to 1.0 while I'm trying to change its value. At this time opacity in shader swatch isn't updating.
-Octane doesn't render any render layers except for masterLayer and I receive an error message:
// Error: Octane: Could not find the camera in layer "Octane". Octane render stopped. //

jmfowler wrote:because i was using a group with a heavy mesh ( without movable proxy switched on ) and then instancing that.

- you can try it with a sphere 90 polygons ( movable proxy off) , put it inside a group by itself and then instance that group 900 times , now hit IPR. you will see.

But in this case you may look at the verbose output, which my say you what takes this long time...
As I just created 900 instances of spheres, with disabled "Movable Proxy" it took 25 seconds to load on my machine: 17 seconds instances (it is not optimised so far) and 8 seconds voxelizing... The peak of memory use by Maya was about 1G during render... About "not seen in render if movable proxy is enabled" - yes I see, it's a bug, will fix it in next version. It is only if you instance groups, if the meshes itself - all is OK...

arh-osa wrote:-Octane doesn't render any render layers except for masterLayer and I receive an error message:
// Error: Octane: Could not find the camera in layer "Octane". Octane render stopped. //

This message appears when the camera you are trying to render from is not included in the layer which you are trying to render...

JimStar wrote:

arh-osa wrote:-Octane doesn't render any render layers except for masterLayer and I receive an error message:
// Error: Octane: Could not find the camera in layer "Octane". Octane render stopped. //

This message appears when the camera you are trying to render from is not included in the layer which you are trying to render...

I tried to associate cameras in Relationship Editor and get the same result. V-Ray for instance works with the same scene correctly for all render layers without error messages.

arh-osa wrote:I tried to associate cameras in Relationship Editor and get the same result. V-Ray for instance works with the same scene correctly for all render layers without error messages.

Strange, it works in my case OK:
I create the empty layer "layer1", if I'll try to render it, I'll get the same error: Select the objects and camera: Add them to that layer: Press IPR, and voila, "layer1" is rendered: