Package Details: vortex 1:2.0.2-1

Git Clone URL: https://aur.archlinux.org/vortex.git (read-only, click to copy)
Package Base: vortex
Description: Nexus Mods' mod manager - native Linux build
Upstream URL: https://github.com/Nexus-Mods/Vortex
Licenses: GPL-3.0-or-later
Conflicts: vortex-git
Submitter: Tymon3310
Maintainer: Tymon3310
Last Packager: Tymon3310
Votes: 6
Popularity: 0.59
First Submitted: 2026-02-14 00:05 (UTC)
Last Updated: 2026-05-31 22:37 (UTC)

Pinned Comments

Tymon3310 commented on 2026-05-06 11:34 (UTC) (edited on 2026-05-06 11:55 (UTC) by Tymon3310)

ok, so i found issue:

beta had a bug that made so it couldnt migrate to new config structure - so it coudnt load it and crashed.

it was fixed in 2.0.0 (that i just pushed), and i discovered that first downgrading to 1.16.9-1, launching it, and then upgrading to 2.0.0 (non beta) fixes this.

so if you were on beta.1 or beta.2 build, downgrade to 1.16.9-1 first

Latest Comments

1 2 3 Next › Last »

AtomicTEM commented on 2026-06-01 23:28 (UTC)

With Fallout 3 I get the error of being unable to discover the game or point to the proper folder because the plugins is looking for Data/fallout3.esm as a requirement to verify that the selected folder is the proper. But since Linux is Case sensitive Fallout3.esm with a capital "F" is not valid and thus fails to set the proper filepath.

I manually edited the Fallout 3 bundled plugin index.js to change the "fallout3.esm" to "Fallout3.esm"

Furthermore once I was able to set the filepath and load into the Fallout 3 game section of Vortex. I was met with the error of Vortex being unable to find Fallout.ini or Falloutprefs.ini as it still look in usr/atomictem/Documents/My Games even though the ini files are not created there.

I install the GOG version of Fallout 3 through Heroic Game Launcher. So the INI files under Heroic Launchers Prefixes for Fallout 3 /home/atomictem/Games/Heroic/Prefixes/default/Fallout 3 Game of the Year Edition/drive_c/users/atomictem/Documents/My Games/Fallout3/ .

Tymon3310 commented on 2026-05-06 11:34 (UTC) (edited on 2026-05-06 11:55 (UTC) by Tymon3310)

ok, so i found issue:

beta had a bug that made so it couldnt migrate to new config structure - so it coudnt load it and crashed.

it was fixed in 2.0.0 (that i just pushed), and i discovered that first downgrading to 1.16.9-1, launching it, and then upgrading to 2.0.0 (non beta) fixes this.

so if you were on beta.1 or beta.2 build, downgrade to 1.16.9-1 first

Chifilly commented on 2026-05-06 09:59 (UTC)

I have the same issue as Plexxl. Firstly it complains that I'm opening version 1.0.0 when I previously ran 1.16.9, and if I continue, I get the same error

Plexxl commented on 2026-05-05 20:26 (UTC) (edited on 2026-05-05 20:26 (UTC) by Plexxl) 

2026-05-05T20:25:19.247Z [INFO] [MAIN] Uncaught Error: Cannot find module './build/Release/vortexmt'
Require stack:
- /opt/Vortex/resources/app.asar/node_modules/vortexmt/index.js
- /opt/Vortex/resources/app.asar/renderer.js
- /opt/Vortex/resources/app.asar/index.html

Tymon3310 commented on 2026-05-05 17:07 (UTC)

@RayJW i agree, changed

@Plexxl more info needed (works for me and on on clean chroot as well)

Plexxl commented on 2026-05-05 15:40 (UTC)

Error: Cannot find module './built/Release/vortexmt'

RayJW commented on 2026-05-05 11:51 (UTC)

@Tymon3310: The SDK is declared as a make dependency. That means when installing the package it is considered an unused dependency once the build is finished. So when removing orphans the SDK will be uninstalled, at which point the application doesn't work any more. The correct thing to do is to add the runtime as a dependency, because the SDK is only needed to build the package, but the runtime is required to run the application.

Tymon3310 commented on 2026-05-05 10:01 (UTC) (edited on 2026-05-05 10:03 (UTC) by Tymon3310)

@Nex_isDumb gamebyro is windows-only for now. Also i considired it, but we need SDK when compiling it, so why add runtime as well?

@Plexxl i forgot to push my changes, sorry

pushed now

Plexxl commented on 2026-05-03 23:19 (UTC)

Hey, you stated that you pushed the 2.0.0_beta.2, but this package is still using 1.16.9

Nex_isDumb commented on 2026-05-01 17:16 (UTC)

I'm getting an error where Vortex cannot find the Gamebryo plugin. I remember also seeing that the Gamebryo plugin was getting skipped or something when it was compiling through the yay installation. If I look in the Extensions page I can see that "Gamebryo Archive Check" and "Gamebryo Plugin Indexlock" are failing. Also, I know it was already suggested, but I also suggest adding dotnet-runtime-9.0 as dependency.

1 2 3 Next › Last »