CK crashes when I try to edit a weapon.

[Yottabit]

I've never had any issues with CK up until the past couple of days. Well, no substantial issues that is. Now when ever I try to edit a weapon, such as the RU556, CK will lock up and then crash. It's happening with all of the modded weapons I have.

 

Also, all of the vanilla weapon previews look as though they're being viewed on a Gameboy or something.

 

I haven't moved, or deleted, any files prior to this issue occurring. This issue has even persisted through a freshly installed CK.

 

Any insight will greatly be appreciated.

[Yottabit]

"has a envmap which is not a cubemap which will cause D3D errors."

 

I think I've narrowed the issue down to this. Any idea as to what this means and how might I go about rectifying the problem?

[ehtyeci]

Environment maps are defined in the shader node or in a material file linked to the nif. A cubemap is an array of textures in one file that forms a cube or sphere with a continuous image in order to create surface reflection or image-based lighting.

In fo4 cubemaps have a very specific size of 513kB, because they are not mipmapped, are 128px and uncompressed argb_8888. Fo4 is very picky about cubemaps, and most definitely won't take a non-cubemap without producing weird results.

As for ck crashing, could be a number of reasons. What edits are you doing?

A screenshot of the gameboy effect would help.

[Yottabit]

Thanks for that bit of info.

 

The only editing I was doing when this issue starting to occur was to the base damage. I was also attempting to place a version of the weapon in the world and encountered the same issue with crashing. I can successfully edit vanilla weapons and place them in the world with no issues.

 

 

Here's an example of the Gameboy graphics I was referring to.

Edited May 19, 2018 by Yottabit

[ehtyeci]

Have you tried loading only a bare minimum plugins?

If you load a large chain of plugins, many which are dependant of others, the ck will break on the first unstable plugin while it does a live ref lookup every time you open an editor. Xedit doesnt do that because it seems to keep all records offline.

If you have Everything Search on your computer, you can keep it open and see if the ck dumps any messages to the EditorWarnings.txt.

Though mostly a last resort, you can try renaming the ck ini files located in the root of fo4 directory, then have ck generate some fresh ones.

I first thought you maybe did some edits to the nif, since a broken nif is the first thing that may cause the ck to crash. In which case, there's a quick way of checking a nif by opening ck, and without loading any plugins go to View > Preview Window and drag & drop a nif file into it. But since you're only editing properties of a formid, this doesn't really help.