Tetrol88 Posted September 14, 2021 Posted September 14, 2021 Ok - Not that anything seems different to what I have stated The last generated Worldspace message/txt https://ufile.io/peob5cnm Dyndolod_SSE_log.txt https://ufile.io/fe6kmc8v Truncated Dyndolod_SSE_Debug_log.txt https://ufile.io/peob5cnm
Ashok0 Posted September 14, 2021 Posted September 14, 2021 Hi, I am using xLODGen Beta 84 and TexGen/DynDOLOD 3.0 with Enderal VR. I have always gone thru the following process without issue: 1. Run xLODGen with Perfect Terrain LOD (as temporary textures for xLODGen generation only) 2. Run TexGen 3. Run DynDOLOD 3.0 These steps have always worked flawlessly for me and I've had no issues with terrain/object/tree LOD. After updating to DynDOLOD Alpha 42, I receive the following error when running DynDOLOD 3.0: Incorrect terrain LOD for MQP01Home. See below for log files: DynDOLOD_ENDERALSE_log.txt: https://ufile.io/vpzxe8pr DynDOLOD_ENDERALSE_Debug_log.txt: https://ufile.io/1c0klc7l I was actually able fix this issue by simply re-running xLODGen and unticking the worldspace for MQP01Home "Home, Sweet Home" [WRLD:0000003C]. DynDOLOD runs fine now and terrain LODs look great! I believe I'm actually all set but was just wondering if the above fix is considered an optimal solution for using xLODGen + Perfect Terrain LOD with Enderal VR? Thanks!
sheson Posted September 14, 2021 Author Posted September 14, 2021 17 hours ago, Ashok0 said: Hi, I am using xLODGen Beta 84 and TexGen/DynDOLOD 3.0 with Enderal VR. I have always gone thru the following process without issue: 1. Run xLODGen with Perfect Terrain LOD (as temporary textures for xLODGen generation only) 2. Run TexGen 3. Run DynDOLOD 3.0 These steps have always worked flawlessly for me and I've had no issues with terrain/object/tree LOD. After updating to DynDOLOD Alpha 42, I receive the following error when running DynDOLOD 3.0: Incorrect terrain LOD for MQP01Home. See below for log files: DynDOLOD_ENDERALSE_log.txt: https://ufile.io/vpzxe8pr DynDOLOD_ENDERALSE_Debug_log.txt: https://ufile.io/1c0klc7l I was actually able fix this issue by simply re-running xLODGen and unticking the worldspace for MQP01Home "Home, Sweet Home" [WRLD:0000003C]. DynDOLOD runs fine now and terrain LODs look great! I believe I'm actually all set but was just wondering if the above fix is considered an optimal solution for using xLODGen + Perfect Terrain LOD with Enderal VR? Thanks! Why would you install "perfect" terrain LOD when using xLODGen to generate terrain LOD? That mod was made by simply running xLODGen to generate terrain LOD for the default Skyrim worldspaces. If you want to use its noise.dds in the game just keep that single texture and remove everything else. "Perfect" terrain LOD includes a renamed SSE-Terrain-Tamriel.esm which doesn't need to be loaded in the normal game, since it is a resource for generating terrain LOD for Tamriel. Installing a plugin that contains records for the Tamriel worldspace, means they are placed into Enderals MQP01Home worldspace, which doesn't make much sense. Worse there could be unintentional overwrites of records if plugins for a different game are installed without checking what happens to the vanilla Enderal game data.
sheson Posted September 14, 2021 Author Posted September 14, 2021 2 hours ago, Tetrol88 said: Ok - Not that anything seems different to what I have stated The last generated Worldspace message/txt https://ufile.io/peob5cnm Dyndolod_SSE_log.txt https://ufile.io/fe6kmc8v Truncated Dyndolod_SSE_Debug_log.txt https://ufile.io/peob5cnm The first post only mentions to truncate the normal log to the last meaningful generation, as it appends each sessions. Do not truncate the debug log. It always contains the last session. Upload the bugreport.txt as explained in the first post.
Viscerous Posted September 15, 2021 Posted September 15, 2021 I also got the "Item not found" error consistently on Alpha 42, I purged the DynDOLOD Standalone folder entirely and used the clean 42 files and then it ran fine. I previously copied it over 39 so there must've been something left in there.
sheson Posted September 15, 2021 Author Posted September 15, 2021 16 minutes ago, Viscerous said: I also got the "Item not found" error consistently on Alpha 42, I purged the DynDOLOD Standalone folder entirely and used the clean 42 files and then it ran fine. I previously copied it over 39 so there must've been something left in there. Yes, that is why following the installations say: Unpack the DynDOLOD Standalone archive into a new 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 or any mod manager folders.
dashr Posted September 15, 2021 Posted September 15, 2021 After upgrading from 0.39 to 0.42 Dyndolod seems to not work correctly. I installed No Grass in Objects V8 last night and everything works fine with it but I ran Texgen and Dyndolod after that. Terrain looks blurry. Mountains look black / don't load correctly. So all in all after all the alpha versions this one seems not to work. Can't revert to the older one, because I don't have it on my pc right now. What logs should I post so maybe anyone could help me out or even better find the issue?
z929669 Posted September 15, 2021 Posted September 15, 2021 6 hours ago, Viscerous said: I also got the "Item not found" error consistently on Alpha 42, I purged the DynDOLOD Standalone folder entirely and used the clean 42 files and then it ran fine. I previously copied it over 39 so there must've been something left in there. I believe it is the old 'default' preset INI that causes this issue. Whenever you run DynDLOD, the settings used are autosaved as the 'default' preset INI (this is how the app remembers previous settings from run to run), so with old mesh rules and other settings trying to load where they don't apply can cuase this or similar issues, I think. I think this because I retain all valid INI edits using WinMerge for all applicable INI files whenever I upgrade to the next Alpha, so I must delete or upgrade all presets to avoid the problem.
z929669 Posted September 15, 2021 Posted September 15, 2021 26 minutes ago, Alaak said: Hm. With the newest Alpha-42 I get the error message: [Window Title] TexGen [Main Instruction] Can not copy resource textures\architecture\whiterun\wrslatefloor01_n.dds to C:\Modding\DynDOLOD3\TexGen_Output\DynDOLOD-temp\textures\architecture\whiterun\wrslatefloor01_n.dds Das System kann den angegebenen Pfad nicht finden. [Content] Help for this message [Exit TexGen] [Footer] DynDOLOD FAQ | Support Forum | Copy message to clipboard That file is definitely present (it is for example part of Pfuscher 2020 and Noble Skyrim). I am using MO2 and assume that the MO2 Magic provides the file correctly to TexGen, which it was doing on all previous runs. I had no problems with this setup with Alpha-11 (which I had used previously). Any advice on how to proceed? Can I give you any helpful information about this error? See OP and previous posts on how to upgrade from previous versions. Overwriting contents requires extra work. it's recommended to install into a clean directory.
Alaak Posted September 15, 2021 Posted September 15, 2021 13 minutes ago, z929669 said: See OP and previous posts on how to upgrade from previous versions. Overwriting contents requires extra work. it's recommended to install into a clean directory. Hm. I already had made that error back when I upgraded to Alpha-11. So this time I deleted the whole DynDOLOD_3 directory and added all the Alpha-42 files to the empty directory. So this should not be the issue. I even did it twice, since I was not sure whether I really did it the first time, but the error persists.
dashr Posted September 16, 2021 Posted September 16, 2021 Thank you sheson. I tried it again but got the same exact error "Item not found". Weirdly enough i just installed dyndolod in a new directory. Still "Item not found" Tested it again today, still the same message.I tested all my drives. New Folder, new location everything. Of course I deleted the whole folder and unpacked a new one. Why is this happening?
dashr Posted September 16, 2021 Posted September 16, 2021 Tried to find the file and create it with no grass in objects. Still the issue persists.
sheson Posted September 16, 2021 Author Posted September 16, 2021 On 9/16/2021 at 6:47 PM, dashr said: Thank you sheson. I tried it again but got the same exact error "Item not found". Weirdly enough i just installed dyndolod in a new directory. Still "Item not found" Tested it again today, still the same message.I tested all my drives. New Folder, new location everything. Of course I deleted the whole folder and unpacked a new one. Why is this happening? From ..\DynDOLOD\docs\help\Errors.html "Item not found or Duplicates not allowed errors are a problem with the tools encountering unexpected situations that need to be reported as explained below." Read the first post, which also explains which log files to upload when making reports. On 9/15/2021 at 6:29 PM, dashr said: After upgrading from 0.39 to 0.42 Dyndolod seems to not work correctly. I installed No Grass in Objects V8 last night and everything works fine with it but I ran Texgen and Dyndolod after that. Terrain looks blurry. Mountains look black / don't load correctly. So all in all after all the alpha versions this one seems not to work. Can't revert to the older one, because I don't have it on my pc right now. What logs should I post so maybe anyone could help me out or even better find the issue? The LOD generation process and the generated LOD files are still the same. DynDOLOD does not affect terrain LOD meshes or textures. Doublecheck/increase the LOD distances in the DynDOLOD SkyUI MCM, in the launcher or with BethINI.
dashr Posted September 16, 2021 Posted September 16, 2021 Will do, thanks again for the fast reply. Hope this helps. bugreport.txt
sheson Posted September 16, 2021 Author Posted September 16, 2021 31 minutes ago, dashr said: Will do, thanks again for the fast reply. Hope this helps. bugreport.txt 46.91 kB · 2 downloads Don't forget to upload the mentioned log and debug_log.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now