# LWC (Large World Coordinates) do not work for First Person Shooters/Driving games. Wobbly rendering artefacts UE5 only (UE4 works fine)

**URL:** <https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748>\
**Category:** World Creation\
**Tags:** Open-World, unreal-engine, UE5-0, question\
**Created:** [September 20, 2022, 5:04pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748 "2022-09-20T17:04:43Z")\
**Posts on this page:** 15\
**Page:** 2

<div class="post-metadata">

**Author:** ![MostHost\_LA](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/mosthost_la/32/907035_2.png) [@MostHost\_LA](https://forums.unrealengine.com/u/MostHost_LA)\
**Post date:** [September 29, 2022, 10:38am UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/24 "2022-09-29T10:38:23Z")

</div>

> [@Lildreas](#):
>
> I’ve got tons of actors, and I need to maintain a stable framerate of 90fps

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.

---

<div class="post-metadata">

**Author:** ![EvoPulseGaming](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EvoPulseGaming](https://forums.unrealengine.com/u/EvoPulseGaming)\
**Post date:** [January 15, 2023, 7:08pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/25 "2023-01-15T19:08:15Z")

</div>

@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.

---

<div class="post-metadata">

**Author:** ![EvoPulseGaming](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EvoPulseGaming](https://forums.unrealengine.com/u/EvoPulseGaming)\
**Post date:** [January 15, 2023, 7:09pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/26 "2023-01-15T19:09:26Z")

</div>

I’ll give this a try myself. Thank you for posting a possible workaround.

---

<div class="post-metadata">

**Author:** ![EvoPulseGaming](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EvoPulseGaming](https://forums.unrealengine.com/u/EvoPulseGaming)\
**Post date:** [January 15, 2023, 7:12pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/27 "2023-01-15T19:12:47Z")

</div>

![image](https://d3kjluh73b9h9o.cloudfront.net/original/4X/e/8/f/e8f6e3edf34ae1936ba57276db3dc9422c43e739.png)  
Not exactly confidence inspiring. This is 5.1

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.

---

<div class="post-metadata">

**Author:** ![MostHost\_LA](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/mosthost_la/32/907035_2.png) [@MostHost\_LA](https://forums.unrealengine.com/u/MostHost_LA)\
**Post date:** [January 16, 2023, 11:28pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/28 "2023-01-16T23:28:01Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![EvoPulseGaming](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EvoPulseGaming](https://forums.unrealengine.com/u/EvoPulseGaming)\
**Post date:** [January 25, 2023, 4:17pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/29 "2023-01-25T16:17:05Z")

</div>

> [@Elitic](#):
>
> #define UE\_LWC\_RENDER\_TILE\_SIZE 262144.0

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:

float3 Offset = (LWCGetTile(Lhs) + LWCGetTile(Rhs)) \* UE\_LWC\_RENDER\_TILE\_SIZE + Lhs.Offset;

The render side of things is still using floats.

---

<div class="post-metadata">

**Author:** ![MostHost\_LA](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/mosthost_la/32/907035_2.png) [@MostHost\_LA](https://forums.unrealengine.com/u/MostHost_LA)\
**Post date:** [January 25, 2023, 5:09pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/30 "2023-01-25T17:09:09Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![EvoPulseGaming](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EvoPulseGaming](https://forums.unrealengine.com/u/EvoPulseGaming)\
**Post date:** [January 27, 2023, 9:05pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/31 "2023-01-27T21:05:16Z")

</div>

Was able to fix the issue OP was having without using origin shifting. (Edit: Do not abuse flagging posts)

---

<div class="post-metadata">

**Author:** ![Dhrewbacca](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Dhrewbacca](https://forums.unrealengine.com/u/Dhrewbacca)\
**Post date:** [February 26, 2023, 3:51am UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/32 "2023-02-26T03:51:14Z")

</div>

Hey @EvoPulseGaming can you explain how you fixed it?

---

<div class="post-metadata">

**Author:** ![EvoPulseGaming](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@EvoPulseGaming](https://forums.unrealengine.com/u/EvoPulseGaming)\
**Post date:** [March 9, 2023, 8:18am UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/33 "2023-03-09T08:18:04Z")

</div>

Currently we made two changes in Engine/Source/Runtime/Core/Private/Misc/LargeWorldRenderPosition.cpp:

//#define UE\_LWC\_RENDER\_TILE\_SIZE 2097152.0  
#define UE\_LWC\_RENDER\_TILE\_SIZE 128000.0

//#define UE\_LWC\_RENDER\_MAX\_OFFSET (2097152.0_0.5)  
 #define UE\_LWC\_RENDER\_MAX\_OFFSET (128000.0_0.5)

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.

---

<div class="post-metadata">

**Author:** ![Gallonmate](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Gallonmate](https://forums.unrealengine.com/u/Gallonmate)\
**Post date:** [May 19, 2023, 11:27am UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/34 "2023-05-19T11:27:11Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![MostHost\_LA](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/mosthost_la/32/907035_2.png) [@MostHost\_LA](https://forums.unrealengine.com/u/MostHost_LA)\
**Post date:** [May 19, 2023, 2:58pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/35 "2023-05-19T14:58:31Z")

</div>

I’ll test 5.2, but it’s possible they introduced a bug. 4.\* is stable at 0,0,0, and ok up to at least 500 units from it.

---

<div class="post-metadata">

**Author:** ![fsk](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@fsk](https://forums.unrealengine.com/u/fsk)\
**Post date:** [July 10, 2023, 5:09pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/36 "2023-07-10T17:09:11Z")

</div>

I have found one reason why stuff flickers, it might be related to the problems you guys are seeing.

> [@Precision loss in vertex shader](https://forums.unrealengine.com/t/precision-loss-in-vertex-shader/1218096/1):
>
> There is a bug (feature?) in UE5 that reduces the precision of object transforms (rotation, scale) for about an order of magnitude. I have been complaining about this since 5.0 first came out and reported it several times. Since Epic for some reason doesn’t want to list the bug I am posting here about it so that at least other people can be aware of it not waste time trying to figure out what is going on (like me). I’m mostly posting because I finally found a workaround. This i…

---

<div class="post-metadata">

**Author:** ![DesertFox](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/desertfox/32/624918_2.png) [@DesertFox](https://forums.unrealengine.com/u/DesertFox)\
**Post date:** [October 26, 2023, 8:04am UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/37 "2023-10-26T08:04:53Z")

</div>

Some improvements for this might be coming in 5.4:

[https://portal.productboard.com/epicgames/1-unreal-engine-public-roadmap/c/1253-large-world-coordinates-on-gpu?utm\_medium=social&utm\_source=portal\_share](https://portal.productboard.com/epicgames/1-unreal-engine-public-roadmap/c/1253-large-world-coordinates-on-gpu?utm_medium=social&utm_source=portal_share)

[![](https://d3kjluh73b9h9o.cloudfront.net/original/4X/4/b/c/4bc31881d1dae6b3b53487dda92318e26e4ee980.jpeg "Unreal Fest Day 2 | Livestream 3") ](https://www.youtube.com/watch?v=JS5N41F4fZQ&t=25263)

---

<div class="post-metadata">

**Author:** ![kr0atan85](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@kr0atan85](https://forums.unrealengine.com/u/kr0atan85)\
**Post date:** [April 21, 2024, 12:52pm UTC](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748/38 "2024-04-21T12:52:31Z")

</div>

Hi, do you put this code in the master material of the static mesh?

[Previous page](https://forums.unrealengine.com/t/lwc-large-world-coordinates-do-not-work-for-first-person-shooters-driving-games-wobbly-rendering-artefacts-ue5-only-ue4-works-fine/652748.md?page=1)
