ActionText and ObjectText are reset, when models are streamed in

Bug Reports Engine Bugs
,
#1

when using StreamingBehavior Improved, when you stream out a model and then stream in it, it redefines the objectText and ActionText of the Proximity Prompts

Here’s a place where you can replicate this effect, just teleport between the quest npcs, and you’ll see the texts reset.
Proximity Stream.rbxl (84.2 KB)

Expected behavior

That it works like the default behavior, where the text is not changed.

2 Likes
#2

Thanks for the report! We’ll follow up when we have an update for you.

#3

In your repro place you are changing the values of ObjectText and ActionText only on the client, the values are left unchanged on the server. This is effectively creating a desync between the client and the server.

When ModelStreamingBehavior is set to Default instances in the Giver models that are not parts or descendants of parts are not streamed out, and as a result any local changes remain.

However, with improved model streaming, or if the Giver models were set to be atomic, then the entire models are streamed out together. This means that any local changes to any of the instances in the model will be lost on stream out, and replaced with the server state of the model on stream in.

I can think of a few different options for your situation:

  1. Change the ActionText and ObjectText values only on the server, not on the client. If you are making per player specific changes then this may not be an option for you.
  2. Use CollectionService or similar techniques to detect when the models are streamed in and make the necessary changes locally when needed.
  3. Don’t use improved model streaming mode.
  4. Use persistent models so the Giver models are never streamed out.

Those are ordered by what I consider the best solutions, with option 1 being preferred if it is viable in your situation.

Sorry for the delay in responding to your bug report. As I indicated we don’t think this behavior is an engine bug, this is expected behavior due to the local changes and client/server desync.

1 Like