GlassDeviant

That's the biggest problem, I hate file names with underscores that only exist to enable poor parsers. I go out of my way to rename my mod archive library consistently and without underscores. Computers exist to automate tasks, but fortunately in the long run MO gets most of them and I only have to fiddle with a few of them. A suggestion to whomever is maintaining/extending MO: The way Nexus files are (supposed to be) named it may be more effective to consider parsing them from the right to the left, taking the version number, then the mod ID, then the much more variable mod name. Then the only difficulties will be with low numbered mod IDs, where now any space or number in a mod name causes a problem.

Better to commit to reporting bugs on a beta than struggle with the release version in its current state.

I hope you are right about the new release, because the current version is a steaming turd. Days I have been fighting with this piece of crap to get SSE modded up even with just a couple dozen mods.

Wouldn't it be easier to just do the cleaning without MO active? The stock ESM files sit in your install folder, the cleaned ESM files go in your install folder, MO doesn't touch them anyway, so you don't have to fuss around with making "Cleaned X" fake mods or any of the other stuff at https://wiki.step-project.com/STEP:Guide#2.B._Clean_the_Update_ESM, you just clean them, make sure they are in the proper place, and get on with the stuff MO actually has a clue what to do with, no need for meta files or any other hand waving. The process at that link is a lot of trouble for nothing.

Never run anything as admin. Any files that are written are given admin ownership, meaning you will not be able to make any changes to them while using your normal account.

In skyrim.ini, [Papyrus] section, fPostLoadUpdateTimeMS=2000 has been set by BethINI. Is this considered safe now? I've always kept it to 500 based on several different sources.

Thanks

Hi, are there particular reasons the BethINI Field of View setting drop down menu has the particular values it does (55.93, 65.00, 70.59 and 85.79, while working with Skyrim LE) or are those just somewhat random values?

"Plus we want to keep Linux and MacOS support an option and the MO vfs is impossible to port." Perhaps this will help with with Vortex: Linux (and MacOS by definition) supports VFSes by default, in fact some distros use one as their default file system now to unify local and remote storage. You can plug a VFS right into your application with FUSE and forget it's even there, and even Windows supports plug-in virtual file systems with the Installable File System mechanism, which is far superior to their old Shell Namespace Extension which didn't fully support low level file system access. No administrator install necessary, as it would be just one file in the existing file system it is hosted on, though it's really not hard if the user has admin access (i.e.: it's their own computer, not some work computer they shouldn't even be using it on). Were you to use a FUSEd / IFS compatible vfs for Vortex, it might make one part of the project a lot easier, or at least it could be a plug-in option for people who can install a vfs on their own. P.S.: Congrats on the new job.

I always install mods from the archives I download manually. Whenever I go to install a mod now, I get only the first word of the archive filename, instead of what the STEP guide says, " If no meta info was collected, it will display the filename of the archive minus the appended Nexus ID and version number." Now, I know I can just click the down arrow in that field and select the full name, but the whole reason we have computers is to automatic repetitive tasks, and my CTS is bad enough already. So how do I get MO to use the full name, sans the Nexus ID and version number, by default?

Should I be using the older Mod Organizer for oldrim/Skyrim LE?

A bit necro-y but relevant: You can save a step by changing the New Variable Value to -Xmx1024M (or 2048M), which will help not just this process but also many other things that use Java, for example newer (and larger) versions of Minecraft. Don't use 2048 unless your computer has at least 6GB of RAM, preferably 8GB or more. Don't forget to leave out the -Xmx1024m parameter in your shortcut as this becomes redundant.

please delete, did not solve the problem completely.

The problem is that MO is still looking for an obsolete version of the .NET libraries. This is ongoing and progressive, as the current version for Windows 7 (actually NT and up supposedly) and up is now 4.6.1 and you cannot install any previous version if you have this one installed. Since other applications use .NET and may require a more recent version, MO needs to be able to detect the presence and version of .NET, no matter which version it is (ideal situation), or just not bother checking since it is everyones responsibility to keep their own computers up to date. Here is an example of how to detect the presence and current version of .NET installed on a computer, it took all of 5 seconds to find with Google and works for all versions of the library that have ever existed: https://blogs.msdn.microsoft.com/astebner/2009/06/16/sample-code-to-detect-net-framework-install-state-and-service-pack-level/ Note that there are two versions. The preferred method of use is to use the first version to detect and the second to verify the install state and version.

I haven't even run anything yet, I just loaded Mod Organizer and it's telling me to load Hearthfires after Dragonborn. That's absolutely ludicrous, why would I load Hearthfires after Dragonborn? Even and old version of MO should know better than that. Heck the last time I used MO it knew better. I've tried today with 1.2.18 and 1.3.8 (both shown as current on the MO page at Nexus) and they both tell me to do this. Edit: OK switched to external loot (but still run from inside MO) and updated the masterlist, this seems to have fixed the problem. So this was a problem with the version of LOOT included with MO then? P.S.: Thanks Greg.

Different. Mod Organizer seems to want me to put Hearthfires after Dragonborn. WTF?

Is there a reason why every guide still recommends using BOSS instead of LOOT, besides "because this is what we've always used"?

I seem to be having a very strange problem that never occurred with NMM, but I don't know if it's necessarily MO or something else that is causing this. Hopefully someone can advise me on how to fix this so I can get back to actually playing my games again, which is after all the end goal for all of us, right? When I level up, my Magicka, Health or Stamina goes up by the amount I have set in the Uncapper ini file, depending which of the stats I chose to raise, but nothing happens to my Carry Weight. I have changed these values and tested the changes and they work fine, giving me increases equal to the newly changed settings. Previously, the same identical ini file wold raise my Carry Weight by 25 points, whether I chose Magicka, Health or Stamina, effectively giving me 25 points of carrying capacity per level no matter what choice I made. Now, it only happens when I increase Stamina (the default/vanilla behaviour), but I get the amount as set in Uncapper (definitely not the default/vanilla amount). The only mod I have that I know affects these values is SkyTweak, and I was using it before with the exact same settings when the Uncapper was working properly. I am using the same versions of these two mods as I was using before. Essentially, the only difference is MO, as I have added no mods that alter these values as far as I am aware. Any ideas?

wow, that seems to indicate that the priority sorting I did should actually break my game, but instead it has (so far) eliminated hard locks and increased my fps significantly (from 40-53 range to 120-300 range). Edit: Aaand that's the end of that, just ctd before even getting to the standing stones. Back to the drawing board.

Can someone briefly explain or point me to an explanation of how Priorities that I set in MO affect the load list produced by LOOT? I did a search on Priority but it didn't really produce any clear answers for me.

Once upon a time I, like you, hated Wrye Bash. Then I discovered that the most important feature of it, the ability to create a Bashed Patch, is incredibly simple to use and can work wonders in making incompatible mods work together. Now, I never play any game that supports it without it, and I still know nothing more about how to use it than how to create a basic Bashed Patch. If you install it in a fodler of its own, it will not mess up your game. My folder structure, to bypass Windows 7's User Annoyance Confounder (UAC), is like so: C:Games C:GamesBOSS C:Games (other stuff) C:GamesNexus Mod Manager C:GamesSkyrim C:GamesSkyrim mods (where Wrye Bash puts MY Skyrim files, don't know why yours would not be here) C:GamesStar Citizen Though I haven't used Mod Organizer (yet), I've used xxxxEdit, FoMM, NMM and other similar tools and am pretty confident in my knowledge and use of them. Since I have no problems other than the usual issues from changing/adding/removing mods in the middle of the game (I am my own worst enemy), I can see one of three things as possible alternative explanations for your problem, though I am not saying any of them is necessarily the case: 1) You did something wrong when you installed Wrye Bash 2) You did something wrong when you installed Mod Organizer 3) You failed to do whatever it takes to get the two working together correctly One thing you might want to consider is reinstalling everything clean from scratch with no mods installed and making sure everything is in its own private place, especially when you are dealing with programs that are utilities for multiple games. BOSS, MO, NMM, Wrye Bash and so on should not be in sub-folders of any game, even if you only use them with one (I made that mistake one time, took me weeks [!] to figure the problem out, including several restores of Skyrim from a clean WinRAR archive). Upon further reading, there is also at least one update to Wrye Bash that fixes some compatibility issues between MO and WB which might make a difference for you. Given the date of your OP I am thinking this would be likely, and no changes to STEP would be necessary (the WB installer is much prefferable to the standalone).