IMPORTANT: Graphic settings do not match the actual settings!

[CptLucky8]

@Flobud

I’ve seen that the VR Texture Resolution, when set on Ultra, shows 1 in the cfg file. When set to Low, it shows 3 in the cfg.

I’m like super confused here For me 3 = Ultra. So to get Ultra we need to set it to Low?

I’m confused because by the inverted logic, ULTRA = 0, not 1. (U:0, H:1, M:2, L:3)

---

@CptLucky8

And from the discussion, here is one of my latest remark:

I’ve not tested all the things discussed here yet, but I’m starting to get a possible explanation:

1. The Texture Resolution value is saved in reversed order

This is not a problem in itself as long as the code reading and writing the value is using the same reversed order, but…

2. Some parts of the rendering engine is using the Texture Resolution setting as a “quality” param

Say Pixel Shader code for specular or something else is using the Texture resolution value in order to lower the processing if you’re using lower texture resolution for example. Then this is a problem, because if the code using the Texture Resolution value as a “quality” param is coded expecting the correct value order, then LOW texture resolution = ULTRA quality param for the other parts, and ULTRA texture resolution = LOW quality param for the other parts.