Kvitekvist Posted December 13, 2021 Posted December 13, 2021 53 minutes ago, Kvitekvist said: Hello, SkyrimVR user herre: I just updated to latest version of Dyndo, and now it seems to require creationclub content? Required file not found: meshes\creationclub\eejsse002\architectuure\eej_towerroof.nif SkyrimVR does not have cc content, any way to get around this? Edit: never mind, this was a user error. Of course i had to update the Dyndo resource v3, not the one for SE.
KatCut Posted December 13, 2021 Posted December 13, 2021 I accidentally downloaded and installed the 2.x version of the resources. I generated texgen with that, then tried to generate dyndolod. OFC it failed and told me to install the right version. I did so. The question now is, do I need to re do texgen? Or is texgen independent of the resources mod?
sheson Posted December 13, 2021 Author Posted December 13, 2021 54 minutes ago, KatCut said: I accidentally downloaded and installed the 2.x version of the resources. I generated texgen with that, then tried to generate dyndolod. OFC it failed and told me to install the right version. I did so. The question now is, do I need to re do texgen? Or is texgen independent of the resources mod? TexGen generates LOD resources. It does not require LOD resources. If it did, it would have warned about the wrong version just like DynDOLOD.
KatCut Posted December 14, 2021 Posted December 14, 2021 7 hours ago, sheson said: TexGen generates LOD resources. It does not require LOD resources. If it did, it would have warned about the wrong version just like DynDOLOD. Thank you for the info. I got one more question tho. I deactivated my bashed patch before generating the lods. Now my occlusion data isn't forwarding my encounter zone changes by the bashed patch. Should I regen dyndolod with the bashed patch enabled or do I need to manually forward dozes many many records by hand?
soupdragon Posted December 14, 2021 Posted December 14, 2021 (edited) So I'm having issues with TextGen its either running out of memory (32bit) or freezing and crashing (64bit version) at a similar spot 32bit 64bit Tried extracting trees as loose files from BSA's winteraspen06.nif as they seem to be where its stopping, no difference https://ufile.io/jfb9h9v4 https://ufile.io/fhyads07 TexGen_SSE_log.zip ~~~~~~~~~~~~~~~~~~~~~~~~~~~ settings used incase its of any value - (n.b. not possible to copy and paste text from the window as it either crashes or theres only the option to exit) Edited December 14, 2021 by soupdragon extra info
sheson Posted December 14, 2021 Author Posted December 14, 2021 3 hours ago, soupdragon said: So I'm having issues with TextGen its either running out of memory (32bit) or freezing and crashing (64bit version) at a similar spot 32bit 64bit Tried extracting trees as loose files from BSA's winteraspen06.nif as they seem to be where its stopping, no difference https://ufile.io/jfb9h9v4 https://ufile.io/fhyads07 TexGen_SSE_log.zip 119.24 kB · 0 downloads ~~~~~~~~~~~~~~~~~~~~~~~~~~~ settings used incase its of any value - (n.b. not possible to copy and paste text from the window as it either crashes or theres only the option to exit) Always use the x64 version. There is no reason to use the x86 version unless a x86 OS is used. Upload the log, debug log and bugreport.txt if there are problems using the x64 version.
soupdragon Posted December 14, 2021 Posted December 14, 2021 Only the 32bit version generates any logs after pressing "Exit Texgen" button: TexGen_SSE_Debug_log.txt and TexGen_SSE_log.txt. The 64bit version crashes without generating any logs. No bugreport.txt file generated none I can find anyway ~~~~~~~~~~~~~~~~~~~~ TexGen_SSE_Debug_log.txt https://ufile.io/l301xsdy TexGen_SSE_log.txt https://ufile.io/3uisjajh
sheson Posted December 14, 2021 Author Posted December 14, 2021 26 minutes ago, soupdragon said: Only the 32bit version generates any logs after pressing "Exit Texgen" button: TexGen_SSE_Debug_log.txt and TexGen_SSE_log.txt. The 64bit version crashes without generating any logs. No bugreport.txt file generated none I can find anyway ~~~~~~~~~~~~~~~~~~~~ TexGen_SSE_Debug_log.txt https://ufile.io/l301xsdy TexGen_SSE_log.txt https://ufile.io/3uisjajh Why do you keep posting irrelevant logiles from the x86 version that have a clear error message? x86 programs are limited by consumer Windows to a max of 3.1GB. xLODGen/DynDOLOD/TexGen write the log files when they are closed. The exception handler writes the bugreport.txt. Looks like the OS, antivir or whatever might just terminate the program without it letting it handle whatever the issue is. Check the Windows Eventlog for related message(s).
soupdragon Posted December 14, 2021 Posted December 14, 2021 (edited) There are no other logs. Thats it. I don't know what else to say. What eventlog? Edited December 14, 2021 by soupdragon
sheson Posted December 14, 2021 Author Posted December 14, 2021 8 minutes ago, soupdragon said: There are no other logs. Thats it. I don't know what else to say. What eventlog? https://en.wikipedia.org/wiki/Event_Viewer
soupdragon Posted December 14, 2021 Posted December 14, 2021 (edited) And wheres the log supposed to be? Edited December 14, 2021 by soupdragon
soupdragon Posted December 14, 2021 Posted December 14, 2021 (edited) Event log: Summary of text: ~~~~~~~~~~~~~ Faulting application name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61b4d4ca Faulting module name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61b4d4ca Exception code: 0xc0000005 Fault offset: 0x0000000000895929 Faulting process ID: 0x740c Faulting application start time: 0x01d7f0d095f5f33c Faulting application path: D:\DynDoLod stuff SSE\DynDOLOD-Standalone.3.00-Alpha-57\TexGenx64.exe Faulting module path: D:\DynDoLod stuff SSE\DynDOLOD-Standalone.3.00-Alpha-57\TexGenx64.exe Report ID: 5e017851-f2ce-478c-8ca3-fb05f842ef21 Faulting package full name: Faulting package-relative application ID: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> - <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Version>0</Version> <Level>2</Level> <Task>100</Task> <Opcode>0</Opcode> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2021-12-14T10:00:27.5361088Z" /> <EventRecordID>15388</EventRecordID> <Correlation /> <Execution ProcessID="0" ThreadID="0" /> <Channel>Application</Channel> <Computer>USER-PC</Computer> <Security /> </System> - <EventData> <Data>TexGenx64.exe</Data> <Data>3.0.0.0</Data> <Data>61b4d4ca</Data> <Data>TexGenx64.exe</Data> <Data>3.0.0.0</Data> <Data>61b4d4ca</Data> <Data>c0000005</Data> <Data>0000000000895929</Data> <Data>740c</Data> <Data>01d7f0d095f5f33c</Data> <Data>D:\DynDoLod stuff SSE\DynDOLOD-Standalone.3.00-Alpha-57\TexGenx64.exe</Data> <Data>D:\DynDoLod stuff SSE\DynDOLOD-Standalone.3.00-Alpha-57\TexGenx64.exe</Data> <Data>5e017851-f2ce-478c-8ca3-fb05f842ef21</Data> <Data /> <Data /> </EventData> </Event> Edited December 14, 2021 by soupdragon
sheson Posted December 14, 2021 Author Posted December 14, 2021 27 minutes ago, soupdragon said: Faulting application name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61b4d4ca Faulting module name: TexGenx64.exe, version: 3.0.0.0, time stamp: 0x61b4d4ca Exception code: 0xc0000005 Fault offset: 0x0000000000895929 Faulting process ID: 0x740c Faulting application start time: 0x01d7f0d095f5f33c Faulting application path: D:\DynDoLod stuff SSE\DynDOLOD-Standalone.3.00-Alpha-57\TexGenx64.exe Faulting module path: D:\DynDoLod stuff SSE\DynDOLOD-Standalone.3.00-Alpha-57\TexGenx64.exe Report ID: 5e017851-f2ce-478c-8ca3-fb05f842ef21 Faulting package full name: Faulting package-relative application ID: Reboot, do not start other programs while running the tool. Check video memory usage while the programs runs to see if usage gets anywhere near its max size. Run one TexGen option at a time. The output can be merged. Check and post if it always happens at the same part. This could be caused by problems with the hardware, overclocking, bad memory, wrong BIOS settings etc.
soupdragon Posted December 14, 2021 Posted December 14, 2021 (edited) Was after a fresh reboot, no other programs running. It keeps happening at exactly the same time/spot repeatedly. No overclocks memory tests fine. Trees only: generates fine. Grass + Rendered only: generates fine. Grass + Rendered + Trees: crashes. HD tree generation (with trees) only: crashes. Vram usage immediately following freeze/crash: DynDOLOD-Standalone.3.00.Alpha-23, the previous last version I have, generates just fine without errors. If anyone has any versions between alpha 24 and 56 and feels like sharing so I can try them out I'd appreciate it. Edited December 14, 2021 by soupdragon
sheson Posted December 14, 2021 Author Posted December 14, 2021 1 hour ago, soupdragon said: Was after a fresh reboot, no other programs running. It keeps happening at exactly the same time/spot repeatedly. No overclocks memory tests fine. Disable HD tree generation: Still crashes. Disable Grass: Still crashes. Disable trees so Resources only: completes successfully So what is the last tree LOD billboard that generates? Is it always the same? What is the resolution of Textures\landscape\trees\TreePineForestBranchComp.dds, its compression format and file size?
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