DS crashes after repeated material selection in the viewport

[mlru]

Plugin version 3.0.12.20
DS version 4.9.1.30
NVidia driver 365.19

Steps to reproduce:
1. load a prop with at least 5 materials into the scene
2. open the Octane viewport
3. select the material zones one after another by clicking on them in the viewport
4. at least at the 4. or 5. click my Studio crashes

I attached the DAZ Studio error report.
The octane debug log doesn't show something helpful:

2016-05-16 12:56:13.184 7616 b3.0.12.19 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2016-05-16 12:56:13.187 7616 b3.0.12.19 +++++ Plugin started.


2016-05-16 12:56:18.986 7616 b3.0.12.19 +++++ Plugin running.

2016-05-16 12:56:19.065 7616 b3.0.12.19 Tried to access null node
2016-05-16 12:56:19.068 7616 b3.0.12.19 Tried to access pin via an invalid ID P_ANIMATION (307)
2016-05-16 12:56:19.070 7616 b3.0.12.19 Tried to access null node pin
2016-05-16 12:56:19.100 7616 b3.0.12.19 Tried to access null node
2016-05-16 12:56:19.103 7616 b3.0.12.19 Tried to access pin via an invalid ID P_ANIMATION (307)
2016-05-16 12:56:19.106 7616 b3.0.12.19 Tried to access null node pin
2016-05-16 12:56:19.109 7616 b3.0.12.19 Tried to access null node
2016-05-16 12:56:19.112 7616 b3.0.12.19 Tried to access pin via an invalid ID P_ANIMATION (307)
2016-05-16 12:56:19.116 7616 b3.0.12.19 Tried to access null node pin
2016-05-16 12:58:06.142 7616 b3.0.12.19 Tried to access null node
2016-05-16 12:58:06.145 7616 b3.0.12.19 Tried to access pin via an invalid ID P_ANIMATION (307)
2016-05-16 12:58:06.148 7616 b3.0.12.19 Tried to access null node pin
2016-05-16 12:58:06.151 7616 b3.0.12.19 Tried to access null node
2016-05-16 12:58:06.154 7616 b3.0.12.19 Tried to access pin via an invalid ID P_ANIMATION (307)
2016-05-16 12:58:06.157 7616 b3.0.12.19 Tried to access null node pin

[face_off]

Does this happen for you on a figure (like Genesis 3), or only props?

Paul

[mlru]

Does this happen for you on a figure (like Genesis 3), or only props?

Paul

I loaded a single G3F and the program didn't crash.
Then I added a car figure (bazze's Musclecar), had the scene rebuild, and DS crashed after several clicks on the car and G3 material zones.
My try in the post above was with props.
Uwe

[face_off]

Thanks Uwe - I cannot replicate this, but have had it in the past. Is it only crashing if the pick cursor is clicked when it's over BOTH the prop and the figure? ie. if you material pick on a pixel when does not contain geometry from both items, does it still crash? And if it DOES crash when only over just the prop or figure, does it crash when picking the prop material, figure material, or both. And is the Material name displayed as you as hovering over the material just before you pick correct?

Paul

[Galatea]

Plugin crashes after material is selected with the material picker.

Plugin version 3.0.15.21
DS version 4.9.0.63
NVidia driver 365.10

Steps to reproduce:

1. Load the starter essential barefoot dancer figure and shaded haven scene.
2. Open the octane view port.
3. Select the barefoot dancer torso material then select the floor material alternating between the two material picker, after picking between the two materials about 5-6 times Daz Studio will crash.

Additional information:

When a single Genesis 3 female figure is in the scene with nothing else in the scene I can use the material picker to make selections multiple times without the plugin crashing.
If I add a hair figure to the Genesis 3 female figure and alternate picking materials between the two, the plugin will crash.

The material name is displayed as I am hovering over the material just before the pick.

Daz Studio Application error report file attached.
I

[face_off]

I think I have finally been able to resolve this issue - and the fix will be in the next release of the plugin (3.0.21.23).

Paul

[Galatea]

I think I have finally been able to resolve this issue - and the fix will be in the next release of the plugin (3.0.21.23).

Paul

Great news! Thanks for the update

[mlru]

I think I have finally been able to resolve this issue - and the fix will be in the next release of the plugin (3.0.21.23).

Paul

very fine! thanks a lot, Paul