EssArrBee

You could set up ENBoost at the very least. It just takes a bit of INI tweaking to get it done. Can't go into it at the moment since I'm on a phone.

I wouldn't update Willow in a playthrough. You'll probably get some red exclamations in the bungalow and could mess up the quests if they are already in progress.

Okay, it will need patching with the UPPs, but mostly for some sandbox stuff, dead body cleanup, and a few missing object bounds. Not sure why it would not

I don't see a problem with the ESPs, but they cannot be merged without permission. There are a few things that they add in which are unique like head parts. Also, the mod alters some of the facial morphs, hair, nose, and tint layers. I don't see anything to dramatic in the plugins that would disqualify it from being in STEP, but it needs to checked in game. I could see some of the changes as actually being fixes in a way. Only a couple NPCs had their races changed, but I don't see that as a problem. The plugins should also be loaded very low unless you really want to install something that alters NPCs from their vanilla appearance, like Seranaholic (not judging ). I'd even recommend overwriting any changes USKP and UDGP make to the NPC records other than clothing or equipment, some of those were botched by the UPPs if you ask me. This is all from me looking at the plugin, but I do have enough experience with this stuff that I can pretty much tell what will be different in game. We would just need to see how different the facial morphs are from their vanilla counterparts. EDIT: Just saw that part about the mounted combat bug, I'll look into that a bit more.

Not everyone installs every Core mod for whatever reason and they can't use the STEP Core patch because it has a dependency from a mod they didn't install.

MO v1.2.0 seems to install some of the mods that required FOMM, but uHUD and OneHUD still do not work. The installers now makes it through to the end now, but the make blank XML files and uHUD can't see what mods are installed. At least it looks like the MO installer is getting closer to making FOMM redundant.

If it doesn't work with the auto update then manually installing it works just fine.

Update just hit. Version 1.2.0- no longer create directories in original data directory - bain installer will now be less picky about the archives supported - updated NCC to be compatible with more recent NMM code base - hack in NCC to allow it to install arbitrary sized files even in 32-bit builds - updated the python27.dll to one that links to msvcr100.dll to get rid of the dependency of msvcr90.dll - ini files created by a call to WritePrivateProfile... are now also rerouted to overwrite - unpacking bsas during installation no longer overwrites loose files (since the loose files would have taken precedence) - some fixes towards qt5 compatibility - force-enabled game esms no longer break keyboard-navigation in plugin list - improved NCC compatibility - crude support for multi-volume archives - updated imageformats plugins - nxmhandler now puts the exe to the top of the list when registering an MO instance, even if it is already in the list - added buttons to backup and restore the modlist and pluginlist - replaced boss integration with loot - configurator now gives better warning messages when encountering an invalid ini file - added an option to show meta info on downloads instead of filenames - MO will now cancel if user tries to run MO vfs-injected - when saving the MO ini file it is now written to a tmp file first and then overwritten - updated to link against boost python 1.55 - added support for mod page plugins - re-introduced the integrated browser - the download list now contains the file description - nexus interface now stores cookies persistently to reduce number of required log-ins - bugfix: WritePrivateProfileString hook attempted to access lpKeyName even when it is null - bugfix: dll search order wasn't set to allow plugins to load the correct qt dlls - bugfix: when resuming a download failed with the server sending a textual error message, MO tried to display everything downloaded before - bugfix: resuming a download didn't trigger a nexus-login when necessary - bugfix: integrated fomod installer only used the first block of data inside a description - bugfix: the add/remove categories function could fail when a filter/grouping on categories was active - bugfix: GetCurrentDirectory returned wrong string length - bugfix: registered bsas in data aren't ordered correctly

I did that for a while, but it just didn't allow for everything you need. The d-pad buttons fill up fast and you run out stuff to bind using two schemes. I do hate that the keyboards aren't analog. I'm a big analog guy for most things and it helps for any game that has sneaking.

Well you can't use Project Nevada with the default controller scheme. You won't have sprint, grenades and vision modes. I did my profile with doubled up buttons by making one function execute on tap and one on hold.

It's not project Nevada. I use an emulator without issue to switch between 1st and 3rd person and have it bound to an analog stick. It may be the profile you use.

Never heard of pinnacle. Is it a emulator? I always like to try out new ones to see if they work better than xpadder.

I'll do a special page for this since I play with a controller whenever I plug into the tv. I use an xpadder profile that uses most of the features from the guide except for the grenade hotkey. I never use grenades except for blowing open locks.

I want the gameplay to be a cross of ME2/3 and DAO. DOn't know how that would work because DAO was semi-turn based, but I think it would be fun to find out. Actually, they should just make a game where you play as Morrigan and go around being a bad ass witch. Just mess everything up and be a completely terrible person. That would be ideal, but I am kinda awful that way when I play games. I always go dark side.

The thing about Bioware is that you can always count on good writing. Even the games people don't care for, ME3 and DA2, have solid writing and dialogue. I am hesitant to pre-purchase the game though, now that the two guys that left the company are not there anymore.

I merged the old dlc patch and every other patch to the STEP Patches, so there may be some duplicate records (ITMs). But they aren't going to mess anything up in STEP and there are so few that will actually be in conflict with other mods that you will not need to mess with it until I feel like changing it.

More core > clock speed with GPUs. Memory is weird because of the lack of a memory controller in GPUs and the divided memory hierarchy since the cores are divided into thread blocks. Also, remember that performance problems with some games is the software. As PC gamers we sometimes forget that and participate in the time honored tradition of throwing more hardware at software problem.

Thanks for the report.

I doubt it will affect the patches. I might have to remove some records but that isn't a big deal to me.

I really need to put in some time into the ENB Guide again. It is really outdated and my understanding on that stuff is so much better than when I started doing all that stuff.

Yeah it's correct do not deactivate the other mods in FOMM because that will mess up other stuff. And yes untick all the UI supplemental mods because a couple have XML files and you don't want something uninstalling them or overwriting them in some weird unpredictable way.

Do not uninstall from MO, just untick the mods.

Really this is do to the lack of Bashed Patch development. You could just tag mods for certain things to make them compatible. I keep ignoring the patching section of my FNV guide because the Bashed Patch works so well if you set up the tags correctly. So, any Python aces out there should get to work.

Uncheck all the UI mods in MO and I mean all them, not just the ones before uHUD. Open FOMM and uninstall uHUD, close FOMM. Check all the UI mods in MO and open FOMM again. Install Rust Town, close FOMM, move the files from the overwrite to Rust Town folder, open FOMM install uHUD, close FOMM. Move the files from the overwrite folder to the uHUD folder in MO. That is the safest way to do it unless you really understand how the whole XML file hierarchy works with FOMM and MO.

Then I don't know what to tell you. Maybe reinstall the mod and keep the BSA, and tick it as well.