![]()
|
|
Are these supposed to be problems with old USSEP mesh conversions or actual issues with existing vanilla meshes?
For example, on floracanisroot01.nif, The actual visible mesh has one BSTriShape node, and one BSLODTriShape node in the unaltered vanilla file. There are no NiTriShape nodes.
This same file as submitted in the above archive has two BSTriShape nodes. I believe this is incorrect and will break the visible harvest state of the mesh.
And to make things even more interesting, USSEP doesn't even have a floracanisroot01.nif file.
Therefore I think everything in the offered archive needs to be double checked against vanilla meshes from the 1170 archives to see if these should even be used at all. It's entirely possible any USSEP versions of these also need to be thrown out if any of them have old block types.
For example, on floracanisroot01.nif, The actual visible mesh has one BSTriShape node, and one BSLODTriShape node in the unaltered vanilla file. There are no NiTriShape nodes.
This same file as submitted in the above archive has two BSTriShape nodes. I believe this is incorrect and will break the visible harvest state of the mesh.
And to make things even more interesting, USSEP doesn't even have a floracanisroot01.nif file.
Therefore I think everything in the offered archive needs to be double checked against vanilla meshes from the 1170 archives to see if these should even be used at all. It's entirely possible any USSEP versions of these also need to be thrown out if any of them have old block types.
It might be an issue with the existing ussep specific versions, yes. Comparisons are needed.
I tried redoing the USSEP mesh conversions myself with an updated tool.
According to Rob, changing the BSLODTriShape to a BSTriShape will not break anything.
Attached Files:
ussep flora.7z
According to Rob, changing the BSLODTriShape to a BSTriShape will not break anything.
BSLODTriShape IS a NiTriShape for one.
but LODTriShapes act as a second LOD system but for within uGrids range
however none of them are setup right by Bethesda and Bethesda has that system disabled by default


Comment #3 Jan 26, 2025 11:59 am
Edited by DarthVitrial on Jan 26, 2025 11:59 am
Showing Comments 1 - 3 of 3