DoubleYou

2.2.9.2 modlist is good. Checked against my install and changelog.

Updated instructions to use fomod template and specify not to install the CRF addon until it is updated.

All currently accepted mods have been added to the dev guide. All currently removed mods have been removed from the dev guide -- with the exception of any Compilation removals All Core mods fitting the above criteria have been checked. Now I'm working on Extended.

I haven't used the Extended skeleton and I didn't notice any issues. We should test that skeleton sometime, however, as it probably is better.

I'm pretty sure that Tech is the only one who has been marking mods accepted this release, and if the OP is correct, the Changelog is up-to-date as per that. I'm going through and making sure everything is hunky-dory. I don't think the wiki got borked. I think we got drunk somewhere. And BTW, I re-re-fixed that horrid DLC Required and DLC Supported thing taking up an absurd amount of space on the mod pages. God, that was annoying!

Are we dropping this or not?

Well, I hope it was after I made some changes. The question is, are we going to include the compilation?

I'm adding back in all the mods that were not removed in the changelog. Until I have confirmation that the Compilation is ready, we might as well be prepared to release without it. We can easily remove mods from the list if we decide to add it.

Should we be pointing users to the 1.5 old file or the new Landscape LITE equivalent, Tech?

HQ Paper is there for me...

Updated instructions.

Okay, updated instructions.

It doesn't cost much fps to set to 0, but looks terrible IMHO.

You used the ''Less Opaque'' splashes?

Is the CRF patch necessary with the STEP Patches, EssArrBee?

Updated the mod page to select neither of the optionals in the fomod, since that appears to be what was used, since no one mentioned that they used the optionals.

How about this: fSunShadowUpdateTime=500000000000 fSunUpdateThreshold=500000000000 I guarantee you will not see the sun transition

I won't be around until late Saturday either, cause I'm working. And hmm... shouldn't this type of thing be in the Release Admin 2.2.9.2 thread instead of the main one?

See the videos. They can be continuously moving, but the timescale is so fast that it really seems odd. It feels like you're in a time-lapse video.

The one that could use the most testing is fLightLODRange, because that pushes the light LOD range very far, and perhaps there is some unknown bug from it.

I do most of my shots with default values for the other settings so that they cannot possibly have an effect on my tests. That's why that bug is in there.

iTexMipMapMinimum may not set the minimum mipmap, upon reflection, but that's what its name implies. I haven't really been able to discover the circumstances where the setting made a difference, and hence have never caught photos as of yet. I'd appreciate anyone who is able to discover where iTexMipMapMinimum has an effect to post their testing results.

Except it isn't optimal to show Fallout_3 instead of Fallout 3. Can't we use %20 or something for the spaces?

If you change the "Texture Quality" setting in the advanced section of the Skyrim Launcher, it modifies iTexMipMapSkip. High sets it to 0 (which means to use the highest resolution of the DDS, i.e., do not skip to a mipmap of lower resolution) Medium sets it to 1 (which tells it to skip the highest resolution of the DDS and go to the texture layer below it, which is half the resolution, i.e., the mipmap), and Low sets it to 2 (which tells it to skip the highest resolution of the DDS, and the half-size mip-map below it, so that it is now 1/4 the resolution of the base texture). Hence, by skipping mipmaps (i.e., skipping through the texture resolution levels which are known as mipmaps), the game changes the texture quality. Hence, the wiki is not incorrect, and I never displayed images for iTexMipMapMinimum. I say Texture Quality for the lay man, and I reference mipmaps for the technically minded, i.e., those who understand DDS textures). The effects of iTexMipMapSkip obviously change the texture quality.

Conflicting Graphics is definitely one of the most performance-costly, but you got lots of VRAM, so it didn't hurt you much.