Barachiel

Yes I did. It's part of the F&L guide.

No, I'm good, but I'm not THAT good. I stay away from the manual optimization.

Welp, that fixed the Quicksave issue! Will report back on the incrementals issue.

Me again. :D So yeah, CASM doesn't work. It used to. It acts like it does. But it doesn't. I can hit F4 once, nothing. hit F4 twice "CASM is saving" message but no new save. Hit it again nothing. I have to hit it a LOT to make it save again. But no new save. Incremental saves, not working. No messages. If it wasn't for the fact that it's in my MCM, I woudln't even know it was installed. I went to the CASM page but none of the help requests there have been answered in over a year, so I'm not wasting my time. I have NVSE installed (GetNVSEVersion reports version 5), the Steam overlay re-enabled (read in an old thread this was required for nvse to work properly, dunno if I believe that, but i'm desparate). I've gone back down to to NVSE 4.5. no fix, and a new error from the Command & Control mod, so reverted back to version 5 beta 2. Uninstalled and reinstalled. Still nothing. Any ideas what's going on?

Thanks for the Ragdoll fix. I did a search, and they're talking about a puple skin tint. I'm talking about the ENTIRE SKIN being bright shiny purple with no details other than heads and hands. Also, just noticed some gamblers in the casinos walking around as nothing but heads and hands. Not just nude, but completly "invisible". I'm guessing it's a missing texture issue.

I'm having three instances of bad textures so far. The first two are near identical. Dead Supermutants and Brahmin Corpses are all warped and deformed. The SM's heads and stretched straight out, the Brahmin look like they've been twisted into a pretzel. Note this only applies to "pre-dead" corpses already placed in the world, not those I kill myself. Second, in the Ultraluxe Bath House half the male bathers have purple skin below the neck. I'll post images and form IDs next time I come across them.

Got it. I'll yank it then. Updating F&L from the 2/5/15 edition to the 9/19/15 edition pretty much broke my saves anyway. I must have been too far along with too many changes. I'll give Inheritance a try though, see what happens. Thanks!

Okay, so I got F&L working on my PC, works great so far. I transferred everything to my laptop. Works great, except for one thing. The ENB doesn't activate. I switched over to the Injector, since I realized my laptop has an Optimus setup. Still wont' activate, and it's running in my icon tray. I deleted the ENB and reinstalled it from scratch, in case I missed something. Nope, still won't kick in. Most of the ENB troubleshooting I see is for the Wrapper version. Any help with the Injector out there? EDIT 1: Tried adding the FalloutMO, FalloutNV, FalloutLauncher, and fn4gb exectuables to the injector ini file. Didn't help. EDIT 2: Tried the Optimus DLL fix. Didn't help.

New Vegas Bounties I & II have been in this guide for as long as I've used it. Was wondering if there was a reason "The Inheritance" and "Russel" weren't also included. I'm tempted to add them, but if they break something, I'd rather not.

Confirmed the problem is with Mod Organizer, somehow, I can run the FNV Launcher, NVSE, and FNV4GB normally and it works every time. The moment I try to load any of them through Mod Organizer, I get black screen and freeze on startup. As for my Mod Order... there is none. I'm only on the Extender section of F&LiNV. The only plugins are the DLC. EDIT: Neverind, I'm an idiot. Like an earlier poster, I didn't have all my BSAs checked on the Archive tab. *SIGH*

Basically it insists Steam isn't running when it is. It gives that error, runs anway, and only loads the Launcher rather than the 4GB version. I've even tried using the -laa argument option the guide suggests. Any ideas? EDIT: Fixed old problem, have new problem. Similar enough I'm not starting a new thread. FIX FOR PROBLEM #1: Set Mod Organizer to "run as administrator" under the compatibility tab of it shortcut. New Problem: Game starts to black screen, immediately freezes and locks up. Have to restart to make it go away, as not even Task Manager can kill it.

... It's possible. Yeah, they remind me of the VEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEEERY distant road textures, just seen way up close. I deleted DynDOLOD from my previous "messed up" install, tried the fix you recommended. Both script seemed to work. No errors, that I saw, at least.

I'm using a stripped down version of it. Only PerMa, the patches, the Dual Sheath Patch, and the Extended Perk Descriptions. Only issues I'm currently having are texture-based, so I'm pretty sure PerMa's not responsible.

So far SRLE is running pretty good. I get the occassional FPS hitch, mainly in combat. But I've noticed an issue. After playing for an hour or two, textures start to get.... weird. For example, I'd finished bopping around Riverwood, clearing out the barrow and Orgmund's Tomb (mod). I go to Whiterun, and the game looks great. On my way up to the city, I turn to encounter the Companionis, then when I turn back, the road I was just on looks... extremely low-res AND is floating a good inch or two off the ground. As I turned and surveyed, i'd notice on one pass, a stone would look good, then on a second, it would look like the road. Any thoughts on what could be doing this?

So I'm using the Optimized Textures off Nexus, as recommended by SRLE. Now that I'm done modding and gotten my game working, i noticed something. In Mod Organizer, all the packs have the greyed out lightning bolt next to it, indicating that they're redundant. I think all the texture mods have replaced everything in them. So... do i need to still be using the optimized textures? or should I just deactivate them?

Well to be fair, I can't test that fix until I get off work, but I'm 99% sure I made that error.

... *facepalm* I always missed the questions on math tests by forgetting to carry the one. Nice to see that trend hasn't changed.

Yeah, you see, I've done that already. I set MO with the Argument field -o "D:\TES5 Output" It just ignores it. Heck, I even made a C:\Output directory just to see if THAT would work. Nope.

Okay, apparently my TES log is too big to upload. https://drive.google.com/file/d/0B81iBpRZ5qDfUjlXT09ZaW02b1E/view?usp=sharing Okay this is weird. in TES5Edit, it's only DynDOLOD TexGen and the Vivid Snow scripts that don't seem to see anything. MergeScript, DynDOLOD World, and Real Shelter scripts all run beautifully.

Here's my LODGen file. I was figuring it was some kind of MO problem, but I've gone over ever tutorial video I can find, and I'm setting it up exactly right, at least according to them. *headscratch* LODGen_log.txt

I'm having a weird problem running the DynDOLOD TexGen script. I'm using SR:LE from this wiki as my guide, following it EXACTLY. I get the DynDOLOD TexGen step... and when I run it i get "Records Processed: 0; Time Elapsed: 00:00". No error message, no crash. It just doesn't find anything to process. But I've loaded all the mods. I've got the Billboards for Vanilla, Vurts, and RAT installed and activated. Yet nothing. When I go to run the Worlds script it runs okay, but it can't find a lot of the LODs for certain trees, i'm guessing because the first script didn't work. I've watched the Quick Launch video and followed the steps in Neovalen's guide to the letter. No idea what I'm doing wrong.

Yup.

Yeah, that's what i did the first time. Everything worked fine, but SkyProc. Weird.

The problem was in the mlink setup. Once i moved it back to the steam directory, everything worked fine. Anyone know how to setup Skyrim on an SSD without breaking MO?

They are. The only thing "weird" i'm doing is that i'm running Skyrim off my SSD with a mlink setup to the usual Steam install folder. But everything ELSE is working just fine, and not having any issues with that setup. I'm running on Windows 10, but that didn't matter last week when I was working on this. Yes, I'm running the latest 32-bit version of Java, and yes when i try to run the patchers separately, I try using the 32-bit Headspace bat files provided by the authors.