Grestorn Posted May 12, 2018 Share Posted May 12, 2018 You determined what? That plugins.txt differs from the order within Vortex? If that would be the case, it would be a major bug. Instead of just claiming that, it would be much more helpful to give an example. Otherwise a bug, if there is one, can never be fixed. As it stands right now, I must doubt that you did everything correctly when you encountered this problem. Link to comment Share on other sites More sharing options...
Tannin42 Posted May 12, 2018 Share Posted May 12, 2018 I launch FNVEdit from Vortex and it's not using the order of plugins as set in Vortex. Additional weirdness: It DOES remove FalloutNV.esm from the active plugins. As Grestorn said, I'd need a bit more info, like screenshots, logs, ..., to see what's happening.Vortex writes the plugins to plugins.txt in the load order as configured in Vortex, that feature is finished and working, at least for the majority of users. If it doesn't for you then that's a bug, but one that is somehow specific to your setup so I need data to determine what makes your system different. Now regarding your additional weirdness: Vortex indeed doesn't put "plugins" into the plugin.txt file if they are loaded by the engine anyway. Basically Vortex writes the minimal plugins.txt to produce a correct results. I Some other tools unfortunately do not handle this correctly as they don't "know" that falloutnv.esm can never not be active.I'll probably change this in Vortex eventually. But the fact that Vortex does remove falloutnv.esm means that vortex does write the plugins.txt so why would it do so in a different order than displayed inside Vortex? Doesn't make sense. I really need that screenshot. Link to comment Share on other sites More sharing options...
jwideman Posted May 12, 2018 Author Share Posted May 12, 2018 You determined what? That plugins.txt differs from the order within Vortex? If that would be the case, it would be a major bug. Instead of just claiming that, it would be much more helpful to give an example. Otherwise a bug, if there is one, can never be fixed. As it stands right now, I must doubt that you did everything correctly when you encountered this problem. It's a reasonable request, but at this time it's just not going to happen. I'll see if I can recreate the problem with Fallout 3 in a day or two. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.