Import from NMM

[rmm200]

Case in point is the topic a few above this one: Skyrim Special Edition mods not deploying

Took me two days - and three pages of give and take - before I established the user imported his mods from NMM.

This is an absolutely vanilla case of Skyrim mods not working when imported.

Might be worth a look as to what is going on.

My solution - that the OP will hate - is to blow away his Vortex installation, clean his Game directory - really clean -

and start again by installing clean mods with Vortex from archives.

I welcome any other ideas...

 

[HadToRegister]

Case in point is the topic a few above this one: Skyrim Special Edition mods not deploying

Took me two days - and three pages of give and take - before I established the user imported his mods from NMM.

This is an absolutely vanilla case of Skyrim mods not working when imported.

Might be worth a look as to what is going on.

My solution - that the OP will hate - is to blow away his Vortex installation, clean his Game directory - really clean -

and start again by installing clean mods with Vortex from archives.

I welcome any other ideas...

 

 

After so many posts of "20 questions"...

 

Where I'm the one asking questions, and the person wanting help answers "Yes" or "No"

I tell them I can't help them anymore because I'm not going to drag the information out of them by playing 20 Questions.

 

You want help, you need to start being more active in the process

[HadToRegister]

Or that one time where someone posted their problem..."Vortex doesn't deploy my mod"

So I answered "Did you try that thing?"

[holytank]

I find this odd that so many people are having issues importing from NMM. I have imported NMM mods for 4 games (Skyrim SE, FO4, FONV, FO3) using Vortex. I made sure to carefully read "Vortex Help" on importing mods from NMM, before attempting any import. I really like Vortex much better than NMM and Loot.

Myself being a retired IT software developer/development manager, it is understandable that any new software application will have some growing pains. :mellow: :laugh: :devil: :cool:

KUDOS to the Vortex team !!!!!!!!!!

[rmm200]

No one here would say Import from NMM is never successful.

There are problem cases - possibly do to not following directions - that lead some people seriously astray.

They are very hard to clean up after, usually leading to the Nuclear option. If the OP sticks around that long.

Those are the cases we see here.

[Zanderat]

Two things that might help, if the import feature remains:

• More clear documentation, really dummy it down.
• Or more analysis needs to be done as to why the import goes wrong for so many people. Can Vortex be made to detect files corrupted by NMM, for example.

[rmm200]

 

Two things that might help, if the import feature remains:

• More clear documentation, really dummy it down.
• Or more analysis needs to be done as to why the import goes wrong for so many people. Can Vortex be made to detect files corrupted by NMM, for example.

 

 

After an Import from NMM and prior to Vortex Deploy - the game directory must be verifyably clean of taint from NMM. No folders with numeric names, no Textures, Meshes, or Scripts folders.

No unrecognized esp, esm, esl or other mod artifacts.

Forcing the OP to do a Steam Verify would not hurt either. And warn them not to run NMM again for that game.

[AugustaCalidia]

I find this odd that so many people are having issues importing from NMM. I have imported NMM mods for 4 games (Skyrim SE, FO4, FONV, FO3) using Vortex. I made sure to carefully read "Vortex Help" on importing mods from NMM, before attempting any import. I really like Vortex much better than NMM and Loot.

Myself being a retired IT software developer/development manager, it is understandable that any new software application will have some growing pains. :mellow: :laugh: :devil: :cool:

KUDOS to the Vortex team !!!!!!!!!!

While Vortex was in alpha testing over a year ago, I did exactly what you did for my Fallout 4 and Skyrim SE games. The importing process was flawless and quick. (A little over 300 mods were imported). There were no instructions then. However, I did exactly what was later incorporated into the instructions for importing from NMM.

 

I say this not to brag but to say that there is a clear path to importing success. I have serious doubts that most people reporting import problems have stayed on that path. (I say "most people" but recognize that some folk have had certifiable technical issues beyond their control.)

 

If the import option is to remain in Vortex, I would endorse Zanderat's request for a dumbed down set of instructions. More than that, I would recommend that there be a check off list that postpones an import until the user has certified that all necessary procautions have been taken.

[Tannin42]

i dont know if you keep such data, but i would be interested to understand how many support issues originate from an attempted import from nmm to vortex, which immediately puts the user on the back foot, and marks vortex as the bad guy.

i suppose i could go off and simply count the number of threads in the support forum that establish an import from nmm at some point in the process.

 

We don't, unfortunately.

The thing is: Counting the threads isn't going to be representative, you don't know how many users just gave up frustrated and never posted.

But we will also not know how many of our users would never have switched to Vortex at all if there wasn't a way to import their mods from NMM. We have absolutely no indication of how many users had their NMM install imported just fine. It could literally be 5. Or 200.000.

 

If there is 5 successful imports and 2000 fails of which 20 got reported, that's one crappy feature that needs to be removed.

If there were 200k successful imports and 20 fails, all of which got reported, I'd argue the feature is well worth it.

 

 

Also: is the import process actually the core issue?

Let's say you

a) import a mod from NMM

b) let it deploy in Vortex

c) go to NMM and uninstall the mod

-> at this point NMM deletes files that "belong" to a vortex deployment, because NMM doesn't give a crap

d) Vortex now tells you in an "External changes" dialog that its files were deleted. You select "Hell yeah I want all my mod files deleted, stop asking me questions!"

 

Your mods are now broken. And you cry and complain about the import process not working.

 

However: Nothing would be different if you had installed the mod fresh in step a!

NMM would still have gone and removed the files in c. You would still have committed those deletions in d.

 

If this is a/the common problem case, removing the import feature doesn't fix anything! We still have to convince users to disable their mods in NMM before they deploy in Vortex or not select "yes, remove everything" in the "External changes" dialog.

[Zanderat]

What you just said, Tannin, isn't clear to users, IMO. I think a rewrite to simplify the directions is much needed, as well as clearer error messages and, as mentioned above, a "checklist" before the import is allowed.