Jump to content

Recommended Posts

Posted
  On 1/5/2023 at 7:21 AM, blueetenicolet said:

txt here: Mega

And In the log of SSEEdit, it seems only read from some esm plugins, not all esm.

  Reveal hidden contents
Expand  

It only lists plugins and worldspaces that have large reference data.

Does the issue still happen if you disable EnhancedWetnessandPuddles.esp?

Posted

I remember being in a similar situation: I can't start the sence that Balgruf lead you to Farengar to talk about bleakfall. Balgruf should lead you to meet Farengar, but he do nothing after dialogue, finally i found it was a guard mod caused that. One guard is considered doesn't matter and was disabled by the author, but in fact he's one Alias in a quest, and it caused that quest cannot run, then caused the bleak fall quest broken.

Maybe this is the same? Some largeReference is Alias in some quest and was disabled by LargeReference workaround, so  caused other quest damaged?

Posted
  On 1/5/2023 at 2:15 PM, blueetenicolet said:

I remember being in a similar situation: I can't start the sence that Balgruf lead you to Farengar to talk about bleakfall. Balgruf should lead you to meet Farengar, but he do nothing after dialogue, finally i found it was a guard mod caused that. One guard is considered doesn't matter and was disabled by the author, but in fact he's one Alias in a quest, and it caused that quest cannot run, then caused the bleak fall quest broken.

Maybe this is the same? Some largeReference is Alias in some quest and was disabled by LargeReference workaround, so  caused other quest damaged?

Expand  

The workarounds do not disable large references. That could only be done by removing them from the worldspace RNAM list in the plugin(s) that add them.

Large references are references with the base record STAT or MSTT. Check the exported list. There is no NPC in that list.

Posted

@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.

Posted
  On 1/6/2023 at 5:56 PM, 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.

Expand  

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.

Posted
  On 1/6/2023 at 6:10 PM, 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.

Expand  

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).

 

Posted
  On 1/6/2023 at 6:29 PM, 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).

Expand  

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.

  • Like 1
Posted
  On 1/6/2023 at 6:46 PM, 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.

Expand  

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.

Posted
  On 1/5/2023 at 10: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

Expand  

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!

Posted

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?

Posted
  On 1/8/2023 at 12:26 AM, 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?

Expand  

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.

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.