sheson Posted June 2, 2023 Author Share Posted June 2, 2023 32 minutes ago, Wulfga said: Alright, I'm just trying to get through this while I still even want to play Skyrim again. I've done this before on v2, this is my first time with v3. I've been Googling and RTFM'ing this for 3 days and I've made what might be progress but doesn't really feel like it yet. I'm following STEP5 religiously. Step Skyrim Special Edition Guide (stepmodifications.org) Running xTexgen64 yields the attached logs. It normally gets to creating textures and simply ends abruptly without error logs or codes. I've been able to capture a couple though, so I'm hoping I can get through posting this successfully. Attached Event Viewer logs also. Attached my modlist; I'm sure I've botched something, but posting a heat log is less anxiety provoking at work than it is here, so please go easy on me. Reasonably certain I've followed the directions here. I'm past the LODgen step, which went much better after I read the manual a second time and switched to the STEP guide. I gave up completely on ever having grass, the instructions there were more than I was interested in diving into when I can't get through it without. Crash happens right there at the memory drop-off. Running from commandline as suggested in other posts launches the app correctly with no errors. I do have AV, but I went overboard potentially and created a dozen exceptions for everything here. I have PHI/CBI on this box, kinda need at least a basic security layer. It's never bothered anything else but mentioning just in case. I've seen these come up while spending over a day reading the other threads: NVIDIA bits: Please tell me what I've left out, and how I can get through this. Thanks in advance. bugreport2jun23.txt 195.67 kB · 1 download apploginfo.txt 3.73 kB · 1 download applogerror.txt 2.45 kB · 0 downloads modlist.xlsx 29.9 kB · 0 downloads Moved to the DynDOLOD 3 Alpha thread. See the first post or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which bugreport.txt and debug log to also upload. The debug log gets replaced with every session, so in case it is still valid to the error, save/upload it it right away. Add RenderSingle=1 under [TexGen] in H:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini and check if it makes a difference. It helped other people one or two thread pages back that also had an exception in the NVIDIA driver nvoglv64.dll Link to comment Share on other sites More sharing options...
Wulfga Posted June 2, 2023 Share Posted June 2, 2023 ..\DynDOLOD\bugreport.txt Doesn't exist. ..\DynDOLOD\Logs\[DynDOLOD|TexGen_SSE_log.txt (truncate large log files to the entire last meaningful generation beginning with the log message "... starting session ..." ) Had left everything in there since it hadn't crashed the same way twice. Followed exact instructions. Yes, I put a date at the end, let's overlook that. ..\DynDOLOD\Logs\[DynDOLOD|TexGen_SSE_Debug_log.txt (always upload entire debug log) Did that. Doing it again. If issue involves LODGen upload/paste ..\DynDOLOD\Logs\LODGen_[TES5|ENDERAL|SSE|TES5VR|ENDERALSE]_[Worldspace]_log.txt (Doesn't exist yet) Attached my .ini in case there's something egregiously wrong in there. Did what you said, I still get to here (which is farther than I get probably 60% of the time). [00:57] Creating textures [01:15] Creating texture H:\Modding\Tools\DynDOLOD\TexGen_Output\Textures\dlc01\lod\dlc01icewalllod.dds with H:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\Render\Skyrim\Objects\dlc01\lod\dlc01icewalllod.nif I can hear the fans spin up a little, then it stalls out and eventually the screen disappears. It took longer to crash this time but I never got past this line. the TexGen_SSE_log (6-2-2023).txt is the run with your ini edit in place. TexGen_SSE.INI I know this is irritating on both ends. I appreciate you even responding at all, and I've done what I can to minimize how irritating my posts are. I could not handle 504 pages of bug reports and questions- I would lose my mind... so, yeah, thanks. TexGen_SSE_Debug_log.txt TexGen_SSE_log (6-2-2023).txt Link to comment Share on other sites More sharing options...
sheson Posted June 2, 2023 Author Share Posted June 2, 2023 19 minutes ago, Wulfga said: Did what you said, I still get to here (which is farther than I get probably 60% of the time). [00:57] Creating textures [01:15] Creating texture H:\Modding\Tools\DynDOLOD\TexGen_Output\Textures\dlc01\lod\dlc01icewalllod.dds with H:\Modding\Tools\DynDOLOD\Edit Scripts\DynDOLOD\Render\Skyrim\Objects\dlc01\lod\dlc01icewalllod.nif If you got to "there" why is that not the last line of the logs you uploaded? The log and debug log show it started to gather base records for billboards (uses CPU) and did not start to render a texture yet. 19 minutes ago, Wulfga said: I can hear the fans spin up a little, then it stalls out and eventually the screen disappears. It took longer to crash this time but I never got past this line. the TexGen_SSE_log (6-2-2023).txt is the run with your ini edit in place. You probably have a hardware, driver, overclocking, BIOS setting, OS issue. TexGen using Open GL API or Tecconv using DirectX API is not supposed to be able cause this no matter what they do. What is reported in the Windows event log? Link to comment Share on other sites More sharing options...
Ravenyan Posted June 2, 2023 Share Posted June 2, 2023 TexGen stuck forever any idea on why this happening? TexGen_SSE_log.txt Link to comment Share on other sites More sharing options...
sheson Posted June 2, 2023 Author Share Posted June 2, 2023 On 6/2/2023 at 5:49 PM, Ravenyan said: TexGen stuck forever any idea on why this happening? TexGen_SSE_log.txt 151.53 kB · 1 download See the first post or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which debug log to also upload. Add LockTexconv=1 under [TexGen] in D:\Mods\Skyrim\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.INI and see if that changes anything. It helped users with the same problem a couple pages back where TexGen seems to be stuck or stopped. Link to comment Share on other sites More sharing options...
Wulfga Posted June 2, 2023 Share Posted June 2, 2023 Quote If you got to "there" why is that not the last line of the logs you uploaded? The log and debug log show it started to gather base records for billboards (uses CPU) and did not start to render a texture yet. I guess I did a bad job explaining that part. That window with the scolling text... if that's your debug log, it doesn't save at all when it just errors out and ends abruptly. I only get it to close normally and create the logs I've attached one out of every... maybe 9 attempts. I'm in the hundreds probably. I have removed overclocking from the CPU, yesterday I think. My graphics card memory is overclocked a little but extremely stable. Attached CPU-Z, because running out of ideas. Attached the only additional log file that survived long enough in that temp folder to grab it. Error log from Event Viewer: Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33 Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9 Exception code: 0xc0000005 Fault offset: 0x0000000001550f2a Faulting process id: 0x0x5484 Faulting application start time: 0x0x1D995612705F484 Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll Report Id: fabd6cbe-c4a7-44ed-9ac3-f7166bb8d365 Faulting package full name: Faulting package-relative application ID: Info log from event: Fault bucket 1897463078308581007, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: TexGenx64.exe P2: 3.0.0.128 P3: 646a6e33 P4: nvoglv64.dll P5: 31.0.15.3598 P6: 646dfba9 P7: c0000005 P8: 0000000001550f2a P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.190bcaf4-91c6-4d6b-aaa4-a1c764e90a88.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.143f5221-3e03-4c96-b9e7-e10fa80b639e.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e5c8fd98-60a4-4bee-9a87-9c3566ef8a34.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.165cd335-cfd1-4050-92c5-b7d3037f165d.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.43564062-c08f-4f02-b8e7-7a71c81d2a0d.tmp.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_TexGenx64.exe_6f6a94369d9c1185cd99bbdf7a6bac316c9e971e_5b7d448d_8f98ccab-d9b2-4a22-81d8-9332586eff8a Analysis symbol: Rechecking for solution: 0 Report Id: fabd6cbe-c4a7-44ed-9ac3-f7166bb8d365 Report Status: 268435456 Hashed bucket: 1dd0260b7426beeeea55249dd5008e8f Cab Guid: 0 WER.297e2947-b1c3-4f61-b940-af707c587f6e.tmp.WERInternalMetadata.xml GHOST-CPUZ.txt Link to comment Share on other sites More sharing options...
sheson Posted June 2, 2023 Author Share Posted June 2, 2023 10 minutes ago, Wulfga said: I guess I did a bad job explaining that part. That window with the scolling text... if that's your debug log, it doesn't save at all when it just errors out and ends abruptly. I only get it to close normally and create the logs I've attached one out of every... maybe 9 attempts. I'm in the hundreds probably. I have removed overclocking from the CPU, yesterday I think. My graphics card memory is overclocked a little but extremely stable. Attached CPU-Z, because running out of ideas. Attached the only additional log file that survived long enough in that temp folder to grab it. Error log from Event Viewer: Faulting application name: TexGenx64.exe, version: 3.0.0.128, time stamp: 0x646a6e33 Faulting module name: nvoglv64.dll, version: 31.0.15.3598, time stamp: 0x646dfba9 Exception code: 0xc0000005 Fault offset: 0x0000000001550f2a Faulting process id: 0x0x5484 Faulting application start time: 0x0x1D995612705F484 Faulting application path: H:\Modding\Tools\DynDOLOD\TexGenx64.exe Faulting module path: C:\Windows\System32\DriverStore\FileRepository\nv_dispi.inf_amd64_3c2bd4a1ec6d228e\nvoglv64.dll Report Id: fabd6cbe-c4a7-44ed-9ac3-f7166bb8d365 Faulting package full name: Faulting package-relative application ID: Info log from event: Fault bucket 1897463078308581007, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: TexGenx64.exe P2: 3.0.0.128 P3: 646a6e33 P4: nvoglv64.dll P5: 31.0.15.3598 P6: 646dfba9 P7: c0000005 P8: 0000000001550f2a P9: P10: Attached files: \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.190bcaf4-91c6-4d6b-aaa4-a1c764e90a88.tmp.dmp \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.143f5221-3e03-4c96-b9e7-e10fa80b639e.tmp.WERInternalMetadata.xml \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.e5c8fd98-60a4-4bee-9a87-9c3566ef8a34.tmp.csv \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.165cd335-cfd1-4050-92c5-b7d3037f165d.tmp.txt \\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER.43564062-c08f-4f02-b8e7-7a71c81d2a0d.tmp.xml These files may be available here: \\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_TexGenx64.exe_6f6a94369d9c1185cd99bbdf7a6bac316c9e971e_5b7d448d_8f98ccab-d9b2-4a22-81d8-9332586eff8a Analysis symbol: Rechecking for solution: 0 Report Id: fabd6cbe-c4a7-44ed-9ac3-f7166bb8d365 Report Status: 268435456 Hashed bucket: 1dd0260b7426beeeea55249dd5008e8f Cab Guid: 0 WER.297e2947-b1c3-4f61-b940-af707c587f6e.tmp.WERInternalMetadata.xml 6.53 kB · 1 download GHOST-CPUZ.txt 248.21 kB · 1 download The log and debug log are both saved when the program is closed. Just send the signal to close once (e.g. clicking the X top right) and then wait a few seconds so the program can save the logs and shutdown properly. As explained in the already linked page https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs, use the RealTimeLog=1 INI setting in case there are no logs or debug logs because the tool is being terminated prematurely. If the screen goes black, then there is probably a hardware (including power supply), driver, overclocking, BIO setting, OS issue. Link to comment Share on other sites More sharing options...
Ravenyan Posted June 2, 2023 Share Posted June 2, 2023 Well I tried but it didn't work unfortunately https://ufile.io/f/eymej Link to comment Share on other sites More sharing options...
sheson Posted June 2, 2023 Author Share Posted June 2, 2023 2 minutes ago, Ravenyan said: Well I tried but it didn't work unfortunately https://ufile.io/f/eymej Remove the "Add" and space in front of the setting LockTexconv=1. It needs to look similar to all the other settings. Link to comment Share on other sites More sharing options...
Ravenyan Posted June 2, 2023 Share Posted June 2, 2023 It worked! Thank you much love <3 Link to comment Share on other sites More sharing options...
runjimmyrun1 Posted June 2, 2023 Share Posted June 2, 2023 Hey! I am new to DynDOLOD, and I am having difficulty generating the lod. I am using the Alpha 3 version. I downloaded and installed all the the required files, followed the instructions from GamerPoet's tutorial, including prioritizing my load order the way that was instructed, generated Texgen, zipped and saved, moved zip folder into Vortex and installed and activated it, where nothing overrides it, and I get through the part of the lod gen where I choose the lands and settings (medium), but it always crashes about 3 minutes in. It's always around LC's Feudal Keep, so I disabled that, to see if it would make a difference, and it still crashed at about the 2:30-3 minute mark of trying. I tried around 5 or 6 times. Am I missing something? Suggestions? Link to comment Share on other sites More sharing options...
sheson Posted June 2, 2023 Author Share Posted June 2, 2023 7 minutes ago, runjimmyrun1 said: Hey! I am new to DynDOLOD, and I am having difficulty generating the lod. I am using the Alpha 3 version. I downloaded and installed all the the required files, followed the instructions from GamerPoet's tutorial, including prioritizing my load order the way that was instructed, generated Texgen, zipped and saved, moved zip folder into Vortex and installed and activated it, where nothing overrides it, and I get through the part of the lod gen where I choose the lands and settings (medium), but it always crashes about 3 minutes in. It's always around LC's Feudal Keep, so I disabled that, to see if it would make a difference, and it still crashed at about the 2:30-3 minute mark of trying. I tried around 5 or 6 times. Am I missing something? Suggestions? Read the first post of this DynDOLOD 3 Alpha thread which log, debug log and bugreport.txt to upload when making posts. Also see https://dyndolod.info/Official-DynDOLOD-Support-Forum Link to comment Share on other sites More sharing options...
Sulazarg Posted June 3, 2023 Share Posted June 3, 2023 On 5/31/2023 at 12:56 PM, sheson said: Read the first post which log and debug log to upload when making posts. Also see https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#In-Game-Screenshots how to take screenshots with information. See answers for https://dyndolod.info/FAQ "Out of place or floating objects" I understand that the Dyndolod overlaps dynamic objects (which change during the execution of quests, for example burned houses in Helgen). Textures that are superimposed on objects are not tangible. Link to comment Share on other sites More sharing options...
sheson Posted June 3, 2023 Author Share Posted June 3, 2023 1 hour ago, Sulazarg said: I understand that the Dyndolod overlaps dynamic objects (which change during the execution of quests, for example burned houses in Helgen). Textures that are superimposed on objects are not tangible. DynDOLOD adds dynamic LOD for dynamic full models. The dynamic LOD should only show outside the active cells, when the full model is not shown anymore. https://dyndolod.info/Official-DynDOLOD-Support-Forum Report the actual problem or error message instead of making assumptions or asking leading questions. Read the explanations and tips below, especially about what information and logs to provide and how. Link to comment Share on other sites More sharing options...
S3R Posted June 5, 2023 Share Posted June 5, 2023 I am getting this error when I try to run DynDOLOD: [00:15] Processing 18533 base records for 3267 object LOD and 384 dynamic LOD models [00:50] <Warning: Property not found ccmtysse001_crusaderglobalshrines in scripts\ccmtysse001_shrinecounter.pex ccmtysse001-knightsofthenine.esl ccMTYSSE001_ShrineActivator "Shrine of Akatosh" [ACTI:FE00D854]> [00:50] <Warning: Property not found targetvalue in scripts\ccmtysse001_shrinecounter.pex ccmtysse001-knightsofthenine.esl ccMTYSSE001_ShrineActivator "Shrine of Akatosh" [ACTI:FE00D854]> [00:50] <Warning: Property not found dlcdwarvenpuzzledungeonhorsecompletemessage in scripts\dlcdwarvenpuzzle_rebuildhorsescript.pex cctwbsse001-puzzledungeon.esm ccTWBSSE001_DwarvenHorseTorsoActivator "Broken Dwarven Horse" [ACTI:0700087F]> [00:50] <Warning: Property not found dlcdwarvenpuzzledungeonhorsemessage in scripts\dlcdwarvenpuzzle_rebuildhorsescript.pex cctwbsse001-puzzledungeon.esm ccTWBSSE001_DwarvenHorseTorsoActivator "Broken Dwarven Horse" [ACTI:0700087F]> [00:51] <Warning: Property not found crystalenableref in scripts\ccbgssse008_vaultopenscript.pex ccbgssse008-wraithguard.esl ccBGSSSE008_WraithguardCrystal "Dwarven Pedestal" [ACTI:FE019814]> [00:51] <Warning: Property not found mylocationdiscovered in scripts\ccbgssse031_fasttravelflagscript.pex ccbgssse031-advcyrus.esm ccBGSSSE031_FastTravel02 "Windhelm" [ACTI:0A0341CB]> [00:51] <Warning: Property not found myquest in scripts\ccbgssse031_fasttravelflagscript.pex ccbgssse031-advcyrus.esm ccBGSSSE031_FastTravel02 "Windhelm" [ACTI:0A0341CB]> [00:51] <Warning: Property not found nocheckneeded in scripts\ccbgssse031_fasttravelflagscript.pex ccbgssse031-advcyrus.esm ccBGSSSE031_FastTravel02 "Windhelm" [ACTI:0A0341CB]> [00:51] <Warning: Property not found mylocationdiscovered in scripts\ccbgssse031_fasttravelflagscript.pex ccbgssse031-advcyrus.esm ccBGSSSE031_FastTravel03 "Dawnstar" [ACTI:0A0341D4]> Can anyone help me with this? It's my first time doing something like this and I only have the official patch installed as a mod. 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