When I play the level with my pawn, the LOD’s don’t change at the expected times. I have to reduce the screen space from what they were (about 0.5) to as low as (0.1) before they change. Sometimes they never use their base LOD even if the mesh takes up all of the screen.
If I put a camera in the level with the same settings though and look through that, the LOD’s change as expected when in the editor.
The camera settings for the pawn camera are:
Spring arm with a socket offset of -7000,0,7000
A camera attached to spring arm with a rotation of 0,-38,-15 and a FoV that changes between 20 and 60 in game (in the screenshot it’s set at 50)
The camera in world has the same camera rotation and fov, but using a spring arm to offset it, I’ve just moved the camera back -7000,0,7000 units to replicate it.
I attempted to reproduce this using the basic LOD asset from the content examples migrated into a new top down template project. However, the LOD works correctly with the FOV changes on my end. You could try recreating the same and see what the differences are in our default asset vs your project.
If that doesn’t help, could you create a test project so I can investigate this further?
is it maybe possible that you have multiple skeletal meshes inside your pawn actor? If yes, i maybe have a fix for you. We had the same issue yesterday and we found a solution.
Your skm’s need to have the same LOD setup.
Iam not sure if both skeletal mesh components need to have the same LOD model amount or itf the settings need to be exactlly the same. I didn’t tested it in all variations that are possible so far.
So i kept it short and just added the same “LOD_Settings” to the same skeletal meshes inside my Actor and it worked for both meshes similiar :).’
What i also did now, is creating and “LOD_Settings Assets” for each sub pawn. Like “Ferrari_F24_LOD_Settings” or “Airbus_A380_LOD_Settings”.
So i can handle the LOD’s unique for each Actor.
Let me know if it helps and i hope it helps.
