migration tool bug: "can't import mods from different game: skyrim vr" from MO2 Skyrim VR portable instance to vortex Skyrim VR per-user i

[KateHanami]

title

Edited September 5, 2022 by KateHanami

[Pickysaurus]

That would imply that MO2 isn't correctly identifying your instance as Skyrim VR. You can copy the contents of your MO2 mods folder to your staging folder to import manually but Vortex will show a warning on next startup with you can ignore.

[KateHanami]

That would imply that MO2 isn't correctly identifying your instance as Skyrim VR. You can copy the contents of your MO2 mods folder to your staging folder to import manually but Vortex will show a warning on next startup with you can ignore.

nope, it's the other way around, vortex thinks Skyrim VR is actually Special Edition and doesn't let me import mods from the "wrong game"

it's important to mention that whenever I install a mod via NMM=1 it tries to move to

D:\vortex mods\downloads\skyrimse\

and sometimes to

D:\vortex mods\downloads\skyrimvr

and my download path is set to

D:\vortex mods\downloads\{game}

so yeah, this been borked for me for over a year so I was just using MO2 for the time

and I have no way to know is AE have any relation to the issue

 

also bump

[Pickysaurus]

Honestly it sounds like this is problem with how MO2 stores mods/games being incompatible with the importer. You can still do this manually as I mentioned before.