CayugaDuck
-
Posts
16 -
Joined
-
Last visited
Everything posted by CayugaDuck
-
Great, this makes sense. Thanks for informing me! I'm glad to learn that MO2 acts this way so I don't get confused again in the future. Yes, I understand now. Thank you very much. This clears everything up for me. It's also good to now be aware of how to access the file paths if I ever need to. Much appreciated for your help, once again! -
Some more information that may be important: I was speaking with a friend who also does modding, and he mentioned how MO2 tends not to save the modded files directly in the base data folder, and that each instance has its own set of file directories. Is this true? They also mentioned that what I was used to may have been a leftover from when I used Vortex instead of MO2, which puts all the modded folders directly into the base data folder. So, perhaps what I was used to was a leftover of Vortex (such as the presets being universal instead of per-instance), and when I reinstalled the game, it got rid of those old Vortex file directories I was using, not knowing that it was leftover from then. Am I correct?
-
Recently, starting in Feburary 13, 2025, had CTD issues with my Skyrim Special Edition modded instances through MO2, and when I was troubleshooting, I deleted and reinstalled my whole game, which seems to have caused a weird disconnect between the game's Data folder and the data folder MO2 calls for. For some reason, when searching for the Data folder through the normal file explorer on my computer, the folder is devoid of any files relating to my mods, other MO2 applications, and even SKSE. What's the strangest part is that if I open the data folder via MO2's "Explore Virtual Folder" feature, all of the files are still there and appear to, for the most part, be working properly. I only noticed an issue when attempting to load my saved racemenu presets and the majority if them didn't show up in-game. Checking the CharGen folder through the "Explore Virtual Folder" function shows that my presets are mostly gone for some reason. Even when I restored them from a backup save I had, they seemed to be reset after loading another save/instance. I tried copying the data files from the Explore Virtual Folder menu and pasting them back into my file explorer data files, and it said that I was trying to paste the the same directory and there was nothing to paste. I also tried making a copy of the Explore Virtual Folder data folder onto my desktop, but when it finished, it appeared the same as my data folder when viewed via my regular file explorer: none of the MO2 or modded files were there. I will note that I do have a backup of my entire Skyrim Special Edition folder from February 13, assumedly before I reinstalled the game, and the data folder appears to be intact. Should I restore my current data folder from this backup? I don't want to do anything rash before I have a better idea what is going on. Here are screenshots of the data folder through my file explorer, and the data folder through Explore Virtual Folder: I am very confused why this is, and why there is a disconnect between the data folders, and why the game seems to work even though I can't see any of the proper files on my computer. Please advise!
-
Yeah, I used ESET before in the past but it was part of a work license, so I do not have access to it anymore. I will corroborate that I had no issues back when I had ESET. Just glad this seems to be the fix we were looking for.
-
Yes, I do use Bitdefender and I was unaware of the Advanced Threat Defense feature. I did as you suggested, adding the provided files to the exception list, and the CTD error continued. BUT, by disabling it completely, my game was able to boot properly! Even was able to load into a save, everything loaded no problem. Tried it with my un-modded instance, as well as my regular gameplay instances. With the Advanced Threat Defense disabled, the game is able to boot, as well as LOOT, FNIS, and Nemesis. Very frustrating! There were no errors or any indication that Bitdefender was interfering with my files like that. Ideally I would like to figure out exactly what it is blocking so I don't need to keep the AVD off entirely, but I am just happy we have seemed to determine what the problem is. If you have any suggestions to what other files or directories I can add to the exception list, please let me know. I really do appreciate all the assistance you have given me. Thank you very much! Edit: Tried adding my base Skyrim Special Edition and Mod Organizer 2 file directories themselves to the exception list, and it was still having the CTD issues, so it seems that keeping it off completely is the only fix as of right now.
-
Here is what my D:\SteamLibrary\steamapps\common\Skyrim Special Edition path looks like, as well as the D:\SteamLibrary\steamapps\common\Skyrim Special Edition\Data looks like: Something I notice immediately is a Veeam vdf file (A file backup software) in my Skyrim Special Edition folder back from February 13th, which is the same day I started to have the CTD issues. But what makes that confusing is that the same file is in my Fallout 4 folder, a game which boots totally fine, so I don't see how that's the issue. If there is anything else that seems out of the ordinary, please let me know. I tried running all three executables, SkyrimSELauncher.exe, SkyrimSE.exe, and skse64_loader.exe directly from the file explorer in the order you specified, and all three still have the same CTD issue upon booting. I also created another un-modded test instance with archive invalidation disabled, profile specific INIs, and it changed nothing. Same CTD. I will note that upon creating all these new instances, this pop-up appears and I've just been pressing "Do Nothing" for all of them. Again, I don't see how this could be the issue because all my gameplay instances were running fine long before the CTD issues and this doesn't seem to change anything. I think the FNIS and Loot errors are notable in that they indicate there is some problem with MO2 reading or writing Skyrim SE files. I can't think of why or what would be causing that. I did set the Skyrim appmanifest file to "Read Only" such that my game would not automatically update, but I did that long before the current CTD issues. I have also set my Fallout 4 appmanifest to "Read Only" and the game works fine through MO2. That's really the only thing I can think of, otherwise I am really at a loss.
-
Did this, still had the CTD. So I guess it's not the configuration files?
-
Upon my first troubleshoots before/after reinstalling I ran the game through steam (which loaded fine, as well as loading a new game without issue), as well as verified the integrity of the game files. The issue persisted. I will admit I am not very savvy when it comes to advanced MO2/SkyrimSE settings, so I would be unaware of any leftover binaries or what that would involve. I'm not sure what setting a profile and enabling the profile specific saves/INI files would entail, or if it would mess with my current save games or game data. Again, I checked my modded FO4 instance, which loads fine, and it too uses a default profile. The only difference is that us uses profile-specific INI files. My usual Skyrim playthroughs that have been encountering the CTD problems also have the profile-specific INI files option selected. Is there anything out of the ordinary I should be looking for in \Documents\My Games\Skyrim Special Edition? Here's what the base directory looks like:
-
That's weird, because my Fallout 4 paths for "Managed Game" also ends with the game application, "Fallout4.exe" and works fine. How would I set it to just the folder directory? It seems to only allow me to select an application or file rather than a folder by itself.
-
All my usual instances are found within the default userprofile appdata paths. I was just creating instances in C: as recommended. Like I said, it seems to be some kind of esoteric read/write or disconnect error with MO2 and Skyrim specifically. The file paths never was an issue in the past and I haven't changed anything since it was working a few months ago. I literally was able to play my game fine, didn't play for a few months, and then it started breaking like this. It has to be some kind of error or change that happened externally with Skyrim that is messing up MO2, I just cannot think of what it could be.
-
When I created this "Skyrim Special Edition (test no mods)" instance, I did make it a global instance and set the file path to C:. Here is the "Base Directory" field for this instance as requested: I also created an un-modded portable instance with the same directory, C:. I attempted to run the game through there for both SKSE and the base Skyrim SE Launcher, had the same CTD issue. Here is an image of the paths and logs for this portable instance: I am beginning to think this has to do with some disconnect or file read/write error between MO2 and Skyrim, since it only seems to break when I run this game specifically, modded or un-modded, through MO2.
-
This is the new instance I have created with the shortest file directory possible (C:/ModOrganizer2). I have no mods installed. Nothing is enabled. I run the game via the MO2 Skyrim Launcher and get the CTD. This is the Log when launching. Is there anything out of the ordinary? I see the error for the ini, but I don't know if that is the issue here. Edit: I just noticed that the path is the default AppData/Local path even though I told it to locate in the base C: drive. Weird. But again, that has never been an issue in the past
-
Yes, I used a global instance and didn't change the default directory. Creating a portable instance as you recommended led to the same crash issue for both the default launcher and SKSE. I installed SKSE as instructed by this video: This is how I have installed it in the past with no problems. The CTD issue began with an install of SKSE that was working merely months before. I attempted to uninstall and reinstall SKSE when the issue began ensuring I was downloading the correct version for my game (skse64_1_6_1170), and the issue persisted. As suggested, I added 489830 to the "Overwrite Steam AppID" and nothing changed. I am really at a loss. It has to be some issue with Skyrim SE specifically, since my Fallout 4 is fine through MO2, but it seems like it isn't just the mods, since a non-modded instance has the same problem. Very confusing.
-
Just tried this by adding a rule for both usvfs_proxy_x64.exe and usvfs_proxy_x86.exe in my Bitdefender firewall allowing access, and still have the CTD before reaching the main menu. I am not sure if this is what you mean by Windows quarantining the exe, so if I am missing something, please let me know.
-
Sorry for the late reply, I wasn't getting email notifications and haven't checked back in a while. "Is MO2 and the game installed outside any Windows protected folders. Like Program Files." - All my instances are stored in my C: drive under Users/"my computer name"/AppData/Local/ModOrganizer. My main MO2 folders ("Mod Organizer 2" and "Mod Organizer 2 Game Directory") are located directly in my 2TB D: drive. It's been this way for years and I've never had any issues. I am also still able to run my Fallout 4 instance through MO2 just fine. The FO4 instance is similarly stored in the same directory as my Skyrim SE instances. "Have you created a new profile and disabled all mods, including skse, and tried to launch the game from the launcher?" - Yes, I created a new instance with 0 mods enabled, and attempted to run the game via "Skyrim Special Edition Launcher" in MO2. I have the same CTD issue before reaching the main menu. "Sometimes Windows has a habit of quarantining usvfs_proxy_x64.exe. Check that this is not the case." - I have tried to run the game with all of my firewalls/antiviruses disabled, and still had the same issue. I will try to whitelist this file and get back to you.
-
I am having a strange crash-to-desktop error when trying to boot skyrim through MO2. Whether I try and run the game through skse_64 or the regular launcher through MO2, the game boots until the Bethesda logo, then crashes to desktop before the main menu. The same error occurs when I tried to make a new instance with no mods, both for skse launcher and the regular skyrim launcher through MO2. The game is able to successfully boot to the main menu if I launch the game from steam (and I am able to start a new game fine), or directly run the skse_64 exe from my files. Another strange quirk is that other applications like FNIS and LOOT crash when I attempt to run their functionality. FNIS crashes when I click “generate” and LOOT crashes when I try to sort the load order. I tried to see if it was a strict MO2 issue by seeing if my modded FO4 would run, which it did perfectly. Other than the inability to fully boot Skyrim, I cannot tell if there are any other issues with my mods or load order or anything as the crash doesn’t return any error message. I have tried reinstalling SKSE, I updated MO2 to the latest version, and completely uninstalled and reinstalled Skyrim, to no avail. My game was working fine last I played in late September, since then I haven’t touched anything. All I have done was set my skyrim steam appmanifest file to read only to avoid updates, which hasn’t been a problem on the past. I am truly lost as to what the issue could be. If you require additional information from me, I’d be happy to provide.
