sheson

That is really appreciated. Thank you very much.

It looks like renumbering worked OK. I would check one or two key changes of the mod to see if it works as expected in the game. The warnings in Fallout.esm are expected and no need for concern.

DynDOLOD 2.x had no updates since years. DynDOLOD 3 is released for alpha testing so people can help with finding and reporting problems. Since you did mention a problem, 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. Also upload the papyrus logs and the c:\Users\[USERNAME]\Documents\My Games\Skyrim Special Edition\SKSE\DynDOLOD.log See https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing Do not paraphrase messages. Provide the actual message. It is unclear if "1.5.97 Steam dll" refers to DynDOLOD DLL SE or the DynDOLOD DLL NG version that works for 1.5.97 and not 1.6.1130+ Which DLL is needed, depends on which papyrus scripts are installed last. However, DynDOLOD DLL SE and DynDOLOD DLL NG are not interchangeable, like DynDOLOD DLL SE and PapyrusUtil are. DynDOLOD DLL NG requires a LOD specifically generated for it. See https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

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. Obviously posts the crash log when making posts about CTDs in the game. https://dyndolod.info/Official-DynDOLOD-Support-Forum Report the actual problem or error message without making assumptions or asking leading questions. Read the explanations and tips below, especially about what information and logs to provide and how. Also see Don't ask to ask, just ask and How do I ask a good question? https://dyndolod.info/Official-DynDOLOD-Support-Forum#Rudimentary-Troubleshooting In case of issues in the game, test if the problem persists without any DynDOLOD output. I will obviously look at the logs regardless of the reason of the CTD and not just make up illogical nonsense just because a filename of a plugin is listed in the load order or suggest to use the Skyrim LE SKSE memory patch with Skyrim SE. How saves, scripts and script instances work is known and documented since decades.

The Skyrim.esm file is probably corrupt. Its CRC32 does not seem to match the current hat ships with 1.6.1170 Load it with a recent version of xEdit and check for similar error messages by the background loader. Verify the game files in Steam to acquire the current version(s) of game the plugins.

Moved to the DynDOLOD 3 Alpha thread. 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. See https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds#Testing, also which papyrus and DynDOLOD.log to upload when having problems with DynDOLOD DLL NG. Obviously post the crash log when reporting crashes in the game. See https://dyndolod.info/FAQ#ILS-or-CTD Dyndolod Problem with worlds config file probably means the file does not exist, which might mean the DynDOLOD patch was not generated for DynDOLOD DLL NG. DynDOLOD DLL NG is not a drop-in replacement. See https://dyndolod.info/Help/Large-Reference-Bugs-Workarounds

Yes, make sure to also load all plugins that have the one you are chaning as master. Once you finalized the load order, make sure to check the entire load order for error with xEdit. In case a plugin was forgotten, it will have unresolved form IDs errors. DynDOLOD also catches thoses errors, but it doesn not check all records, like the xEdit check does.

Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen and DynDOLOD logs and debug logs to upload. Post useful screenshots of affected fulls model with more informative console as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots What are the "troubles" and what does "terrain popping" or "tree popping" mean exactly? Newer runtime versions obviously did not change how the game loads and renders full models and LOD.

The problem might be that you are trying to reorder form IDs while xEdit is in FO4VR game mode while it has to be done in FO4 mode while plugins of version 1.0 are supported. You would need to start xEdit with the -fo4 command line argument. If you do not have Fallout4, you should be able to do that together with the -d -m and -p command line arguments setting the data folder and INI folder and plugins.txt to the ones of the VR version. https://dyndolod.info/Help/Command-Line-Argument Once the plugin is loaded in the FO4 game mode without any error messages, renumber the form IDs. That should list lots of form IDs being changed in the messages log. Once done, change the plugin version to 0.95 and then save. Then load the plugin in FO4VR mode to check there are no more x is being overridden by y messxages.

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. Also upload ..\DynDOLOD\Logs\DynDOLOD_SSE_Object_Report.txt Report the actual problem in the game. Provide useful screenshots of the full model with more informative console as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots The MODT - Model Information element is not the same as the MODS - Alternate Textures element. The entries of MODT - Model Information are not Texture Sets. The entries of MODT - Model Information list the textures the vanilla model uses. The entries do not affect which textures the model uses in the game. That is what MODS - Alternate Textures entries do.

XLODGen, TexGen and DynDOLOD are all based on the latest xEdit sources available on github, so they closely follow the builds posted on the xEdit Discord. Fallout4VR needs plugins version 0.95 and formIDs over 0x800. How and which xEdit version works best to change the formIDs is probably best asked on the xEdit discord or maybe experienced people of the FO4VR community that must deal with issue on a daily basis.

The TexGen log, debug log or the plugin have not been provided. The xEdit log is truncated, so it is unclear which xEdit version the xEdit log is from. I assume it is from xEdit 4.0.3. TexGen is based on the latest xEdit version. Load the plugin with the latest xEdit version and check if the background loader reports x is being overridden by record y. If not, make sure TexGen loads the same plugin. In any case, you can also just check if the plugin contains records with form IDs < 0x800 manually.

No the plugin is not save to use with Fallout4 VR in this state. The records being overwritten will cause issue n the game and with saves that can not be fixed.

Use the x64 version as explained by the installation instructions https://dyndolod.info/Installation-Instructions Upload new log, debug log and bugreport.txt if problem persists.

From the log: [00:08] Background Loader: Warning: Record [DOOR:00000004] in file Fallout4.esm is being overridden by record [GMST:01000004] in file Fallout 4 AI Overhaul.esp. [00:08] Background Loader: Warning: Record [STAT:00000005] in file Fallout4.esm is being overridden by record [GMST:01000005] in file Fallout 4 AI Overhaul.esp. [00:08] Background Loader: Warning: Record [STAT:00000006] in file Fallout4.esm is being overridden by record [GMST:01000006] in file Fallout 4 AI Overhaul.esp. [00:08] Background Loader: Warning: Record [NPC_:00000007] in file Fallout4.esm is being overridden by record [GMST:01000007] in file Fallout 4 AI Overhaul.esp. There are many more. If that is the plugin you already worked on with xEdit to change the form ID issue, then it didn't work as expect. It may be because you used and older or newer version of xEdit that now works differently. Try with xEdit 4.0.3 and the original plugin. You will have to ask on the xEdit discord or maybe check on a Fallout4 VR related forum. Maybe report the issue in case it didn't work with the most recent version so it can addressed.

No logs or modified plugin were provided. No xEdit log has been provided either. TexGen/DynDOLOD is a modified xEdit. This error is reported by the xEdit background loader. I asked you to load the plugin in xEdit and check the background loader log messages for the x is being overridden by record y messages. Are you reporting that this does not happen? There should be no records having a form ID below 0x800.

https://dyndolod.info/Installation-Instructions Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\. See Updating how to update existing installation and save games. Do not install the tools into special Windows folders like c:\users\ Do not install the tools into Vortex folders. Do not install the tools into game folders. Do not install the tools into paths containing "textures".

No logs, error messages or the updated plugin were provided. If "the same error message still comes up" then the load order still contains the reported error. Load the plugin in xEdit and check the background loader log messages for the x is being overridden by record y messages.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which TexGen log and debug log to upload when making posts. This is an error reported by the xEdit background loader. Fallout4VR does not support form IDs in the range 0x000 to 0x7FF. It also does not support ESL flagged plugins. https://dyndolod.info/Messages/Record-Is-Being-Overridden. This is is a well known and documented limitation. AFAIK there is no DLL yet to add support for the lower range form IDs and/or ESL support. Form IDs need to be higher than 0x800. If you have problems with using xEdit, you should report or ask for help on the xEdit discord.

You would have to ask Bethesda why they made terrain LOD textures that do not match the actual full textures and do not match the terrain in the active cells or why they created shaders and post processing effects that make the difference worse or the map have a greenish etc. Terrain LOD meshes and textures can be added or removed any time. They have standard file names and thus are interchangeable. Note that terrain LOD Level 32 is used in the game in far distance and the map and a brightness difference will be visible unless you increase the terrain LOD multiplier INI setting at the cost of performance. https://dyndolod.info/Help/Mod-Configuration-Menu#Settings, https://dyndolod.info/Help/Terrain-LOD-and-Water-LOD, https://dyndolod.info/Help/xLODGen#Terrain-LOD-Textures-Brightness, https://dyndolod.info/Mods/Maps-And-Map-Mods

As I wrote before, the terrain LOD textures for all LOD levels match the full textures in the active cells 1:1 if the brightness, contrast, gamma settings are left alone. The brightness, contrast, gamma affect the end result equally. If you want only a specific texture or two to be different, then you would need to change/replace the full landscape texture temporality. In any case, the differences are because of post processing effects, overlay textures and INI settings applied in the game.

From the changelog: DynDOLOD DLL NG and Scripts - do not reset currently disabled persistent large references To improve the coastlines of terrain LOD meshes on the map generated by xLODGen, set the Optimized Unseen dropdown to 550 with a quality lower than 10 (0 for best) for LOD level 32 as explained on the first post and https://dyndolod.info/Help/xLODGen#Generating-Terrain-LOD-Meshes

Get DynDOLOD DLL NG Alpha 18. It hopefully fixes the CTD.

A record being overwritten itself typically does not cause issues. Was there something wrong with the overwrite? Could you link or upload the version of the plugin you were using?

Can you load the entire load order into xEdit, enter 0009DAA3 into the top left form ID field and hit enter to bring up the record. Check which plugin is the last overwrite to the very right. Is it Nature of the Wild Lands.esp? Which version are you using? It does not seem to be the one from 2.4 or was the plugin modified? Could you link or upload it?