Hypn0sef Posted January 12, 2021 Share Posted January 12, 2021 (edited) I'm back to tearing out my hair. Here's the whole story: For months I've been working on a huge Redguard palace. All along the way I never had a CTD when testing it in game, it ran at 60 fps consistently. When trying to make the BSA (archive) I got a ton of textures and a few meshes corrupted. This was causing both the game and CK to crash and I was close to throwing in the towel, this is when I made my previous post. I figured it out due to CK Fixes, replaced all the textures and meshes, and now everything looks perfect in the CK again. BUT when I went to test in game, it crashes. Every time. I tried COCing to different cells, some with NPCs, some without, thinking that was the issue. CTD every time. I had never had this happen before, all the textures and meshes are in the right place, it looks fine in CK, what the hell? I was about ready to post it!If anyone knows what could be causing this that would be a huuuuge help and it'll get you a place of pride in the credits section. What's super strange is that the exterior area works just fine, everything renders properly and runs at 60 fps, so it has to do specifically with interior cells, or navmesh, I'm really not sure. But considering that everything works fine in the CK, I feel like it'll just be some small fix I need to do. Oh and I cleaned it in TESEdit and LOOT and Vortex both say it's clean. Edited January 12, 2021 by Hypn0sef Link to comment Share on other sites More sharing options...
dylbill Posted January 12, 2021 Share Posted January 12, 2021 I'm not sure why you'd be getting ctd's now. Have you tried testing on a new game? You can also try doing a clean install of skyrim to see if that helps (backup your current skyrim folder somewhere else.) Link to comment Share on other sites More sharing options...
Shadeybladey Posted January 12, 2021 Share Posted January 12, 2021 All I know is that you have to test the mod on a saved game that has never seen the mod, otherwise old scripts etc can be baked in. So, yeah, if you do not have a save that is "clean" of your mod, maybe try it with a new game, and then activate your mod when you are clear of Helgen. :) Link to comment Share on other sites More sharing options...
Hypn0sef Posted January 12, 2021 Author Share Posted January 12, 2021 Okay I just tried 'validating integrity of game files' then starting a new game without the mod. Activating the mod, going back in, and it still CTDed. I'm screwed. Link to comment Share on other sites More sharing options...
Shadeybladey Posted January 12, 2021 Share Posted January 12, 2021 That's such a shame, after so much work. Did you try checking it with TES5Edit again, to see if there any conflicts? As I'm sure you know, one problem with the CK is if you cick OK to anything, even without changing anything, it gets registered as an edit. I found that to my cost, so I always click cancel if I just look at something without changing it. The other possibility is Navmesh, as you suggested. Make sure it's everywhere it needs to be and there's no double layers etc. :smile: Link to comment Share on other sites More sharing options...
maxarturo Posted January 12, 2021 Share Posted January 12, 2021 The fact that everything works fine in CK doesn't mean that everything is fine, CK will run even if there are issues with your mod. It could be an abundance of reasons starting by the highest suspect that is a "Corrupted Nif", i would recommend you to do the following: - Create a 'Test ESP' and add small groups of your objects to a 'Test Cell' starting by the meshes that are common in all your 'Interior Cells', then just 'COC' to your Test Cell, this way you will narrow down and eventually find the culprit, also place an actor near your meshes so that it can be affected if the mesh has a corrupted "BSFadeNode" or collision. * There is no need to add to your cell 'Vanilla Assets' just your meshes and anything that's been modify. Don't ever blindly trust "Modder Resources" and always check/examine them to their last NOD before using them. At one point more than a year and a half ago, i also encounter ctd issues whenever i tried to COC to any of my interior cells, i had to examine one by one every single mesh from all the 1713 of them, and in the end the culprit was a single mesh from "Modder Resources" that was completely F***** UP !!!, in CK it would look all fine but it was causing CTD everytime i tried to enter any of my cells. - Examine or let any of your "Experienced Friends" in the field to look at your textures, this is also a reason of mods CTDs since the majority of modders don't have the knowledge required to create textures and they actually have no idea of what they are doing. "BUG HUNT" and "CTD HUNTS" is a painful and time consuming procedure, you need to arm yourself with patience and in order to succeed you must take it slowly so that you won't miss anything. Link to comment Share on other sites More sharing options...
Hypn0sef Posted January 12, 2021 Author Share Posted January 12, 2021 @Maxarturo thanks that's really helpful. What's strange is that since everything worked in game prior with these same mod assets something must've been corrupted along the way. I just did a nifscan and it failed on a few meshes which I replaced with clean ones but still got a CTD so I'm gonna try test cells with various assets at a time. I have one question though. So I'm experiencing a CTD whenever trying to COC to any cell, even tiny ones with very few assets. Did you have a CTD when COCing to cells without the corrupted mesh, or only ones with it? Cause if it's the latter I don't know of any assets that each of my cells share. Link to comment Share on other sites More sharing options...
Hypn0sef Posted January 12, 2021 Author Share Posted January 12, 2021 Wait, just as I say that I COCed to a small cell and it worked! Link to comment Share on other sites More sharing options...
maxarturo Posted January 12, 2021 Share Posted January 12, 2021 In my case the corrupted mesh was used in all cells, it was a "Deco / Latern" mesh. Link to comment Share on other sites More sharing options...
Hypn0sef Posted January 12, 2021 Author Share Posted January 12, 2021 I don't think there's any meshes used in each of the cells that are causing crashes Link to comment Share on other sites More sharing options...
Recommended Posts