sheson

Loading large load orders will require more memory than the x86 version might be able to use.

The link lists bugreport.txt only Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire TexGen log, debug log to also upload when making posts. If there are not such logs, then report that. Do not set -lodgen tool mode in the command line arguments. See https://dyndolod.info/Mods/Skyrim-Special-Edition-GOG-Skyrim-Anniversary-Edition-GOG how to properly set the command line arguments for the Skyrim GOG version: Do not link to files or folders in mod manager profiles. Link to the files and folders used by the game. A properly setup and working mod manager updates the actual INI files in their default location also used by the game.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which entire TexGen log, debug log and bugrport.txt if it exists to upload when making posts.

There shouldn't be a problem loading the entire load into xEdit x64 version.

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.