World rebasing does not cause halts or slowdowns based on amounts of items.
Or else, just imagine how long it would take to rebase something with foliage. It would never be seamless.
But do continue to be convinced you are doing things right. By all means.
The end result is that eventually your company will be forced to hire an actual professional like me to implement a proper rebasing system instead of someone who doesn’t understand the basics of computing.
And sure, he’s found a bug.
No one said thats a bad thing.
What has been repeatedly said is that who cares.
No one should expect the engine to function with any precision past 200m from origin.
Unless you dont understand math, then sure, you can expect anything you like.
@MostHost_LA OP repeatedly pointed out that in UE4 they were able to go massive distances without issues.
Basically, the OP’s use case should be a valid, and jitter free experience. And it would appear that with a slight modification to the engine noted above fixes/improves the issue at hand.
Hi @Elitic, can confirm your suggested value of 524288.0 worked like a charm. We were having issues where individual bones in our animation/skeleton would increase in jitter the further from 0,0,0 you were. I tested up to 995740, 1147270, 62 coordinates without seeing the jitter AT ALL.
Math is not an opinion.
Though by your own writing it already seems clear that 2x2 is 24 for you. You are perfectly free to wallow in your own ignorance.
LWC are still busted in 5.1 along with HLOD generation and a bunch of other issues, including but not limited to rendering pipeline and nanite problems.
Just like before, you need rebasing to deal with anything that requires any kind of accuracy.
That’s unlikely to change, ever, really.
I’m out at 1,000,000 x 1,000,000 and attached meshes to my skeleton don’t shake anymore. I used #define UE_LWC_RENDER_TILE_SIZE 128000.0
1048576.0 /* Maximum distance representable by a float whilst maintaining precision of at least 0.0625 units (1/16th of a cm) - Precision issues may occur for positions/distances represented by float types that exceed this value */
So 2097152.0 would be 1/8th of a cm at max tile distance. Which is way too loose for what we needed.
Seems that TILE_SIZE does some form of offset/rebasing:
So is the animation/skeletal mesh, and you are looking for micrometer precision on most world applications for skinned mesh usage.
Anything above 1mm precision will cause possible gaps and lines in composite characters, even when properly merged.
Ergo, world origin shifting is the only way to achieve this.
Our world is only ~20km x 20~km, so we were able to do this. I don’t think this would work in the max 80x80km.
There is still a very faint jitter, which was acceptable for us as you would need stop moving and stare at it pretty hard to see it.
Honestly would be nice to see a WorldSettings slider that let you choose a tile/render offset and spits out the “recommended max world size”.
Also, (I have not tried this yet) you could reduce the UE_LARGE_WORLD_MAX size. It is 87km square by default. As the comment suggests:
// Note: Modifying WORLD_MAX affects UE_LWC_RENDER_TILE_SIZE in Engine\Source\Runtime\Core\Private\Misc\LargeWorldRenderPosition.cpp and may introduce precision issues in shaders using world coordinates.
Jittering meshes is still a problem in UE5.2
Origin shifting does not help much at all. In fact you can even see some very, very small amount of jitter at a 0.0 world location.
