Jump to content
  • 0

Skyrim Redesigned: Putting Money Bags and Alchemy Table textures through DDSopt?


Tykune

Question

So I've been having an issue with the money bags and alchemy table having black and rainbow textures, but then i read somewhere that putting them through DDSopt can fix it? How do I go about doing this to fix the texture? Or is there another way of going about it?

Link to comment
Share on other sites

10 answers to this question

Recommended Posts

  • 0

Here's our DDSOpt Guide: https://wiki.step-project.com/Guide:DDSopt

 

It's strange that only certain users have this issue. I've never seen it myself.

From what I've researched up, users with low to medium graphic settings get these issues, but those using high settings have no issues with it. Looking into the texture files, I noticed that alchemyworkbench01.dds and moneybag01.dds are missing mipmap textures. Could this be the issue?

Link to comment
Share on other sites

  • 0

Change this iTexMipMapSkip=1 to this iTexMipMapSkip=0 in your SkyrimPrefs.ini under [Display] and test to see if the issue persists.

Fix confirmed. I wasn't even aware such an option existed in SkyrimPrefs. What exactly was this doing?

Link to comment
Share on other sites

  • 0

Yes, any textures missing proper mipmaps will glitch heavily if iTexMipMapSkip is set to anything else than 0.

 

0 is default for ultra (and maybe high) settings. Not a "rogue" ini tweak, but definitely a bad idea (performance impact is close to 0)

 

 

 

I believe iTexMipMapSkip set the number of mipmap to skip from the default's size when fully rendered. So if a texture is 2k (2048x2048), and have all of its mipmap (1024x1024, 512x512, 256x256, 128x128, ...):

iTexMipMapSkip = 0 will use all of the mipmaps, when lookep up close the texture will be the 2K one

iTexMipMapSkip = 1 will use all of the mipmaps, but not the original size (no matter how close you look at the texture n-gaùme, it's max resolution will be 1024x1024)

iTexMipMapSkip = 2 will skip both the 1024x1024 and the 512x512

etc...

 

Which would explain why textures without mipmaps glitch when this setting is set to anything else than 0. An interesting experiment would be to generate textures with a single mipmap (a 2K texture with a single 1K mipmap), and see if iTexMipMapSkip = 1 is still ok but iTexMipMapSkip=2 glitch. That would basically validate the above hypothesis.

 

 

This setting serve as a quick way to reduce the rendered texture's quality to slightly help performances. However, textures are still loaded completely and thus eat the same amount of VRAM regardless of this setting (only Fallout 4 with its optimized mipmaps chunk in its .ba2 archive can go around this), which is why the tweak isn't helping performances much. Better always have it to 0 and pick your textures size using your brain.

Edited by Kesta
Link to comment
Share on other sites

  • 0

Yes, any textures missing proper mipmaps will glitch heavily if iTexMipMapSkip is set to anything else than 0.

 

0 is default for ultra (and maybe high) settings. Not a "rogue" ini tweak, but definitely a bad idea (performance impact is close to 0)

 

 

 

I believe iTexMipMapSkip set the number of mipmap to skip from the default's size when fully rendered. So if a texture is 2k (2048x2048), and have all of its mipmap (1024x1024, 512x512, 256x256, 128x128, ...):

iTexMipMapSkip = 0 will use all of the mipmaps, when lookep up close the texture will be the 2K one

iTexMipMapSkip = 1 will use all of the mipmaps, but not the original size (no matter how close you look at the texture n-gaùme, it's max resolution will be 1024x1024)

iTexMipMapSkip = 2 will skip both the 1024x1024 and the 512x512

etc...

 

Which would explain why textures without mipmaps glitch when this setting is set to anything else than 0. An interesting experiment would be to generate textures with a single mipmap (a 2K texture with a single 1K mipmap), and see if iTexMipMapSkip = 1 is still ok but iTexMipMapSkip=2 glitch. That would basically validate the above hypothesis.

 

 

This setting serve as a quick way to reduce the rendered texture's quality to slightly help performances. However, textures are still loaded completely and thus eat the same amount of VRAM regardless of this setting (only Fallout 4 with its optimized mipmaps chunk in its .ba2 archive can go around this), which is why the tweak isn't helping performances much. Better always have it to 0 and pick your textures size using your brain.

Thanks for the explanation. I will definitely remember it for picking texture options in the future.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

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

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.