Nov 06, 2016  I have Skyrim Special Edition installed in my Steam folder. I have downloaded the brand new version of Loot 0.10.0. I have made sure to delete any old Loot folders from version 9.2 in my User folder. I start Loot and it does not detect my Skyrim SE game. I tried manually adding Skryim SE to Loot and pointed to the Skyrim SE directory under Steam.

1. Why Is Loot Not Detecting Skyrim Se
2. Loot Not Detecting Skyrim Settings
3. Loot Not Detecting Skyrim Season

Good morning.I have been trying to run the latest release of LOOT on my computer but LOOT fails to detect TES V: Skyrim and LOOT will not recognize TES V: Skyrim if I manually input the path. The odd thing is that LOOT doesn't crash when I start up the app but LOOT will crash if I attempt to do anything with the UI.Here are the paths I manually tried inputting for TES V: Skyrim:. C:Program Files (x86)SteamsteamappscommonSkyrim. C:/Program Files (x86)/Steam/steamapps/common/Skyrim. C:Program Files (x86)SteamsteamappscommonSkyrimData. C:/Program Files (x86)/Steam/steamapps/common/Skyrim/DataBefore anyone asks I have installed both MSVC 2015 x86 redistributable and 7-Zip.

To ensure UAC was not causing problems I tried running LOOT as administrator before uninstalling and re-installing LOOT to the root of the C: drive. However the problem persists.I don't know if this helps but I ran an earlier version of LOOT.

I believe it was release 0.9.2. It worked like a charm.

I went back to that version and installed it to see if it would work after uninstalling release 0.10.2 and deleting%LOCALAPPDATA%LOOT but LOOT 0.9.2 does not work anymore unfortunately. It fails to work in the same way release 0.10.2 does. I see the same issue across the board:0105/055359:ERROR:maindelegate.cc(752) Could not load cefextensions.pakP.S. I'm using Windows 10 and here are my debug logs from%LOCALAPPDATA%LOOT.I'm open to all suggestions and helping you in debugging this issue in anyway possible.Thank you very much for your time and effort. Hi @WrinklyNinja.I didn't think it was an issue with the redist because if it is required than LOOT shouldn't launch at all given if there are aqueduct checks for all required dependencies when the app is first launched.

Hi @WrinklyNinja.I completely uninstalled LOOT 0.10.2 from my computer, deleting the%LOCALAPPDATA%LOOT directory, ran CCleaner, ran Skyrim launcher as per request, reinstalled LOOT 0.10.2 and it works like a charm now! Thank you so very much!I also like the enhancement request you opened. It would help describe the issue to the user so they would know what it is and how to remedy it. I was searching through the issues here on Github and searching for issues across the web. All the information about what helped others didn't help me at all. I really appreciate your time and effort towards this project. It really helps out modders like me who are new to the modding game.

Maybe one day when I learn more about C I can contribute on bugfixes and enhancements.Again thank you and Happy New Years!

Changed. Groups that contain installed plugins can no longer be deleted in the groupseditor. Clicking on a group in the groups editor will now display a list of theinstalled plugins in that group in the editor’s sidebar. An error message is now displayed for each plugin that belongs to anonexistent group. Game configuration can now include the root Registry key when specifying aregistry key. If no root key is specified, HKEYLOCALMACHINE is used.

Therecognised root keys are:. HKEYCLASSESROOT. HKEYCURRENTCONFIG. HKEYCURRENTUSER. HKEYLOCALMACHINE. HKEYUSERS.

Updated the Russian translation. Updated libloot to v0.14.6. Updated CEF to v74.1.16+ge20b240+chromium-74.0.3729.131.

Updated nlohmann/json to v3.6.1. Updated spdlog to v1.3.1. Fixed. Plugin counters would be set to zero after cancelling a load order sort. The user interface would not display default values for some data ifoverriding values were removed (e.g. Added.

An error message will now be displayed for any light plugin that contains newrecords with FormIDs outside the valid range for light plugins. A warning message will now be displayed for any plugin that has a headerversion that is older than is used by the game, to help draw attention toplugins that have been incorrectly ported from older games.

The header versionchecked is the value of the version field in the HEDR subrecord of theplugin’s TES4 record. A section to the documentation that explains LOOT’s sorting algorithm. Fixed. Creating a new group by pressing the Enter key after typing a name in theGroups Editor input field no longer leaves the group creation button enabled. Incorrect handling of non-ASCII characters in plugin filenames when gettingtheir active load order indices, which could lead to incorrect indices beingdisplayed in the sidebar.

Incorrect handling of non-ASCII characters in games’ LOOT folder names. Fixed. LOOT now checks that its game subdirectories are actually directories, notjust that they exist, erroring earlier and more helpfully when there issomehow a file with the same name in the LOOT data directory.

Windows 7 users can now update their masterlists again without having tomanually enable system-wide TLS 1.2 support. This was an issue after GitHubdisabled support for older, insecure versions of TLS encryption becauseMicrosoft didn’t enable TLS 1.2 support in Windows 7 by default. Fixed via theLOOT API. Fixed. Loading or saving a load order could be very slow because the pluginsdirectory was scanned recursively, which is unnecessary. In the reported case,this fix caused saving a load order to go from 23 seconds to 43 milliseconds(via the LOOT API). Plugin parsing errors were being logged with trace severity, they are nowlogged as errors (via the LOOT API).

Chromium console messages are now logged with severity levels that bettermatch the severity with which they appear in the console (via the LOOT API). Saving a load order for Oblivion, Fallout 3 or Fallout: New Vegas now updatesplugin access times to the current time for correctness (via the LOOT API). Changed. LOOT now stores its settings in a settings.toml file instead of asettings.yaml file. Changed.

If no game is detected when LOOT is launched and a valid game path or Registry key pointing to a game path is added in the Settings dialog, LOOT will select that game and refresh its content when the new settings are applied. Most exception-derived errors now display a generic error message, as exception messages are no longer translatable. Only metadata syntax exceptions still have their message displayed in the UI.

Improved robustness of error handling when calculating file CRCs. Improved consistency of error logging.

Why Is Loot Not Detecting Skyrim Se

Errors and warnings are now always logged, even when debug logging is disabled. The First Time Tips and About dialogs are now fully translatable, with the exception of the legal text in the About dialog. Updated Russian translation. Fixed. A crash could occur if some plugins that are hardcoded to always load were missing. Fixed by updating to libloadorder v9.5.4. Plugin cleaning metadata with no info value generated a warning message with no text.

The LOOT update checker will no longer display an empty error dialog if the update check is unable to connect to the GitHub API (eg. Changed. When saving a load order for Fallout 4 or Skyrim SE, the official plugins (including DLC plugins) are no longer written to plugins.txt to match game behaviour and improve interoperability with other modding utilities.

LOOT now uses Skyrim Special Edition as the folder name for storing its Skyrim SE data, to mirror the game’s own folder naming and improve interoperability with other modding utilities, and automatically renames any SkyrimSE folder created by LOOT v0.10.0. Updated Russian translation. Updated Chinese translation.

Fixed. When saving a load order for Fallout 4 or Skyrim SE, the positions of official plugins (including DLC plugins) in plugins.txt are now ignored if they are present and a hardcoded order used instead. Note that there is a bug in Skyrim SE v1.2.39 that causes the DLC plugins to be loaded in timestamp order: this behaviour is ignored. If the LOOT installer installed the MSVC redistributable, the latter would silently force a restart, leading to possible data loss. It was possible to open the metadata editor between sorting and applying/cancelling a sorted load order, which would then cause an error when trying to close the editor. The editor is now correctly disabled during the sort process. Changed.

LOOT now supports v0.10 of the metadata syntax. This breaks compatibility with existing syntax, which may cause existing user metadata to fail to load. Fixed. Cached plugin CRCs causing checksum conditions to always evaluate to false. Data being loaded twice when launching LOOT.

Updating the masterlist when the user’s TEMP and TMP environmental variables point to a different drive than the one LOOT is installed on. Incorrect error message display when there was an issue during initialisation.

Sidebar plugin load order indices not updating when sorting changed plugin positions. The “Has User Metadata” icon not displaying when priority metadata was changed. Fixed. Error when applying filters on startup. Hidden plugin and message counters not updating correctly after sorting. An error occurring when the user’s temporary files directory didn’t exist and updating the masterlist tried to create a directory there.

The installer failing if LOOT was previously installed on a drive that no longer exists. Changed. The content refresh menu item is now disabled during sorting. The conflicts filter toggle buttons have been removed from the plugin card menus, and the filter re-implemented as a dropdown menu of plugin names in the Filters sidebar tab. Enabling the conflicts filter now scrolls to the target plugin, which is no longer highlighted with a blue border. The layout of the Filters sidebar tab has been improved.

The CEF (3.2704.1427.g95055fe), and libloadorder (9.4.0) dependencies have been updated to the versions given in brackets. Some code has been refactored to improve its quality. Changed. Improved detail of metadata syntax error messages. Improved plugin loading performance for computers with weaker multithreading capabilities (eg. Non-hyperthreaded dual-core or single-core CPUs). LOOT no longer displays validity warnings for inactive plugins.

LOOT now displays a more user-friendly error when a syntax error is encountered in an updated masterlist. Metadata syntax support changes, see the metadata syntax document for details. LOOT’s installer now uses Inno Setup instead of NSIS. LOOT’s installer now uninstalls previous versions of LOOT silently, preserving user data, instead of displaying the uninstaller UI. Updated German and Russian translations. Updated libgit2 to v0.23.0. Fixed.

“Cannot read property ‘push’ of undefined” errors when sorting. Many miscellaneous bugs, including initialisation crashes and incorrect metadata input/output handling. Metadata editors not clearing unsaved edits when editing is cancelled. LOOT silently discarding some non-unique metadata: an error message will now be displayed when loading or attempting to apply such metadata. Userlist parsing errors being saved as general messages in the userlist. LOOT’s version comparison behaviour for a wide variety of version string formats. This involved removing LOOT’s usage of the Alphanum code library.

Fixed. The settings.yaml included with the installer was very old. Inactive incompatibilities were displayed as error messages. They are now displayed as warnings. Masterlist entries that matched the same plugin were not being merged. Now one exact match and any number of regex matches will be merged.

Masterlist updating failed when a fast-forward merge was not possible (eg. When remote has been rebased, or a different repository is used). Such cases are now handled by deleting the local repository and re-cloning the remote. Masterlist updating failed when the path to LOOT’s folder included a junction link.

Masterlists would not ‘update’ to older revisions. This can be useful for testing, so now they can do so. Crashes when trying to read corrupt plugins and after masterlist update completion. LOOT would crash when trying to detect a game installed to a location in which the user does not have read permissions, now such games are treated as not being installed. Plugins with non-ASCII description text would cause codecvt to wstring errors. LOOT would accept any file with a.esp or.esm extension as a plugin. It now checks more thoroughly, by attempting to parse such files’ headers.

LOOT would only detect Skyrim plugins as loading BSAs. Plugins for the other games that also load BSAs are now correctly detected as such. Depending on the plugins involved, sorting could produce a different load order every time it was run. Sorting now produces unchanging load orders, using existing load order position where there is no reason to move a plugin. Fixed. The uninstaller not removing the Git repositories used to update the masterlists.

Loot Not Detecting Skyrim Settings

Loot Not Detecting Skyrim Season

Miscellaneous crashes due to uncaught exceptions. Plugin priorities are now temporarily “inherited” during sorting so that a plugin with a low priority that is made via metadata to load after a plugin with a high priority doesn’t cause other plugins with lower priorities to be positioned incorrectly. The default language is now correctly set to English. Defaults for the online masterlist repository used for Nehrim. Endless sorting loop that occurred if some user metadata was disabled.