sheson Posted June 18 Author Share Posted June 18 1 hour ago, Soulmancer said: I tried to run Dyndolod Alpha .173 x64 but I got an Assertion failure (E:\Delphi\Projects\DynDOLOD3\Core\wbImplementation.pas, line 8480) Here is the bug report log. https://paste.ee/p/EVyLv here is the DynDOLOD_SSE_log.txt https://paste.ee/p/NmRzC Debug log is here. https://drive.google.com/file/d/1hGt9AP4_VHPNw21XIMxkutKxWGKQiZUf/view?usp=sharing Never experienced this before but running again to see if it's repeatable. I did check xEdit for errors and can't see an issue I've not addressed EDIT: re-ran and the had the same error again. 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. Follow https://dyndolod.info/Updating#New-DynDOLOD-Version to rename the old installation folder first, then generate from scratch instead of trying to update existing DynDOLOD output: If updating of the TexGen output or DynDOLOD output is desired for a new DynDOLOD version, typically generate and update from scratch: Remove or backup old TexGen output, old DynDOLOD output Run TexGen and install its output as explained on the generation instructions. Run DynDOLOD and install its output as explained on the generation instructions. In case any of the updating instructions below are unsuccessful, also generate from scratch. This can cause CTD in the game and would be one of the things to fix when error checking the load order with xEdit: <Warning: Found a NULL reference, expected: ACTI,ADDN,ALCH,AMMO,APPA,ARMA,ARMO,ARTO,ASPC,BOOK,CONT,DOOR,FLOR,FURN,GRAS,IDLM,INGR,KEYM,LIGH,LVLC,LVLN,MISC,MSTT,SCRL,SLGM,SNDR,SOUN,SPEL,STAT,TACT,TREE,TXST,WEAP Errors Fix.esp [REFR:66015749] (places NULL - Null Reference [00000000] in GRUP Cell Temporary Children of BleakwindBasinExterior01 [CELL:000099A2] (in Tamriel "Skyrim" [WRLD:0000003C] at 0,0))> If problem persist with new and clean installation and generating new output from scratch, upload new DynDOLOD log and debug log and bugreport.txt if it exists. Link to comment Share on other sites More sharing options...
Soulmancer Posted June 18 Share Posted June 18 9 hours ago, sheson said: 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. Follow https://dyndolod.info/Updating#New-DynDOLOD-Version to rename the old installation folder first, then generate from scratch instead of trying to update existing DynDOLOD output: If updating of the TexGen output or DynDOLOD output is desired for a new DynDOLOD version, typically generate and update from scratch: Remove or backup old TexGen output, old DynDOLOD output Run TexGen and install its output as explained on the generation instructions. Run DynDOLOD and install its output as explained on the generation instructions. In case any of the updating instructions below are unsuccessful, also generate from scratch. This can cause CTD in the game and would be one of the things to fix when error checking the load order with xEdit: <Warning: Found a NULL reference, expected: ACTI,ADDN,ALCH,AMMO,APPA,ARMA,ARMO,ARTO,ASPC,BOOK,CONT,DOOR,FLOR,FURN,GRAS,IDLM,INGR,KEYM,LIGH,LVLC,LVLN,MISC,MSTT,SCRL,SLGM,SNDR,SOUN,SPEL,STAT,TACT,TREE,TXST,WEAP Errors Fix.esp [REFR:66015749] (places NULL - Null Reference [00000000] in GRUP Cell Temporary Children of BleakwindBasinExterior01 [CELL:000099A2] (in Tamriel "Skyrim" [WRLD:0000003C] at 0,0))> If problem persist with new and clean installation and generating new output from scratch, upload new DynDOLOD log and debug log and bugreport.txt if it exists. I did fix the NULL error record, and have now made sure the new version of dyndolod has been extracted to an empty and benign folder. I was trying to update existing plugins and I made sure I wiped the output folder of everything except the Dyndolod.esp, Dyndolod.esm and Occlusion.esp. I thought it's because my Dyndolod output generation was pointing into my active MO2 mod list so I tried changing the output destination to an empty folder outside of my mod folder. After this it is still hitting on the same assertion error. I am also using the latest Dyndolod Resources and Dyndolod DLL NG. There were no issues generating TexGen. I'll try generating the output from scratch next time to see if it's the same result but updating the plugins is preferable. I believe the last time I created Dyndlod from scratch was in .169 Link to comment Share on other sites More sharing options...
GerithorDunedain Posted June 18 Share Posted June 18 Hello! This is the error I'm getting. I've attached my load order as well. I've made sure I have the most current versions of DynDOLOD and the Resource pack, as well as DynDOLOD DLL. [00:08] Background Loader: finished Loading configuration files C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_skyrimesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_alpha_skyrimesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_copy_skyrimesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_dawnguardesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_copy_dawnguardesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_dragonbornesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_copy_dragonbornesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_waterforenbesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_copy_waterforenbesm.txt Game: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\SkyrimSE.exe, Version: 1.6.1170, Date: 2024-05-27 13:30:19 SKSE: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\skse64_loader.exe, Version: 2.2.6, Date: 2024-01-17 13:11:36 PapyrusUtil DLL: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\PapyrusUtil.DLL, Version: 4.6, Game Version: 1.6.1170, Date: 2024-01-18 21:36:10 DynDOLOD DLL: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD.DLL, Version: 3.0.29.1130, Game Version: SE/AE 1.6.1130+, Date: 2024-05-19 18:00:00 Item not found Error: Item not found. The message dialog has been copied to the clipboard https://paste.ee/p/3NHqG Link to comment Share on other sites More sharing options...
ExquisiteLemon Posted June 18 Share Posted June 18 (edited) 10 hours ago, sheson said: 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. Always upload the entire log, do not trim or post only a few lines. https://dyndolod.info/Generation-Instructions#Prerequisites Finalize the load order. Install mods and their requirements. Sort and resolve conflicts. ... Typically create all other patches first. Especially all patches affecting exterior worldspaces in any way should be done before generating LOD. Generated DynDOLOD patch plugins should be required by other plugins other than Occlusion.esp. The DynDOLOD LOD patch should never be patched itself. Something is going or done wrong if this happens. The crash log shows Light: 0 Regular: 0 Total: 0 The game can not work work without any game plugin like Skyim.esm etc. This might be missing master or not having BEES installed. So for whatever reason, the current Dyndolod.esm does not seem to be compatible with the current release of Requiem. Specifically, Requiemfortheindifferent.esp. After removing Dyndolod_Output from load order and re running the patcher, and then re installing Dyndolod_Output, the game works fine, no more CTD and Dyndolod is working as intended in game. I don’t really know the specifics of why the Requiem patcher no longer works with Dyndolod for me at least, but that is what I have narrowed down my CTD on launch too. I would like to say thank you for all the helpful links and advice for trouble shooting, the new kids generated with LodGen look phenomenal. Edited June 18 by ExquisiteLemon Link to comment Share on other sites More sharing options...
sheson Posted June 18 Author Share Posted June 18 4 hours ago, Soulmancer said: I did fix the NULL error record, and have now made sure the new version of dyndolod has been extracted to an empty and benign folder. I was trying to update existing plugins and I made sure I wiped the output folder of everything except the Dyndolod.esp, Dyndolod.esm and Occlusion.esp. I thought it's because my Dyndolod output generation was pointing into my active MO2 mod list so I tried changing the output destination to an empty folder outside of my mod folder. After this it is still hitting on the same assertion error. I am also using the latest Dyndolod Resources and Dyndolod DLL NG. There were no issues generating TexGen. I'll try generating the output from scratch next time to see if it's the same result but updating the plugins is preferable. I believe the last time I created Dyndlod from scratch was in .169 https://dyndolod.info/Generation-Instructions Select a dedicated output path. The dedicated output path should be 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. Link to comment Share on other sites More sharing options...
sheson Posted June 18 Author Share Posted June 18 14 hours ago, GerithorDunedain said: Hello! This is the error I'm getting. I've attached my load order as well. I've made sure I have the most current versions of DynDOLOD and the Resource pack, as well as DynDOLOD DLL. [00:08] Background Loader: finished Loading configuration files C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_skyrimesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_alpha_skyrimesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_copy_skyrimesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_dawnguardesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_copy_dawnguardesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_dragonbornesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_copy_dragonbornesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_noalpha_waterforenbesm.txt C:\Skyrim Mods\DynDOLOD\Edit Scripts\DynDOLOD\Configs\DynDOLOD_SSE_TexGen_copy_waterforenbesm.txt Game: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\SkyrimSE.exe, Version: 1.6.1170, Date: 2024-05-27 13:30:19 SKSE: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\skse64_loader.exe, Version: 2.2.6, Date: 2024-01-17 13:11:36 PapyrusUtil DLL: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\PapyrusUtil.DLL, Version: 4.6, Game Version: 1.6.1170, Date: 2024-01-18 21:36:10 DynDOLOD DLL: C:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data\SKSE\Plugins\DynDOLOD.DLL, Version: 3.0.29.1130, Game Version: SE/AE 1.6.1130+, Date: 2024-05-19 18:00:00 Item not found Error: Item not found. The message dialog has been copied to the clipboard https://paste.ee/p/3NHqG Moved to the DynDOLOD 3 thread. Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Links which entire TexGen log and debug log to upload when making posts. Was there not a link Click on this link for additional explanations and help for this message with the message that opens https://dyndolod.info/Messages/Exceptions#Item-not-found https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions Link to comment Share on other sites More sharing options...
Soulmancer Posted June 19 Share Posted June 19 9 hours ago, sheson said: https://dyndolod.info/Generation-Instructions Select a dedicated output path. The dedicated output path should be 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. The output I pathed to e:\DynDOLOD_Output\ The process completes successfully if I build from scratch but I still get the same assertion error if I try to update using the old plugins EDIT: don't know if this is relevant, but according to the date stamp it seems to be finishing updating the Occlusion and Dyndolod ESPs according to the date modified stamp and creating the meshes and textures... but it is not updating the Dydolod.ESM or creating the SKSE folder. Link to comment Share on other sites More sharing options...
sheson Posted June 19 Author Share Posted June 19 14 hours ago, ExquisiteLemon said: So for whatever reason, the current Dyndolod.esm does not seem to be compatible with the current release of Requiem. Specifically, Requiemfortheindifferent.esp. After removing Dyndolod_Output from load order and re running the patcher, and then re installing Dyndolod_Output, the game works fine, no more CTD and Dyndolod is working as intended in game. I don’t really know the specifics of why the Requiem patcher no longer works with Dyndolod for me at least, but that is what I have narrowed down my CTD on launch too. I would like to say thank you for all the helpful links and advice for trouble shooting, the new kids generated with LodGen look phenomenal. If the load order changes, automatically generated patch plugins may become out of date and need to be generated again. Link to comment Share on other sites More sharing options...
sheson Posted June 19 Author Share Posted June 19 5 hours ago, Soulmancer said: The output I pathed to e:\DynDOLOD_Output\ The process completes successfully if I build from scratch but I still get the same assertion error if I try to update using the old plugins EDIT: don't know if this is relevant, but according to the date stamp it seems to be finishing updating the Occlusion and Dyndolod ESPs according to the date modified stamp and creating the meshes and textures... but it is not updating the Dydolod.ESM or creating the SKSE folder. Updating, especially across versions changes is not guaranteed to work. Is there an error updating output that was generated with the same version? Link to comment Share on other sites More sharing options...
Soulmancer Posted June 19 Share Posted June 19 7 hours ago, sheson said: Updating, especially across versions changes is not guaranteed to work. Is there an error updating output that was generated with the same version? Understandable. I had not tried updating with same version, but I will in the future. I have read instructions for updating on an existing save. Does the same apply to generating from scratch? I guess my concern there is wont the exclusive dyndolod form IDs be different when creating from scratch? … On an existing save isn’t that bad? akin to compacting form records to ESL flag a plugin mid save? Link to comment Share on other sites More sharing options...
sheson Posted June 19 Author Share Posted June 19 7 minutes ago, Soulmancer said: Understandable. I had not tried updating with same version, but I will in the future. I have read instructions for updating on an existing save. Does the same apply to generating from scratch? I guess my concern there is wont the exclusive dyndolod form IDs be different when creating from scratch? … On an existing save isn’t that bad? akin to compacting form records to ESL flag a plugin mid save? https://dyndolod.info/Help/Clean-Save The DynDOLOD plugins or the Occlusion.esp itself are very simple and mostly self contained. That means removing and/or updating does not have any known ill-effects, if following the below procedure. The clean procedure only needs to be done if generating new DynDOLOD output from scratch (in case a 3rd party plugin that is a master in a DynDOLOD plugin has been removed for example) or when switching from PapyrusUtil to DynDOLOD DLL or vice versa for an existing save game. There is no need for a clean save when updating existing DynDOLOD plugins and/or Occlusion.esp. Link to comment Share on other sites More sharing options...
Morti Posted June 19 Share Posted June 19 (edited) The newest version's changelog says: fixed an item not found error The problem is that this is what I have with TexGen: [05:06] [GetRequiredBillboards] <Debug: Processing Update.esm SnowGrass02 [GRAS:000F17FE]> [05:06] [GetRequiredBillboards] <Debug: Ignoring Meshes\landscape\grass\rockgrasswater01.nif bounds volume 0, height 0 Update.esm RockGrassWater01 [GRAS:000F871D]> [05:06] [GetRequiredBillboards] <Debug: Processing Update.esm SnowGrass01Light [GRAS:000F17FD]> [05:06] [GetRequiredBillboards] <Debug: Processing Update.esm SnowGrass01Forest [GRAS:000BC025]> [05:06] [GetRequiredBillboards] <Debug: Processing Update.esm WaterCoralGrass01 [GRAS:0007AACC]> [05:06] [GetRequiredBillboards] <Debug: Ignoring Meshes\landscape\grass\watercoralgrass01.nif bounds volume 155.261077880859, height 86 Update.esm WaterCoralGrass01 [GRAS:0007AACC]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\fieldgrassflowers02.nif FieldGrassFlowers17:0 Shader Flags 1: Vertex_Alpha | Recieve_Shadows | Cast_Shadows | Own_Emit | Remappable_Textures | ZBuffer_Test Update.esm FieldGrass02 [GRAS:001098CA]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\fieldgrassflowers02.nif FieldGrassFlowers17:0 Shader Flags 2: ZBuffer_Write | Double_Sided | Vertex_Colors | EnvMap_Light_Fade Update.esm FieldGrass02 [GRAS:001098CA]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\snowgrass02.nif SnowGrass02:0 Shader Flags 1: Vertex_Alpha | Recieve_Shadows | Cast_Shadows | Own_Emit | Remappable_Textures | ZBuffer_Test Update.esm SnowGrass02 [GRAS:000F17FE]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\snowgrass02.nif SnowGrass02:0 Shader Flags 2: ZBuffer_Write | Double_Sided | Vertex_Colors | EnvMap_Light_Fade Update.esm SnowGrass02 [GRAS:000F17FE]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\snowgrass01.nif SnowGrass01:0 Shader Flags 1: Vertex_Alpha | Recieve_Shadows | Cast_Shadows | Own_Emit | Remappable_Textures | ZBuffer_Test Update.esm SnowGrass01Light [GRAS:000F17FD]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\snowgrass01.nif SnowGrass01:0 Shader Flags 2: ZBuffer_Write | Double_Sided | Vertex_Colors | EnvMap_Light_Fade Update.esm SnowGrass01Light [GRAS:000F17FD]> Item not found [06:00] 00000000 ??? 0104c2e7 TexGenx64.exe DynDOLODResourceStrings 930 dynMessageDialog 00fca699 TexGenx64.exe xeMainForm 4920 TfrmMain.DoGenerateLOD 0102af78 TexGenx64.exe xeMainForm 17745 TfrmMain.tmrGeneratorTimer 007c0080 TexGenx64.exe Vcl.ExtCtrls TTimer.Timer 007bfea8 TexGenx64.exe Vcl.ExtCtrls TTimer.WndProc 005e49f3 TexGenx64.exe System.Classes StdWndProc 6fffff63 user32.dll DispatchMessageW 0085f65e TexGenx64.exe Vcl.Forms TApplication.ProcessMessage 0085f6d3 TexGenx64.exe Vcl.Forms TApplication.HandleMessage 0085fb2a TexGenx64.exe Vcl.Forms TApplication.Run 01d46eb0 TexGenx64.exe DynDOLOD 184 initialization 6fffffed kernel32.dll BaseThreadInitThunk 6ffffff4 ntdll.dll RtlUserThreadStart Item not found Error: Item not found. [06:01] [TMessageDialog.Dialog] <Debug: Creating TTaskDialog> [06:01] [TMessageDialog.Dialog] <Debug: [TMessageDialog.Dialog] Executing TTaskDialog> [06:07] [TMessageDialog.Dialog] <Debug: Gathering> User says "Exit TexGen" Forced LINK to the log files. I tried some cleaning mods etc. but nothing really impacts the thing. The folder is new, no overwritten old version. The modlist is also new. Also tried it a few times and sometimes it says "DATA - DATA" after "item not found" Edited June 19 by Morti Link to comment Share on other sites More sharing options...
sheson Posted June 19 Author Share Posted June 19 2 hours ago, Morti said: The newest version's changelog says: fixed an item not found error The problem is that this is what I have with TexGen: [05:06] [GetRequiredBillboards] <Debug: Processing Update.esm SnowGrass02 [GRAS:000F17FE]> [05:06] [GetRequiredBillboards] <Debug: Ignoring Meshes\landscape\grass\rockgrasswater01.nif bounds volume 0, height 0 Update.esm RockGrassWater01 [GRAS:000F871D]> [05:06] [GetRequiredBillboards] <Debug: Processing Update.esm SnowGrass01Light [GRAS:000F17FD]> [05:06] [GetRequiredBillboards] <Debug: Processing Update.esm SnowGrass01Forest [GRAS:000BC025]> [05:06] [GetRequiredBillboards] <Debug: Processing Update.esm WaterCoralGrass01 [GRAS:0007AACC]> [05:06] [GetRequiredBillboards] <Debug: Ignoring Meshes\landscape\grass\watercoralgrass01.nif bounds volume 155.261077880859, height 86 Update.esm WaterCoralGrass01 [GRAS:0007AACC]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\fieldgrassflowers02.nif FieldGrassFlowers17:0 Shader Flags 1: Vertex_Alpha | Recieve_Shadows | Cast_Shadows | Own_Emit | Remappable_Textures | ZBuffer_Test Update.esm FieldGrass02 [GRAS:001098CA]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\fieldgrassflowers02.nif FieldGrassFlowers17:0 Shader Flags 2: ZBuffer_Write | Double_Sided | Vertex_Colors | EnvMap_Light_Fade Update.esm FieldGrass02 [GRAS:001098CA]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\snowgrass02.nif SnowGrass02:0 Shader Flags 1: Vertex_Alpha | Recieve_Shadows | Cast_Shadows | Own_Emit | Remappable_Textures | ZBuffer_Test Update.esm SnowGrass02 [GRAS:000F17FE]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\snowgrass02.nif SnowGrass02:0 Shader Flags 2: ZBuffer_Write | Double_Sided | Vertex_Colors | EnvMap_Light_Fade Update.esm SnowGrass02 [GRAS:000F17FE]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\snowgrass01.nif SnowGrass01:0 Shader Flags 1: Vertex_Alpha | Recieve_Shadows | Cast_Shadows | Own_Emit | Remappable_Textures | ZBuffer_Test Update.esm SnowGrass01Light [GRAS:000F17FD]> [05:06] [AddModel] <Debug: Meshes\landscape\grass\snowgrass01.nif SnowGrass01:0 Shader Flags 2: ZBuffer_Write | Double_Sided | Vertex_Colors | EnvMap_Light_Fade Update.esm SnowGrass01Light [GRAS:000F17FD]> Item not found [06:00] 00000000 ??? 0104c2e7 TexGenx64.exe DynDOLODResourceStrings 930 dynMessageDialog 00fca699 TexGenx64.exe xeMainForm 4920 TfrmMain.DoGenerateLOD 0102af78 TexGenx64.exe xeMainForm 17745 TfrmMain.tmrGeneratorTimer 007c0080 TexGenx64.exe Vcl.ExtCtrls TTimer.Timer 007bfea8 TexGenx64.exe Vcl.ExtCtrls TTimer.WndProc 005e49f3 TexGenx64.exe System.Classes StdWndProc 6fffff63 user32.dll DispatchMessageW 0085f65e TexGenx64.exe Vcl.Forms TApplication.ProcessMessage 0085f6d3 TexGenx64.exe Vcl.Forms TApplication.HandleMessage 0085fb2a TexGenx64.exe Vcl.Forms TApplication.Run 01d46eb0 TexGenx64.exe DynDOLOD 184 initialization 6fffffed kernel32.dll BaseThreadInitThunk 6ffffff4 ntdll.dll RtlUserThreadStart Item not found Error: Item not found. [06:01] [TMessageDialog.Dialog] <Debug: Creating TTaskDialog> [06:01] [TMessageDialog.Dialog] <Debug: [TMessageDialog.Dialog] Executing TTaskDialog> [06:07] [TMessageDialog.Dialog] <Debug: Gathering> User says "Exit TexGen" Forced LINK to the log files. I tried some cleaning mods etc. but nothing really impacts the thing. The folder is new, no overwritten old version. The modlist is also new. Also tried it a few times and sometimes it says "DATA - DATA" after "item not found" Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which bugreport.txt to also upload. https://dyndolod.info/Messages/Exceptions#Item-not-found Link to comment Share on other sites More sharing options...
Morti Posted June 20 Share Posted June 20 7 hours ago, sheson said: Read the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which bugreport.txt to also upload. https://dyndolod.info/Messages/Exceptions#Item-not-found https://pastebin.com/kScrGKzL Link to comment Share on other sites More sharing options...
sheson Posted June 21 Author Share Posted June 21 On 6/20/2024 at 7:44 AM, Morti said: https://pastebin.com/kScrGKzL Check if there is anything different with this test version https://mega.nz/file/1VAgHJ6J#Ejhao_JjMxKCfHjrGmHsEUFQ9Tr0iQkrbkgcYBqr4CA If not, upload new TexGen log, debug log and bugreport.txt Link to comment Share on other sites More sharing options...
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