Octane and DS Instances problem

[LittleFisky]

Hi! There is some scenes in my library that have a lot of instances. Octane can load the scene, but all instances are misplaced. I saw a topic about Stonemason's scenes, But in my case scene is working!

Octane Plugin version: R4.0.0.41 Subscription. DAZ Studio version: 4.11.0.231

Octane render on the left, IRay - on the right (IRay is a bit darker: I rendered it for comparsion)

[face_off]

Hi. If you can provide a simple scene which reproduces the instances issue, I can take a look. At a guess, perhaps there is some sort of nested instance structure in the scene which the plugin is not handling.

Paul

[birdovous]

Sometimes I face similar problem with misplaced objects upon scene load. Selecting "Reload / Rebuild Scene" in the Octane Render Viewport usually fixes the issue (at least for me).

[LittleFisky]

Hi. If you can provide a simple scene which reproduces the instances issue, I can take a look. At a guess, perhaps there is some sort of nested instance structure in the scene which the plugin is not handling.

Paul

I tried to recreate the situation by myself, but everything went very good. I found that the only scene I have problems with is a "Fern Lake" by Stonemason

[TRRazor]

I found that the only scene I have problems with is a "Fern Lake" by Stonemason

As it is the case with every other Stomemason prop, where instancing comes built-in with the prop.

The OCDS plug-in (to this date) hasn't caught on to the UltraScatter shnnanigans Stonemason is playing, designing his props.
Would be great to see this getting fixed some day.

[UHF]

This is still dead in Octane for Daz. Its a real shame. I really wish I could use this scene.

[UHF]

OK.. there is a script (which needed a quick update.. available 35 days from now) which will convert scenes including Ultra Scattered instances into objects;
Instances to Objects;
https://www.daz3d.com/instances-to-objects

Willow Creek by stonemason is a serious mess for Octane to handle;
https://www.daz3d.com/willow-creek

Ideally the plug in developer would look up the single function call that can to solve this... but if you run this script from Daz it will do the conversion.

However it results in an insanely large number of objects seriously slows Daz. Turn off 'visible in view pane', and 'selectable in view' for all the converted instances.

The Octane plugin is another concern. Do not use the plug in without taking some precautions and being careful. (It renders fine, but using the plug in is an effort.)

Before attempting to even look at or edit textures, make sure only a single texture is selected in materials under Scene Surfaces. Otherwise the plugin will hang forever (I gave up after 5 minutes) when the menu attempts to highlight all the surfaces using that material. There are like 1700 (?) Grass Instances in Willow Creek.

You still have to deal with horrific lists of items when you start to work the textures. Its insane. Be patient and you will get through this.

Save Often, and double check that you only have one material visible under Scene Surfaces.

[UHF]

So even after you do all that, there's still a limit or a bug in the plug in. I can edit all the textures, but either I can't save them all or it won't load\apply them all. This is after you put up with the 5 minute save and load times.

In addition, there is something utterly broken with the stonemason cameras. I cannot understand nor decipher what they do, but all cameras get set generating 4x4 pixel renders this happened even if I reset the render window size. I cannot reverse, or fix this. I cannot use any cameras at all after loading the stonemason cameras.

A hint here... he's an Octane user, and its entirely possible some old Octane crap is in his camera settings. I dunno... is there a filter for old Octane crap (assuming that's the issue)? I did load the cameras with the 4 'don't load' options ticked off at the bottom of Octane preferences. Does that affect cameras?

[UHF]

Never mind that last bit... It seems to have saved. (I had loaded the scene one additional time with 4 'don't load' options, so maybe that cleared it up.) I now have a working scene, although its a bit of a chore to work with.

[face_off]

Thanks for posting this. Fixing the loading of grouped instances in the plugin is not a simple thing, and will require rewriting the code that handles instances. It is high on the TODO list.

Paul