sheson
-
Posts
13,181 -
Joined
-
Last visited
-
Days Won
431
Everything posted by sheson
-
Upload the debug log for that please. Doublecheck if there is a bugreport.txt in the same folder as DynDOLOD.exe. Check if there is a zip file in ..\DynDOLOD\Edit Scripts\Export\*.zip
-
I have two different ESM to test to see if this can be still narrowed down to something more concrete. One is 963kb (9860099 bytes) while the other is 929kb (951422 bytes). Let me know if either makes a difference or not. Test the plugins with that second to last papyrus test script the last toml where things happen later than "usual". DynDOLOD.esm DynDOLOD.esm
-
It is normal that you can enter text into the messages tab of xEdit/DynDOLOD. As far as I can tell you are using the normal release version of Windows 11 and not some beta/preview, so it is most likely not the problem. Check if there is a bugreport.txt in the same folder as the DynDOLOD exe. Add the command line argument -autoexit to the arguments starting DynDOLOD to see if it automatically saves and zips without waiting for the prompt/input.
-
The is the terrain underside mesh. Increase object/terrain LOD distances and/or lower the underside mesh, so it does not peak through. https://dyndolod.info/Help/Terrain-Underside#Troubleshooting
-
The task manager shows DynDOLOD working and two LODGen still running as well. DynDOLOD is waiting for them to finish. Open up the LODGen windows to see what they are working on.
-
Moved to the DynDOLOD 3 Alpha thread. As explained on the first post use search to find similar questions and answers. See https://stepmodifications.org/forum/topic/17510-dyndolod-300-alpha-105/?do=findComment&comment=265437 and set the object bounds to 0 as explained in the replies.
-
Autocorrect... I meant tfc to fly closer to the spot. LOD may start to rapidly cycle through LOD levels making things weird though. Once close type tll to disable all LOD to see if something else is there that remains.
-
The first step would be to determine what the bright spot actually is. Terrain or object LOD or something else and to compare it to vanilla LOD / no xLODGen output. Get closer. Make use of TLC.
-
The worldspace has no temporary cells, so that is probably why the bounds are undefined. Not sure if this is a CK bug or just a wild edit or something undefined and if/what the consequences are. Next version will just continue.
-
Yes, replace both the "default" and "min"
-
For time being, set the bounds to valid numbers like 0.
-
Run this test version of TexGen https://mega.nz/file/xEJBTarA#zQPw9J9g4VZqnRlnTevplIrnaHyaZqtsvL3rdIBsnbk It should mention the worldspace the error happens in. Then check the Object Bounds of all plugins modifying that worldpace.
-
Yes, it is possible that DynDOLOD has a more information when it encounters the same problem.
-
https://dyndolod.info/Installation-Instructions Use 7-Zip to unpack the DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory ... Do not unpack into a folder still containing older versions. There seems to be a worldspace with weird wordspace bounds https://dyndolod.info/Messages/Worldspace-Bounds. Unfortunately the log does not hint which one. You might spot it if you check the worldspace records in xEdit. Next version will try to print which worldspace has the issue. The error does not affect the TexGen output anymore, so you can use it. What happens when you run DynDOLOD? There should be a similar error?
-
It makes sense to me. Thanks for reporting.
-
Looks like a race condition. Does it run through or mention a different texture when you try again?
-
Why do you keep posting screenshots of TexGen that shows the prompt? It seems to be working. When the DynDOLOD messages window shows like this, it does not react to mouse or keyboard? Can you move the scroll bar down? Is there any CPU usage in the task manager? After starting DynDOLOD, either the wizard or advanced options window shows. When you click cancel, there will be a prompt to asking to exit, check log or restart. Does that work? See what happens if you do not select to generate Occlusion.
-
I have no idea what the screenshot is supposed to be showing "wrong" since there is no comparison that shows how it is "right". Do you mean the snowy peak? If something is transparent it will show the sky or other stuff behind it. If there is a terrain underside mesh, increase object/terrain LOD distances and/or lower it, so it does not peak through. LOD meshes and textures are always the same and do not affect how weathers or lighting works.
-
Do you get the Exit, check log, restart prompt when using the cancel button on the wizard/advanced window? See if there is anything different after deleting the Themes folder and running DynDOLOD then.
-
The TexGen log seems to be from a session after the problem was fixed. I was interested in the logs where you had a problem and claimed it was the same as you have now in DynDOLOD. The DynDOLOD log again shows that the save message was sent to the OS to make the prompt. Maybe the OS decided to hide the save prompt behind the messages log window or off screen even though it is supposed to be always in front of the messages window. If not other windows has focus you could try just hitting enter so it selects the "save" option. You should be able to to minimize/maximize or move the message log window - if the buttons top right or the cow icon top left do not work, try shift + right click on the task bar icon to get menu with the minimize/maximize. Otherwise try alt tab between different programs. If all fails, use the task bar right click "show desktop" to minimize all windows and then click DynDOLOD in the task bar again to maximize it. If the prompt is still not visible, right click task bar again and choose one of cascade windows/show windows stacked/show windows side by side. If the save prompt exists anywhere it should show up eventually.
-
1) do not post screenshots/information from other people that do not show your problem. We know how things are supposed to look. 2) Do not install the game into special Windows folder like Program Files x86 to avoid issues with UAC, antivir, etc. What problems did you have in TexGen that you fixed? Upload the log and debug log as explained on the first post. There must have been an error that actually stopped the program with a proper message? The summary only shows if there are certain error or warnings that need fixing or review or for reverse checking in case a problem is noticed in the game.
-
1) How do you make a screenshot of the prompt if it does not show up? If it does not show up, how did the debug log record "Save DynDOLOD plugins, save plugins and zip output, exit DynDOLOD without saving, check the log? If 'Check log' is selected, the DynDOLOD plugins will be saved and the log can be checked." and then trying to save the plugins? 2) The "game" does not mean DynDOLOD, it means Skyrim Special Edition. 5) Wait. Check if it uses CPU in task manager.
-
The debug log shows save message prompt showed and then some problems while saving. Which means the program just stopped afterwards same as "check logs" and waits for user to close. Are you saying when you try again it now does not reach the prompt anymore and even stops before that? Do not install the game into special Windows folders like Program Files x86 to avoid issues with UAC, antivir etc. Restart Windows. Delete both the output and the log folder (or delete entire DynDOLOD folder and unpack it again anew) and run again. If problem persists upload new logs and double check the same folder where DynDOLOD exe is for a bugreport.txt. Then delete log folder again and test if there is anything different generating without Seasons checked. If error still persists upload those log files as well. In case it does not close itself because of a problem, only click the X top right once and then wait a bit, so it has time to save the log files.
-
Use a file service for large log files as explained on the first post and in my signature. It seems likely that something blocks files access, which prevents the xEdit code from completing saving the plugins. If the user aborts something by exiting, it is normal for the log to show that in the log.
-
Upload the log and debug log and bugreport.txt if it exists as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Use the "Copy message to clipboard" and paste the text instead of making screenshots as explained at https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages Disable the realtimelog and try again. In case there still is not proper unresolved form ID message, upload new log, debug, bugreport.txt if it exists. https://dyndolod.info/Generation-Instructions#Prerequisites Finalize the load order. Install mods and their requirements. Sort and resolve conflicts. Clean and error check the load order with xEdit. Clean every plugin that LOOT suggests to clean ...
