sheson
-
Posts
13,180 -
Joined
-
Last visited
-
Days Won
431
Everything posted by sheson
-
Can you try to bring the LODGen.exe command prompt window to the front to see if it shows any more than info than its log?
-
DynDOLOD builds on top of xLODGen to make LOD generation easier by automating things, so it can also automates Occlusion generation settings. Good. I could not replicate any problems with All for vanilla + DynDOLOD High. That is kind of expected of course, since something else must be at play as well. We will probably find out eventually in the future if it happens for more people.
-
The pastebin doesn't seem to be public.
-
That because DynDOLOD uses mode -Flat +Border. Try the same when generation Occlusion with xLODGen. No need to generate it for all those cell that can not be reached.
-
Just truncate the log files to the last generation with the error, then you should be able to upload it here, or use https://pastebin.com/ for example.
-
I would be interested what happens when you let DynDOLOD generate the TVDT data instead. You could do a test from scratch just with that worldspace. It's a bit odd how updated cell records in Solstheim are supposed to affect fast travel in Tamriel. You have Engine Fixes installed that by default warns about too many ref handles? Not that updated cell records in Occlusion.esp should have any effect on that in particular.
-
Generate occlusion for that worldspace only without DynDOLOD in the load order. If it still happens then, generate Occlusion for that worldspace only without Bashed Patch. If it still happens then, upload Occlusion, assuming it only has plugins which are no patches generated by tools as masters. Otherwise continue to remove patches one by one, so that it only has master I can download from Nexus.
-
The null reference is fine (you will also find in in Skryim.esm, the most left plugin) and not causing the exception. The line of the assert is form the source code. It tells me where to look. It basically tells us that something is going unexpectedly wrong with the data, hence me asking you to check / screenshot the records. Let me know if the same happens when using DynDOLOD.exe
-
Dynamic Distant Objects LOD - DynDOLOD for Skyrim and Enderal 2.98
sheson replied to sheson's topic in DynDOLOD & xLODGen
Exception in unit process line 87: Can not copy [REFR:02013CD0] (places PlaneMarker [sTAT:00000017] in GRUP Cell Temporary Children of DLC1VampireCastleExterior06 [CELL:000018DE] (in Tamriel "Skyrim" [WRLD:0000003C] at -43,37)) from Dawnguard.esm into DynDOLOD.esp Assertion failure (C:\Delphi\projects\DynDOLOD\wbImplementation.pas, line 13947)Check log lines above the exception for additional hints. Check the FAQ and search official forum for those errors. FAQ: DynDOLOD.exe: Can not copy xxxx from xxxx.esp into xxx.espA: Often caused by a broken bashed patch. Use a newer Wrye Bash version to create the patch or do not use the merge patches option. A: There is a plugin in the load order with errors. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help. https://forum.step-project.com/topic/14114-error-can-not-copy-refr000b7365-places-planemarker-stat00000017-in-grup-cell-temporary-children-of-solitudeorigin-cell00037ee9-in-solitudehttps://forum.step-project.com/topic/14205-can-not-copy-refr000a1ff7-places-farmlumbermill01waterwheel02/https://forum.step-project.com/topic/14136-can-not-copy-refr0b0259dc-places-farmlumbermill01waterwheel02/https://forum.step-project.com/topic/14127-can-not-copy-refr0c16904c-places-spatiowall01-stat00057a17-in-grup-cell-persistent-children-of-cell00000d74 -
1) Make a backup. 3) With xEdit remove worldspace from Occlusion.esp at a time. 4) If the problem still happens go to 1) 5) If the problem went away, restore backup and goto 3) removing a different worldspace In the end you hopefully have only one worldspace left. Which one? Which mod adds it?
-
It all looks fine. You could do a test run without the plugin, then we will be sure it is not it and can look at other things. If that doesn't change anything can try running DynDOLOD.exe instead of DynDOLODx64.exe.
-
Looks like the last plugin is MCWT_MageLightMaintenance.esp. You are using the latest version of Misc. College of Winterhold Tweaks from 24th August 2019? Everything looks fine and that plugin works here as well, so its probably not it. Can you do that screenshot again, but before taking it, right click anywhere in the right window and uncheck Hide no conflict and empty rows. There will be more stuff shown.
-
An example for a free external image hoster would be https://imgur.com/upload
-
Use a free external image hoster/file service for large files. Nothing sticks out in the error check. None of those errors should cause the issue DynDOLOD runs into. You should look into resolving the 'Error: Could not be resolved' / 'Quest Alias not found' ones.
-
No need (its impossible) to fix errors in the master files, just clean them. Just scan with xEdit for errors and see what it says for the other plugins from mods. After closing xEdit all those message are saved to a log in the same folder where xEdit is. Post it. I might spot something. Also load entire load order into xEdit, then enter 3C into the FormID field top left and hit Enter key. Unfold [+] 0000003C Tamriel Click on [+] 00000D74 Persistent Worldspace Cell to update the right window to the data for that record. Scroll to the very right to show the last plugins to overwrite the record. Post a screeshot of the entire xEdit window. I might spot something.
-
Something seems to be going very wrong. Not quite sure yet how best to troubleshoot. Everything works fine with TreeLOD=1 and High? Post which version of EVT you are using and the exact install options.
-
updating 2.69 to 2.72 and now ctd when saving
sheson replied to delweyn's question in DynDOLOD & xLODGen Support
Yes, that mods is obsolete now. Either use xLODGen or DynDOLOD to generate updated TVDT data that fixes holes in the LOD without the negative performance impact. See https://forum.step-project.com/topic/14250-skyrim-tvdt-occlusion-data/ -
Use the x64 version obviously, as Windows artificially limits max system memory to about 3.1GB for x86 applications. If you already use the x64 version, make sure to use the latest version. Reduce settings. Don't use 3D tree LOD models in LOD level 8/16. Only you can answer the question about texture sizes by testing yourself for your load order, hardware and personal preference. The TexGen manual explains how to update textures and texture atlases without running the entire process again, so testing is a matter of a couple minutes.
-
updating 2.69 to 2.72 and now ctd when saving
sheson replied to delweyn's question in DynDOLOD & xLODGen Support
The problem is very unlikely to be the DynDOLOD version used to generate the LOD mod. CTD when saving is a common issue regardless of DynDOLOD being in the load order or not. Test with a new game. Make sure to carefully follow the update procedure for existing save games. Test without DynDOLOD. Make a clean save. Consider using a save tool to remove orphaned scripts. -
Set FasterCreate=0 in DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini and run again. We might get a better error message. Check the load order for errors with xEdit.exe before generating LOD. Fix all errors. See this video for help.
-
Use the x64 version. Set a dicated output folder with -o Do not install the game / anything into Program Files x86
-
In case of Bruma missing meshes are expected, since the that mod ships is a cut version. Warnings and errors about missing meshes are printed to fix the issues. Disabling mods to not see messages is typically not a valid course of action. Get the latest version 2.72, it should not just close and instead stop with the exception message again as its supposed to. Follow the instructions from the message.
-
Not sure why you are disabling mods. There is no such instruction in the TexGen manual. It will end up using the wrong source texture to generate the single object LOD textures. See if there is a DynDOLOD_SEE_log.txt file in the log folder and check its last lines for useful messages/hints.
-
I suggest to read the manuals and then test different settings to learn all about the tools to use them to their full advantage to create LOD mods as perfect as they can be. DynDOLOD has sane presets to choose from so first time users are not overwhelmed. xEdit/xLODGen is a CK replacement. No such luxury.
-
It is pointless to have in the load order. The last plugin to overwrite the CELL record wins. As I explained in the past, it is a bad idea to remove all TVDT data from all of Tamriel. No need to have worse performance in the non affected cells for no reason.
