Changing a push model property without marking it as dirty can cause desync when the actor goes in and out of dormancy

When the actor goes out of dormancy, it will replicate its push model property, even if it hasn't been marked as dirty. In this case, it seems the value of the property is not written to the shadow state on the server.
If the property is set back to its original value (i.e. the value that was replicated before it was changed and not marked as dirty), the server won't detect that the property has changed, and so it won't be replicated to the client, causing the desync.

1. Download licensee test project from linked UDN
2. Start a PIE session with a dedicated server and client
3. Observe the logs showing the property desync between the server and client

See linked UDN for more detailed repro steps.

How does TextureRenderTarget2D get TArray<uint8> type data?

How do I set a material as a post-processing material?

Why does the REMOVE method of map container remove elements have memory leaks?

Do I need to call Destory method to remove components from Actor when Destory method to remove Actor?

Where can I download the source address of the deployment cotum service associated with the PixelStream plugin?

What is the cause of the packaging error falling back to 'GameUserSettings' in ue5?

What is the difference between Camera and CineCamera?

How does TArray loop correctly remove elements in blueprints?

In UE5.4, custom variables in the level blueprint cannot be set to default values, and the eyedropper tool is also unavailable, whereas in UE4.27, these features work normally.

What controls of umg have mouse wheel events in UE4.27?