Creation-Kit-Platform-Extended
Creation-Kit-Platform-Extended copied to clipboard
Perchik71
Loading Files a Second Time Causes an Infinite Hang
Not sure if it's a base CK issue or a CK Fixes issue that made its way to CKPE but if you try to load any ESM/ESL/ESP (even an empty one) after having already loaded a few the CK will infinitely hang on the "Loading Files..." dialogue window.
Task Manager doesn't show any noticeable increase in CPU or Memory usage by the CK when this happens.
Reloading is possible, I've tried it many times. However, this is not the norm. Since in the original you will get a CTD in SSECK. Edit: First of all, technical features are needed, it is very likely that this is an eternal waiting for the thread.
When working on multiple mods in the LE CK I would always reload files and it worked perfectly.
Since in the original you will get a CTD in SSECK.
When you say this, does that mean it was an issue introduced in the SE CK?
As for technical details, do you mean stuff like my CK and CKPE version? If so, CK version is 1.5.73.0 (however this issue also occurred on version 1.6.438.0 with the original SSE Creation Kit Fixes) and CKPE version is 0.3.0.0 (according to CKPE_Loader.exe), build 734.
SLE CK != SSE CK. It's funny that people don't compare the two originals to each other. But only after modifications. They look the same, but inside they are different, and the architecture is different. This mod will never support LE for these reasons. I meant your PC. Since I have no problems.
Ah sorry! I know there's a big difference between the two and was never asking for LE CK support, just that it worked in that one. I know at least one other person that has this same issue so it would be great to get a fix for it if possible is all.
I'd take it the only PC specs that matter for this stuff would be the CPU, Motherboard, and possibly RAM? If not I can give more info. CPU: AMD Ryzen 7 5800X3D Motherboard: MSI MAG B550 Tomahawk RAM: Kingston 32GB KF432C16BBK2/32 Fury Beast CL16 3200MHz DDR4
Again, sorry if I'm misunderstanding that part.
In principle, it is quite powerful. As soon as I get a chance to see something like this, I'll take a look.
It seems that this problem has been partially solved since 1.6.1130.0. And arises from the abundance of loose files. Edit: Partly because, unlike its predecessors, nif's either won't loaded or it will cause CTD.