TexGen/DynDOLOD out of graphics memory Linux

[Vraylle]

I'm attaching the realtime log, as that's the only one I can generate.

I'm running TexGen for SSE under Proton 9.0.4 on Linux. The PC has 64GB RAM and 8GB swap.

After scanning the load order, TexGen displays "Gathering base records for billboards". Then memory usage (RAM and SWAP) go to 100% and the entire system freezes. After about 15 minutes, the entire Wine prefix dies/crashes. Memory is recovered but the swap remains about half full. I can see from the realtime log that it seems to be doing work, but since it uses everything it looks like the OS is killing the process when it gets the chance (again, about 15 minutes later).

I've been looking for a way to restrict the memory available to that process to just let it run and see what happens, but haven't had any luck yet.

I will say this is the first time I've run it on this particular PC, but I've run it many, many times prior.

[sheson]

21 minutes ago, Strigifowl said:

After recently getting back into modding did I of course install the latest version of Dyndolod 3. However, for whatever reason when I attempt to run Texgenx64.exe it crashes without generating any logs when it attempts to load in billboard records. I also had an issue with running DynDOLODx64 but I solved it by adding LockTexconv = 1 to it's .ini however doing the same for texgen's .ini file didn't help. Also to note is that my CPU and RAM usage spikes up heavily right before Texgen crashes.

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which bugreport.txt to upload if it exists and how to enable the realtimelog in case the tool is being terminated prematurely. Also check the Windows Event log for related entries as explained.

[Strigifowl]

Here is the generated log I get when running TexGen with realtime log on.
https://paste.ee/p/0FaTpRLT

Looking into it a bit myself it seems the issue has something to do with the way OpenGL handles memory in the program. Which is interesting considering this hasn't been an issue previously and I have upgraded my ram since the last time I used TexGen (went from 8 gb to 16 gb). Any idea why it might have produced this behaviour?

[sheson]

9 hours ago, Strigifowl said:

Here is the generated log I get when running TexGen with realtime log on.
https://paste.ee/p/0FaTpRLT

Looking into it a bit myself it seems the issue has something to do with the way OpenGL handles memory in the program. Which is interesting considering this hasn't been an issue previously and I have upgraded my ram since the last time I used TexGen (went from 8 gb to 16 gb). Any idea why it might have produced this behaviour?

Moved to an appropriate thread with the same issue.

This seems to be an issue with a newer graphics driver.

Download the test versions of TexGen and DynDOLOD and add the INI setting to their INIs as discussed in the posts above.

[k5nn]

Is it possible to ask for a reupload on the test version of DynDOLOD specified on this thread? yes I too am running into this issue
 

I tried downloading it myself but it seems to have been taken down

https://mega.nz/file/dQYnTRoB#czPPP8mkKmsMwAatOJaPi90CG9RsGMNsOuUwHDdMbv8

 

Thank you kindly

Edited August 14 by k5nn

[sheson]

1 hour ago, k5nn said:

Is it possible to ask for a reupload on the test version of DynDOLOD specified on this thread? yes I too am running into this issue

I tried downloading it myself but it seems to have been taken down

Thank you kindly

Moved the post to the appropriate thread.

Whatever changes were added to the test version several months ago are included in the alpha versions that were released since then.

See https://dyndolod.info/Official-DynDOLOD-Support-Forum#Use-the-Latest-Versions

https://dyndolod.info/Official-DynDOLOD-Support-Forum

[k5nn]

so I have done the ff

downloaded the latest standalone version of dyndolod from nexus

installed the resources

allowed the scripts NG to overwrite the resources

did the ff changes to Texgen_SSE.ini

1) added TextureCache=10

2)changed MaxTextureSize from 8192 all the way down to 256

3) changed the RenderThreads from 2 to 1

no log file appears and still exhibits the same symptoms as the original problem the RAM and swap filling up but once the bottle/wine instance exits ram is freed but the swap file doesn't seem to go back to zero

I decided to try running texgen from dyndolod2 and it but since I don't not have any billboards I could'nt get past the texgen step do you advise I stick to dyndolod2 for the time being?

Edited August 15 by k5nn
additional details specifically about what happens to RAM when the bottle/win instance exits

[sheson]

1 hour ago, k5nn said:

so I have done the ff

downloaded the latest standalone version of dyndolod from nexus

installed the resources

allowed the scripts NG to overwrite the resources

did the ff changes to Texgen_SSE.ini

1) added TextureCache=10

2)changed MaxTextureSize from 8192 all the way down to 256

3) changed the RenderThreads from 2 to 1

no log file appears and still exhibits the same symptoms as the original problem the RAM and swap filling up but once the bottle/wine instance exits ram is freed but the swap file doesn't seem to go back to zero

I decided to try running texgen from dyndolod2 and it but since I don't not have any billboards I could'nt get past the texgen step do you advise I stick to dyndolod2 for the time being?

Read all of this section https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs and then upload the log(s) it explains to upload, e.g. the realtime log if everything else fails.

[k5nn]

here are the results of the run with RealTimeLog=1

I have also included the texgen_sse.ini used in the failed run

https://drive.google.com/drive/folders/1FIcMm6o-76pKnAT4XoSpRi-MnJKcYHnt?usp=drive_link

[k5nn]

adding the texgen logs via pastebin

https://pastebin.com/59THm9w1

[sheson]

14 hours ago, k5nn said:

here are the results of the run with RealTimeLog=1

I have also included the texgen_sse.ini used in the failed run

https://drive.google.com/drive/folders/1FIcMm6o-76pKnAT4XoSpRi-MnJKcYHnt?usp=drive_link

Restore the default TexGen_SSE.ini from the download archive, add the MaxRenderResolution=4096 INI setting under [TexGen] as explained in this post https://stepmodifications.org/forum/topic/21027-texgendyndolod-out-of-graphics-memory-linux/#findComment-285656

[k5nn]

it works now thanks and apologies for missing that one however is it possible to add the MaxRenderResolution=4096 INI setting under to the FAQ instead for future reference?

[mrmalin]

i now changed from i9-13900k to 9950x3d and drivers from nvidia-dkms 575.64.05-1 to nvidia-dkms-open 580.76.05 and still suffer the same trouble. could you provide a permanent download link to the test build exe and a config that works? 

only settings to run that work is

• MaxMultiSamples=4
• MaxRenderResolution=4096
• LoadGLCompressed=0

but its really slow

Edited August 22 by mrmalin

[sheson]

41 minutes ago, mrmalin said:

i now changed from i9-13900k to 9950x3d and drivers from nvidia-dkms 575.64.05-1 to nvidia-dkms-open 580.76.05 and still suffer the same trouble. could you provide a permanent download link to the test build exe and a config that works? 

only settings to run that work is

• MaxMultiSamples=4
• MaxRenderResolution=4096
• LoadGLCompressed=0

but its really slow

Read https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which log and debug log or realtime log to upload when making posts.

As already explained above, whatever changes were added to the test version several months ago are included in the alpha versions that were released since then.

As already explained above, only set MaxRenderResolution=4096 to work around the recent Nvidia Linux drivers to consume all main memory.

https://stepmodifications.org/forum/topic/21129-opengl-invalid-value-from-twbrenderloadglmultiimage/#findComment-287241
https://stepmodifications.org/forum/topic/21129-opengl-invalid-value-from-twbrenderloadglmultiimage/#findComment-287412

 

[mrmalin]

hello again, using the 196 build now on nvidia-open-dkms-580.82.07- memory crash is gone now but opengl error after few minutes of generating files in texgen.

image

TexGen_SSE_log.txt
TexGen_SSE_Debug_log.txt (mediafire, cause 43mb in one run)

 

[sheson]

13 minutes ago, mrmalin said:

hello again, using the 196 build now on nvidia-open-dkms-580.82.07- memory crash is gone now but opengl error after few minutes of generating files in texgen.

TexGen_SSE_log.txt
TexGen_SSE_Debug_log.txt (mediafire, cause 43mb in one run)

https://dyndolod.info/Messages/Exceptions#OpenGL
This can be also a bug with the tools encountering unexpected situations. Add GLDebug=1 under [TexGen|DynDOLOD] in ..\DynDOLOD\Edit Scripts\DynDOLOD\[TexGen|DynDOLOD]_[GAME MODE].INI and make a report with the log, debug log and bugreport.txt as explained on the official DynDOLOD support forum.

Run again with GLDebug=1 and upload those logs. Also upload bugreport.txt if it exists or report that it doesn't exist.