[MAJOR] Almost all hidden properties are now disallowed, they have been allowed since UEFN released until 34.30.

[Velocity_Zero]

@Kev.EG

I mention 37.00 because we plan on making those unexposed property validation warnings into errors again - the thing that prompted this thread in the first place (but hopefully should not be an issue now that we’ve identified the key properties from this thread and actually exposed them).

Well, in that spirit I hope we’ll get some good news for this as well:

Request for official exposure of the desired server tick rate

Summary In the past Epic Games performed multiple tick rate switches in public. The last switch to 60 TPS caused many creators to oppose the silent change as many had hard coded animations to the known 30 TPS. However I personally view that particular issue as a developer error. The second to last switch happened on LEGO islands where the TPS dropped to 20 TPS. I would like to request for official exposure of the the desired tick rate setting that controls the server TPS. Having the ability to …

While I understand that you might not officially provide a comment on this particular request. I’m sure there are some islands already published with that setting being used and even I need it for better transform accuracy in order to fight the following problem:

[EXTREMLY CRITICAL] [BUG] Fortnite servers report unreliable / unstable / highly fluctuating translation via `GetTransform` on `fort_character` and `fort_vehicle`

Summary positional.GetTransform is unstable and reports unexpected translation values. This issue is more apparent when calculating the velocity between two translation vectors and moving the character or vehicle at a relatively constant top speed in a single direction. Additionally some dirty values repeat in a certain pattern (see rocket racing car when standing still). While dirty transform values that appear when standing still could be filtered out, smoothing dirty transform values while mo…