Jump to content

Question

Posted

as soon as texgen reaches gathering resources the ram and vram fill up in a matter of seconds causing the kernel to end the program. there are no logs for texgen created.

im running texgen through mo2 through proton experimental, here are some information about my system 

Hardware

Computer Information:

Manufacturer: Micro-Star International Co., Ltd.
Model: MPG Z790 CARBON WIFI (MS-7D89)
Form Factor: Desktop
No Touch Input Detected

Processor Information:

CPU Vendor: GenuineIntel
CPU Brand: 13th Gen Intel(R) Core(TM) i9-13900K
CPU Family: 0x6
CPU Model: 0xb7
CPU Stepping: 0x1
CPU Type: 0x0
Speed: 5500 MHz
32 logical processors
24 physical processors
Hyper-threading: Supported
FCMOV: Supported
SSE2: Supported
SSE3: Supported
SSSE3: Supported
SSE4a: Unsupported
SSE41: Supported
SSE42: Supported
AES: Supported
AVX: Supported
AVX2: Supported
AVX512F: Unsupported
AVX512PF: Unsupported
AVX512ER: Unsupported
AVX512CD: Unsupported
AVX512VNNI: Unsupported
SHA: Supported
CMPXCHG16B: Supported
LAHF/SAHF: Supported
PrefetchW: Unsupported
BMI1: Supported
BMI2: Supported
F16C: Supported
FMA: Supported

Operating System Version:

"Arch Linux" (64 bit)
Kernel Name: Linux
Kernel Version: 6.15.7-arch1-1
X Server Vendor: The X.Org Foundation
X Server Release: 12401008
X Window Manager: KWin
Steam Runtime Version: steam-runtime_1.0.20250519.130917

Client Information:

Version: 1751405894
Browser GPU Acceleration Status: Disabled
Browser Canvas: Unavailable
Browser Canvas out-of-process rasterization: Disabled
Browser Direct Rendering Display Compositor: Disabled
Browser Compositing: Disabled
Browser Multiple Raster Threads: Enabled
Browser OpenGL: Disabled
Browser Rasterization: Disabled
Browser Raw Draw: Disabled
Browser Skia Graphite: Disabled
Browser Video Decode: Disabled
Browser Video Encode: Disabled
Browser Vulkan: Disabled
Browser WebGL: Unavailable
Browser WebGL2: Unavailable
Browser WebGPU: Disabled
Browser WebNN: Disabled

Video Card:

Driver: NVIDIA Corporation NVIDIA GeForce RTX 4090/PCIe/SSE2
Driver Version: 4.6.0 NVIDIA 575.64.03
Desktop Color Depth: 24 bits per pixel
Monitor Refresh Rate: 143 Hz
VendorID: 0x10de
DeviceID: 0x2684
Revision Not Detected
Number of Monitors: 1
Number of Logical Video Cards: 1
Primary Display Resolution: 3840 x 2160
Desktop Resolution: 3840 x 2160
Primary Display Size: 27.44" x 15.43" (31.46" diag), 69.7cm x 39.2cm (79.9cm diag)
Primary VRAM: 24564 MB

Sound card:

Audio device: Intel Raptorlake HDMI

Memory:

RAM: 64052 Mb

VR Hardware:

VR Headset: None detected

Miscellaneous:

UI Language: English
LANG: en_US.UTF-8
Total Hard Disk Space Available: 936786 MB
Largest Free Hard Disk Block: 809447 MB

Storage:

Number of SSDs: 4
SSD sizes: 1000G,1000G,1000G,1000G
Number of HDDs: 0
Number of removable drives: 0

i tested 194 with MaxMultiSamples=8 and MaxTextureSize=8192 and also 4/4096, then it drops an opengl error that i cant find on the forum. sadly i couldnt test with your testbuild you mentioned in the other thread about linux memory issue.

  • Answers 48
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

Posted Images

Recommended Posts

  • 0
Posted
22 minutes ago, metaltortoise88 said:

https://www.mediafire.com/folder/bj76zl4dt66d2/Texgen_Logs

Using Dyndodod 3 Alpha 194, Dyndolod Resources Alpha 57, and Dyndolod DLL NG Alpha 36.

This started happening the last couple of days. I was on an older Nvidia driver from a month or two ago and would get an OpenGL error some of the time, but upon re-running texgen, I could get it to successfully run to completion after one or two tries. I regret not saving the logs from the other day, but I no longer have them. Yesterday I updated my drivers to the latest version and now I get this error every time. The error never points to the same texture file and it always happens about 1 minute in.

I've tried using NVCleanstall to remove unnecessary bloatware, and completely removing my drivers and installing them from scratch. Nothing has worked so far. My next move I guess is to try to figure out what driver I was using when I could still get Texgen to finish some of the time, but I wanted to post here in hopes that there's a better solution. Thank you.

Is there no bugreport.txt? See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs

The latest driver is 580.88. Is just released today, so install that.

If issue persists, set GLDebug=1 under [TexGen] in E:\Skyrim\tools\DynDOLOD\Edit Scripts\DynDOLOD\TexGen_SSE.ini as explained in https://dyndolod.info/Messages/Exceptions#OpenGL and upload new logs.

Then add RenderSingle=1 under [TexGen] and try again. If issue persists also add StitchThreads=1 under [TexGen]
If still fails with those 2 settings, also upload those logs.

  • 0
Posted

No bugreport.txt was generated. I tried earlier today with both 580.88 and 577.00(the logs I provided were on this version) and got the same error. However, I just now revered back to 576.52 and Texgen ran to completion without issue.

I will update my drivers back to 580.88 sometime today when I have more time and try those settings and provide new logs. Thank you!

  • 0
Posted (edited)

Hello,

I am turning to the forums because I have tried everything I could read on the forums and the FAQ's page to no avail, and was hoping more experienced eyes could spot anything I may have missed.
I keep experiencing an OpenGL error at a specific point while running TexGenx64

OpenGL: invalid operation from TwbRender.SceneSet for C:\Modding\tools\DynDOLOD\TexGen_Output\textures\dyndolod\lod\trees\srg_treepineforestdeadsnowl01_53207c82_trunk_1


I was able to successfully resolve linux memory issues and crashing with the help of the FAQ and the forums by modifying my TexGen_SSE.ini.
I was able to successfully resolve previous OpenGL errors which would not allow the TexGen Options GUI to load.
However, I have not been able to resolve the current issue with OpenGL after setting the TexGen Options and starting the generation according to the Step 2.3 SkyrimAE guide.

Please find logs attached with included system specs.
Briefly, I'm on Bazzite linux (Bazzite 42 Kinoite) using official NVIDIA drivers (non-opensource) using Lutris to run MO2.
Wine version: GE-Proton(latest)
I, initially, forgot to upload my TexGen_SSE.ini file, but have done so here

Any help would be greatly appreciated!

Thank you.

Edited by linuxmod
forgot to add link to ini file.
  • 0
Posted
On 8/15/2025 at 6:46 PM, linuxmod said:

Hello,

I am turning to the forums because I have tried everything I could read on the forums and the FAQ's page to no avail, and was hoping more experienced eyes could spot anything I may have missed.
I keep experiencing an OpenGL error at a specific point while running TexGenx64

OpenGL: invalid operation from TwbRender.SceneSet for C:\Modding\tools\DynDOLOD\TexGen_Output\textures\dyndolod\lod\trees\srg_treepineforestdeadsnowl01_53207c82_trunk_1


I was able to successfully resolve linux memory issues and crashing with the help of the FAQ and the forums by modifying my TexGen_SSE.ini.
I was able to successfully resolve previous OpenGL errors which would not allow the TexGen Options GUI to load.
However, I have not been able to resolve the current issue with OpenGL after setting the TexGen Options and starting the generation according to the Step 2.3 SkyrimAE guide.

Please find logs attached with included system specs.
Briefly, I'm on Bazzite linux (Bazzite 42 Kinoite) using official NVIDIA drivers (non-opensource) using Lutris to run MO2.
Wine version: GE-Proton(latest)
I, initially, forgot to upload my TexGen_SSE.ini file, but have done so here

Any help would be greatly appreciated!

Thank you.

There is no need to enable the realtime log if the normal TexGen log and debug log and a bugreport.txt are generated. So disable that RealTimeLog=0.

Why do you set LoadGLCompressed=0? Was there an error without it? If so, upload those logs and bugreport.txt.

Why are you setting RenderTexturesSingleThread=1?

Try the latest NVIDIA drivers for Linux, which seem to be 580.76.05

For some reasons other users also had success updating their BIOS.

  • 0
Posted (edited)
7 hours ago, sheson said:

There is no need to enable the realtime log if the normal TexGen log and debug log and a bugreport.txt are generated. So disable that RealTimeLog=0.


Sometimes when generating billboards(after the TexGen options app window/gui) TexGen would freeze/hang my system, and I would have to turn my computer off and back on.
I wasn't sure, what was causing it, and if those logs would be useful so I added them just in case.
I have since turned this off and rerun TexGen according to your instructions below.

 

7 hours ago, sheson said:

Why do you set LoadGLCompressed=0? Was there an error without it? If so, upload those logs and bugreport.txt.


Yes, there was an error without it. Logs provided here.
I have to set 'LoadGLCompressed=0' to get to the TexGen options gui to start generating the billboards.
If I do not have that in my ini the TexGen options gui doesn't appear and an error appears, see in bugreport.txt on newly attached logs, and I'm made to close TexGen.

 

7 hours ago, sheson said:

Why are you setting RenderTexturesSingleThread=1?


Good question, I thought it was helping get to the TexGen options gui, but it turns out once I returned my ini back to default, re-added the Step 2.3 instructions for TexGen_SSE.ini, and then isolated each setting one by one. I found this may not be useful.
This has been removed from any further testing, unless advised to re-add.

 

7 hours ago, sheson said:

Try the latest NVIDIA drivers for Linux, which seem to be 580.76.05


Currently in use during the new batch of testing, can verify in the debug log posted.

 

7 hours ago, sheson said:

For some reasons other users also had success updating their BIOS.


I saw that in the forums, but didn't think anything of it, but since you referenced it I did look into it and my BIOS did in fact need updating, but still getting same errors.

 

The only edits to the TexGen_SSE.ini that have been made on this new round of testing are the following:
 

[TexGen]
GLDebug=1
MaxRenderResolution=4096

;[Step Modifications]
GrassModelHeightMultiplier=1.15
TreeMSAlphaThreshold=144
ObjectMSAlphaThreshold=96

Edited by linuxmod
added ini config.
  • 0
Posted
On 8/19/2025 at 11:50 PM, linuxmod said:


Sometimes when generating billboards(after the TexGen options app window/gui) TexGen would freeze/hang my system, and I would have to turn my computer off and back on.
I wasn't sure, what was causing it, and if those logs would be useful so I added them just in case.
I have since turned this off and rerun TexGen according to your instructions below.

Yes, there was an error without it. Logs provided here.
I have to set 'LoadGLCompressed=0' to get to the TexGen options gui to start generating the billboards.
If I do not have that in my ini the TexGen options gui doesn't appear and an error appears, see in bugreport.txt on newly attached logs, and I'm made to close TexGen.

Good question, I thought it was helping get to the TexGen options gui, but it turns out once I returned my ini back to default, re-added the Step 2.3 instructions for TexGen_SSE.ini, and then isolated each setting one by one. I found this may not be useful.
This has been removed from any further testing, unless advised to re-add.

Currently in use during the new batch of testing, can verify in the debug log posted.

I saw that in the forums, but didn't think anything of it, but since you referenced it I did look into it and my BIOS did in fact need updating, but still getting same errors.

The only edits to the TexGen_SSE.ini that have been made on this new round of testing are the following:

[TexGen]
GLDebug=1
MaxRenderResolution=4096

;[Step Modifications]
GrassModelHeightMultiplier=1.15
TreeMSAlphaThreshold=144
ObjectMSAlphaThreshold=96

Moved posts to the appropriate thread for the original error.

If the system hangs or crash you might want to double check hardware (power), OS and drivers. If possible, try NVDIA drivers from a couple month back like beginning of the year.

Run this test version of TexGen https://mega.nz/file/tMJXUIga#M1ql_yZbkNghUNAkub2y80lXuDWM-XIMB8Eti3N-yk4 with just the changes to the INI you have posted. Upload new log, debug log and bugreport.txt.

  • 0
Posted
On 8/20/2025 at 3:27 AM, sheson said:

Moved posts to the appropriate thread for the original error.

If the system hangs or crash you might want to double check hardware (power), OS and drivers. If possible, try NVDIA drivers from a couple month back like beginning of the year.

Run this test version of TexGen https://mega.nz/file/ZcwHgbiC#LIk95GoQsc9AOgxElmV5TKLf_ybstqGxAFYJBW5rVzI with just the changes to the INI you have posted. Upload new log, debug log and bugreport.txt.

Hey,

Sorry for the delay.
Please see logs here using the test version of TexGen provided above.
The issue is the same, but now I'm also getting errors on missing textures.
I received these same errors on the steam version as on the gog version (elaborate on that below).
I'm not sure if anything can be determined via the logs, but I'm grateful for any further help you can provide.
I'm thinking of maybe switching to Endeavour OS, as I believe I have more control of the nvidia drivers there.
It'll just take me a while to migrate my setup.

[Background]
I've been extremely curious and stubborn on getting this to work, and have been as exhaustive as possible on my methodology.
First, to make sure I didn't do anything wrong when initially going through the Step 2.3 methodology, I decided to take another path.
Because I run my games via Lutris and then they have to launch Steam in order to launch the mo and then launch the app or game, I decided to take out all the complexity of that whole process and the time to launch!
I decided to  just run the gog version of skyrimAE and make the necessary changes(ex. using SKSE_gog, race menu for GOG, etc...) to be able to launch from Lutris directly.
Essentially to mitigate any extra complexities and mental load on managing all this.
As for the freezing, I also looked at my hardware and all the connections, disassembled PC and reassembled etc.
I ordered new ram and replaced it yesterday; no freezing has occurred since then, so far.
At the time, I was using Bazzite nvidia closed source/proprietary drivers, I have since switch to Bazzite nvidia open source drivers to see if this would change any results.
Unfortunately, all these changes have me stuck in the same spot.

re: downgrading NVIDIA drivers.
Bazzite ships with nvidia drivers built-in to the os, and they only have a 90 day rollback allowance.
So, I don't have the ability to switch to drivers different than the ones I have currently tested, 570.xx and 580.xx.
Moreover, when they made the switch from Bazzite v41(last known successful drivers, 565.xx) to Bazzite v42(current 570.xx-580.xx), my understanding is there is a bug which does not allow downgrading from v42-v41. I think it's an upstream Fedora issue(?).

Thank you and hope we can find a solution!
 

  • 0
Posted
6 hours ago, linuxmod said:

Hey,

Sorry for the delay.
Please see logs here using the test version of TexGen provided above.
The issue is the same, but now I'm also getting errors on missing textures.
I received these same errors on the steam version as on the gog version (elaborate on that below).
I'm not sure if anything can be determined via the logs, but I'm grateful for any further help you can provide.
I'm thinking of maybe switching to Endeavour OS, as I believe I have more control of the nvidia drivers there.
It'll just take me a while to migrate my setup.

[Background]
I've been extremely curious and stubborn on getting this to work, and have been as exhaustive as possible on my methodology.
First, to make sure I didn't do anything wrong when initially going through the Step 2.3 methodology, I decided to take another path.
Because I run my games via Lutris and then they have to launch Steam in order to launch the mo and then launch the app or game, I decided to take out all the complexity of that whole process and the time to launch!
I decided to  just run the gog version of skyrimAE and make the necessary changes(ex. using SKSE_gog, race menu for GOG, etc...) to be able to launch from Lutris directly.
Essentially to mitigate any extra complexities and mental load on managing all this.
As for the freezing, I also looked at my hardware and all the connections, disassembled PC and reassembled etc.
I ordered new ram and replaced it yesterday; no freezing has occurred since then, so far.
At the time, I was using Bazzite nvidia closed source/proprietary drivers, I have since switch to Bazzite nvidia open source drivers to see if this would change any results.
Unfortunately, all these changes have me stuck in the same spot.

re: downgrading NVIDIA drivers.
Bazzite ships with nvidia drivers built-in to the os, and they only have a 90 day rollback allowance.
So, I don't have the ability to switch to drivers different than the ones I have currently tested, 570.xx and 580.xx.
Moreover, when they made the switch from Bazzite v41(last known successful drivers, 565.xx) to Bazzite v42(current 570.xx-580.xx), my understanding is there is a bug which does not allow downgrading from v42-v41. I think it's an upstream Fedora issue(?).

Thank you and hope we can find a solution!
 

Run the updated test version from this post https://stepmodifications.org/forum/topic/21129-opengl-invalid-value-from-twbrenderloadglmultiimage/page/2/#findComment-287412

Report results. If there is an error set GLDebug=1 in the INI and run again and then upload the log, debug log and bugreport.txt.

In any case get glew-2.2.0-win32.zip from https://github.com/nigels-com/glew/releases, unpack the folder ../bin/Rel4ease/x64 and run the two exes. Upload the two txt files they generate.

The missing texture messages are a result of the OpenGL error when trying to load those textures.

  • 0
Posted
1 hour ago, sheson said:

Run the updated test version from this post https://stepmodifications.org/forum/topic/21129-opengl-invalid-value-from-twbrenderloadglmultiimage/page/2/#findComment-287412

Report results. If there is an error set GLDebug=1 in the INI and run again and then upload the log, debug log and bugreport.txt.

In any case get glew-2.2.0-win32.zip from https://github.com/nigels-com/glew/releases, unpack the folder ../bin/Rel4ease/x64 and run the two exes. Upload the two txt files they generate.

The missing texture messages are a result of the OpenGL error when trying to load those textures.

Downloaded and ran

  • glew exes
  • new test texgen

here are the logs from all.

This time around even with GLDebug=1 a bugreport.txt did not generate, but all other reports did.
Hope these logs are useful. 

  • 0
Posted
21 hours ago, linuxmod said:

Downloaded and ran

  • glew exes
  • new test texgen

here are the logs from all.

This time around even with GLDebug=1 a bugreport.txt did not generate, but all other reports did.
Hope these logs are useful. 

Get new test version from this post https://stepmodifications.org/forum/topic/21129-opengl-invalid-value-from-twbrenderloadglmultiimage/page/2/#findComment-287412

Report results. If there is an error set GLDebug=1 in the INI and run again and then upload the log, debug log and bugreport.txt.

 

  • 0
Posted (edited)
1 hour ago, sheson said:

Just uploaded another new test version to that post. Upload new logs.

new logs

I know we're going back and forth here, but just wanted to express my deepest gratitude for helping me troubleshoot this!!
Your efforts are much appreciated. Thank you.
Hopefully we can figure this out.

Edited by linuxmod

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.