Обнаружена ошибка плагина script extender

Обновлено: 23.06.2023

3 мая. 2020 в 3:45

So anyway last night I was downloading some mods, and today I was going to play but then the game won’t launch. Vortex got an error saying exactly this, word for word: ‘Last time you ran the game, one or more script extender plugins failed to load. This normally happens when you try to load mods that are not compatible with the script extender. To fix this problem you can check for an update on the mod page or disable the mod until it is updated.

Error(s) reported: StorageUtil.dll (Campfire — Complete Camping System 1.11): not a valid dll (code 193)

Now I know for a fact that mod doesn’t need an update, so I did the only logical thing and disabled it, still no dice. So I did some research, a lot of people were saying to try a variety of different things, none of which helped (although some of the tips did put me a step in the right direction) however, one person said that installing mods made for the base 32 bit version of Skyrim won’t work with the 64 bit Skyrim SE, and indeed last night I did install mods made for the 32 bit version, so it sounds obvious right? Disable those mods, here’s where the problem lies, I have no way of knowing what those mods are, I could go back and check the websites, one by one, but with nearly 200 mods installed, that would take forever and I’m not willing to do that. There has to be an easier way, is there any way to check if a mod was made for Skyrim or Skyrim SE? Please help because I’m not willing to check every single website one by one, especially if it may not even fix the problem.

3 мая. 2020 в 4:10

First thing is to check that you are using skse64. If that checks out (you should only use skse64 with SE), then you should typically only install mods for SE. There are a few exceptions, but not many (some textures). Vortex will tell you which Skyrim version is associated with the mod.

3 мая. 2020 в 4:41

I’m unfamiliar with Vortex, but in this case it is giving the error in a manner I understand. Campfire is packaged with a defunct form of the noted dll. You must install and place this below it (in an overwriting position).

Depending on how Vortex works you may have to go so far as to hide the ancient util that Campfire packaged with. I can’t guide you how to do that on that manager.

Why can I not change the plugin load order directly (drag & drop)?

With Vortex, unlike other mod managers, you do not need to manually change the load order — Vortex sorts plugins automatically based on LOOT.

You can, however, control in what order individual or groups of plugins are loaded by either setting a dependency (i.e. declaring that one plugin needs to load after another) or by making use of groups to accomplish the same thing for several plugins at once.

Please consult our knowledge base for an in-depth explanation for our reasoning to opt for automatic load order sorting over the traditional dragging and dropping of plugins.

Why did you create Vortex instead of continuing Nexus Mod Manager (NMM)?

The short answer is that the code for Nexus Mod Manager is based on games that are now over 10 years old (Oblivion and Fallout 3) and, after numerous revisions, has become untenable, especially considering that the scope and standards for functionality we want to provide and add in the future have evolved massively in the meantime.

Please consult our knowledge base for a more thorough answer to this question.

Do I need LOOT/I want to use LOOT for sorting/Is there a difference between LOOT sorting and Vortex sorting?

As Vortex uses LOOT internally to sort plugins, there is no need for you to install LOOT. Vortex sorts your plugins based on LOOT and according to your own, custom rules (if specified). LOOT’s functionality is therefore already implemented into Vortex.

How do I use the various Script Extenders — SKSE, SKSE64, F4SE — with Vortex?

How do I add a tool to Vortex?

If you install certain tools such as FNIS, or SKSE in the default directories, Vortex may be able to detect them automatically. If the automatic detection fails, you can still add tools manually by simply navigating to e.g. the tool’s executable file in the respective installation folder.

Just like the Script Extender for Bethesda games, tools are added on the dashboard. Click the dashboard and navigate to the tool list where the preconfigured tools are found.

Press the “Add Tool” button to add a tool that is not preconfigured. If the tool is a regular Windows GUI application, then the “Target” needs to be set to the tool’s executable file. The “Start In” field should then fill in correctly automatically and reference the executable’s location.

Once you have set that, choose a name and save.

I’ve set up a tool but it’s not working. What can I do?

If the tool is not an .exe file, it cannot usually be run directly, but instead needs to be run through an «interpreter», such as Java for .jar files, Python for .py files, and cmd for .cmd or .bat files.

Vortex tries to support as many of these automatically as possible, but it can only support interpreters that are correctly installed and detectable by Vortex.

If Vortex does not automatically support your interpreter, you will have to put the path of the interpreter into the «Target» field and the name of your tool into the command line. In some cases further parameters might be required.

For example with Java the “Target” field should be something like.

. whereas the “Command Line” should read:

What can I do if Vortex fails to update/install?

The Vortex installer will be unable to write to the installation folder if some of the files contained therein are still in use by another process, such as for example antivirus programs, resulting in a failed installation.

Ensure that no security software is hampering the process (e.g., Windows Defender, BitDefender, Malwarebytes, etc.). Often, restarting your computer and/or updating or ensuring that Vortex related services and directories are ‘whitelisted’ can resolve these issues. Refer to the associated software’s website for more information.

Note: As part of the update process, Vortex will delete the Vortex folder (where the program itself is stored, not your mods and/or downloads) and, after that, install the new version. Should the update process fail, it is safe to simply download the newest available version from the Vortex download page and install it.

The installer will automatically detect the existing installation and update accordingly.

Can I have different mod profiles (for e.g. different characters) in Vortex/How do I set up profiles in Vortex?

Yes, Vortex does come with such functionality. To enable it, you need to access your settings and under “Advanced” toggle “Enable Profile management” on. This will add a new section to your sidebar under General called “Profiles” where you can manage your individual mod profiles.

I am getting an error saying “Plugins not sorted because of cyclic rules”. What does that mean?

This means that one or several of your custom plugin rules are contradictory. For instance, if you set plugin A to load after plugin B and plugin B to load after plugin A, the two rules contradict each other and Vortex will be unable to sort your plugin list and instead put out the error message “Plugins not sorted because of cyclic rules”. This can also be caused by cyclic rules regarding plugin master/slave relationships.

Alternatively, group specific rules can be the cause as well. In general, LOOT utilises elaborate rules to ensure a conflict free setup and will at times ignore conflicting group rules to achieve that end. However, at times LOOT will be unable to do that resulting in the same «cyclic rules» error.

As the internal LOOT sorting system Vortex employs is free of cyclic rules, this only occurs with rules you set up yourself.

If you click on “More” you will be provided with more information as to which plugins are affected by cyclic rules which should help you to resolve the conflict.

What does «deployment» (and “purge”) mean?

Vortex breaks the installation of mods into two phases. The first phase is the process of extracting the mod archive and going through the installer (if there is one). This phase places the files of the mod in a separate «mod directory» where it doesn’t affect the game yet.

In the second phase, «deployment», files are then linked into the game directory at which point they begin to affect your game’s installation. Also, mods that have been disabled will have their links removed during «deployment», so you can think of deployment as «committing» your mod selection to the game.

The reason Vortex does this is because the deployment phase can be done very quickly (usually taking only a few seconds) and it doesn’t require any further user interaction. This allows you to quickly toggle mods between «disabled» and «enabled» and change profiles without having to go through the entire installation process of all mods again.

After enabling advanced settings (Settings > Advanced > Enable advanced mode) you also get the option to “Purge Mods”. Purging is the opposite of deployment: it removes all the links Vortex previously installed. This is not a destructive operation and can easily be undone by clicking «Deploy Mods» to restore the links.

You can use this feature to prepare for a backup, if you want to keep your backup from containing the links, or if you want to restore your game directory to a vanilla state without uninstalling your mods.

I have installed a mod but the corresponding esm/esp doesn’t show up. What can I do?

Many mods, such as texture replacers, do not come with a plugin file (esp/esm).

If you are certain that the mod you installed includes a plugin file and it still does not show up after installation, it might be related to deployment. The Plugins screen in Vortex only shows deployed files. If you have disabled automatic deployment and not deployed manually after installing the mod, the plugin won’t show up in the list and the mod will not affect your game.

To rectify this, navigate to your Mods screen and make sure your mods are deployed correctly.

Vortex does not list DLCs in the plugins.txt file. Is this a bug?

This is intentional and should not pose a problem. The games will load certain esms automatically and in a hard-coded order so whether or not they are listed in the plugins.txt, and in what order, is irrelevant. Vortex does not list them in the plugin.txt as to not raise the false expectation that you are able to manually reorder the DLCs.

For that same reason DLCs have no «Enable/Disable» toggle in the Vortex UI.

(How) can I enable/disable/remove multiple mods/plugins/downloads at once?

You can Ctrl+Click to select multiple items, Shift+Click to select a range, or Ctrl+A to select all items in the respective lists. The buttons along the bottom of the table (and only these) will then affect the entire selection.

How can I stop Vortex from handling Nexus Mods links?

Just like any software, Vortex cannot be set to «unhandle» a protocol type once it has been set to handle it. Whichever application is the last to announce that it wants to handle a certain protocol type (Nexus Mods links, in our case), will take priority.

Therefore, rather than stopping Vortex from handling Nexus Mods links, you would need to force whichever mod manager you prefer to handle them instead.

Should I delete «x» files/folders from my Vortex installation?

No. All files and folders managed by Vortex have a specific purpose and removing them may cause unexpected side effects up to and including the application crashing.

I am getting a «Application state is invalid» message after updating. Is something wrong?

As Vortex is maintained and updated by the development team, more and more sanity checks are added to ensure orphaned parts of the application state are cleaned up properly. This is not an error and choosing the «Repair» option will take care of orphaned parts ensuring that your Vortex installation is kept up to date.

How is Vortex deployment different to Mod Organizer’s VFS?

Both methods achieve a similar result but go about it in different ways. The VFS used by Mod Organizer (originally designed by Tannin, Lead Vortex Developer) has been heavily customised to work with Gamebryo (Bethesda’s Elder Scrolls and Fallout series) games and popular tools for that modding scene. Using this approach in Vortex would have the following drawbacks:

• There is no stable high-quality VFS with a free-to-use licence.
• VFS methods require extensive customisation to work with different tools, hard links are supposed natively as they are no different to access normal system files.
• Diagnosing errors in VFS deployment is considerably more difficult.
• USVFS is a Windows-only feature, whereas hard links are supported on all platforms. This means Vortex would be easier to support Linux or Mac operating systems.
• USVFS can often trigger false positives on anti-virus software.
• Hard links have no performance impact on the game, whereas USVFS will access files considerably slower.

This is not to say that using VFS is worse or bad, simply that Vortex did not opt for this as a default deployment method.

You can quickly return to a clean data folder by «purging» mods (this option needs to be revealed by activating «advanced settings» in Settings > Interface > Enable Advanced Mode). Purging is not a destructive operation and can be reversed by redeploying your mods.

I am getting an error about disc space (error: ENOSPC: no space left on device). What is wrong?

Vortex will inform you when you are running out of disk space and won’t be able to perform tasks such as installing or deploying mods if not enough space is available. To address the issue, free up some space on your hard drive to enable Vortex to perform its tasks.

Vortex crashes with a white screen. What should I do?

Some users are reporting occasional crashes that manifest themselves as white screens inside Vortex. Often, users are in addition presented with an error message when Vortex is restarted. There are several, potential reasons for this occurring and the following outlines a couple of these scenarios with possible solutions and/or workarounds.

Cause: Vortex currently (up to 0.16.12) does not deal well with unhandled exceptions from the installer script. While Vortex should not crash in this case and instead report a proper error message, even if Vortex did handle the error correctly it is rather likely that the mod installation would still fail.

Solution/Workaround: Please send in a link to any mod that triggers this and as a workaround, see if there is a manual install option.

Vortex crashes when trying to open the settings page

Cause: This is possibly caused by running Vortex on Windows 7 without the «Platform update» (which is not included in service packs!) What happens is that the «Theme» settings page tries to acquire a list of installed fonts from Windows and due to an incompatibility between the outdated Windows 7 and the library we use to retrieve the fonts, Vortex crashes.

Solution/Workaround: The best solution is to install the platform update. Option 2 is to go to the extensions page and disable the «theme-switcher» extension.

Vortex crashes trying to install any mod

Vortex crashes when the game crashes

Cause: All cases of this occurring that we are aware of feature an exception code of 0xe0000008. This indicates the system is out of memory or has other memory related issues.

Solution/Workaround: If you are able to reproduce this issue, please check your task manager and see how much memory Vortex actually uses around the time of the crash. Vortex itself shouldn’t be allocating additional memory while it’s sitting in the background. If you find Vortex using more memory than it should, please report your findings via our feedback system or our support forums.

Next, please verify that you have Virtual Memory enabled in Windows (System->Advanced system settings ->Advanced->Performance Options->Advanced and that you either have the size managed by the system and there is enough free disk space for two times your RAM, or, if you have a custom size set, make sure that the max value is at least 2x your RAM. So if you have 16GB of RAM, you need room for at least 32GB of Virtual Memory.

If this is the case and you still see these crashes, you may want to look into freeing up memory while the game is running: Close all unnecessary applications (including Vortex) while the game is running. If the game is still crashing, disable the more memory heavy mods.

There is another possible cause: A hardware defect in your RAM modules or an incompatibility between memory modules and mainboard or too much overclocking. These kinds of problems can be extremely hard to figure out because they may occur inconsistently when your system is under load and actually accesses the broken bits in the module. The only way to know for sure if your RAM is ok and can deal with the clock is to run a proper RAM check.

How do you know if the RAM check is «proper»? If it is able to run under DOS and takes at least a couple of hours. There is no way to test the entire RAM from a Windows application and there is no way to do a stress test in a few seconds, any windows application that claims to test your RAM and is done in 5 minutes is unreliable.

My game is crashing after migrating to Vortex

This is not caused by Vortex. It is most often revealing problems with your setup that Nexus Mod Manager had hidden away or you have defined file conflicts differently to how the files were set up in NMM.

It is also possible that when removing Nexus Mod Manager, important files such as ENB/Reshade/Script Extenders were corrupted and require reinstallation (either with Vortex or manually).

Each setup is different and very hard to troubleshoot. We recommend finishing any game you are currently playing with your old mod manager and starting fresh with Vortex for your next game.

Why is Vortex blurry?

Vortex (and other Electron apps) may appear blurry, this is caused by the FXAA (Fast Approximate Anti-Aliasing) feature which is part of the Nvidia graphics software.

Follow the instructions, which are to update the mods in question so that they will work with the version of SKSE64 that you’re using.

l0udXD

I’ve been having trouble with this issue for a long time how can i fix this?

Attached Files

AugustaCalidia

Mayor of Talos Plaza

Follow the instructions, which are to update the mods in question so that they will work with the version of SKSE64 that you’re using.

Vvandemarr

i have this problem how tyo fix it. extratools .dll (manually installed) not a valid dll (code 193)

chip594

Follow the instructions, which are to update the mods in question so that they will work with the version of SKSE64 that you’re using.

I tried that, tried doing a quick update check, full check, even checking manually. They’re all updated. I took a screenshot:

Edited by chip594, 22 May 2020 — 01:36 PM.

AugustaCalidia

Mayor of Talos Plaza

What happens if you just click «Ignore»?

GreenStarRiot

I’m having this issue as well and I’m not sure why, because everything is updated. I’m going to try reinstalling the mods that the plugins are broken for I guess

Pickysaurus

Isn’t code 193 implying you’ve installed the plugins on the wrong version of Skyrim?

GreenStarRiot

I think so, but my mod is supposedly for SE version so I’m not sure why that would happen. It’s the most up to date file I could find.

Kourtana

Im having a similar issue as well, except it is for these plugins:

These plugins also causes all animations to fail and everyone is at the stiff t-pose. I believe this may have something to do with FNIS based mods, but im unsure which one is causing it.

If you need my load order, I am more than happy to provide when asked!

horacio6siix

Пробовал переустанавливать? Она у тебя находится непосредственно в папке с игрой? Совместимая ли у тебя версия OBSE? (вообще -то вы должны задавать вопросы, а не я))
Может я попробую прислать тебе версию, которая у меня?

гдето нашел плагин к обсе 0015 и в описании ссылка на 0005
а вообще ЗИ (лицензия) + нодвд + обсе = пашет

Начал снова играть в Облу после 2-х летнего перерыва. Решил накачать модов и плагинов.
Но вот не пойму, что за дополнение «OBSE» и почему без него нельзя устанавливать некоторые другие моды?

Что оно из себя представляет?

Er Nesto Pitchfork, аналогично… Сижу, изучаю, качаю, вношу изменения

OBlivion Script Extender — набор скриптов, которых нет в стандартной Обле. Это не дополнение, а прога, сама запускающая облу и отслеживающая работу скриптов.

К OBSE вообще полезно ставить Wrye Bash и «предупреждалку», т. к. иногда (и такое бывает, хоть OBSE и «теневая» программа) Обливион на ОБСЕ реагирует не очень хорошо, и например при выходах из игры выдаёт ошибку.

Ошибка на выходе — вещь привычная и, в отличии от самой OBSE, на геймплей влияния не оказывающая. Неужели с Wrye Bash ошибка на выходе исчезнет? o_o

Хицугая, я выше ссылку дал. Качай Stable или Beta Version и будет счастье. Содержимое распакуй в папку Oblivion и для запуска Облы кликай obse_loader.exe

Блин, народ, помогите.
Долго не решался устанавливать ОБСЕ, так как не доверял ей. Вот недавно все же установил что б добавить в игру несколько модов.
Так у меня теперь проблема: при выходе с каких-либо подземных локаций (пещеры, форты, шахты) у меня «благодаря» ОБСЕ не загружает текстуры. Точнее: мой перс видит только компас и линейку жизни/силы/выносливости, все остальное — черное.
В таких ситуациях я пытаюсь загрузить последний сейв, но иногда и он криво загружается — тоже все вокруг чернее ночи.(((
Выход только один: выхожу с игры и захожу в последний сейв стандартным способом (не через ОБСЕ). Тогда персонажем выхожу с подземной локации, сохраняюсь, и снова выхожу с игры чтоб теперь зайти в нее через ОБСЕ.((( Долгая история, но хуже всего то, что некоторые моды тогда нет смысла устанавливать.((

Может у кого-то такое уже было. Помогите.

Er Nesto Pitchfork
А почему ты собственно винишь в своих бедах именно OBSE? Возможно дело в подключенных модах или в самой игре. Я, например, протестировал у себя свыше 50 таких модов, и нигде не наблюдал проблем с текстурами. Да и вообще OBSE это расширитель скриптового языка, каким образом он может воздействовать на текстуры? Еще хотелось бы узнать, какие именно OBSE-моды ты подключал.

Download curated lists of mods easily, our «Collections» feature has entered Open Alpha. Check our wiki to get started.

• All games
• Skyrim Special Edition
• Mods
• Bug Fixes
• SSE Engine Fixes (skse64 plugin)

File information

Last updated

Original upload

Created by

Uploaded by

Virus scan

Tags for this mod

9125 comments

• premium
• 6,018 posts
• 123 kudos

Updating these instructions for 5.3.3+:

BASE REQUIREMENTS: This is an SKSE64 plugin. Therefore, you need to have the correct version of SKSE64 installed to use this mod. If you are playing the Special Edition (1.5.x), you will need the latest SE version of SKSE64. If you are playing the Anniversary Edition (1.6.x), you will need the latest preliminary AE build of SKSE64. If you don’t have SKSE64 installed or don’t know what SKSE64 is, STOP. DO NOT attempt to install this mod until you know what the hell you are doing. Go learn what SKSE64 is and why you might want it here. Recent installation instructions video here. Come back once you are better educated and have SKSE64 properly installed.

(1) RECOMMENDED: Completely remove all files and uninstall any previous installations of SSE Engine Fixes prior to starting.

(2) DO a fresh download, install and enable/deploy of the required all-in-one Address Library for SKSE Plugins with your mod manager. You will need to install the latest Special Edition (1.5.x) OR Anniversary Edition (1.6.x) version of the Address Library depending on which version of the game you are playing. If you’re getting error 1114 or 617, it’s probably because you don’t have the Address Library installed or properly enabled.

(3) DO download and install the latest x64 version of the required Microsoft Visual C++ Redistributable for Visual Studio 2019 (on the linked page, it’s the download that reads x64: vc_redist.x64.exe). Install it even if you think you already have it installed. Yes, it’s a Windows install. Double click the downloaded file, follow the prompts, and yes you’ll need to reboot. If you’re getting error 126, it’s probably because you don’t have the C++ Redistributable installed.

(4) DO a fresh download, install and enable of Part 1 of SSE Engine Fixes with your mod manager. You will need to install the latest Special Edition (1.5.x) OR Anniversary Edition (1.6.x) version of Part 1 depending on which version of the game you are playing. EngineFixes.ini has been replaced with EngineFixes.toml in 5.3.3+. Open the UTF-8 encoded .toml file in Notepad to make your setting changes. You can delete the old EngineFixes.ini.

(5) DO NOT install Part 2 of SSE Engine Fixes with your mod manager. Instead, download it manually and EXTRACT the Part 2 zip, then copy and paste the 3 dll files from there directly into /steamapps/common/Skyrim Special Edition/. DO NOT simply place the zip file in that directory. DO NOT create a folder with the 3 files in that directory. DO NOT place the extracted files in your /Data directory. Part 2 is compatible with both the Special and Anniversary editions of the game.
OPTIONAL: If you are using Vortex, you can download and install Part 2 using the Mod Manager Download, but before deploying, double click the item in Vortex and change the Mod Type to Engine Injector. Then enable/deploy Part 2.

DO NOT RENAME your skse64 executables. If you have already done so, you will need to CHANGE THE FILE NAMES BACK to the original skse executable names. That means skse64_loader.exe and SkryimSE.exe. Skyrim.exe and adding an INI, as several obsolete guides tell you to do to get skse launching from Steam, WILL NOT WORK. SSE Engine Fixes needs the original skse64_loader.exe and SkyrimSE.exe file names and files.

If you want to launch from Steam, add skse64_loader.exe as a Non-Steam Game. If Steam is open you can also launch skse64_loader.exe from a shortcut or from the mod manager and still get achievements in your Steam SSE Library and the overlay. The original Steam SSE page will always execute the standard launcher, but you can still see your achievements and screenshots there if you launch via skse64 using one of these other methods.

If you are getting Error 193, you are running an Oldrim plugin and need to uninstall it and find the SE version.

If you want to verify that Engine Fixes is running ok, open your d3dx9_42.log in your SSE game folder. It should look something like below when Engine Fixes is running properly. Don’t worry about the line reading «failed to search dll plugin directory» — this just means you don’t have other plugins that use the DataDLLPlugins directory installed.

skse64 plugin preloader — d3dx9_42
exe path: X:SteamLibrarysteamappscommonSkyrim Special EditionSkyrimSE.exe
loaded into SkyrimSE.exe or SkyrimVR.exe, proxying SkyrimSE d3dx9_42 funcs and registering preload hook
success
hook triggered, loading dll plugins (meh’s loader)
failed to search dll plugin directory
DLLPlugin loader finished
hook triggered, loading skse plugins
found plugin «EngineFixes» for preloading
attempting to load found plugins
attempting to load «X:SteamLibrarysteamappscommonSkyrim Special EditionDataSKSEPluginsEngineFixes.dll»
loaded successfully and Initialize() called
loader finished

Читайте также:

  

• P1346 ошибка тойота 1nz

  

• Как проверить высоковольтные провода мультиметром на ваз

  

• Ошибка p1770 альфа ромео

  

• Ошибки на панели приборов газель бизнес

  

• Ошибка дроссельной заслонки пежо боксер