DoubleYou

BOSS is set to open the log file with your default internet browser, which on your system is a 64bit version of Internet Explorer. Mod Organizer cannot hook 64bit processes, so it throws this error. It is harmless, but it may mean you may not see the log upon BOSS run.

Can't do that until 2.2.9 guide is live.

You can also use Mod Organizer's Lock feature on plugin order to get the desired effect.

If that's the case, you probably are using 1.0.7. You have to manually update to the latest version if so.

That's shadow striping. There are probably multiple ways to get rid of it, but I normally suggest to go in SkyrimPrefs.ini and increase iBlurDeferredShadowMask under [Display] to something like 5.

Computer bugs are not like allergies. You are crashing in ways that are more typical of modding problems than in memory problems (opening door of Whiterun = CTD normally means mod conflict or bad mod code (go on esp/script/mesh witch hunt). Skyrim Memory Patch 3.0 allows you to load more things in memory before crashing. Setting too high values for the memory settings is most likely the cause of the CTDs that jonwd7 is experiencing. ENBoost allows you to use more memory than the 32bit nature of the Skyrim engine allows.

https://wiki.step-project.com/Guide:Mod_Organizer_Advanced#Migrating_from_NMM_to_Mod_Organizer

Because I have so many files downloaded through NMM. Is there a way to transfer all these files from the Nexus Mod Manager directory to the Mod Organizer directory?Cut and Paste ;)

I don't know if I like the idea of bringing jonwd7's issues over here. He seems to be on a personal rant. Your issues don't seem like issues stemming from the memory patches, but something else.

Accepted mods are only moved to the anthology upon release of the STEP version containing it.

You need the Bashed Patch even when using Mod Organizer.

Settings --> Reset Dialogs?

Serious HD is very good. You should definitely use it.

Ok. I didn't wait for them to load since I figured it was the Nexus acting up. Fixed the image links. As for the files not being there to hide, you must have installed it wrong then. Did you perhaps accidentally hit "replace" instead of "merge" when you installed the SMIM patch?

I've seen this problem on a friend's computer before, and I never figured it out. Basically, somehow BUM sees all all active mods as inactive. It's real strange. The only thing I could do was manually edit the rules.

I think I would agree with you.

Install the version that doesn't require BOYD.

First: Install using the STEP Guide. Extended in pack form is currently in development. Probably should add that as a warning to the pack page. Core profile would only include core mods. Extended profile would "extend" upon Core and add Extended mods (in some cases, different versions of Core mods may be used). The appropriate STEP Patch is used for each profile. Second: Don't use the BCFs. They are leftovers from Wrye Bash days. Third: Currently STEP recommends to extract all BSAs. BSA is an archived format of storing game files. It is debatable as to the best practice, although it currently doesn't really matter very much. Fourth: The SkyUI installer doesn't recognize that the scripts are present within Mod Organizer since it cannot see the virtual file system. Simply install anyway ignoring the warning. Fifth: Packs normally are built upon STEP Core, so you need to at least copy the Core profile when installing a pack. Proper pack support and instructions should come with 2.3.0

https://wiki.step-project.com/Guide:Mod_Organizer#Mod_Groups At bottom middle of the left pane is a drop-down menu saying "Nexus IDs" in your case. Select "No Groups"

I normally just manually enter the correct number in the corresponding meta file.

Could you take a picture of the file in explorer (PrntScr)?

You're confusing load order with installation order. BOSS will place the ESPs where they belong.

Chat isn't a great idea for something like STEP, since it's always better to have threads that can come up in google search, rather than a lot of information that gets lost in a chatbox. :|This. Sent from Florida using my Enslaved Black Alligator.

If using ENBoost and not the ENB part of it, set bFloatPointRenderTarget=0