Starfield Extension has been updated to support load ordering and plugins.txt

[TheDoctor217]

Good evening - Not too sure what I am doing wrong.  I have 4 mods total and am using the Game Pass Version.  I have enabled the new loading order function, deployed the mods and I am stuck.  In the load order screen 2 of the 3 loads are locked and have an exclamation mark with "Not Managed by Vortex"  The 3rd I can clock on, but I cannot move it up or down.  I only use Vortex for modding, so I am not sure I understand why it is telling me they are not managed by Vortex.  I have purged, uninstalled, reinstall, redeployed, disabled, restarted Vortex, and enabled.  Feels like I am just missing something, or flipping another switch.  Thanks in advance for any help.

 

[AugustaCalidia]

11 hours ago, TheDoctor217 said:

Good evening - Not too sure what I am doing wrong.  I have 4 mods total and am using the Game Pass Version.  I have enabled the new loading order function, deployed the mods and I am stuck.  In the load order screen 2 of the 3 loads are locked and have an exclamation mark with "Not Managed by Vortex"  The 3rd I can clock on, but I cannot move it up or down.  I only use Vortex for modding, so I am not sure I understand why it is telling me they are not managed by Vortex.  I have purged, uninstalled, reinstall, redeployed, disabled, restarted Vortex, and enabled.  Feels like I am just missing something, or flipping another switch.  Thanks in advance for any help.

 

The two "Not Managed" plugins are part and parcel of the vanilla game that you downloaded.  That is why they are not managed by Vortex and why they cannot be moved in the load order.

[Akopian]

@Nagevit is reassuring that these things are being examined. Especially a way of managing conflicts in ba2 files. Until your reply, nobody has seemed interested. And of course, managing load order is a big deal for the plugins. You might want to add a warning, if you have not yet, that it will merely be alohabetizing in the short run. For me, I have just had to learn how to do it all on my own. 

[TennesseeTuxedo]

I logged another ticket for negative performance that may be related to this release and this feature. 

These two new events below occur when deploying, enabling, disabling any mod and take 50 extra seconds.  I think the first might be related to the load order feature and seems to run even if we haven't turned on the feature, which I have not. 

The second I am not sure what it is related too but it is new to this release.  Why do we need a 30 second memory scan when enabling or disabling a mod?  If this is important for troubleshooting I'd recommend moving it to startup so you can get the memory values once and perhaps also run it if you create a ticket within Vortex so that data can be sent along (I've created tickets in Vortex before but not clear if that actually does anything, I've never gotten a response submitting a problem from within Vortex).

 

New events in the vortex log related to this release:

• (+22 seconds)    Fri, 22 Dec 2023 07:40:59 GMT - info: [new-file-monitor] file list snapshot saved filePath=C:\Users\xxxxxxxx\AppData\Roaming\Vortex\starfield\snapshots\snapshot.json, duration=996
  • Recommend this be turned off unless we turn on the load ordering
• (+28 seconds)     Fri, 22 Dec 2023 07:41:30 GMT - info: memory usage growing fast usage=783.4 MB, previous=502.7 MB, max=4.00 GB
  • Recommend this to run once when launching Vortex, possibly also when creating a trouble report in Vortex (if that feature works)

For my part, as an active long time user of Vortex, and daily user of it for Starfield, I don't plan to use load ordering feature unless there is LOOT conflict resolution level functionality to it that we get for games such as Fallout 4 and Skyrim.  The LOOT thread sounds pessimistic about this functionality being achievable.

 

[ensozer0]

Could the Plugin Management problem have anything to do with LOOT removing support for Starfield?