VrayStochasticFlakes - scale not mappable

[rcm_andy]

Hi,

i noticed that in comparison to previous vray versions the flake_scale paramater of the StochasticFlakesMtl is no more mappable/keyable/expression.... I recently switched to a newer version which broke my shader as it looses the connection when the scene is referenced into another.

You can´t make the connection either via connecting the ports/connection manager/mel scripts. See screenshot attached.

What is the reason for that ?

Thanks,
Andy

[intercard]

Hello Andy !!

So this is correct !! I checked your issue and only you can connect it using drag and drop from Attribute editor...

I hope this advice helps you until a member of the DEV Team check your problem. (I seem to remember that it is a new algorithm, therefore it brings important modifications and a more realistic result.)

[hermit.crab]

The parameter is designed to accept float values only, hence why we hid its map input (notice there's no map button as well). Yes, dragging and dropping does work, however, the map will be evaluated to a float value.

[rcm_andy]

For me either drag/drop of an remapValue node is blocked:

// Error: line 1: The attribute 'VRayStochasticFlakesMtl1.flakeScale' cannot be connected to 'remapValue1.outValue'.

[rcm_andy]

The parameter is designed to accept float values only, hence why we hid its map input (notice there's no map button as well). Yes, dragging and dropping does work, however, the map will be evaluated to a float value.

To me that is not a good explanation for hiding a previosly available value/port. Other float/integer non RGB ports are available. To follow your logic there should even less ports available.

What i don´t understand is why you change a basic things like that without a reason (at least to me)

[iliyana.vladeva]

Hello!
As described above, the flake scale parameter is supposed to accept only float values, it is not supposed to work with texture connections.
All changes made in that regard prompt the expected usage.
I can see that in your case this leads to some issues, so this was logged in our internal bug tracking system under VMAYA-11048 for further consideration.

Meanwhile as a workaround you can execute

vray setAttrConnectable "<nodeName>" "<attributeName>" 1;

Example:

vray setAttrConnectable "VRayStochasticFlakesMtl1" "flakeScale" 1;