sheson

The slot is not used by the shader setting. Will be fixed in the next version.

That's OK, no further reply typically means the problem is resolved or a question answered sufficiently. I do appreciate a timely +1 as signal as well.

Pay attention to the messages reported in the DynDOLOD log. For example look for message that start with <Error: Deleted reference "pluginname" https://dyndolod.info/Messages/Deleted-Reference The mentioned plugin(s) needs to be cleaned. Pay attention to similar LOOT messages. https://dyndolod.info/Generation-Instructions#Prerequisites Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean .. Error checking the load order with xEdit will report possible unrecoverable errors in the load order like unresolved Form ID in a single run. Also fix plugins for which Warning: Reference attached to wrong cell is reported. See https://dyndolod.info/Messages/Reference-Attached-to-Wrong-Cell I suggest to learn basic modding knowledge by following a proper modding guide.

Great! You should now be able to follow the usual generation instructions and continue with DynDOLOD. Also get the test version for DynDOLOD. I have uploaded a new test version. If you could run it without LoadGLCompressed=0 (or LoadGLCompressed=1) and upload new logs that would be great. In case there is an error, also add LoadGLCompressed=0 to the DynDOLOD INI, otherwise don't and try to run as is. You may want to test with just one small worldspace like BlackReach first to verify atlas texture generation does not fail.

Moved the post to the appropriate thread for the message. See posts above. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-Search The log archive does not contain any DynDOLOD logs. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. In the meantime see https://dyndolod.info/Messages/Can-Not-Resolve-Cell There is a problem with the mentioned cell record. Check the log message for related messages above about the cell or the mentioned plugin. As explained in the Generation Instructions, finalize the load order, install mods, sort and resolve conflicts. Clean and error check the load order with xEdit to find and fix errors before generating LOD. There might be a problem with Update.esm or a plugin overwriting the mentioned cell record. https://dyndolod.info/Generation-Instructions#Prerequisites Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean .. Error checking the load order with xEdit will report possible unrecoverable errors in the load order like unresolved Form ID in a single run.

There is a new test version for you to run.

Use the Copy message to clipboard link and paste the text instead of a screenshot as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Copy-and-Paste-Text It got replaced by sstuccowallint01lod.dds Next DynDOLOD Alpha version will be aware of that change, until then there is DynDOLOD Resources Alpha 44.1

The Resources are updated. The updated impextbridge01_lod.nif should be included since I wrote that in the reply which typically means I updated the source for the archive already.

Some, not sure how random. It won't be that obvious like with this particular normal map texture, though. Check its mipmaps, the 4th (64x64) is already flat.

Get the latest test version from https://dyndolod.info/Downloads/Test-Versions and generate new output. The preview should match the generated texture for the same resolution. The preview typically starts at 512x512. The problem was a mipmap issue were it might have randomly used the largest mipmap (similar to setting UseMipmaps=0 in TexGen INI) instead of filtering the appropriate mipmap levels. Note that the snow01_n.dds in Skyrim LE has mipmap that go basically flat, so if you render smaller output resolution it will become even flatter, which should match further away full models better.

Replace all 6 the files in Z:\Users\thomas.b.mitchell\Downloads\DynDOLOD\Edit Scripts\DynDOLOD\shaders\ with the ones in the attached archive. Then run again and upload new logs. Shaders.7z

We are making progress one OpenGL command in the setup phase at a time. It really does not seem to support anything that was introduced after 2.1. We should be able to get somewhere eventually, as long as you are willing to test and upload new logs. I am not quite sure how many more errors until we got through the setup phase. in the end we hopefully have just a somewhat slower generation without multisampling. It should still generate acceptable results. So, run new test version, upload new logs....

Yes, in that case it seems it is something in TexGen. The preview should match the output or vice versa. I will look into it, but might be a day or two.

You seem to have a much bumpier textures\landscape\Snow01_n.dds normal map texture replacing the vanilla one.

Keep the setting LoadGLCompressed=0 Run the new test version and upload the new logs.

Moved to the DynDOLOD 3 Alpha thread. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD log and debug log to upload when making posts. https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages Pay attention to log messages and read their explanations. https://dyndolod.info/Messages/Texture-Resolution A texture that is added to a texture atlas can technically use any resolution, since the atlas texture resolution meats the requirement. Tree/grass LOD billboards are typically never used directly. In case there are 3rd party LOD billboards listed in the message (textures\terrain\LODGen\*), remove all 3rd party LOD billboards and instead use TexGen to generate all the desired LOD billboards. See TexGen Configuration for more. The message might be reported for billboard textures used by object LOD models that do meet the filename conventions required for 3D tree LOD models for DynDOLOD. See https://dyndolod.info/Official-DynDOLOD-Support-Forum and https://dyndolod.info#DynDOLOD-3-Alpha Verify if the reported textures are actually from the TexGen output run for the current load order and report that together with the logs. If that is the case, it is probably because the object LOD models do not meet DynDOLOD filename requirements for 3D tree LOD models.

Moved to a similar thread. The TexGen logs do not show an entire generation session. Make sure it rendered textures\dlc01\lod\DLC01IceSnow.dds. It seems the DynDOLOD Resources for Skyrim LE contain an outdated LOD model. Replace ..\Meshes\dlc01\lod\lakesnow01_lod.nif with the one attached, then Execute LODGen for DLC01FalmerValley again in Export mode to update the object LOD meshes. lakesnow01_lod.nif

Upload a useful screenshot of the full model with more informative console as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload when making posts. If you have the same problem, thennthe same sution applies. No link to a post with the "same problem" was provided. While DynDOLOD Plugins might be using a full model NIF and full textures provided by vanilla or mods, it typically does not change their appearance. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting Make sure things look as expected without DynDOLOD output. If that changes anything, make sure to generate LOD for the current load order. See https://dyndolod.info/Help/Glow-LOD about the LightingShader INI settings.

Did you make any changes to C:\Modding\DynDOLOD SSE\DynDOLOD\Edit Scripts\DynDOLOD\Rules\DynDOLOD_SSE_legacyofthedragonbornv5esm_High.ini? Restore the default DynDOLOD_SSE_legacyofthedragonbornv5esm_high.ini from the DynDOLOD download archive. Probably best to unpack the DynDOLOD Standalone again into a new empty folder. Then start DynDOLOD as usual, select high to load the rules and generate just LOD for Tamriel, no need to Occlusion etc. for test.

Also upload the DynDOLOD debug log as explained in the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

Get the new test version. Add LoadGLCompressed=0 under [TexGen] to the TexGen_SSE.INI. Upload new logs.

I uploaded a new test version to run and upload the new logs for.

The DynDOLOD log only contains a session that starts the tool without generating anything. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which DynDOLOD log and debug log to upload. Make sure they both contain the entire last LOD generation session. Explain in which worldspace the in-game screenshots were made. Outside or inside the city walls? Is the main museum building missing in Tamriel or in the SolitudeWorld? Parent->Child being checked is not supposed to have an affect the museum building being visible in both worldspaces in this case. The xEdit screenshot shows a new reference in a DynDOLOD plugin not overwriting any other record. See https://dyndolod.info/Official-DynDOLOD-Support-Forum#xEdit-Screenshots

Data will just be copied from the json data found in the load order or the defaults baked into the DLL. Just the plugin name and id will be updated accordingly for the copied base record. If you need different values, make sure there is a json defining them for the original based record. In case of your screenshot that seems to be 0x00051577.