# LODSync: negative r.SkeletalMeshLODBias freezes synced LODs (USkinnedMeshComponent::GetDesiredSyncLOD returns -1 == INDEX\_NONE) 

**URL:** <https://forums.unrealengine.com/t/lodsync-negative-r-skeletalmeshlodbias-freezes-synced-lods-uskinnedmeshcomponent-getdesiredsynclod-returns-1-index-none/2854993>\
**Category:** Character & Animation\
**Tags:** unreal-engine, Epic-Pro-Support, question\
**Created:** [October 14, 2026, 7:23pm UTC](https://forums.unrealengine.com/t/lodsync-negative-r-skeletalmeshlodbias-freezes-synced-lods-uskinnedmeshcomponent-getdesiredsynclod-returns-1-index-none/2854993 "2026-10-14T19:23:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 14, 2026, 7:23pm UTC](https://forums.unrealengine.com/t/lodsync-negative-r-skeletalmeshlodbias-freezes-synced-lods-uskinnedmeshcomponent-getdesiredsynclod-returns-1-index-none/2854993/1 "2026-10-14T19:23:57Z")

</div>

USkinnedMeshComponent::GetDesiredSyncLOD returns MeshObject-\>MinDesiredLODLevel + LODBias with no clamp (SkinnedMeshComponent.cpp, //UE6/Main [Content removed] which ILODSyncInterface::GetDesiredSyncLOD documents as “the desired LOD is not known”.

ULODSyncComponent::UpdateLOD skips any driver with DesiredSyncLOD \< 0 (LODSyncComponent.cpp line 221). When every driver wants LOD0 there is no valid setting, so UpdateLOD makes no SetForceStreamedLOD or SetForceRenderedLOD calls, and every synced component keeps the forced LOD from the last frame that had a valid driver. Since LOD streaming support was added to LODSync in 5.4, that forced rendered LOD is the best LOD available on all components on that frame. With streaming, the group can lock onto LOD2 or LOD3 and stay there for as long as the driver wants LOD0. For us this showed up as close-up characters on console rendering low LODs indefinitely, while the editor (bias 0) looked fine.

The component’s own LOD selection clamps the same sum: UpdateLODStatus\_Internal (line 4909) uses FMath::Clamp(MinDesiredLODLevel + LODBias, 0, MaxLODIndex). A positive bias has a related problem: GetDesiredSyncLOD can return a value past NumLODs - 1. With a CustomLODMapping, GetSyncMappingLOD (LODSyncComponent.cpp line 352) passes an out-of-range source LOD through unmapped before UpdateLOD clamps it at line 255, so the group can sync to a different LOD than the driver renders.

Anyone using LODSyncComponent with a negative r.SkeletalMeshLODBias hits this. That bias is a scalability CVar and a common way to reduce LOD popping on consoles. Still unclamped in //UE5/Main [Content removed] and in 5.7 and 5.8.

Suggested fix, in USkinnedMeshComponent::GetDesiredSyncLOD:

```auto
- return MeshObject->MinDesiredLODLevel + LODBias;
+ return FMath::Clamp(MeshObject->MinDesiredLODLevel + LODBias, 0, GetNumLODs() - 1);

```

This is safe because MinDesiredLODLevel is never negative, so INDEX\_NONE still only comes from the no-asset / no-MeshObject branch, and LODSync is the only engine caller. We are shipping this locally.

Workarounds: r.ForceLOD, ULODSyncComponent::ForcedLOD, or not using a negative r.SkeletalMeshLODBias.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![anonymous-edc](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@anonymous-edc](https://forums.unrealengine.com/u/anonymous-edc)\
**Post date:** [October 14, 2026, 7:24pm UTC](https://forums.unrealengine.com/t/lodsync-negative-r-skeletalmeshlodbias-freezes-synced-lods-uskinnedmeshcomponent-getdesiredsynclod-returns-1-index-none/2854993/2 "2026-10-14T19:24:00Z")

</div>

**Steps to Reproduce**  
1. Unmodified engine, any template project (e.g. TP\_ThirdPerson). Create an Actor with a SkeletalMeshComponent whose mesh has 4 or more LODs, and a LODSyncComponent with that component in Components To Sync as Drive. A second SkeletalMeshComponent set to Passive shows the effect on the rest of the group, but one Drive component is enough.

2. Set r.SkeletalMeshLODBias -1 (on consoles this typically comes from a device profile).

3. Run “log LogLODSync Verbose” and switch the viewport to Level of Detail Coloration \> Mesh LOD Coloration.

4. PIE with the actor far enough away that it renders LOD3. Then move the camera close in a single frame (teleport the pawn, or a Sequencer camera cut) so the mesh’s screen size wants LOD0.

Call path:

ULODSyncComponent::UpdateLOD

-\> ILODSyncInterface::GetDesiredSyncLOD

-\> USkinnedMeshComponent::GetDesiredSyncLOD returns MinDesiredLODLevel (0) + LODBias (-1) = -1

-\> UpdateLOD skips the driver because DesiredSyncLOD \< 0

-\> no valid setting, so no SetForceStreamedLOD / SetForceRenderedLOD calls that frame (or any frame while the mesh wants LOD0)

Expected: The group renders LOD0, the same as the component does without LODSync (UpdateLODStatus\_Internal clamps the biased LOD to 0).

Actual: The group stays on LOD2, the forced LOD from the last frame that had a valid driver, for as long as the mesh wants LOD0. The “LOD Sync Drivers” and “LOD Sync : Current LOD” verbose lines stop logging. In a cooked build with LOD streaming this also happens on a normal approach: the group locks onto whatever LOD was resident on the last valid frame.

[Attachment Removed]

---

<div class="post-metadata">

**Author:** ![DDeVoe](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/ddevoe/32/1000886_2.png) [@DDeVoe](https://forums.unrealengine.com/u/DDeVoe)\
**Post date:** [October 14, 2026, 9:06pm UTC](https://forums.unrealengine.com/t/lodsync-negative-r-skeletalmeshlodbias-freezes-synced-lods-uskinnedmeshcomponent-getdesiredsynclod-returns-1-index-none/2854993/3 "2026-10-14T21:06:03Z")

</div>

Hey there,

I’ve logged an issue and I’m going to try and get your suggestion in the next hotfix. You can follow it here: [https://issues.unrealengine.com/issue/UE-402879](https://issues.unrealengine.com/issue/UE-402879)

[Attachment Removed]
