z929669 Posted January 6, 2023 Share Posted January 6, 2023 @sheson As I have confirmed for AMD cards, the 22.5.1 drivers work with latest version of DynDOLOD, but that version doesn't appear to be available for latest Radeon XT-series AMD cards, and the latest drivers reportedly still have the OpenGL issue with DynDOLOD. Is there no way to resolve this on DynDOLOD side? Because it's very likely not going to be 'fixed' by AMD, because there is quite likely nothing wrong with their drivers. I can help with testing when I have time if you have parameters. Link to comment Share on other sites More sharing options...
sheson Posted January 6, 2023 Author Share Posted January 6, 2023 16 minutes ago, z929669 said: @sheson As I have confirmed for AMD cards, the 22.5.1 drivers work with latest version of DynDOLOD, but that version doesn't appear to be available for latest Radeon XT-series AMD cards, and the latest drivers reportedly still have the OpenGL issue with DynDOLOD. Is there no way to resolve this on DynDOLOD side? Because it's very likely not going to be 'fixed' by AMD, because there is quite likely nothing wrong with their drivers. I can help with testing when I have time if you have parameters. Read the first post and https://dyndolod.info/Official-DynDOLOD-Support-Forum what logs and bugreports to provide when posting about problems with the latest alpha version. Link to comment Share on other sites More sharing options...
z929669 Posted January 6, 2023 Share Posted January 6, 2023 8 minutes ago, sheson said: Read the first post and https://dyndolod.info/Official-DynDOLOD-Support-Forum what logs and bugreports to provide when posting about problems with the latest alpha version. Relevant logs have been provided in the past by those of us with AMD cards and using driver versions > 22.5.1, and logs aren't applicable to my question and comment above. I'm asking if there is appetite for resolving the new AMD issues with the latest versions of DynDOLOD. I will take your response to mean that those of us on AMD should install the latest drivers and post those logs as applicable. This is a viable path forward as long as there is a path to resolving besides "rely on AMD deprecated drivers" or "buy an NVIDIA" or "wait for AMD to fix" (when nothing is broken from their standpoint). Link to comment Share on other sites More sharing options...
sheson Posted January 6, 2023 Author Share Posted January 6, 2023 22 minutes ago, z929669 said: Relevant logs have been provided in the past by those of us with AMD cards and using driver versions > 22.5.1, and logs aren't applicable to my question and comment above. I'm asking if there is appetite for resolving the new AMD issues with the latest versions of DynDOLOD. I will take your response to mean that those of us on AMD should install the latest drivers and post those logs as applicable. This is a viable path forward as long as there is a path to resolving besides "rely on AMD deprecated drivers" or "buy an NVIDIA" or "wait for AMD to fix" (when nothing is broken from their standpoint). No logs and no bugreports about the known AMD issue with older DynDOLOD versions have been provided for the latest alpha version as far as I remember. I beg for them every time a user posts about that problem. I have no ideas what the "new AMD issues with the latest versions of DynDOLOD" is supposed to be as I do not recall any logs or bugreports about it either. 1 Link to comment Share on other sites More sharing options...
z929669 Posted January 6, 2023 Share Posted January 6, 2023 15 minutes ago, sheson said: No logs and no bugreports about the known AMD issue with older DynDOLOD versions have been provided for the latest alpha version as far as I remember. I beg for them every time a user posts about that problem. I have no ideas what the "new AMD issues with the latest versions of DynDOLOD" is supposed to be as I do not recall any logs or bugreports about it either. The "new" issues with respect to AMD drivers for the Radeon 7900XT were reported on one of our Nexus mod pages. After looking further, I found that the known compatible version of the drivers are not available for that card. So I got to thinking that those with latest AMD GFX (myself as yet not included) will be out of luck unless they are prepared to troubleshoot on this forum with proper logs and testing parameters. As you know, this is often difficult, given that few people want to test/troubleshoot. I will be in a position to do so in the near future, so I will upgrade my drivers and begin that testing if you have appetite to work through these issues. For now, I'm running 22.5.1 drivers without issue, but I'd like to keep up with their updates as they roll out. There may be a new version out there now for my card. I also want to hold of upgrading my GFX until I know there is a path to resolution for AMD. I'll be posting back here in the coming weeks to work this issue, so thanks for the clarity. Link to comment Share on other sites More sharing options...
ElCapitan8866 Posted January 6, 2023 Share Posted January 6, 2023 On 1/5/2023 at 5:10 AM, sheson said: Read the first post which log and debug log to upload when making posts. Set the Season Type in po3_SeasonsOfSkyrim.ini accordingly to the list which should be above the setting. ;0 - disabled ;1 - permanent winter ;2 - permanent spring ;3 - permanent summer ;4 - permanent autumn Set Season Type = 0 to generate the default grass cache. See https://dyndolod.info/Help/Grass-LOD#No-Grass-LOD-Check-List Hi Sheson, thank you for the feedback. On reviewing the No Grass LOD Check List I found that TexGen was not producing any grass LODs. A little more research and I found that I needed to recalculate boundaries for all grasses in the Seasonal Landscapes plugin using the CK. After that, produced all 5 grass caches (name accordingly for each season plus the default one), ran xLodgen, then TexGen, then Dyndolod, finally disabled the grass cache and the use Crass Cache option under the NGIO ini, and viola! Good beautiful landscapes with matching distant terrain, object, trees, and grass LODs for each season. Thank you again! Link to comment Share on other sites More sharing options...
TZV4344 Posted January 8, 2023 Share Posted January 8, 2023 First of all I would like to apologize for any rudeness in my wording as I use DeepL. Perhaps the load order checking method has changed since Alpha109, but I am getting errors in profiles where no problems were detected in 108. I would like to try to correct it to the correct load order, but where should I look in the log? Link to comment Share on other sites More sharing options...
Jake0233 Posted January 8, 2023 Share Posted January 8, 2023 It seems that the latest update to DynDOLOD produced an error when I have the mod "Teldryn Seros" installed. An error occurred when this mod is installed including its Lux Patch. Here are the logs when I attempted to build the LODs: https://ufile.io/ro63bf07 https://ufile.io/y6j2vpat https://ufile.io/2vxljsp1 Link to comment Share on other sites More sharing options...
blueetenicolet Posted January 8, 2023 Share Posted January 8, 2023 On 1/7/2023 at 12:31 AM, sheson said: Test with this version of DynDOLOD DLL NG https://mega.nz/file/JIxxWLyR#WQ5Da9xkK-jRVANdI31lmYA1BTngNKrkUB7OxgJBn9U If the issue does not happen and if there are no other weird side effects, this is an actual fix. I 'm going on business trip now, i can test it about 2 days later. Link to comment Share on other sites More sharing options...
sheson Posted January 8, 2023 Author Share Posted January 8, 2023 8 hours ago, TZV4344 said: First of all I would like to apologize for any rudeness in my wording as I use DeepL. Perhaps the load order checking method has changed since Alpha109, but I am getting errors in profiles where no problems were detected in 108. I would like to try to correct it to the correct load order, but where should I look in the log? Read the first post which log, debug log and bugreport.txt (if it exists) to upload when making posts. As explained of the first post, if there are error messages prompts, read the entire message carefully and click the link "Click on this link for additional explanations and help for this message" or read https://dyndolod.info/Messages or https://dyndolod.info/Help for the associated help topics yourself. If help with a message is required, use the "Copy this message to clipboard" link and past the text. Link to comment Share on other sites More sharing options...
sheson Posted January 8, 2023 Author Share Posted January 8, 2023 6 hours ago, Jake0233 said: It seems that the latest update to DynDOLOD produced an error when I have the mod "Teldryn Seros" installed. An error occurred when this mod is installed including its Lux Patch. Here are the logs when I attempted to build the LODs: https://ufile.io/ro63bf07 https://ufile.io/y6j2vpat https://ufile.io/2vxljsp1 It looks like the new alpha version was not installed into a new and empty folder. https://dyndolod.info/Installation-Instructions Use 7-Zip to unpack the 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\. It seems you started DynDOLOD one more time after the issue, thus the debug log that shows the problem has been replaced. Please run DynDOLOD again to get new debug log and bugreport and upload them. https://dyndolod.info/Messages/Can-Not-Copy-Record Check the mentioned cell record xx0D7D2F in Lux - Teldryn Serious.esp in xEdit if you can spot a problem and the entire plugin for errors. Double-check what is the last plugin to overwrite the cell record. Test if it works without the batched patch. Link to comment Share on other sites More sharing options...
SirLach Posted January 8, 2023 Share Posted January 8, 2023 Greetings. Long time supporter / user - first time posting in these forums. I have just upgraded to Alpha 109 from Alpha 106 and reran my LOD generation. No issues on 106 but I have encountered a repeatable error on 109. [Main Instruction] Can not copy [CELL:641102FC] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:641102F4]) from DBM_HelgenReborn_Patch.esp into DynDOLOD.esp. [Content] Access violation at address 000000000105A903 in module 'DynDOLODx64.exe'. Read of address 0000000000000000 Helgen Reborn.esp [CELL:641102FC] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:631102F4]) Logs/Files here -> https://drive.google.com/file/d/1LPvitPttV2X0MF0tydgEYtRBBUdbacDG/view?usp=sharing The only change I have made external to upgrading to Alpha 109 is to update Far Object LOD Improvement Project SSE. Link to comment Share on other sites More sharing options...
Jake0233 Posted January 8, 2023 Share Posted January 8, 2023 (edited) 54 minutes ago, sheson said: It looks like the new alpha version was not installed into a new and empty folder. https://dyndolod.info/Installation-Instructions Use 7-Zip to unpack the 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\. It seems you started DynDOLOD one more time after the issue, thus the debug log that shows the problem has been replaced. Please run DynDOLOD again to get new debug log and bugreport and upload them. https://dyndolod.info/Messages/Can-Not-Copy-Record Check the mentioned cell record xx0D7D2F in Lux - Teldryn Serious.esp in xEdit if you can spot a problem and the entire plugin for errors. Double-check what is the last plugin to overwrite the cell record. Test if it works without the batched patch. I did what you asked and its still producing the same error. Here are the logs: https://ufile.io/foq80jxa = Bug Report https://ufile.io/z77kdxrb = Debug_Log I also tried to run it without the Lux Patch but it still produced an error at the same cell record from the original mod this time. There were also no errors between the patch and its master. I tried also running without the Bashed Patch earlier but still no avail. Edit: the lux patch came from the official patches in the Lux page Edited January 8, 2023 by Jake0233 Link to comment Share on other sites More sharing options...
sheson Posted January 8, 2023 Author Share Posted January 8, 2023 8 hours ago, SirLach said: Greetings. Long time supporter / user - first time posting in these forums. I have just upgraded to Alpha 109 from Alpha 106 and reran my LOD generation. No issues on 106 but I have encountered a repeatable error on 109. [Main Instruction] Can not copy [CELL:641102FC] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:641102F4]) from DBM_HelgenReborn_Patch.esp into DynDOLOD.esp. [Content] Access violation at address 000000000105A903 in module 'DynDOLODx64.exe'. Read of address 0000000000000000 Helgen Reborn.esp [CELL:641102FC] (in aaaWereBalokDungeonWorld "Staadomaar Temple" [WRLD:631102F4]) Logs/Files here -> https://drive.google.com/file/d/1LPvitPttV2X0MF0tydgEYtRBBUdbacDG/view?usp=sharing The only change I have made external to upgrading to Alpha 109 is to update Far Object LOD Improvement Project SSE. 7 hours ago, Jake0233 said: I did what you asked and its still producing the same error. Here are the logs: https://ufile.io/foq80jxa = Bug Report https://ufile.io/z77kdxrb = Debug_Log I also tried to run it without the Lux Patch but it still produced an error at the same cell record from the original mod this time. There were also no errors between the patch and its master. I tried also running without the Bashed Patch earlier but still no avail. Edit: the lux patch came from the official patches in the Lux page Thanks. Same problem. Will be fixed next version. Edit: Should be fixed in Alpha-110 Link to comment Share on other sites More sharing options...
TZV4344 Posted January 8, 2023 Share Posted January 8, 2023 9 hours ago, sheson said: Read the first post which log, debug log and bugreport.txt (if it exists) to upload when making posts. As explained of the first post, if there are error messages prompts, read the entire message carefully and click the link "Click on this link for additional explanations and help for this message" or read https://dyndolod.info/Messages or https://dyndolod.info/Help for the associated help topics yourself. If help with a message is required, use the "Copy this message to clipboard" link and past the text. I was going to post the log when I got home, but it seemed to be exactly the problem that was fixed in alpha-110. Thanks for the update. Link to comment Share on other sites More sharing options...
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