|
|
发表于 2024-5-7 03:21:15
|
显示全部楼层
SkyrimSE.exe+12FDD00
Probable Callstack: BSShader::unk_xxxxxxx+xx mentioned FIRST or with the HIGHEST PRIORITY
*This is associated with a broken nif file. Unfortunately, it is hard to discern which mod is the issue since the log is created after the nif file has been processed. In cases like these, a broken nif can even lead to NO CRASH LOG BEING GENERATED AT ALL!!
FIX: When put in this situation, one can systematically root out the cause of the issue by disabling each mod in one's load order and starting a new test save to replicate the issue, or running CAO(Cathedral Assets Optimizer) over all your mods. While the second option can fix the issue, it can also bring issues of its own, depending on the level of optimization you choose in CAO. Not only is the first option more accurate, but it will help others be aware of faulty meshes or nif files that plague this mods. The downside is the time it takes to deal with the issue. Therefore, I suggest disabling about 10 mods each test save from the bottom of the load order up. If you are lucky enough to know which surrounding area contains the nif file that is broken, it can be much easier to relocate to that location every save file to ensure the CTD's appearance.
SkyrimSE.exe+12FDD00
可能的调用堆栈：BSShader::unk_xxxxxxx+xx 首先提到或具有最高优先级
*这与损坏的 nif 文件有关。不幸的是，由于日志是在处理 nif 文件后创建的，因此很难辨别哪个 mod 是问题所在。在这种情况下，损坏的 nif 甚至可能导致根本不生成任何崩溃日志！！
FIX：在这种情况下，可以通过禁用加载顺序中的每个模组并开始新的测试保存来复制问题，或者对所有模组运行 CAO（大教堂资产优化器）来系统地找出问题的原因。虽然第二个选项可以解决问题，但它也会带来自己的问题，具体取决于您在 CAO 中选择的优化级别。第一个选项不仅更准确，而且还可以帮助其他人了解困扰此 mod 的错误网格或 nif 文件。缺点是处理问题需要时间。因此，我建议从加载顺序的底部向上禁用每个测试保存的大约 10 个 mod。如果您有幸知道哪个周围区域包含损坏的 nif 文件，则可以更容易地将每个保存文件重新定位到该位置以确保 CTD'
以上内容机翻
https://www.nexusmods.com/skyrimspecialedition/mods/23316
关于文中提到的排查nif问题的软件CAO |
|
变色卡
千斤顶
