Is SkyUI compatible with GOG's version of Skyrim SE? I'm having trouble getting it to work. Here are the steps I followed:

1. I installed Skyrim SE using GOG Galaxy.
2. I installed SKSE using the "Current GOG Anniversary Edition build 2.2.3 (game version 1.6.659)" from skse.silverlock.org
3. I downloaded SkyUI "SkyUI_5_2_SE" from nexusmods: www.nexusmods.com/skyrimspecialedition/mods/12604?tab=files
4. I unpacked "SkyUI_SE.esp" and "SkyUI_SE.bsa" to "<INSTALLATION_DIR>/Data".
5. I ran the game via "skse64_loader.exe."

The SKSE seems to be working, as it prints the SKSE version number in the pause menu. However, SkyUI is not working, and I still have the stock inventory menu. Am I doing something wrong?

Yes, it's compatible. The problem is that you did a manual installation, so you would need to activate the mod manually by editing some text files...

It is recommended to use a mod manager, managers will handle everything automatically, without the need to edit anything.
"Vortex" and "Mod Organizer 2" are the most popular ones, both support Skyrim GOG version.

Vortex is probably the easiest to get started with, while MO2 has some advanced features (which can be confusing for beginners).

Gamerpoets have video tutorials teaching how to use them:
https://www.youtube.com/watch?v=4NlSuXy_SFU&amp;list=PLlN8weLk86XjD_Wi9PsU_KYCuZqiaDos2

Look in (your username)/appdata/local/Skyrim Special Edition GOG/

You should have two files there, plugins.txt and loadorder.txt.

If they're not there, that's the problem, let me know and I'll explain how to fix it.

edit -- while I was typing this someone suggested using Vortex, good idea. There were a few more hoops to jump through back when SSE GOG was released, hopefully that's been fixed in the current Vortex.

The answer to your first question is yes, SkyUI works fine in SSE GOG.

Thanks for your interest in my problem. I'm familiar with MO2, so I installed it, then installed SkyUI through MO2, and ran the game (Skyrim SE GOG) via the SKSE launcher. However, the result is the same as with a manual installation - SKSE is working, but SkyUI is not working. Am I missing any steps? "AppData/Local/Skyrim Special Edition GOG" exists but is empty on my system.

OK, if you have another folder in appdata/local named "Skyrim Special Edition" (minus the "GOG") MO2 may have put the loadorder/plugin files there.

If so, copy them to the "Skyrim Special Edition GOG" folder and SkyUI should work.

If that works, then follow the instructions in this topic to create a registry entry and symlink to "Skyrim Special Edition GOG", mods should then work normally.


https://www.gog.com/forum/elder_scrolls_series/how_to_make_skyrim_seae_work_with_all_mod_tools_like_sseditlootetc

Thank you for the solution, unpacking "game_skyrimse.dll" to the "plugins" subdirectory of MO2 made SkyUI work! :)

Unfortunately, this fix has caused a new problem, where the language of the game keeps changing to English, and I would like to have the game in Polish. Is there a setting or command line switch that would force the game to a particular language?

Also, a little off-topic, are there any mods that do not work with the GOG version of Skyrim SE but work on the Steam version? I have seen people mention this in several places, but I would like to know if this is still the case.

In the Skyrim.ini file C:\Users\Username\Documents\My Games\Skyrim Special Edition GOG\
under [General] it should have sLanguage=ENGLISH (can't check, I don't have the GOG version installed any more)
I don't use MO2, but it might have a Skyrim.ini file that overrides the default one. Yes. That's the reason I uninstalled the GOG version.
Any mod that injects a .dll file needs to be made specifically for the GOG version, and I think those that haven't been by now, probably never will be.
A lot of the NPC mods I use require Enhanced Character Edit which has not been made available for the GOG version, so I've just stuck with my steam version.

As far as "replace the game_skyrimse.dll" in the plugins directory, I'm not sure what versions of MO2 and the dll MO2 this worked for because this caused my MO2 to crash, because it recognized the dll as an incorrect dll. This was tested on my system that runs Windows 7 Pro with several versions. The solution I found was to update MO2 to a version 2.5+ and I did get it working, but that was done on another PC running Windows 10 Pro because MO2 now lacks compatibility.