Certain mesh 100% CTD's game when trying to equip it

[Allnarta]

 Maybe someone more experienced in FO4 meshes could help me?

 

I got a mesh that cause 100% CTD when I try to equip it ingame, but I see absolutely nothing wrong with it neither in Nifskope, OS or blender.

 

What I tried and tested:

-It's not dismemberment

-It's not something visibly different in mesh structure

-It's not skeleton or ClothExtraData

-It's also not mesh or shader property as those are all identical

-It's also not tri morphs because in last try to test I didn't attach stringextradata so game cannot read tri file for this armor I'm really lost now.

 

Here's mesh, maybe someone can look at it?

 

Also one of last crash logs.

crash-2025-05-27-17-25-59.log CourserM.7z

[Allnarta]

Also to clarify, if I plain export this mesh from blender to .fbx, import to OS, re-weight and all that - mesh do not CTD after. It looks like issue is in something that export with Nifly and import with OS carry over in a nif file.

[JB.]

Not an expert but the buffout log points out (among other things) these bones from the robe. 

 

 

- Name: "Cloth_BN_Dangly_01" | 1
- Name: "Cloth_BN_Dangly_03" | 2
- Name: "Cloth_BN_Robes_K_003" | 2
- Name: "Cloth_BN_Robes_K_004" | 1
- Name: "Cloth_BN_Robes_K_005" | 1

 

 

And outfit studio also indicates them as bad bones.

 

 

 

If you right click and then click on “bad bones”, you will get options to repair it.

 

 

You could also build this outfit again but this time remove the robe, just to test it ingame. 

 

Edited May 27, 2025 by JB.

[Allnarta]

Meshes never CTD because of bad bones though, only have distorted look ingame.

 

It was Shader Type - mesh has Envioement Map chader set in shaders list, but had Type set to default. As it turns out, it makes game shit itself.