How do I run the game in DEBUG/DEVELOPER mod to see corrupted/bad texture files?!

[Deleted4610270User]

I am so sick and tired of badly-compressed textures or texture made in some way that Fallout 4 will not accept after patch 1.3! I use many textures (20GB worth) and ever since the new patch, many of the old textures that worked fine with patch 1.2, now cause CTD's after patch 1.3.45/1.3.47. I have to go inside my Textures folder, and spend MANY HOURS cutting and pasting a ton of textures to properly isolate the one causing CTD's. Then I remove it and CTD's stop happening. The problem is that after path 1.3 I had several textures, each one causing CTD's in a different location. I already got rid of 3 that allowed me to have CTD-free gameplay in several areas, but other areas still get CTD's. Its 100% caused by texture files. I thought maybe settings were causing it, but it doesn't matter what settings I used or if I reset .INI files, etc. CTD's will happen when Fallout 4 does not like some specific textures.

 

I know with patch 1.2, one developer incorrectly compressed or not compressed a texture that caused CTD's. Then he admitted to it and corrected it. Again, in my case, CTD's are caused by specific texture files.

 

I do not understand why the same textures that worked with patch 1.2 no longer work with patch 1.3. I also need to find a way to isolate those textures without going folder by folder, file for file, and testing God-knows how many areas!

 

1. What do I do now to get rid of these bad textures? Going folder by folder and file by file is CRAZY and SUPER time consuming.

2. Is there some sort of a DEBUG or DEVELOPER mode which would log information and then tell me which exact texture caused the crash or maybe which texture was last loaded, so I can capture its name and delete it? There's GOT to be something like that.

3. Maybe someone can create a Texture Verification Tool or some mod that will simply test if Fallout 4 will load those textures???

 

[Deleted4610270User]

Thanks! I figured it out. I was changing to many variables to make a proper conclusion, but it seems ever since 1.3 patch, to make the game work without crashes, I absolutely had to set:

iPresentInterval=1

and

bForceIgnoreSmoothness=0 (apparently this one has nothing to do with Mouse Acceleration, but somehow affects textures)

 

Again, thanks for helping me out. With 1.2 Patch, I set

iPresentInterval=0

and

bForceIgnoreSmoothness=1

 

With settings above and 1.2 patch, I got very responsive motion and to make sure no errors happened, I used ENB V-Sync=True and Frame Rate Limiter = 60. This no longer works. Oh well, at least there are no more crashes of any kind!

 

Thanks!