Give Feedback
0 of 0
videogame_asset My games
Install hundreds of mods with the click of a button.
Notifications
notifications_off
No unread notifications right now
You're up to dateYou're up to date
Notification Settings
Show notifications for:
Tracking preferences
169 comments
This F4SE plugin does what it advertises it does, which is allow older game exe versions to load plugins with the newer header version. However if those plugins are using FormIDs in the range of 0x001 - 0x7FF, and those records are not intended to be hardcoded overrides, then they will malfunction. This is not a bug of this mod or the author of the mod being used. This is the limitation of using an old game version that does not properly support the newer produced content. Since the VR version of Fallout 4 was never updated, this will always be the case until Bethesda does so.
The behavior prior to game exe version 1.10.162 was to use forms in that range as hard coded overrides even if they weren't explicitly set as overrides of the hard coded FormID. An example: A new plugin creates a form, ID = 7. The engine would still treat it as an override of 0x00000007 even though it might be loaded as 0x4B000007.
I hope I'm not misunderstanding? I just wanted to write this simple-to-understand (imho) explanation.
If you're using just about any other manager then you may need to download manually and add the archive to the respective manager in the proper game mode. From there the same folder renaming may apply.
I only have two mods that are having version incompatibility issues, and they still keep popping errors.
I have F4SEVR, and I re-installed it just in case. I've installed this both through a mod manager and manually as described; no dice.
I had actually suspected as much, and went ahead and moved the .dll to this location, which for me is [location]\Fallout 4 VR\Data\F4SE\Plugins
I have two plugins that fail, but really only care about one. Both pop the error when running the game while launching from F4SEVR.
If you don't have any further suggestions I'll go ahead and visit the Discord per your recommendation. Thank you again for your help.
I’m having the same issue with two mods showing this error message. I might just give up and find out how to edit their version anyways.
If that's the case then some other mod you're using is the cause. See the second paragraph in the first sticky message above. That's most likely the issue.
If it is not, then it's a broken mesh included in a mod by some plugin that's being able to load because of this mod.