MAXScript gets "undefined" from material property in FStormMatProject helper

[GSystem]

MAXScript gets “undefined” from the material property in the FStormMatProject helper although this property has an assigned material.
Will this be fixed?

[Karba]

Material is not assing directly as for regular gometry. it is set via projection parameters

[GSystem]

Material is not assing directly as for regular gometry. it is set via projection parameters

Yeah, I know. I wanted through maxscript to take the material that is assigned in the "material" slot of the FStormMatProject helper and replace it with another:

But when I try to get this material through maxscript (ie $.material), I always get "undefined"

[Karba]

Then I don't know... I am not strong in max script.

[GSystem]

Then I don't know... I am not strong in max script.

I think this is due to the fact that there is a conflict of property names.
The fact is that the property name "material" is reserved in 3ds max as the global property name, with which you can access the material assigned to the scene node.
This conflict can be resolved if you give a different property name to the internal parameter FStormMatProject helper, corresponding to the slot "material: "
For example, it could be "material_decal" or "mat_decal" or even just "mat". The main thing is that these names are not identical.
It would be nice if you changed this, since many use the capabilities of maxscript to speed up and simplify the execution of many tasks in the 3ds max environment.

[GSystem]

Thanks for the update in which you fixed this, Karba!
Now I can take material from the FStormMatProject helper using the $.proj_material parameter and the problem no longer exists!