Instance of HISM will bug the material custom data float IF moving on the current location.

[SophiaWolfie]

I came accross this bug in CPP. When i move my instance sometimes it happens that my instance is moving to the position it is already currently in.

So if you are moving your instance and the position happens to be the same, this will reset the material Custom Data float to its default value.

Is there a way to fix this?

Video and project:

TestBugISMMaterial.rar (1.8 MB)

[3dRaven]

Maybe not a potential fix but you could add a macro to check if the transform has changed since the last update and just skip the update instance transform node if the value remains the same. (yes this would require caching and an extra branch)

For a minute I thought the c++ version would work but it just defaults to the instance parameters

[SophiaWolfie]

Yup this is the only solution. This or just refresh the SetCustomDataFloat. Both work. Though the one that checks if location is the same will not be enough for situations where rotate and scale only.