z929669

Yes, Nexus files are never 'deleted', and using the API is an option, but we support MAs in their decisions, so our policy is to avoid providing the API links in such cases. This mod will be removed in 2.4, but we don't have an alternative at this time. You can try this mod as a replacement. Let us know what you think after trying the different options.

Yes, Nexus files are never 'deleted', and using the API is an option, but we support MAs in their decisions, so our policy is to avoid providing the API links in such cases. We'll likely be moving to RIM - Real Ice reMastered for 2.4.

LOL ...I linked to https://www.nexusmods.com/skyrimspecialedition/... instead of https://www.nexusmods.com/skyrim/... Murphy's law that the same mod ID pointed to that mod on the SSE subfolder at Nexus.

@DoubleYou Should we let DynDOLOD Resources override this, since that mod might have a better chance to capture updates to address potential reported issues with affected LODs? This came up for me in testing for 2.4, when I found Additional DynDOLOD Resources, which Phlunder recommends overriding DynDOLOD Resources. When I dug into both of those, FOLIP-SSE surfaced as a player in LOD assets covered by both. For compatibility with LE, his mods use LE nif versions, and rule of thumb should be to use SE nif versions where available (all else being equal). For these models, either one will work, but SE is more efficient and contemporary. FOLIP-SSE and DynDOLOD Resources both adopt the SE nif format, so I'm suggesting asset priority could be: Additional DynDOLOD Resources FOLIP-SSE DynDOLOD Resources ...if you recommend likewise.

This mod is now superseded by Additional DynDOLOD Resources and will be dropped in 2.4.

Discussion topic: Additional DynDOLOD Resources by Phlunder Wiki Link This is technically an LE mod that applies to all versions of TES5. It effectively replaces Glacier LOD Meshes. What's more is that it covers roughly 100 vanilla LOD meshes not covered by DynDOLOD Resources. Think of this as a vanilla LOD mesh replacer that should be overridden by DynDOLOD Resources and FOLIP. As such, this will be tentatively 'accepted' for 2.4. I've tagged as 'testing' at this time for admin purposes.

What is missing besides Just Ice that you have found?

Look for BOD2 flags in ARMOR records in xEdit in the plugin for the hair mod you are using to see if adding/removing the "31-Hair" flag resolves.

Do you have large sectors (> 512 kb) on the drive you are running the game? If so, it's likely related to that and can be fixed by this mod (also see the first post on that mod).

This mod is now super simple to install just as it should be Install both main files, merging when asked.

First, I don't think BP officially supports any mod managers specifically aside from MO. I'll wager it's possible to install and run BP through Vortex, but it probably would require some manual configuration. Our team uses MO, so we are not well versed in how Vortex works. I played with Vortex a couple of years ago to explore Collections, but I lost interest, due to Vortex asset-conflict management (and other things) being a PITA compared to MO. I forget if I got BethINI working or not. If you really want to know why it's not working, review/post its log file ("/BethINI Pie/logs/<latestDatetimeFolder>/log.log"). BP should be installed as a stand-alone app into your modding tools location into its own folder beside other tool folders like xEdit, LOOT, DynDOLOD, etc. In MO, you just add the BP executable and you're good to run through MO ("BethINI Pie" only ...the old 'BethINI' didn't run through MO natively). The MO VFS places all instance/profile-specific modding assets in their native paths (as if no mod manager were used), so it just works. With mod managers outside of MO (or no mod manager), BP should be used as a standalone app just like any other. It's 'smart' enough to find your game path and INIs, I think. See this GamerPoets vid for an overview of general installation and the extra step if using MO. Pay close attention to how to configure the game and game INI paths on BP launch. If I were running Vortex, I would first install BP standalone and modify my game INIs. Then I would install Vortex and configure it for that game so I know it's using my BP-modified game INIs. Once Vortex is installed, I forget where it installs its basis for each game (and game INIs) or if it uses the base game folder for all vanilla files like INIs. It probably doesn't though and probably uses copies of volatile game assets like game INIs into something like a 'profile'. Once you know for sure where the game INIs are for your Vortex game instance, you can simply point BP to that INI location, and it should work fine.

The MA took it and others down, so just skip that one for now. We'll address this in the 2.3 guide short-term over the next few days and in the dev 2.4 guide long-term.

No, just CG or not-CG. You can reference our most recent recommendations in the dev guide. CG grass will never match LOD at all ToD for all weathers and in all locations. It's quite maddening for perfectionists.

Now I see. I honestly don't know. @DoubleYou may know if camera or bow INI settings may have something to do with this.

It's not clear from the video what the issue is.

You definitely should be using Grass Cache Helper NG, so keep that enabled, or you won't have grass. This mod should be enabled along with NGIO when creating the grass cache, which should then be installed as a mod in MO (just a /grass folder). Be sure you aren't using Grass Cache Fixes, and disable/delete it if you are. That mod will sort it's plugin at higher priority than the Step patches, which causes grass to not render. Be sure your grass BethINI Pie settings are correct. Sort plugins with LOOT before creating the grass cache.

Precaching grass requires > 9 min for sure. It should be more like 25-90 min. Revisit BethINI Environment settings and NGIO settings. NGIO has had several recent updates, and I haven't tested with the latest versions yet.

Be certain you have all of the correct versions and resources installed and that this is what you also used to generate LOD. If you are using DynDOLOD DLL, be sure it's the correct and latest version. Then if you still have issues, please post logs.

Template updated Added support for OblivionRE Added SEO enhancements (for any page where this template is used) Subtitle is now required Author will always be populated using the most recent editor's user name by default (unless explicitly defined) When used on a GameSpace page, the corresponding game flare/logo will always be used Added automatic Guide Category assignment Refactored code with inline comments

First, if a MO download is stuck, you should right click the broken download and select 'pause', then `resume`. If that doesn't kick it in, then it's correct to cancel then delete it. Then close and restart MO. You never got to the installation, which is right click > Install. The rest of what you are seeing has nothing to do with cancelling or deleting the download. You must've made other changes. Uninstalling/reinstalling MO2 is not the solution. It sounds like you are either on the wrong MO instance or on the wrong profile than what you expect. Executables don't just delete themselves. You either must remove them via the GUI or via ModOrganizer.ini (inside the instance folder set). Because you also have SKSE problems and can't launch via the launcher, it all sounds like you are working in the wrong instance. Try changing MO instances using the first menu icon at upper left of MO. Restart MO after changing. Instances are different than profiles, so when you say you can run the launcher in a different profile, it doesn't make sense. Maybe this is true from a different instance though. Have a look at our instances vs profiles article to see if that helps you sort it out.

Doh! I missed that this was the xEdit forum. Good call.

It's not clear what mods provide "Platinum Perks.esm" or "live wire", but it sounds like you did not update a configuration file properly. Specifically, you did not enclose the added string name of the item in quotes, and it has spaces with the word 'of' inside. So it looks like a parsing error in the config, passing 'of' instead of some value.

Probably a combination of Vokrii and sneak. You were in combat with the deer momentarily, and when you snuck successfully, you exited combat, yielding the XP for light armor. Vokrii provides some enhanced early leveling for light armor, I think. I'm guessing you were wearing ≥ 2 pieces of light armor? Vokrii actually overhauls the perk tree to be more cohesive and to give stealth/mage/weaponless characters more opportunity to level relative to the vanilla tree, which makes it more practical to play such classes. A couple of those mods might touch leveling indirectly, but I can't speak to them.

Use "Download with mod manager" on Nexus (best if MO is open in the background), and be sure you have Nexus integration enabled under MO settings to have access to the Nexus API. If you download a mod from another source, you can still try to get metadata from Nexus if the mod is also on Nexus. If it isn't, you can modify the info in the mod's 'meta.ini' in the mod directory via Explorer. Also, you can right click a package in MO Downloads (right pane) when it has the triangle warning (no meta), and "Open meta file" for edit, or click "Query info". No idea what you mean about "package.txt", but that's a question for MO devs via their Git repo > Issues.

This has been resolved. Good to know. I'll add a note to update this in CL if I can confirm the issue and how to resolve.