Hi!

I'm hoping someone else has run into the same issue and can give me some hints what I might try to fix this.

My problem is that over time, the z-axis positioning of my relatively new Elegoo Neptune 4 Max seems to become slightly unstable. That is, after I level the bed and adjust the z-offset, everything looks fine. However, if I move up and down by a couple of centimeters for a few times, the z-offset is wrong again.

Due to this, I had to restart quite a few prints now, because wrong z-offset leads to a bad first layer.

Now I wonder what I should attempt first in order to fix this?

At work we are currently investigating how we could add a reasonably sane optional type for blueprint.

We have modified the native TOptional type heavily, to make it more convenient, by adding Map()/Bind()/Flatten() methods.

Now we would like to add a similarly convenient optional type for Blueprint use.

We have already started working on a UBlueprintCompilerExtension to detect invalid pin connections, but we haven't started on the actual data type itself.

Does anyone know about a plugin that offers this functionality?

Or, alternatively some good resources on how one can write custom Blueprint graph nodes with wildcard pins?