Removing SurfaceAppearance in a StreamingMesh model during runtime forces mesh into streamed version

Bug Reports Engine Bugs
#1

Issue Type: Display
Impact: High
Frequency: Constantly
Date First Experienced: 2021-04-17 00:04:00 (-04:00)
Date Last Experienced:

Reproduction Steps:

  1. Create a model with the LevelOfDetail set to StreamingMesh
  2. Add in MeshParts to the model
  3. Add SurfaceAppearance objects to the meshes
  4. During runtime, remove one of those SurfaceAppearance objects
  5. Observe that the model goes into its “streaming mesh” mode.

It appears that the model will go back to normal if the SurfaceAppearance object is placed back (via script; can’t be cut/pasted back)

Expected Behavior:
The expectation is that the model does not go into its streaming mode when a SurfaceAppearance object is removed.

Actual Behavior:
The model goes into its streaming mode.

A video of how I discovered this in my game:

A video of the issue isolated in Studio:

Workaround:

20 Likes
#3

Thanks for the report! We’ve filed a ticket to our internal database and we’ll follow up when we have an update for you.

4 Likes
#4

I don’t think it’s related to SurfaceAppearance, it’s the same when you delete Parts. Basically when a model has less instances than the server, it’s considered still streaming. So I think the workaround is delete objects from the server.

3 Likes
#5

Ah, ok! Unfortunately that workaround won’t work for me, since I am specifically trying to change the appearance only for the client (I am trying to create a “highlight” effect, which requires me to remove the SurfaceAppearance temporarily).

2 Likes
#6

Deleting objects created in client should be fine. You can remove it in the server and create SurfaceAppearance in client.

#7

I’ve only been deleting from the client, not server

#8

To clarify:

  • if the object is created on the server, but deleted from a local script on the client, it will trigger bad behavior from an LOD perspective
  • if the object is created on the client and also deleted on the client, both actions should not interfere with LOD
2 Likes