jags78 Posted April 13 Share Posted April 13 Hello modders I haven't been modding fallout 4 for the last 2,5 years, so my problem may be already well known... except to me. While waiting for Classic Holstered Weapons System (CHW) to update to NG, I dug out my old simple weapon apparels and started adding some more. The old 27 holsters i created work fine, but a new one i'm making now is crashing the game to desktop when i try to preview the holster (the deliverer). Following points work fine: - weapon appears on the player - weapon appears in my inventory - i can drop and pick up the holster, physics and collision work - i can see the model when i hover over it when it's in a container Following points DON'T work: - CTD when i preview the holster - holster does not show when i'm trying to modify it in the armor workbench. I double-checked the bgsm paths, the forms, there are no dependencies to other mods, i x-checked with my old mods... but i can't see the problem. I'm using Outfit Studio v5.6.3.0, NifSkope v2.0 Dev 9 and FO4Edit v4.1.5f... does anybody have a clue or a hint what i can do? Thx and greetings jags78 Link to comment Share on other sites More sharing options...
pepperman35 Posted April 14 Share Posted April 14 The only thing I can think off hand is textures. Might be worth a quick look to see if they are the correct size, etc. Link to comment Share on other sites More sharing options...
South8028 Posted April 14 Share Posted April 14 Besides textures, errors in nif immediately cause ctd. Yes, textures must be multiples of 8. 64, 128, 256, 512, 1024, 2048, 4096, 8192. But nif can also contain an error. For example, if I leave some value or reference empty in nif, then ctd immediately. Link to comment Share on other sites More sharing options...
jags78 Posted April 14 Author Share Posted April 14 Thx for the reply Lil update... I think i can exclude the textures and the mesh. I took one of my old holsters and changed the path to the model to the new mesh. The game does NOT crash when previewing the holster with the new mesh. The problem seams to be somewhere in the forms of the plugin (esl flagged esp). I'll have to go through the plugin and rebuild it step by step to see where it starts crumbeling. Since I've been gone from the modding scene for a while, I can't shake the feeling that the problem is with the software I'm using, since my MO is the same as it's been pre NG. I may also downgrade FO4Edit. Keep you posted. If someone reads this in the meantime and had a similar experience I would be glad for the solution they found. Thx in advanced. Link to comment Share on other sites More sharing options...
jags78 Posted April 14 Author Share Posted April 14 Solved it... kinda The problem seams to be with the current version of FO4Edit that I'm using, which seams weird to me. I recreated the plugin with a different method and now the mod works. Method 1: Copy a working plugin. Load it in FO4Edit, remove all Forms and step by step add the required Forms by creating them from scratch or 'copying them as new records'... this method led to CTD Method 2: Copy a working plugin. Edit the pre-existing entries and then remove the forms I do not need... this one worked. Both plugins are as good as identical. Same amount of forms, references, variables, entries, aso. I compared them side by side, but method 1 (my preferred method) seams to make trouble. If I had to guess the problem, I'd say FO4Edit leaves some residue when deleting all existing forms or something goes tits up when I copy entries as new records into the 'emptied' plugin. So not really a solution in my opinion, but a workaround for something that worked fine with a prior FO4Edit version. I still may downgrade if possible (if it works with FO4 NG) to see if this problem persists. I would be curious to hear if anybody else noticed this kind of problem with FO4Edit v4.1.5f. Link to comment Share on other sites More sharing options...
jags78 Posted April 14 Author Share Posted April 14 F*** MY F*** AND CALL ME A B**** !! I take everything back!!! 2 of my keywords where still declared as mod associations instead of attachment points. what a pain. Hope you learned something of my mistakes, DO NOT OVER-ANALYZE. Just open your eyes... sorry for wasting your time pepperman35 and South8028. Have a good one... Link to comment Share on other sites More sharing options...
Recommended Posts