MSFS24 MSFS 2024 SDK – GLTFValidator warning ±65504 in bufferView[7] / accessor[7] – impossible to identify the source

[Riptide-Airways]

Hello,

I have a scenery object that compiles correctly in MSFS 2024, but the new SDK GLTFValidator reports these two warnings:

GLTFValidator | Found in ...\FIMP2026_RA_Poste_Alimentation.gltf - Data below '-65504.000000' was clamped. In bufferView[7]: '' for accessor[7]: ''

GLTFValidator | Found in ...\FIMP2026_RA_Poste_Alimentation.gltf - Data above '65504.000000' was clamped. In bufferView[7]: '' for accessor[7]: ''

There are no errors, only these two warnings.

The object was created in Blender 4.2 and exported with the MSFS 2024 Blender exporter.

I have already:

• applied all transformations (Ctrl+A → All Transformations)
• cleaned the mesh
• removed unnecessary vertices/triangles
• performed mesh cleanup/purge
• checked the object hierarchy
• checked the geometry for abnormal/extreme coordinates
• re-exported the object
• deleted the previous .gltf and .bin files before recompiling

The model itself displays correctly in MSFS 2024 and the package builds successfully.

What I cannot determine is what exactly bufferView[7] / accessor[7] refers to in this glTF file.

Is there a recommended way to identify the actual data responsible for the ±65504 values?

Could this be related to vertex positions, UV coordinates, normals, or another glTF accessor generated by the exporter?

Any advice on how to trace bufferView[7] / accessor[7] back to the corresponding mesh/object in Blender would be greatly appreciated.

Thank you!

 

[ronh]

EDIT: may have made a mistake - (either 7 or less) OR (7 or more) for the mesh lookup


There are two methods to figure this out.

Brute force - only export parts of your mesh, hiding or deleting (temporarily) - until you find the mesh causing the issue.

use notepad++ (or similar) to open the gltf and look for accessor 7.

Notepad++ has a json viewer extension.

Open the file and set up json viewer in Plugins - json viewr - select show - then select format

Open the accessor 7

nothing to see here.

Open the meshes and look at the indices number - find 7 or find a mesh that is close to 7 AND more than 7

that name should be the one. - my case here fuselage.mesh.004 (NOTE: this is the mesh name not the node name)

if you want to find the node name then look at the mesh number - my case is 1
open nodes and look for mesh: 1

 

[Riptide-Airways]

Thank you very much, ronh, for this incredibly effective explanation!

Your method worked perfectly.

I had the MSFS 2024 SDK GLTFValidator warning:

±65504 in bufferView[7] / accessor[7]

and I was completely unable to determine which object in my Blender scene was responsible for it.

I followed your second method exactly:

accessor → mesh → node

and this led me to the mesh FIMP2026_Verre_Face.

I then temporarily removed that mesh from the Blender scene and exported the GLTF again.

After recompiling the package, the result was immediate:

0 errors — 0 warnings.

The warning had completely disappeared.

So your method allowed me to identify the problematic mesh with absolute certainty.

This was particularly useful because the scene contains quite a large number of meshes, and trying to isolate the problem by brute force would have taken a considerable amount of time.

Your explanation was therefore not only theoretically correct, but directly applicable and extremely efficient in a real MSFS 2024 project.

I had been staring at the accessor[7] warning without knowing how to connect it back to an actual object in Blender. Your explanation made that connection very clear.

So a very big THANK YOU for taking the time to explain this!

I will definitely keep this procedure as a reference for future GLTFValidator warnings:

accessor → mesh → node → Blender object

It is a much more precise approach than randomly removing objects and repeatedly exporting until something changes.

Excellent explanation, excellent method, and in my case: 100% successful.

Thanks again, ronh!