MeshPart.Material = Forcefield, unintended behaviours

Bug Reports Engine Bugs
#1

I am using two identical mesh-parts to create a glow effect, this works really well.
https://i.gyazo.com/a3b29b7a1a3cf71a6296153daf594f70.mp4

However, I noticed that once I change the internal part’s transparency property, even the smallest amount, it takes on the properties of ForceField. It’s current materials are set to SmoothPlastic.

image
image1220×636 666 KB

Not only this, but the inverse can then happen. If I have another identical MeshPart with its transparency changed and then set a part to use forcefield, the part with forcefield takes on transparent properties.

image
image1036×344 290 KB

In order to then fix this bug, I have to ensure every identical part has its transparency set to 0 and then change its material from Forcefield to something else to Forcefield.

Setup:

  • Lighting
    • ShadowMap (Though this happens on any lighting setting)
  • 3 parts
    • One normal MeshPart
    • One MeshPart with ForceField material
    • One Normal MeshPart used to alter its transparency property

This is a fairly simple repro problem I’m finding too, if you are able to repro, post a screenshot here. If you have a use-case, I’d be interested to hear it but I’m sure this is an unintended behaviour

3 Likes
#2

its looks like a bug indeed, we’re working on a fix

5 Likes
#3

Also seems to happen when I set something to force field (can even delete it) and then try moving objects… they take the force field effect when being moved.

#4

That’d be the transparency of the part when moved. Normally they go about .5-.3 transparency, with this bug any transparent identical object will be force-field, thus auto-force field.

#5

This sounds very similar to an old bug with neon. Maybe they’re caused by the same oversights.

#6

Yes, but my problem is on ANY part that hasn’t ever even been forcefield before