Note for Flatpak users: If you're using Steam Flatpak, you may need to use the S drive when choosing the staging folder path. Do not attempt to install Vortex from Steam Deck Game Mode, ever. NET 6, and once installation completes, restart Vortex. Make sure you follow Vortex's instructions to install. The current minimum recommended Proton version for Vortex is GE-Proton8-2. Side-note: steamtinkerlaunch also has built-in support for Mod-Organizer 2, which does not have support for as many games but may work more reliably on Linux. But I'm downloading from the DefEd section on Nexus.Vortex Mod Manager (Vortex) is a mod manager for multiple games on Nexus Mods. Unless it's like you said before, the mods being for the Classic edition and don't work in the Definitive. But they don't work from there.Īnd it's not just that they aren't shown in the mod menu ingame, they don't work at all, the containers still look vanilla, have backgrounds and stuff. I guess if I was to extract them manually, I would do that the same way. Well Vortex in fact didn't create those folders on it's own, it COPIED them from the downloaded mods, it extracted the mods there into the Definitive Edition mods folder in the Documents. These don't work for me from the Mod folder in Divinity Original Sin 2 Definitive Edition in the Documents section. The "pak" mods (all from Steam Workshop) are in the mod menu in the game, but nothing from Nexus. But it created folders called "Public" and "Shared" and "NativeMods" and whatnot and in game it doesn't even show up, that there should be some "No background in containers" mod and others. Sorry for misleading you there, I have the mod folder already in "Documents\Larian Studios\Divinity Original Sin 2 Definitive Edition\Mods", it's the same folder as those "pak" files are in, Vortex might be anything, but for once did it right.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |