Particle image rendering messed up after changing Orientation

[SkyyOrbs]

I have a particle system where the image changes after editing some properties. Undoing doesn’t fix the texture, but setting the texture again on the particle does fix the visuals.

Original particles:

After changing the particle Orientation, the particles render wrong, see below image. Hitting undo or setting the property back doesn’t fix them.

If I close Studio when the particles are in the “bad” state, they’re fixed upon reopening studio.

Here’s the particles:
badparticles.rbxm (4.3 KB)

[Focia19]

This is just an acknowledgment announcement!

We’ve filed a ticket to our internal database, and we’ll follow up when we have an update!

Thanks for the report!

[CoastalStarlight]

The reason this bug is happening is because the particle emitter is applying the FlipbookLayout property you have set when you adjust the unrelated parameters (brightness, orientation, etc).

When the particle texture is initially set, we do an explicit check to see if the given texture is flipbook compatible, and force it to not use the flipbook layout if the texture is incompatible. This is why resetting Studio or removing and reapplying the texture fixes the issue. However we don’t do this when adjusting unrelated parameters. This is a bug, so I’m gonna submit a fix. Thanks for pointing out.

If you’d like to fix this issue locally in the meantime, you’ll have to set the FlipbookLayout explicitly to None instead of Grid2x2. Unfortunately you can’t actually modify this value when your texture is flipbook incompatible, so you’ll have to switch the texture to one that is (just look up any 64x64 decal in the toolbox), then fix the FlipbookLayout value, then switch the texture back to your original.

[SkyyOrbs]

Thank you! I modified an existing particle from a particle pack which is probably how I got into this weird state.

[CoastalStarlight]

This bug should be fixed in release 652 now.
I’m guessing you probably used the work around I described to fix the issue, but if you didn’t this bug should no longer be happening.
Thanks for the report