z929669

Then you posted on the wrong topic. Your issue probably has nothing to do with ENB either. It's probably mods you are using not compatible with the game runtime and SKSE versions you are using. You may not be using the correct SKSE version either. You should disable ENB for the time being and troubleshoot from there. Then create a post in a topic relevant to your issue if you are still having problems.

I'm fine with adding this one. Marked accepted for 2.2.0 (let me know if you disagree)

Marked accepted for 2.2.0

This can only happen if something was changed. Since there have been no game updates or SKSE updates recently, then it has to be something you changed. Paste the texture name into the right pane of MO data tab to get the source mod for the texture. It will likely be related to a mod impacted by this change.

Not sure what ReadMe you are talking about, but this is the corrected link. That topic might have some relevant recent posts, but the xLODGen topic is what you want, I think. @DoubleYou has been working on FO4 LOD for a while now, so he will likely have some good insights.

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.

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

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

I agree this is a no-brainer. Has anyone tested it? Barring any issues, it's self evident. EDIT: was going to put it in testing and realized that this is brand new. It's getting lots of attention, and has a few compatibility issues. Nothing bad for Step, but may be worth letting this one stew a bit before adopting.

It sounds like you have possibly multiple portable instances of MO or an instanced local version and a portable one from Wabbajack. I'm honestly not following, so I'm inclined to point you to our guide to establish a clean config/env rather than attempting to comprehend/resolve a one-off use case.

The 2.2.0 guide is nearly ready for release if you want to wait for that. Just applying the finishing touches, so maybe by this weekend sometime.

Echoing what Mercury71 posted, and also keep in mind that Skyrim Legendary Edition (LE) can be considered to be a previous version of Skyrim. Skyrim Special Edition (SE) is identical to Skyrim Anniversary Edition (AE), which is just a rebranding of SE with the four new vanilla plugins as Mercury71 described. So SE = AE to be clear. It's quite confusing, because most people (and Bethesda marketing) don't make this obvious. When you see mods supporting Skyrim v1.5.97, know that this is a deprecated version of SE prior to the release of AE (the new SE) and many mod authors still support it by popular demand (which adds to the confusion). Additionally, previous versions of AE are also supported by some mod authors. Ultimately, the versioning is a mess, because many obsolete versions of the game are still supported for modding: https://steamdb.info/app/489830/patchnotes/ The additional Creation Club (CC) mods for SE constitute the Anniversary Upgrade, which now costs $6 (down from $20) and can be purchased through Steam. This is the only version of Skyrim that Step supports today (though we still have the LE guide from years ago, but it's not actively supported). See the Guide links in the top menu of these forums for links to the Step Guides. Just remember that Skyrim Anniversary Edition = Skyrim Special Edition (latest version of the game 1.6.640). Following our AE guide will give you the simplest path to modding the most current version of the game and teach you what is needed to navigate customizing things for yourself. PS: please don't create topics in ALL CAPS.

See the top of forum and DynDOLOD OP for what to provide for support. You will need to provide this information.

We can take a look, but please use the tool for creating mod pages in the future. I will modify the OP for you this time. Thanks

Works for me and is a good enhancement that removes the issue of not knowing when you are about to start drowning. I think it fits the Mandate, since in reality, one whould know when one is about to start drowning, but this is impossible in a game without an indicator. It's subtle and non-invasive, IMO. Marked accepted

Discussion topic: Hearthfires Extended and Creation Club Fishing Patch by MrD518, Nechigawara Wiki Link I was given access to do this months ago and, I finally got around to updating the mod page with permission from the MAs, who did not seem to want to do this.

Yeah, all those errors are related to downstream mods with dependencies on the extenders that themselves were fine. That's why the smoke test worked.

If the initial test was successful a week ago, your extenders are all fine. You probably have an incompatible mod that relies on one of these extenders. looks like you may want to reinstall RaceMenu.

I would not whitelist file extensions but rather the EXEs as Mousetick has listed. Otherwise, you largely obviate the usefulness of you AV. See this sticky post for info on managing Windows Security OS software. I thought Windows Defender was bundled with Windows Security in Win10. I am on Win 11 and use ESET rather than Windows Security OS default. Either way, Defender should not be running when you invoke these apps. Make sure it's not performing a scheduled scan when you reboot or something. If it is, you can either let that process finish first, or reset the scan scheduler or whatever MS is trying to 'help' you with.

Mods like Crash Logger have not been updated. Those that Mercury linked will work though, so that may have been the issue. Those mods are not in the 2.1.0 guide, but more information on their substitutes is here.

Did you successfully launch the initial smoke test recently, or did you do this weeks/months ago? Some of the extenders in the 2.1.0 guide are not compatible with the recent game update to 1.6.640 (e.g., Crash Logger). The list and the alternatives is here.

Your issues are related to the 2.1.0 guide having been created for the previous version of the SSE runtime. We are currently preparing the 2.2.0 guide for the latest version of the game (1.6.640)

Much of this sounds like havok bugs, so it is very possible, yes. Always troubleshoot any issues by first getting your game INI files in order. Once that's done, you can safely assume that problems are not game-INI related. Basic BethINI config for LE should still apply. Our BethINI SSE instructions have more detail and > 90% applicable to LE I think. BethINI itself will adjust things based on the game chosen for INI modifications. Above all, read the LE mod page description. Once your game INI files are 'good' you can begin looking at other potential sources of your issues.

Are you using any of your own added mods not in the 2.1.0 guide? Did you skip any mods? Are you continuing from a savegame you had prior to installing the guide?