linuxmod
Citizen-
Posts
14 -
Joined
-
Last visited
linuxmod's Achievements
Citizen (2/12)
0
Reputation
-
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
results with new test version test 1: default INI, as shipped with DynDOLOD 3.00-68518-Alpha-194, no changes. result 1: successful 19m52s test 2: same INI as "test 1" added RenderSingle=0 result 2: SUCCESS @ 6m59s!! no hangs/freezes, no memory errors, no errors!!! test 3: same INI as "test 1" changed RenderSingle= from 0 to 1 (not sure if this is the same as test 1, but ran it nonetheless) result 3: success @ 20:50s -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
open source nvidia drivers - successful completion - debug log proprietary nvidia drivers - unsuccessful - crash to desktop - realtime log proprietary nvidia drivers - unsuccessful - computer froze - realtime log So, it looks like with "RenderSingle=0" computer doesn't freeze each time, just some of the time. It looks like some of the time after creating billboards it hangs on the second texture and then crashes to desktop. The other time it looks like it gets past that second texture and then just hangs the system. Hopefully these logs help. -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
Here is my latest round of testing First test: set GLDebug=0 and RenderThreads=2, removed RenderSingle=0. Compression: default(BC7 quick). First result: no freezes, no errors, time to completion 19m50s. Second test: same as first, just changed RenderThreads=4. Second result: no freezes, no errors, time to completion 19m50s. Looks like changing RenderThreads from 2 to 4 doesn't affect speed of completion. Third test: same as first (RenderThreads=2). Compression DXT1/DXT5. Third result: no freezes, no errors, time to completion 20m09s. Fourth test: same as second (RenderThreads=4). Compression DXT1/DXT5. Fourth result: no freezes, no errors, time to completion 20m09s. Re: switching to proprietary drivers I will do so, test and report back. Ok, so switched to nvidia proprietary drivers. Test: set GLDebug=0, RenderThreads=2, RenderSingle=0. Compression: default(bc7 quick) Result: TexGen closes abruptly, no computer freezing/hanging. This occurs at the same time above: after it completes billboards and moves to textures. Test 2: set GLDebug=0 and RenderThreads=2. Removed RenderSingle=0. Compression: default(bc7 quick) Result: no freezes, no errors, time to completion 19m41s. Lmk if there's anything else you'd like me to test. Thank you. -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
I'll be away from my computer for a few hours, so will continue testing then. Here's what I go so far: First test, I set GLDebug=0, RenderSingle=0, RenderThreads=2 My computer froze after about 17min when it switched from creating billboards to creating textures. Second test, kept everything the same as above, but changed RenderThreads=4 , got the same result as above. Maybe still something hardware related occurring. I remember when I was troubleshooting myself before I reached out via forums, my computer never responded well to RenderSingle=0. Idk, if that means anything but just wanted to mention. Will continue troubleshooting when I return. -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
IT WORKED!! slowly(2:49:46) but worked. Thank you! I did not receive any errors that stopped generation. I did receive only two errors that it was not able to find the two following files: smim_shack_roof.dds and smim_shack_roof_n.dds I assume I didn't install this mod correctly. Here are the logs. ** I couldn't upload to pastee.dev as logs were too large (debug log is around 24-26MB), used another app instead. If you have troubles retrieving the logs, I can try another way. Should I continue on to DynDOLOD, or should I fix the above errors with the two missing files and run the same test version of TexGen again? -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
As instructed: [reset ini to GLListDebug=0] ran TexGen, GUI appears, press start to gen textures, then errors. [changed ini to GLListDebug=1] errors at gen textures, as above, logs retrieved. logs uploaded -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
I got to the GUI and then got an error soon after starting to creating textures. I added GLListDebug=1. Logs here. -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
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. -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
Latest logs 09.01.2025 -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
Alright here are the new reports - provided my ini file, just in case. -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
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. -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
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! -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
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 -
OpenGL: invalid value from TwbRender.LoadGLMultiImage
linuxmod replied to mrmalin's question in DynDOLOD & xLODGen Support
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.

