sheson Posted February 7, 2022 Author Share Posted February 7, 2022 8 minutes ago, hanzabu said: sry i dont know which log file you r refering too, the only files generated r those i posted, do u want me to copy the output in xlodgen window ? The SSELODGen_log.txt is saved when xLODGen is closed. Link to comment Share on other sites More sharing options...
hanzabu Posted February 7, 2022 Share Posted February 7, 2022 7 minutes ago, sheson said: The SSELODGen_log.txt is saved when xLODGen is closed. sry i'm an idiot, i didn't close xlodgen for the file to get generated, here u go & thx for your patience (it would be wise to name those test binaries differently, so we can communicate more effectively) SSELODGen_log.txt Link to comment Share on other sites More sharing options...
sheson Posted February 7, 2022 Author Share Posted February 7, 2022 11 minutes ago, hanzabu said: sry i'm an idiot, i didn't close xlodgen for the file to get generated, here u go & thx for your patience (it would be wise to name those test binaries differently, so we can communicate more effectively) SSELODGen_log.txt 2.59 MB · 0 downloads Great! Good to know that test version #4 works as it is based on beta 87. Now if you could also run test version #3. I expect it to fail. Upload SSELODGen and bugreport please to conclude the troubleshooting. Link to comment Share on other sites More sharing options...
hanzabu Posted February 7, 2022 Share Posted February 7, 2022 17 minutes ago, sheson said: Great! Good to know that test version #4 works as it is based on beta 87. Now if you could also run test version #3. I expect it to fail. Upload SSELODGen and bugreport please to conclude the troubleshooting. here r results for test version #3 it did fail and rather quickly compared to the others bugreport.txt SSELODGen_log.txt Link to comment Share on other sites More sharing options...
sheson Posted February 7, 2022 Author Share Posted February 7, 2022 11 minutes ago, hanzabu said: here r results for test version #3 it did fail and rather quickly compared to the others bugreport.txt 109.11 kB · 0 downloads SSELODGen_log.txt 703.49 kB · 0 downloads Thanks for all the help. That's all I need. Keep using the last version (#4) that worked. Link to comment Share on other sites More sharing options...
myztikrice Posted February 12, 2022 Share Posted February 12, 2022 Where can we see the changelog for xLODGen? 1 Link to comment Share on other sites More sharing options...
sheson Posted February 12, 2022 Author Share Posted February 12, 2022 6 hours ago, myztikrice said: Where can we see the changelog for xLODGen? On the xEdit discord. Link to comment Share on other sites More sharing options...
Mephitic Posted February 12, 2022 Share Posted February 12, 2022 (edited) Beta 88 crash. Fortunately I have 86 still archived. No problems with that version - all else identical. bugreport.txtLODGen_log.txt No SSELODGen_log.txt was created. I assume that is because the window closed itself - I didn't get the chance. Edited February 12, 2022 by Mephitic Link to comment Share on other sites More sharing options...
sheson Posted February 13, 2022 Author Share Posted February 13, 2022 2 hours ago, Mephitic said: Beta 88 crash. Fortunately I have 86 still archived. No problems with that version - all else identical. bugreport.txt 128.5 kB · 2 downloads LODGen_log.txt 51.37 kB · 1 download No SSELODGen_log.txt was created. I assume that is because the window closed itself - I didn't get the chance. Do not generate into any mod manager folders, especially not into active mod folders while the mod manager is running. Generate into a dedicated output folder outside of game and mod manager folders. The install as a mod. If xEdit/xLODgen closes "itself" it writes the log file. If it is prematurely terminated by the OS then it can't do that. No need to upload the LODGen log from the meshes generation if there does not relate to the problem. Check if the error is repeatable. Then check with this test version. If the error is not happening consistently try to generate several times if possible. Link to comment Share on other sites More sharing options...
Mephitic Posted February 13, 2022 Share Posted February 13, 2022 (edited) 2 hours ago, sheson said: Do not generate into any mod manager folders, especially not into active mod folders while the mod manager is running. Generate into a dedicated output folder outside of game and mod manager folders. The install as a mod. If xEdit/xLODgen closes "itself" it writes the log file. If it is prematurely terminated by the OS then it can't do that. No need to upload the LODGen log from the meshes generation if there does not relate to the problem. Check if the error is repeatable. Then check with this test version. If the error is not happening consistently try to generate several times if possible. Moving the output destination to a dedicated directory outside the mod manager's sphere of influence did not improve the situation, the program still crashed. The OS must have closed it because a progress bar briefly appeared with a message to the effect of "Stand by a moment" then the window disappeared and no SSELODGen_log.txt was created. I tried the test version and that did complete successfully. Thank you for your help and advice. Edited February 13, 2022 by Mephitic Link to comment Share on other sites More sharing options...
sheson Posted February 13, 2022 Author Share Posted February 13, 2022 4 hours ago, Mephitic said: Moving the output destination to a dedicated directory outside the mod manager's sphere of influence did not improve the situation, the program still crashed. The OS must have closed it because a progress bar briefly appeared with a message to the effect of "Stand by a moment" then the window disappeared and no SSELODGen_log.txt was created. I tried the test version and that did complete successfully. Thank you for your help and advice. Thanks for testing. Uploaded as beta 89 Link to comment Share on other sites More sharing options...
Zanderat Posted February 14, 2022 Share Posted February 14, 2022 (edited) How long should generating occlusion.esp take? It's up over two and a half hours at this point (for a minimal load order, no new worlds, etc.) I don't recall it ever taking this long before. Thanks. edit: it seems to have woken up. When it finishes I will post the total overall time, if for other reason so that others can compare. Edited February 14, 2022 by Zanderat Link to comment Share on other sites More sharing options...
sheson Posted February 14, 2022 Author Share Posted February 14, 2022 21 minutes ago, Zanderat said: How long should generating occlusion.esp take? It's up over two and a half hours at this point (for a minimal load order, no new worlds, etc.) I don't recall it ever taking this long before. Thanks. edit: it seems to have woken up. When it finishes I will post the total overall time, if for other reason so that others can compare. Impossible to answer. Link to comment Share on other sites More sharing options...
nognow Posted February 19, 2022 Share Posted February 19, 2022 I started getting this error message with the new version 90, it wasn't like that in the previous version I used (85). Fallout New Vegas, via MO2. Latest Microsoft Visual C++ Redistributable, antivirus turned off. [00:00] [NVDLC02ZionCanyon] Generating Object LOD [00:01] [NVDLC02ZionCanyon] No options file found: C:\Games\FNVLODGen\Edit Scripts\FNVLODGen_HonestHearts_NVDLC02ZionCanyon_Options.txt [00:01] [NVDLC02ZionCanyon] Saving LODGen data: C:\Games\FNVLODGen\Edit Scripts\LODGen.txt [00:01] [NVDLC02ZionCanyon] Building LOD textures atlas: C:\Games\FNVLODGen\Output\textures\landscape\lod\NVDLC02ZionCanyon\Blocks\NVDLC02ZionCanyon.Buildings.dds with 70 textures [00:01] [NVDLC02ZionCanyon] Objects LOD generation error: Error while loading images from memory 000000006C420050 (5570688 Bytes) (file format: dds). Exception Message: Integer overflow [00:01] LOD generation complete FNVLODGen_log.txt Link to comment Share on other sites More sharing options...
sheson Posted February 19, 2022 Author Share Posted February 19, 2022 1 hour ago, nognow said: I started getting this error message with the new version 90, it wasn't like that in the previous version I used (85). Fallout New Vegas, via MO2. Latest Microsoft Visual C++ Redistributable, antivirus turned off. [00:00] [NVDLC02ZionCanyon] Generating Object LOD [00:01] [NVDLC02ZionCanyon] No options file found: C:\Games\FNVLODGen\Edit Scripts\FNVLODGen_HonestHearts_NVDLC02ZionCanyon_Options.txt [00:01] [NVDLC02ZionCanyon] Saving LODGen data: C:\Games\FNVLODGen\Edit Scripts\LODGen.txt [00:01] [NVDLC02ZionCanyon] Building LOD textures atlas: C:\Games\FNVLODGen\Output\textures\landscape\lod\NVDLC02ZionCanyon\Blocks\NVDLC02ZionCanyon.Buildings.dds with 70 textures [00:01] [NVDLC02ZionCanyon] Objects LOD generation error: Error while loading images from memory 000000006C420050 (5570688 Bytes) (file format: dds). Exception Message: Integer overflow [00:01] LOD generation complete FNVLODGen_log.txt 1.75 MB · 0 downloads Check if there is a bugreport.txt. Upload it if it exists. 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