OH72

I've tried both. When initially, the game didn't show me the savegames anymore, I activated profile-specific savegames and manually copied the savegames into the profile savegame folder, so that they are in both locations. As I've shown above, MO2 has no problem finding the saves. They are listed in the savegames tab. I've also disabled cloud saves in Steam (and re-enabled, and disabled again, didn't change anything). The only saves that I see once I start the game are the ones in the picture below

The problem isn't that files were "lost" in that sense - I know where the save games are. They are - since I manually copied them - both in the MyGames folder and in the AppData\Local\ModOrganizer\SkyrimSE\profiles MO2 sees them (cf. picture), but when I run SSE, even from MO2, it doesn't see them.

As I had huge files in \Documents\, I've disabled automatic syncing of the whole folder long ago. As I said, when I go to my OneDrive folder itself, there's only a Fallout4 folder there, the SSE folder is absent, as are all other folders. And the Fallout4 folder just has the default content the game installed on installation and isn't up to date in any way. I also have the Business version of OneDrive independently of the personal one, but that's syncing its own folder only anyway and isn't going anywhere until I have a NAS, because it's what's preventing me from losing my work in an HD crash - and I've had some of those.

Do you have a link?

OneDrive shouldn't be monitoring those folders. The only content of MyGames on OneDrive is for Fallout4.

I did that. As I said, I even copied the saves, so at the moment, they are in both folders. MO2 sees the save games, as I said, they are in MO2's savegame tab. But for some reason, the game itself doesn't see them.

Played SSE yesterday without a problem. Started the game through MO2's SKSE for SSE today, and suddenly the only savegames I am shown are some cloud saves that seem to have happened while testing mods. The save games are in MyGames, and by now, I've also copied them into a profile-specific folder in MO2's appdata, they are SHOWN in the savegames tab of MO2, but the game will find neither copy when started, only the always same two saves, and none of the 25 regular saves plus my three autosaves plus a quicksave that are there. Any ideas?

I downloaded A Quality World Map, first directly through the Organizer, then manually. In either case, the mod didn't install. Whether doubleclicking on the download section or making a manual install, nothing happened. The log file read: 00:36:17 [D] looking for plugins in C:\Program Files (x86)\Steam\steamapps\common\Skyrim\Mod Organizer\plugins 00:56:02 [D] using mod name "A Quality World Map and Solstheim Map - With Roads" (id 4929) -> A Quality World Map - New Installer-4929-8-4.7z ModOrganizer used was v2.0.8.3

I have been "playing" the game for a few minutes for testing purposes, installing mod by mod. Then I ran BodySlide and now the game refuses to run. So while MO may have passed all the previous changes correctly to the game engine, it's far from given that this is the case for the changes made by BodySlide. As it stands, running BodySlide through MO was the last thing I did before the game started crashing reproducibly. I'm baffled how BodySlide could provoke such changes, which is why I'm asking here.

Hi all. So I was just rebuilding my game mod by mod using MO, always running the game for a few minutes to allow MCMs to build and check for game stability. Everything fine. Then I ran BodySlide and suddenly, I reproducibly crash on gamestart, usually after the dragon symbol appears but before the menu shows up. Repeated about a dozen times by now, i only reached the menu once and then crashed on save load. Due to the early crashes, there's barely anything in the Papyrus log: [09/23/2016 - 01:26:39PM] Papyrus log opened (PC) [09/23/2016 - 01:26:39PM] Function GetEffectMagnitudes in the empty state on type Ingredient does not exist. Function will not be flagged as callable from tasklets. [09/23/2016 - 01:26:40PM] Update budget: 1.200000ms (Extra tasklet budget: 1.200000ms, Load screen budget: 500.000000ms) [09/23/2016 - 01:26:40PM] Memory page: 128 (min) 512 (max) 76800 (max total) [09/23/2016 - 01:27:06PM] Cannot open store for class "ddunequiphandlerscript", missing file? [09/23/2016 - 01:27:06PM] Cannot open store for class "ddunequipmcmscript", missing file? [09/23/2016 - 01:27:11PM] Cannot open store for class "follower3dnpc", missing file? [09/23/2016 - 01:27:12PM] Cannot open store for class "_arissa_inpc_behavior", missing file? [09/23/2016 - 01:27:12PM] Cannot open store for class "chherdingquestscript", missing file? Now I'm a bit baffled how running BodySlide could have that effect. Especially after the mods I installed before that, I restarted the game several times, and it worked reasonably well. And to revert the changes, do I simply delete the meshes introduced?

I just updated Frostfall to 3.0 and now Mod Organizer is complaining because DynDOLOD expects Chesko_Frostfall.esp. Is there any way to remedy this without going through the whole installation process again?

Ok, for whatever reason, updating MO was sufficient to make the game realize it was there again... which makes this problem solved. Unfortunately, one of the original problems which triggered the whole affair still remains.... but that's a different issue... The issue is solved now, so I'm marking it now...

These are present, and the mo_path.txt is correct. Will check the other points.

Anyone else with an idea?

As I pointed out above, I'm using the Steam version, so I don't launch from within MO, but rather from Steam, using the ScriptExtender workaround. Of course I use OBSE, and here's what's in my plugins folder: Not sure why the image doesn't load, here's the link: https://drive.google.com/file/d/0B5La8b7zAKTseURBaW5QZVhhZmM/view?usp=sharing Naturally, I did not regenerate the ini from a launcher launched from within MO, since I can't launch from within MO. But as I stated, the old ini in MyGames, of which I evidently kept a backup, works even less, it leads to CTD at game start.