Issues with the 'Locked to Index' function

[duckyduckyquackquack]

Okay I'm trying to make sense of how this feature actually works and how to apply it across my Fallout 4 profiles. I am using the Bullet Time (Slow Time) mod in combination with FO4 Hotkeys mod, so that when I press a combination of buttons on my controller it activates and deactivates the bullet time effect in game. To do this obviously I have to set up an entry for this in the Hotkeys.ini file installed by the Hotkeys mod. This is pretty simple to do and reads as: Shift-Xenon_B=player.equipitem XX000803 where the XX000803 relates to the ID of the item in game to generate the effect, obviously replacing the XX with the actual Mod Index value from Vortex to actually be able to use the item.

 

The problem is across my many Fallout 4 profiles, with various combinations of mods, the Autosorting/Loot Ordering of mods means that the SlowTime.esp never occupies the same place in the load order/mod index across any profile. This means unless I remember to go into the Hotkeys.ini file and edit it before I launch the game then when I load up the game and a save, the mod doesn't work and the controller shortcut/hotkey doesn't work. This is obviously quite a pain.

 

What I want to do is lock the Slowtime.esp to load at specific and constant place across all profiles, which I thought the Locked to Index would allow. So I loaded up my first profile and found the esp at Mod Index 54, now I know all my other profiles have more mods installed and enabled then this profile, but this esp has no dependencies or master requirements so I want to set it so that 54 is the Locked Index for the esp now, so its in the same place for every profile meaning I don't have to keep editing the hotkeys.ini file. So in Vortex I activate the Locked to Index button and then the weirdness ensues.

 

The Mod has been sorted by the autosorting feature already to load at index 54, so I assume having 54 in the box would be all I have to do. However the instant I press the locked to index button, red text appears that says, "Actual Index Differs. If this is the case after sorting it may be this index isn't possible." and bizarrely the mod now moves to Index 57. So I again figure that maybe it wants to be that index, so again change the value in the box to be 57, hoping it'll lock it to this place across all profiles. Again the red text appears and now the mod moves to index 5A.

 

Everytime I change the value in the Index Box, Vortex cries its not possible to lock the mod here and then moves it even further down the order. If I remove the value, the Mod goes back to its original place at 54.

 

So can someone tell me what I'm doing wrong and how to make this function actually work, because its driving me mad now.

[Tannin42]

Odd. What you're trying to do is absolutely sensible and this is what the feature is supposed to support so your expectation is correct and from your description it appears that you use it correctly.

This is more likely a bug. I'll investigate this on monday, this is certainly not the most well-tested feature.

[Liolande]

hi! i also have a problem with "lock to index" ... it does not work for 2 esp files, and there is no other file on the same index! it say it cant and... it ignor my load order completly!

help!

[HadToRegister]

  On 4/8/2019 at 8:16 PM, Liolande said:

hi! i also have a problem with "lock to index" ... it does not work for 2 esp files, and there is no other file on the same index! it say it cant and... it ignor my load order completly!

help!

 

You shouldn't NEED to use "Lock to index" if you allow Vortex to sort your load order.

[paulleboucher]

Hello,

 

I think I have the same problem. I am trying to set my load order myself by using the tool "look to index" because the "manage rules" is not working...

The complex dependencies of my many mods require me to do it manually to work well and not impact my fps in game.

 

And for some reasons couple of my pluggins ignor my load order.

 

(I disabeled the Autosort)

 

Thanks for your work and help

[BigBizkit]

When you say "manage rules" is not working, what exactly seems to be not working for you?

 

Locking plugins to an index should only be used for e.g. mod development, when you are testing stuff. It is not intended as a substitute for plugin rules.

[AugustaCalidia]

  On 5/1/2019 at 10:57 AM, paulleboucher said:

Hello,

 

I think I have the same problem. I am trying to set my load order myself by using the tool "look to index" because the "manage rules" is not working...

The complex dependencies of my many mods require me to do it manually to work well and not impact my fps in game.

 

And for some reasons couple of my pluggins ignor my load order.

 

(I disabeled the Autosort)

 

Thanks for your work and help

 

Disable any locks to index, turn auto-sort back on, sort, then use group assignments to fine tune anything that needs it. Using "lock to index" as a universal sorting tool creates nothing but headaches.

[dalantoc]

I have a ring-based HUD mod that I equip/unequip via hotkeys, and need the ring's formid locked for the scheme to work. I've seen that switching profiles causes Vortex to give the ring plugin a sorted load order regardless of "locked to index". Strangely, only on the 1st run (via F4SE_loader) after switching. Subsequent runs were back to the "locked" index number. So it was supposed to be locked to 51, but in-game the plugin's stuff started with 4E. Restarted game & checked, plugin stuff is back to 51.

 

JMHO, "locked to index" is problematic.

[Pickysaurus]

Please can you report this via the "Send feedback" option in Vortex including steps to replicate it. This topic is from 2019 so isn't going to be particularly relevant.

 

In 99% of cases lock to index is unnecessary, but if you've found a bug that can be reproduced we'll look into it.