Jump to content

CTD on save caused by dds with invalid data (Win10 Problem)


Dreifels

Recommended Posts

I had this issue several times when I generated DynDoLod output new with a mod new istalaled, and the mod was original of Skyrim LE and converted (not by me). It is replicateabe. WIth the new DynDoLod output all looks fine, until you hit a point where just this dds gets loaded, and you try to do a save. you get a .tmp with size 0 and a CTD. DynDoLog gives no error message when generating. (same with corrupt niif)

 

The same problem, w/o DyndoLod you can have with installing of any old LE based mod. One buggy dds or nif is right good for a CTD.

 

Most times I coould reconvert them, but not aalways and not all, The modder has to do this.

 

This is a special runtime problem of Win10. It may cause CTDs on systems with new installed Win10/64 ONLY, as Win10 cannot install the old runtimes because "newer version already exist".

This problem is not with systems, which had installed Win7 along with Skyrim LE before and got updated to Win10, because these system got the old runtimes times ago and they got not deleted, but Win10 does still read them.

So it may be that on an older System these dds work fine, but if you take a system with brand new Win10 you get a CTD. And I have a new Win10/64 system and get just these CTDs)

These dds need to get converted new and correctly using runtime versions delivered with Win10 only.

 

I just run again in this problem with "Vigilant"

all, Ordenador, DDSConverter 2.2, and NifScan 0.3.2 report invalid Data for mass of .dds

 

Issues are in HiRes Pack 4K Landscape-1-6-0-a\HiRes4KPackBC7_Landscape\Data\textures\
and in Vigilant SE v162\00 Core Files\Data\textures\

Reports below

  Reveal hidden contents



 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...