Kalessin42

LOL. Well, then I guess that I get to look like an idiot. Well, the nexus page quite specifically talks about reporting issues with regards to SE, and nifscan definitely reports errors on nifs which have gone through SSE Nif Optimizer and thus - if I understand correctly - should be in the newer format at that point. What it says about meshes that have gone through the SSE Nif Optimizer seems to align with what NifSkope says, which strongly implies that it understand the new SSE format - certainly it doesn't complain about it being in an unknown format, and it doesn't choke on it. So, between what the nexus page says and what nifscan at least seems to do when using it, I don't know how it could be the case that it doesn't support the newer format, since it definitely seems to. But I clearly don't understand the situation properly. In any case, if nifscan can be trusted when processing the nifs in the DynDOLOD SE resources, then I would argue that what it's complaining about should be fixed, but if it can't be trusted, then obviously, it should be ignored.

Actually, according to nifscan's nexus page, it checks stuff that's specific to SSE - including catching some stuff that works in LE but not SE, and for some textures, it has the option to convert them to a format supported by SE if they aren't already. It works just fine on meshes that have been run through SSE Nif Optimizer. And looking in nifskope for what nifscan reports for various nifs, it at least seems to be legit, though I don't know how likely the random crashes that nifscan's documentation claims will happen actually are. I expect that nifscan is only found on the Skyrim LE section of the nexus and not the Skyrim SE portion simply because its author doesn't want to put it in multiple places (e.g. Mator has done the same with Merge Plugins and Mator Smash), but either way, based on what it's documentation says, it definitely supports SSE at least partially at this point. A common complaint that nifscan has for the meshes in the DynDOLOD Resources for SE is duplicate names - e.g. dyndolod resources se\meshes\lod\imperial\impextlighthouse01alternativetexture_lod_1.nif Block [0]: Name ImpExtLighthouse01:12 is used more than once in children nodeswhich nifskope usually fixes when you just resave the mesh (though it won't fix it if a node has the same resource listed as a child multiple times instead of having multiple children with different IDs but the same name). The most common complaint that nifscan has for the DynDOLOD resaurces is that bit 9 in BSXFlags isn't set correctly or that there needs to be a BSXFlags with bit 9 set, and there is no BSXFlags. e.g. dyndolod resources se\meshes\lod\dbm\museumglow_lod_1.nif Block [0]: Mesh uses SLSF1_External_Emittance but BSXFlags with set bit 9 is missing.and as far as I can tell, what it says is correct. I just don't know how likely it (or any of the other problems reported) are to cause random crashes in practice. However, the nifscan documentation certainly seems to think that they cause random crashes that are hard to track down. So, I'd definitely argue that they should be fixed unless it's known that what nifscan is reporting is wrong.