neiljwd

I'm just gonna write here to share knowledge, tho I'm sure it's been covered in the previous ten pages: If you have ANY textures/meshes in your standarard Fallout 4 Data folder (Steam install), then Mod Organizer 2 will FAIL to LOAD YOUR TEXTURES. I spent ages faffing and cursing. Turns out I had 1 tiny Pre-war Money Ttexture and mesh from a Mod that didn't come rar'd. And it was stopping any and all of my meshes/textures applying in game through Mod Organizer 2 Alpha for Fallout 4. Hours of tuning and fussing wasted over a 30 second fix :( Was frustrating coz .esps and such worked, just not textures. For what it's worth, I also read that sometimes having 2+ mods affecting the same file (a conflict) within MO can stop any appearing in game, not what I experienced but mentioned in the same place that uncovered the above problem for me. Hmm, is there an "official" topic to leave should feedback? I suppose th whole point of an alpha is bug testing...

Marvellous sir! I turned on 3.5 framework, and my problem 1 went away, MO reporting no errors. Thank you :) Didnt fix Bodyslide not being able to Save As in case any1 wonders, but I think the above is valuable information for all! I have a work around for being unable to "save as" within Bodyslide opened via Mod Organizer 2 Alpha, in case anyone else encounters it: Go to \Caliente's Beautiful Bodies Enhancer -CBBE-\Tools\BodySlide\SliderPresets within you MO Mods folder. Make a backup copy of CBBE.xml. Now you can edit CBBE.xml. Add new presets by copying a full preset, then just give it a new name. Or just change the names of some presets you don't use. You can now edit these sliders as normal, and just save to overwrite the main file with you editided in names.

They did not, adjusting them yieldwd no better results :( However I did then delete EVERY bit of MO that was in the app data folder, and this then let me re-install MO -yay! :: I'd over-looked it, as id set my paths to custom locations, and it hadn't been removed when i'd uninstalled MO. This does though leave me back where I started, with the problem in my 1st post. Ergo, I'm missing something to do with the .net framework- but not enough to actually stop MO from working/modding Fallout. But perhaps it's rlated to the fact the Bodyslide executable wont save AS... . If that makes sense to anyone.

Thanks for offering help! Sadly, I tried that, and creating a default folder within profile, didn't work. And as I said, I copied an installation of MO 2.04 Alpha across from another PC. It works 100% on my crappy 6 year old machine, but not on my spangly new Skylake. So that means there's something MY PC is missing, as opposed to the installation file being broken. Just hoping someone can identify this hidden dependency and save future people from this ball ache.

Well Darn, so I uninstalled it, and then reinstalled in C:\MO, as per your advice. It installed 1st time, which was nice, but now the program won't open. Just says "FAILED TO CREATE DEFAULT", same as this guy on github. I tried copying across an installation from my old PC, and it still creates the same error. So now im superstuck. Fix : Short answer: Uninstalll MO and all its files and MAKE SURE YOU DELETE C:\Users\USERNAME\AppData\Local\ModOrganizer folder! A re-install will hopefully then work. :) Long answer: Hi, I just had this issue, and 'fixed' it. I did a TONNE of stuff prior, that may have helped(unlikely mind), but I can only tell you my final few steps, that allowed me to have MO working again. First I completely uninstalled it, and all my path location for mods, cache, profiles etc. Turned out the very original ModOrganizer folder had remained in C:\Users\USERNAME\AppData\Local\, and hadn't been removed. Once I deleted that folder, I restarted my PC (and did a registry clean/fix in CCleaner, doubt that matters tho). After the restart, I ran the installer again, and it worked :) Hope this helps, please comment if it so other sufferers know to try it. :)

BACKGROUND I had MO 2.0.4 Alpha install just fine once, however had to reinstall windows, so I'm now on a 100% fresh Windows 10 Pro 64bit install, so it's very likely im missing some common core components. I am the only PC user, and an admistrator. MO is run as an administrator. Each of its 4 "paths" in preferences are NOT set as read only. Problem 1, install/dotnet. (solved) MO reports an issue with dotnet (for NCC) FIXED!: Turn on .network 3.5 Problem 2, saving via executable. My second issue is in regards to Bodyslide executable opened via ModOrganizer, I can't save as. No matter where to or what I name a Preset- I cannot save a new preset. Says "The filename is not valid" I can save tho, overwiting a preset, just not create my own new ones. I've tried both versions of bodyslide, normal and 64bit.exe, both set to run as administrator. It should be noted- this problem existed PRIOR to my above installation issue, when I'd installed MO alpha 4 fine. So apologies for this long winded double problem, tried to be thourough, please help!

Seems unlikely :

Thank you!

REmoved