OcDS 1.2.120.34xx - BUG REPORTS

[michael_g]

In the node editor, when you select RGBspectrum the RGB spectrum does not appear it stays on power.

[t_3]

In the node editor, when you select RGBspectrum the RGB spectrum does not appear it stays on power.

see it. in fact the panel does not update after the change; if you click away and back the panel shows the change; rather annoying, so expect to see an update later today...

[michael_g]

In the node editor, when you select RGBspectrum the RGB spectrum does not appear it stays on power.

see it. in fact the panel does not update after the change; if you click away and back the panel shows the change; rather annoying, so expect to see an update later today...

Yes so it does, ok cool. Has the renderer changed to? it seams a lot faster.

[t_3]

Yes so it does, ok cool. Has the renderer changed to? it seams a lot faster.

the rather big step from octane 1.13 to 1.20 indeed means lots of engine improvements and notable better speed also...

[Isotemod]

I'm having no joy from replace active maps.

I'm using this on a genesis figure to create a skin material for Torso then copy paste to head and replace active maps so it swaps the torso maps with the head maps on the new material.

At the moment it doesn't swap the maps.

[t_3]

I'm having no joy from replace active maps.

I'm using this on a genesis figure to create a skin material for Torso then copy paste to head and replace active maps so it swaps the torso maps with the head maps on the new material.

At the moment it doesn't swap the maps.

have you used template nodes or just so? might be some bug lately incorporated with the templates (that affect changing non-template maps)...

[Isotemod]

I'm having no joy from replace active maps.

I'm using this on a genesis figure to create a skin material for Torso then copy paste to head and replace active maps so it swaps the torso maps with the head maps on the new material.

At the moment it doesn't swap the maps.

have you used template nodes or just so? might be some bug lately incorporated with the templates (that affect changing non-template maps)...

This was not template nodes.

I attempted to use template map nodes after tha but the paste operation resulted in a crash so untill the detailed instructions for there use is out i'll wait before attempting them again.

EDIT

I couldn't wait and tried the templating which worked fine this time.

But to confirm replace active maps does not work at this time.

[DrHemulen]

I think there's an issue with the VRAM monitor



I'm also still getting the issue where the viewport is "decoupled" from the rest of the system, and it doesn't update with changes, no matter which buttons I press (or if I close/open it). It was the same in the old version.

[t_3]

I think there's an issue with the VRAM monitor
I'm also still getting the issue where the viewport is "decoupled" from the rest of the system, and it doesn't update with changes, no matter which buttons I press (or if I close/open it). It was the same in the old version.

can you pls post or pm me a screenshot that ideally shows the vp and the preferences tab when in this state, and a short description what particular steps lead to this? (like i.e. open ds with a scene, or open ds then open scene, or drop content or whatever else).

what exactly is the behavior: no more render updates? or no updates from either material and/or render settings and/or environment changes, and/or camera changes; or just no geometry updates?

in addition: the "reload" button in the viewport does a few things more when ALT+clicked or CTRL+clicked; CTRL-click forces a geometry reload even when the geometry wasn't changed, ALT-click deletes all geometries from octane and rebuilds them; also turning final on/off will completely rebuild a scene in two different states (as long if not limited by scaled/ies mesh lights and instances) - does any of that change the situation?

can you still use picker tools and see node/material labels when hovering over the viewport using the respective tools?

[t_3]

@DrHemulen first and apart from all that just posted: what gpu/amount of available vram do you have?