OTOY Forums

DrHemulen wrote:It's weird, because it actually works well with the autogenerated materials. It's only when I try to drop my own materials on the autogenerated ones things go wrong. Also I can't map a single OCD material to a DAZ surface sometimes. This is just ignored.

its more a problem on the surface.

i.e. a bot genesis consists of close to 1000 material ids in total; around half of them will show up in the rendering, the other half needs to be skipped, as they mean surfaces replaced by grafted surfaces. in total there are 428 material pins rendering. when auto mats are created, it is guaranteed, that any of the 428 pins receive a material. but they now need to be mapped to 160 daz materials that visually represent the geometry surfaces, that will in the end also serve as link anchors for the oc <> ds mat link interface - and that is the point where things are going to mess up, as i'm not able to work out how to map them together correctly. so the ui only shows a fraction of what is handled internally, and that particular fraction might not contain all needed mappings, so replacing links later on won't affect all matching surfaces.

if i would present all 428 mat pins, it would probably work without problems, but i guess it also won't be much fun to edit such a number of material links...

Material to surface drag/drop lag caused by instantly displaying the target surface's parameters on hover leads to accidental selection of other mats and sometimes entire groups. This is not related to any viewport drag and drop.

I just noticed that just by merging certain poser props into DS will cause a good scene to start duplicating mats like I reported earlier.
It appears that poser props with the bones trigger the bug...

vortex3d wrote:I just noticed that just by merging certain poser props into DS will cause a good scene to start duplicating mats like I reported earlier.
It appears that poser props with the bones trigger the bug...

i have already found the reason and most probably fixed it. need a few hours testing with all the various import/load scenarios.

btw _this_ above is an expected result: materials will be only grouped by their skeleton*) root object - so adding a skeleton prop twice into a scene will also result in of course identical materials for both of them. the bug was that this did indeed also happen when loading a scene thus overruling the previous setup.

*) the limited grouping is mostly targeted at figures or i.e. hair props, where you usually like to have mats separated per figure, even when they are identical at the beginning, but it therefore also happens with props that are set up as skeletons...

vortex3d wrote:Material to surface drag/drop lag caused by instantly displaying the target surface's parameters on hover leads to accidental selection of other mats and sometimes entire groups. This is not related to any viewport drag and drop.

i was already close to dump the selection update during drag and drop.

the idea was once to give some additional info about what is going to be (re)linked, but it turns out that the full node display isn't really helpful anyway. it's a bit tricky to allow the needed selection change but omit the selection update, but possible.

ps: since there are now preview renderings for scene mats (as soon they are back at least), i'm most probably going to show the target preview only - this'd give a bit more info about the link result, but will be lag-free...

t_3 wrote:

vortex3d wrote:Material to surface drag/drop lag caused by instantly displaying the target surface's parameters on hover leads to accidental selection of other mats and sometimes entire groups. This is not related to any viewport drag and drop.

i was already close to dump the selection update during drag and drop.

the idea was once to give some additional info about what is going to be (re)linked, but it turns out that the full node display isn't really helpful anyway. it's a bit tricky to allow the needed selection change but omit the selection update, but possible.

ps: since there are now preview renderings for scene mats (as soon they are back at least), i'm most probably going to show the target preview only - this'd give a bit more info about the link result, but will be lag-free...

Awesome, thanks!

t_3 wrote:

vortex3d wrote:The "Automatic material updates after content loads" option is adding negative numbers next to the each related material with every change.
So far this feature strips Octane materials upon related surface changes in DS.

should be both fixed now (the latter was somehow connected with the multiplying mat issue).

btw, thanks for the constant issue updates

You're very welcome, and thank you for making this plugin even better!

Octane Render Main UI (F12) will not start after fatal crash (Same tab crash as previously reported).
I tried restarting DS several times and flushed the RAM, but no luck.
I'll cold boot my PC and see if that solves it, but I think it's file corruption.

vortex3d wrote:Octane Render Main UI (F12) will not start after fatal crash (Same tab crash as previously reported).
I tried restarting DS several times and flushed the RAM, but no luck.
I'll cold boot my PC and see if that solves it, but I think it's file corruption.

No luck, I re-installed the plugin, but the main UI still does not start.
The viewport works and renders as expected.
The DS Log shows no errors or warnings.
Clean installing next.

vortex3d wrote:

vortex3d wrote:Octane Render Main UI (F12) will not start after fatal crash (Same tab crash as previously reported).
I tried restarting DS several times and flushed the RAM, but no luck.
I'll cold boot my PC and see if that solves it, but I think it's file corruption.

No luck, I re-installed the plugin, but the main UI still does not start.
The viewport works and renders as expected.
The DS Log shows no errors or warnings.
Clean installing next.

sry for the textures tab crash - it'll be probably a good idea to not use it until i have sorted this out.

as for the main pane not showing up - could it be that ds has mixed up the pane position to somewhere outside the screen? if so it will help to restore the workspace layout: main menu > window > workspace > ...

ps: the viewport position is controlled and saved/restored by the plugin itself, the main/nge panes are controlled by studio.