xcal68
-
Posts
23 -
Joined
-
Last visited
Recent Profile Visitors
232 profile views
xcal68's Achievements
Thane (4/12)
0
Reputation
-
That fixed my issue. Multiple files were reported in the console, but only interrupted generation one time. Thanks. I'll report the issues to the mod authors.
-
It's the error that tells you there's a circular reference in a _swap.ini file and to "permanently" remove all references to Dyndolod. I don't actually need troubleshooting help. Did you still need logs? I can consider it when I'm home, if you do.
-
More of a feature request: Would it be possible to make it so all the swap errors are found at once, instead of stopping the entire process when it finds one? Run the program... stops on a circular swap... run the program... stops on a circular swap and over and over. I have tons of _swap.ini.
-
That seems to have resolved it for me, too. It started up and I was able to move forward. Running fine in the background as I type this. Edit - Finished successfully.
-
I get the UAC popup. I click 'yes'. Command window opens/closes quickly, since there's no work to do.
-
Getting error with 153: [Window Title] TexGen [Main Instruction] Executing Texconvx64.exe returned error code C0000005. [Content] "C:\Games\Skyrim Modding Tools\DynDOLOD\Edit Scripts\Texconvx64.exe" Click on this link for additional explanations and help for this message For qualified help and advice or to report a problem make a post on the official DynDOLOD support forum. [Exit TexGen] [Footer] Online Help | Support Forum | Copy message to clipboard I have gone through The error does not happen in 152. Logs can be found here: https://drive.google.com/file/d/1QQ49lreoIii-sMMVrcGttQzgKoLgKnuN/view?usp=sharing
-
Sorry, I know this is old, but I'm having troubles searching. Can you confirm it is still supposed to work like this? I'm using the latest release (130), and the occlusion plugin isn't consistently doing this. I rebuilt from scratch earlier today. When I started testing/playing, I noticed a water seam. Looking in xedit, the occlusion plugin had taken an unexpected xcwt-water record 35 times. Edit - it looks like the occlusion plugin is taking whatever water record dyndolod.esm has, so maybe it's that which is not gathering the correct 'last' record? Edit - Looks like a few xlcn-location and some editor id records, as well. Another edit - Not sure if these are helpful, but here's the plugin and I think the logs you want: Click (Just realized the plugin will be pointless unless you have the same load order haha...)
-
You recently install Skyrim Extended Cut - Saints and Seducers? It happens to me, too, but only with that mod enabled. I tested with only that mod enabled, too. Edit - Addressed here:
-
TexGen fixed in 102 - trunks are back. Thanks.
-
Just confirming the same issue with texgen as quochunganhphu. I'll see about logs if I have time later. Just confirming for now.
-
Ah cool, thanks. So nothing for me to be concerned with, which I'm guessing is why no log haha...I'm probably 1 of only a couple who noticed.
-
Speaking of logs heh... Was 79 released twice? Wondering the difference between the two, as I currently am creating LODs with the first one.
-
Can Not Copy Resource / The system cannot find the path specified
xcal68 replied to ravenRpg38's question in DynDOLOD & xLODGen Support
Ignore me. -
Thanks for the update. Alpha 35 resolved both issues for me.
-
Just reporting an issue with the DynDOLOD 3, Alpha 34, related to the UI. When adding a new rule (right click > insert) in the "Mesh and Reference rules" section of the Advanced window, the last line gets pushed down (as expected), but you cannot scroll down to see it. Adding further rules continues to push the last line further down, out of sight. At first I thought it was removing or overwriting the rule that you happen to be right clicking on, but if you remove a rule, it brings the hidden line back up and it's viewable again. This does not happen in Alpha 33. As a side note, I'm also getting the "Item not found" error that RockGodOne and verrik are reporting, which was introduced (for me) in Alpha 34. This issue is not present when generating LODs in Alpha 33 (which I've reverted back to for now). I'll consider posting logs for that, if I get a chance, but for now I really just wanted to mention the UI thing.
