sheson Posted January 4 Author Posted January 4 1 hour ago, dnmt said: debug: https://drive.google.com/file/d/1wTtsddvtBSKsGLS-7dm_3V4RfAIj5qoa/view?usp=sharing log: https://drive.google.com/file/d/1Yognlv-So93GK3txm5YXif5432VPDjix/view?usp=sharing Thanks. Based on the logs, the LOD generation looks it was successful and can be used as is. Once there is a test version or new alpha version in the near future, test again without the GLDebug setting.
Carmen_san_diego Posted January 4 Posted January 4 I see that this issue has been reported by other users, but I'm also having trouble: OpenGL: invalid operation from TwbRender.LoadTexture for 6742CE5A while processing 6742CE5A (4). I have ensured several times that I am using the latest DynDOLOD version, resources, and DLL. Using AMD Adrenalin 25.12.1 drivers, and even did a clean re-install of said drivers. TexGen seems to run just fine and never reports any exception -- it's when I run DynDOLOD.exe that I receive the exception. It's *always* for a different texture each time; doesn't matter which mods I have enabled. Bug report attached. Thanks so much for your hard work! Bug Report Debug logs are massive, as you might expect. Links here: https://www.mediafire.com/file/lzw839a92kuz0y4/DynDOLOD_SSE_Debug_log.txt/file https://www.mediafire.com/file/rbnxp9pjqydodx3/TexGen_SSE_Debug_log.txt/file
Sham111111 Posted January 4 Posted January 4 7 hours ago, sheson said: The drive link is asking for a login. Provide a working link for the DynDOLOD debug log. Do not install DynDOLOD over older versions. See https://dyndolod.info/Installation-Instructions Use 7-Zip to unpack the entire DynDOLOD Standalone archive into a new and empty 'DynDOLOD' directory that is outside of special OS folders like 'Programs Files' or 'Program Files (x86)', User, Documents, Desktop, Download and also not in SteamApps, game, Data or any mod manager folders. For example C:\Modding\DynDOLOD\. Ensure that the directory structure is preserved. See Updating how to update existing installation and save games. See https://dyndolod.info/Updating See answers for https://dyndolod.info/FAQ#Entire-LOD-missing. Start with checking object LOD distances in https://dyndolod.info/Help/Mod-Configuration-Menu-NG#Settings and since you are using ACMOS, make sure you checked the Level32 checkbox in the advanced mode. See https://dyndolod.info/Help/Advanced-Mode Hello sheshon, Thanks for your reply. I saw the warning from Dyndolod about old installation files so I had deleted all of it and pasted the new ver in, I guess it still shows in the log files. Yes, there was nothing on the minimap as well. No trees, no building like how it should be. I have changed the Google Drive access, and I will rerun DyndoLod tonight after work with "Level 32" checked.
sheson Posted January 4 Author Posted January 4 41 minutes ago, Carmen_san_diego said: I see that this issue has been reported by other users, but I'm also having trouble: OpenGL: invalid operation from TwbRender.LoadTexture for 6742CE5A while processing 6742CE5A (4). I have ensured several times that I am using the latest DynDOLOD version, resources, and DLL. Using AMD Adrenalin 25.12.1 drivers, and even did a clean re-install of said drivers. TexGen seems to run just fine and never reports any exception -- it's when I run DynDOLOD.exe that I receive the exception. It's *always* for a different texture each time; doesn't matter which mods I have enabled. Bug report attached. Thanks so much for your hard work! Bug Report Debug logs are massive, as you might expect. Links here: https://www.mediafire.com/file/lzw839a92kuz0y4/DynDOLOD_SSE_Debug_log.txt/file https://www.mediafire.com/file/rbnxp9pjqydodx3/TexGen_SSE_Debug_log.txt/file See the first post and/or https://dyndolod.info/Official-DynDOLOD-Support-Forum#Post-Logs which normal log of DynDOLOD to also upload when making posts. Click on the Click on this link for additional explanations and help for this message of the message as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Messages/Exceptions and scroll to the OpenGL section: 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. Delete old logs. Add GLDebug=1 to the DynDOLOD_SSE.ini, then run again and upload new log, debug and bugreport.txt (if it exists) please.
sheson Posted January 4 Author Posted January 4 22 minutes ago, Sham111111 said: Hello sheshon, Thanks for your reply. I saw the warning from Dyndolod about old installation files so I had deleted all of it and pasted the new ver in, I guess it still shows in the log files. Yes, there was nothing on the minimap as well. No trees, no building like how it should be. I have changed the Google Drive access, and I will rerun DyndoLod tonight after work with "Level 32" checked. The debug log shows that Level32 was not set. If you installed ACMOS with the uLockedObjectMapLOD=32 INI setting option, that might be the reason. For quick test, you could change the INI setting back to 16. If that make object LOD appear again, then generate new output with the Level32 checkbox checked.
ikonomov Posted January 4 Posted January 4 I am currently using Community Shaders with Grass Lighting installed so that I can adjust the amount of Subsurface Scattering and the brightness. The brightness setting can make the full grass look brighter or darker compared to the billboards, but I can adjust the brightness of the billboard grass in TexGen. What I'm having trouble with is adjusting the billboards to match the full grass when having Subsurface Scattering settings that's different than 0%. I'm trying to make it work with 50%, but it makes the billboard grass facing away from the sun too dark (or the grass facing towards the sun too bright). I tried setting ComplexGrassBillboard=5 and ComplexGrassBacklightMask=25, but those settings seem to make no difference. I'm using vanilla grass (without the complex grass mod for it) and forcing TexGen to generate complex billboard textures for it by setting ForceComplexGrass=2. Is there any way I can adjust the Subsurface Scattering amount that's used during billboard texture generation? And if that's not possible, I'd appreciate any explanation as to why ComplexGrassBillboard=5 and ComplexGrassBacklightMask=25 settings seem to have no effect. log and image files facing west, 0% SSS https://www.dropbox.com/scl/fi/vu4a2wwtt6pozcv86lmk7/west_0-SSS.png?rlkey=btpxuvcegxy5k06kles4hfe04&st=fl3x5c9q&dl=0 facing west, 50% SSS https://www.dropbox.com/scl/fi/smip20i7mgfgruq9ck4ko/west_50-SSS.png?rlkey=0vew21zgfilpdmrkyouieih30&st=e3kflzpa&dl=0 facing west, 0% SSS (ComplexGrassBillboard=5 and ComplexGrassBacklightMask=25) https://www.dropbox.com/scl/fi/77kq5h7xynh8j2vlngfri/west_0-SSS.png?rlkey=i2uedck0ipuowx9qjcygrwlji&st=bn88jjmi&dl=0 facing west, 50% SSS (ComplexGrassBillboard=5 and ComplexGrassBacklightMask=25) https://www.dropbox.com/scl/fi/8m8o23hqzsgrrxiuyu7qf/west_50-SSS.png?rlkey=7tdgvzmv6hqctrz7vo2u03vxd&st=47i5r5i8&dl=0
sheson Posted January 4 Author Posted January 4 2 hours ago, ikonomov said: I am currently using Community Shaders with Grass Lighting installed so that I can adjust the amount of Subsurface Scattering and the brightness. The brightness setting can make the full grass look brighter or darker compared to the billboards, but I can adjust the brightness of the billboard grass in TexGen. What I'm having trouble with is adjusting the billboards to match the full grass when having Subsurface Scattering settings that's different than 0%. I'm trying to make it work with 50%, but it makes the billboard grass facing away from the sun too dark (or the grass facing towards the sun too bright). I tried setting ComplexGrassBillboard=5 and ComplexGrassBacklightMask=25, but those settings seem to make no difference. I'm using vanilla grass (without the complex grass mod for it) and forcing TexGen to generate complex billboard textures for it by setting ForceComplexGrass=2. Is there any way I can adjust the Subsurface Scattering amount that's used during billboard texture generation? And if that's not possible, I'd appreciate any explanation as to why ComplexGrassBillboard=5 and ComplexGrassBacklightMask=25 settings seem to have no effect. log and image files facing west, 0% SSS https://www.dropbox.com/scl/fi/vu4a2wwtt6pozcv86lmk7/west_0-SSS.png?rlkey=btpxuvcegxy5k06kles4hfe04&st=fl3x5c9q&dl=0 facing west, 50% SSS https://www.dropbox.com/scl/fi/smip20i7mgfgruq9ck4ko/west_50-SSS.png?rlkey=0vew21zgfilpdmrkyouieih30&st=e3kflzpa&dl=0 facing west, 0% SSS (ComplexGrassBillboard=5 and ComplexGrassBacklightMask=25) https://www.dropbox.com/scl/fi/77kq5h7xynh8j2vlngfri/west_0-SSS.png?rlkey=i2uedck0ipuowx9qjcygrwlji&st=bn88jjmi&dl=0 facing west, 50% SSS (ComplexGrassBillboard=5 and ComplexGrassBacklightMask=25) https://www.dropbox.com/scl/fi/8m8o23hqzsgrrxiuyu7qf/west_50-SSS.png?rlkey=7tdgvzmv6hqctrz7vo2u03vxd&st=47i5r5i8&dl=0 Check one of the generated BTOs, like Tamriel.4.8.0.bto in NifSkope. Select a grass LOD block and check its BSLightingShaderProperty sets Shader Flag 2 Back_Lighting. Check that its BSShaderTextureSet defines 3 textures, with the second to last (8th with array index 7) sets textures\DynDOLOD\maps\gray_25.dds. Check that textures\DynDOLOD\maps\gray_25.dds exists in the DynDOLOD output. If all that is the case, you could test if changing that texture to textures\white.dds makes a noticeable difference for that grass block in the game. If not, test in the game without CS to verify it works as expected with the default shader. You could use https://www.nexusmods.com/skyrimspecialedition/mods/68640 so the generated normal maps have a bit more definition.
jepster Posted January 5 Posted January 5 14 hours ago, sheson said: Click on the link Click on this link for additional explanations and help for this message about billboards not fitting as explained in https://dyndolod.info/Official-DynDOLOD-Support-Forum#Read-Log-and-Error-Messages to open https://dyndolod.info/Help/Texture-Resolution: The maximum possible resolution of textures generated by DynDOLOD can be set by changing the setting MaxTextureSize at the ..\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_[GAME MODE].ini. Typically the size of textures added to the object LOD atlas textures or tree LOD atlas textures should be controlled in the advanced mode. Standard tree LOD only supports a single tree LOD atlas texture per worldspace and a maximum of 256 billboards. In case there is not enough space for all the tree LOD billboard textures to fit onto the tree LOD texture atlas, resize some tree LOD billboards (use lower settings in TexGen) or lower the max tile size billboard in the advanced mode. Alternatively use ultra tree LOD. I suggest to not change the stitched/object and max billboard size to insane values and instead leave the defaults of 256, 256 and 1024 based on the screen resolution of 1080. Maybe increase one step. There is typically no use for 4k LOD textures/billboards. That is just a waste of VRAM. Having to create several object LOD atlas textures means more draw calls. What confuses me is that with the previous version I have been fine with my insane settings I am always taking screenshots of the settings so I can compare in detail: Even tried lowering them to 2k without success / same error. The reason why I am going to such values is that I play in VR with a resolution of 2160x2160 per eye. With the screen much closer to the eyes it really makes a difference. Not a huge one, but more of a difference than say 4k cutlery
ikonomov Posted January 5 Posted January 5 Everything is as it should be. Checking with a white texture did the trick. The problem was that with ComplexGrassBacklightMask=25 the difference wasn't noticeable. Because the RGB value affects all colors, the lighted LOD grass doesn't have the same colors as the full grass. Still, I was able to get a decent transition with about 30% grass subsurface scattering in CS and being able to control this brightness value made all the difference. I'll do some further experimentation, but so far raising ComplexGrassBacklightMask to around 70 looks pretty good. Thank you for your help Sheson. 1
beefstuscemi Posted January 5 Posted January 5 18 hours ago, sheson said: Disabling a mod is a troubleshooting step and not fixing the invalid *.JSON file. I suggest to simply fix the *.JSON file (with notepad for example) and remove the comma, so that the file validates and the mod works as expected. Removing the extra comma as you suggested did indeed resolve the issue. I've reported this to the author of the corresponding mod. Thanks again for the help. 1
AYANAMINAY Posted January 5 Posted January 5 Hello sheson, I encountered the error: "OpenGL: Invalid operation from TwbRender.LoadTexture for B344739D while processing B344739D (4) while processing textures\nature_of_the_wild_lands\elm\elm.dds." I set Debug=1. When switching back to version 196, there was no issue. I also tried updating my drivers, but it didn't help. https://www.mediafire.com/file/b8ffikhwyni7ds1/bugreport.txt/file https://www.mediafire.com/file/0vbbuaspwlf1r54/DynDOLOD_SSE_Debug_log.txt/file https://www.mediafire.com/file/6cgpgtqmybrj785/DynDOLOD_SSE_log.txt/file
sheson Posted January 5 Author Posted January 5 21 minutes ago, AYANAMINAY said: Hello sheson, I encountered the error: "OpenGL: Invalid operation from TwbRender.LoadTexture for B344739D while processing B344739D (4) while processing textures\nature_of_the_wild_lands\elm\elm.dds." I set Debug=1. When switching back to version 196, there was no issue. I also tried updating my drivers, but it didn't help. https://www.mediafire.com/file/b8ffikhwyni7ds1/bugreport.txt/file https://www.mediafire.com/file/0vbbuaspwlf1r54/DynDOLOD_SSE_Debug_log.txt/file https://www.mediafire.com/file/6cgpgtqmybrj785/DynDOLOD_SSE_log.txt/file Debug=1 just prints the debug messages to the normal log in addition to the debug log. https://dyndolod.info/Messages/Exceptions OpenGL section: 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. Delete old logs. Add GLDebug=1 to the D:\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini, then run again and upload new log, debug and bugreport.txt if it exists please.
sheson Posted January 5 Author Posted January 5 8 hours ago, jepster said: What confuses me is that with the previous version I have been fine with my insane settings I am always taking screenshots of the settings so I can compare in detail: Even tried lowering them to 2k without success / same error. The reason why I am going to such values is that I play in VR with a resolution of 2160x2160 per eye. With the screen much closer to the eyes it really makes a difference. Not a huge one, but more of a difference than say 4k cutlery Increase the already mentioned MaxTextureSize setting in E:\Skyrim VR jepster\tools\DynDOLOD\Edit Scripts\DynDOLOD\DynDOLOD_SSE.ini to 16384 or add TreeLODMaxAtlasSize=16384 to it. I suggest to read the information in https://dyndolod.info/Help/Texture-Resolution how to test/find sensible texture resolutions. increasing by one step should be sufficient. Also see https://dyndolod.info/Updating how to keep the content of the preset folder to automatically keep the settings of the last generation. Upload new DynDOLOD log, debug log and bugreport.txt if it exists.
AYANAMINAY Posted January 5 Posted January 5 After adding GLDebug=1 as required, the dyndolod was generated successfully. However, even after removing GLDebug=1, the error still occurs. Here is the log file generated during the successful build: https://www.mediafire.com/file/jq0q53tck59e28r/DynDOLOD_SSE_Debug_log.txt/file https://www.mediafire.com/file/sh67mh18gcqkq14/DynDOLOD_SSE_log.txt/file
sheson Posted January 5 Author Posted January 5 24 minutes ago, AYANAMINAY said: After adding GLDebug=1 as required, the dyndolod was generated successfully. However, even after removing GLDebug=1, the error still occurs. Here is the log file generated during the successful build: https://www.mediafire.com/file/jq0q53tck59e28r/DynDOLOD_SSE_Debug_log.txt/file https://www.mediafire.com/file/sh67mh18gcqkq14/DynDOLOD_SSE_log.txt/file Thanks. Get the latest test version of DynDOLODx64.exe from https://dyndolod.info/Downloads/Test-Versions Delete old logs and then run again without GLDebug=1 to see if there is any change. Upload new log, debug log and bugreport.txt if it exists.
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