Closed AtomCrafty closed 3 years ago
Turns out this was an issue with a symlinked game directory where Nemesis resolved the symlink rather than accessing the virtual file system created by MO2.
Hey, how did you fix it? I have the exact same issue and can't figure out what's the problem at all
My game directory was symlinked. Don't do that, the virtual file system doesn't support symlinks.
the problem is i didn't do any symlinking or anything, i did a fresh install
Then unfortunately I don't know what's causing your issue.
Nemesis starts fine from Windows Explorer, but won't load when launched through MO2. Any ideas what could cause this or how to fix it?
Here's the MO2 executable setup, but it also happens when I start the executable from within the VFS explorer: