FAQ. Q. Game updated... A. New updates do not break this loader, the loader itself might get overwritten and you'll need to reinstall. Go to whatever installed native mods page and check for updates. A. If you believe it stopped working, check the file size of `bink2w64.dll`, correctly installed Native Mod Loader should be 227 kb, if it's the same size as the `bink2w64_original.dll`, it means game update has reverted the files. You'll need to reinstall this mod to overwrite it again.
Q. Manual Install:
Extract both bink2w64.dll and bink2w64_original.dll from archive file into your game's bin folder e.g steam path (this may vary): "D:\Program Files (x86)\Steam\steamapps\common\Baldurs Gate 3\bin"
(Important!) Confirm replacement/overwrite when prompted.
Q. Vortex Install:
Download and Install this mod with Vortex.
Click 'Install as Replacer', ignore error and continue.
Double click this mod
Select 'Engine Injector' in 'Mod Type' dropdown !! Important
Click the 'Deploy Mods' button, or 'Deploy' in the notification.
Q. I don't have `NativeMods` folder! A. This is just the loader. If the native mod you are installing doesn't come with a proper folder structure, you can create `NativeMods` folder yourself. It should be at the same level as the loader (`bink2w64.dll` and `bg3.exe`).
Q. 我没有 `NativeMods` 文件夹! A. 此mod仅是插件加载器，如果你正在安装的原生插件没有自带该文件夹，你可以在bin文件夹中新建一个 `NativeMods` 文件夹。此文件夹应该和`bink2w64.dll`及游戏文件`bg3.exe`在同一层。
Installation Steps (for dummies like me, Mod Manager Download):
1. Download/Install Vortex 2. Download/Install this mod 3. Enable and Download as mod not as replacer. 4. Ignore the error message 5. Double click on the name of the mod itself (NativeModLoader) 6. Scroll down to Mod Type and click on it, then select "Engine Injector" 7. You're done.
If you receive an error regarding bink2w64, you may have mods that require you to select "Engine Injector" (step 5 and 6, but for said mods). When you boot up Baldur's Gate 3 through LariLauncher you may receive a warning message regarding incompatible mods, it should work regardless (unless outdated).
EDIT: Updated - 11 April 2024, 11:39AM Just a temporary heads-up for some people who are having trouble getting either Native Mod Loader, BG3 Script Extender, and/or Achievement Enabler to work nice with each other...
Spoiler:
Show
If you are having trouble with BG3 Script Extender and Native Mod Loader not working together, allegedly there is something going on with the newest BG3SE update v(2024 March 29), as mentioned within their respective Posts pages (as well as other mod's Posts pages).Native Mod Loaderand Achievement Enabler still works as intended, with Hotfix #23, Hotfix #24, and Hotfix #25.
Possible solutions:
1) Uninstall BG3SE (2024 March 29), and re-install the previous BG3SE v(2024 March 28); some have claimed that this works as a temporary fix, until their next update. Or...
2) Try placing/moving BG3SE (2024 March 29)'s 'DWrite.dll' file into the 'NativeMods' folder (...\Baldur's Gate 3\bin\NativeMods); some people claim this also works as a temporary fix, until their next update.
EDIT: Updated - 8 September 2024, 9:05PM REMINDER: If you are now using (or plan on using) the most recent version of BG3 Script Extender { v(2024 April 30); aka v20 }, please install it the usual/normal way (as described on their Installation notes)---DO NOT install it using the fix that was used for BGSE v(2024 March 29) ---This install-method-fix is only intended for BGSE v(2024 March 29) !
Welp, I finally got around to updating my game to Patch 7 yesterday...purged all previous game files, and also purged ALL my mods' files, then reinstalled a fresh new Patch 7 updated game (Steam), then re-downloaded and reinstalled (Manual installs) all my mods (some were updated for Patch 7; others were confirmed still working with Patch 7; a few I am still currently testing for Patch 7 compatibility)...I can say that this mod (NML) is still working as advertised, with the new Patch 7 update. All my mods that list NML as a Requirement (and were ALSO updated for Patch 7) are working fine.
If you are having problems with NML not working for you, then it's either due to an installation error (FYI~ Vortex/MO2 are known to occasionally mess up installs resulting in mods not working, as well as messing up uninstalls resulting in left-over files causing errors/conflicts), and/or a mod conflict (you may be using a mod that needs to be updated for Patch 7).
Be aware that Patch 7 made a lot of significant changes to the game, resulting in a lot of mods getting broken. If you are using a mod that has not been updated for Patch 7, and has no solid/official confirmation that it is compatible with Patch 7, uninstall those mods.
Side Note, Regarding "LoadLibrary failed" Errors:
matzan481 13 September 2024, 1:42PM Guys if you are getting the "LoadLibrary failed on NativeMods\BG3NativeCameraTweaks.dll" error please install latest microsoft visual c++ redistributable (easy to google) that fixed the issue for me immediately
Updated - 2 October 2024, 10:26PM Regarding the Patch 7 Hotfix #27 update: Native Mod Loader is unaffected by the new update (Hotfix#27) that Larian dropped yesterday (1 October 2024).
Updated - 18 October 2024, 12:15PM Regarding the Patch 7 Hotfix #28 update: Native Mod Loader is unaffected by the new update (Hotfix#28) that Larian released on 16 October 2024.
Updated - 25 November 2024, 12:26PM Regarding the Patch 7 Hotfix #29 update: Native Mod Loader is unaffected by the new update (Hotfix#29) that Larian released on 21 November 2024. The new update only applies changes to Console players, as mentioned on their Patch Notes.
Updated - 19 April 2025, 10:51PM ! NEWS ! Regarding the Patch 8 update: I redownloaded and using the original mod files from the Main Files 'NativeModLoader Version 1', and both the 'bink2w64.dll' and 'bink2w64_original.dll' files from the archive are still working fine as advertised, with the new Patch 8 update (Steam; Manual installs). The renaming-method of the new 'bink2w64.dll' that comes with the Patch 8 update is not necessary, UNLESS you're having troubles getting NML to work for you, then try the renaming-method and if it works, hella nice. :)
Patch 8 fix/workaround/update whatever, not the first one to whrite this but maybe i can help make it more clear.
So because Im a simple man and didnt get what to do to make this work at first: Here a step by step guide for the folks struggling to get this to work. You want the original bink2w64.dll which came with patch 8 AND the bink2w64.dll that came with this mod. To do so rename the original bink2w64.dll that came from patch 8 to bink2w64_original.dll and copy the bink2w64.dll to the same folder. Usually C:\Program Files (x86)\Steam\steamapps\common\Baldurs Gate 3\bin
1. locate the bin folder for bg3, usually C:\Program Files (x86)\Steam\steamapps\common\Baldurs Gate 3\bin 2. rename the original bink2w64.dll to bink2w64_original.dll 2. download this mod manually 3. copy only the bink2w64.dll from this mod into the bin folder 4. check if you have both a bink2w64.dll and a bink2w64_original.dll 5. done.
Extract both bink2w64.dll and bink2w64_original.dll from archive file into your game's bin folder e.g steam path (this may vary): "D:\Program Files (x86)\Steam\steamapps\common\Baldurs Gate 3\bin"
(Important!) Confirm replacement/overwrite when prompted.
Download page:
Extract to game's root folder, confirm overwrite when prompted.
They are the same location, just worded/phrased differently. The "bin folder" is located within the game's "root folder".
Thank you. I was under impression we could put those two files outside of bin folder which would make it within root folder but outside of bin folder. I don't understand how they could be same but thanks for quick help anyways. I just extracted the two files into the bin folder.
But I see the reasoning since when unzipped the two files are already inside a folder called bin so it could work both ways. Just, description page said to extract the two files and not the bin folder they're in into the game's bin folder so I did by those words because it seemed most sure fire way to be safe.
Sorry, I'm bad at english and modding. Thanks for letting me know though. Seems everything is where it should be now
BG3ScriptExtender does not effect NML. If reinstalling BG3SE fixed your issue, then it was probably a different mod that was causing errors or conflicts.
Still works if you take the new bink2w64 from the patch and rename it to bink2w64_original.dll (If you already had the native tweaks dlls in your files you might need to delete them and verify game files in steam to get the updated dll)
@Matheus rename it to bink2w64_original.dll, they actually updated the original dll this time so the one included in this is outdated. if you had these in the files when you updated you'll need to take them out and verify integrity of files in steam, rename the new dll and only take bink2w64.dll from the zip
is the correct procedure : 1 verify game files in steam before updating (using steam bg3 properties/Betas/realease_patch_7_hf3 ) 2 delete old "bink2w64_original.dll " 3 update to patch 8 4 rename the new "bink2w64.dll" to "bink2w64_original.dll " 5 manually past "bink2w64.dll" of this mod in place of the new "bink2w64.dll", but do Not past "bink2w64_original.dll " of this mod.
TL;DR only use this mod's "bink2w64.dll" and Not "bink2w64_original.dll ", after renaming Patch8 new "bink2w64.dll" to "bink2w64_original.dll " ?
After updating to patch 8 and manually running Steam's file verification (which will automatically replace the file bink2w64), I simply placed the two new mod files (April 16, 2025), and it works fine.
Now this is strange… Your trick worked for me the first time but after shutting it down and booting it back up to see if it was a fluke, it didn't work the second time. It gets stuck at 100% again. I tried booting it up a couple more times but it's the same. I repeated the process and it still didn't work after that first time.
(And I don't understand why it would - why would the game be "aware" of a different version of a file that it's not using? - if the fix is working for some it might be something about the verifying and repairing process, like the game has to know that the version 8 bink file has beren put into the folder? But it hasn't worked for me anyway.)
I will probably be doing my updating/mods-testings (as mentioned on the edited last Sticky above) this coming weekend (hopefully, unless something else comes up). Also cuz I like to wait a few days or so after new Patches/Updates/Hotfixes are released, for other mods to get updated, if needed. Also the timing of the release of the Patch 8 update kinda worked against me...one day before my burpday, and today I'm too hung over to get all that shiz done and updated and tested, lmao. 😵 🤢 🪦 👻
1) removing all the native mods I was using, i.e. I deleted the .dlls and log files for Native Camera Tweaks and WASD movement from the NativeMods folder in the bin folder (I retained only the .tomls which had my config tweaks, after checking in Notepad++ just to see if anything had changed in the .tomls for the update 8 versions of those mods),
2) deleting the bink2w64.dll from this mod that was in the bin folder (renaming the original bink2w64.dll - which wasn't from this mod, but was the one that came with update 8 on a verify and redownload - back to normal) and then deleting the SDL2.dll from WASD movement and replacing it with the update 8 version (which I'd also renamed to original).
3) checking that the game ran.
4) manually unzipping this mod, Native Camera Tweaks and WASD Movement and then renaming the original update 8 bink2w64.dll to bink2w64_original.dll, and putting the bink2w64.dll from this mod into bin, then taking the .dlls (only) from NCT and WASD and putting them in the NativeMods folder in bin.
5) all working
My suspicion is this: formerly WASD added its own SDL2.dll file to bin, the update 8 version doesn't. I think maybe where I went wrong was in confusedly retaining the older WASD version of SDL2.dll. For some reason this was creating an error related to Native Camera Tweaks (but probably nothing to do with it really, just an artifact of having the wrong file).
Yep, typically when a new Patch/update/hotfix is released, NML will usually only require a reinstall, while it's more probable (but not always) other mods that list NML as a requirement that can break and need updating (i.e. WASD, NCT, others).
EDIT - 19 April 2025, 11:05PM After doing a complete/fresh reinstall of the game (Steam) for the Patch 8 update, nuking all associated game folders/files (including Hidden ones), as well as nuking all mods associated folders/files, I redownloaded+reinstalled (Manual installs only; I don't use Vortex/MO2) the four holy mods: Native Mod Loader, Achievement Enabler, Native Camera Tweaks, and WASD, and everything is working flawlessly for me (phew! Praise be Lolth, lol!). I should also make mention that I do not have BG3ScriptExtender, nor BG3ModManager installed, as of yet (but they will be eventually/at some point; need to do other testing of things without them installed for now).
Also, I did not have to do any of that "renaming" stuff that some have suggested. The original files from the Main File's 'NativeModLoader Version 1' downloaded archive ('bink2w64.dll' and 'bink2w64_original.dll') are still working fine, as advertised, with the new Patch 8 update. If some of you, for whatever reason, can't get NML's original mod files to work on your end, then give the renaming-method that some claim to work, a try. If that works for you, then hella nice. :)
I know it's not what many people like to do. But the way that worked 100% for me was to update the game, delete the 2 bink2w64 files, and send Steam to repair it, that way the Native mode loader, camera tweaks and WASD worked normally. (Of course I did a complete installation of these mods with their current att.)
eh, not a fan of using an actual feature of Nexus to insult people. We get it, people don't read the directions, putting that little snarky joke isn't going to make them suddenly read.
It's not meant to be taken as an insult. It's called humor. Poking at one of the biggest, if not THE biggest reason for 97-99% of all "mod doesn't work" complaints, due to people never reading everything before they install a mod. Lol.
877 comments
Q. Game updated...
A. New updates do not break this loader, the loader itself might get overwritten and you'll need to reinstall. Go to whatever installed native mods page and check for updates.
A. If you believe it stopped working, check the file size of `bink2w64.dll`, correctly installed Native Mod Loader should be 227 kb, if it's the same size as the `bink2w64_original.dll`, it means game update has reverted the files. You'll need to reinstall this mod to overwrite it again.
Q. Manual Install:
Q. Vortex Install:
Q. I don't have `NativeMods` folder!
A. This is just the loader. If the native mod you are installing doesn't come with a proper folder structure, you can create `NativeMods` folder yourself. It should be at the same level as the loader (`bink2w64.dll` and `bg3.exe`).
Q. 我没有 `NativeMods` 文件夹!
A. 此mod仅是插件加载器，如果你正在安装的原生插件没有自带该文件夹，你可以在bin文件夹中新建一个 `NativeMods` 文件夹。此文件夹应该和`bink2w64.dll`及游戏文件`bg3.exe`在同一层。
1. Download/Install Vortex
2. Download/Install this mod
3. Enable and Download as mod not as replacer.
4. Ignore the error message
5. Double click on the name of the mod itself (NativeModLoader)
6. Scroll down to Mod Type and click on it, then select "Engine Injector"
7. You're done.
If you receive an error regarding bink2w64, you may have mods that require you to select "Engine Injector" (step 5 and 6, but for said mods). When you boot up Baldur's Gate 3 through LariLauncher you may receive a warning message regarding incompatible mods, it should work regardless (unless outdated).
Just a temporary heads-up for some people who are having trouble getting either Native Mod Loader, BG3 Script Extender, and/or Achievement Enabler to work nice with each other...
EDIT: Updated - 8 September 2024, 9:05PM
REMINDER:
If you are now using (or plan on using) the most recent version of BG3 Script Extender { v(2024 April 30); aka v20 }, please install it the usual/normal way (as described on their Installation notes)---DO NOT install it using the fix that was used for BGSE v(2024 March 29) ---This install-method-fix is only intended for BGSE v(2024 March 29) !
If you are having problems with NML not working for you, then it's either due to an installation error (FYI~ Vortex/MO2 are known to occasionally mess up installs resulting in mods not working, as well as messing up uninstalls resulting in left-over files causing errors/conflicts), and/or a mod conflict (you may be using a mod that needs to be updated for Patch 7).
Be aware that Patch 7 made a lot of significant changes to the game, resulting in a lot of mods getting broken. If you are using a mod that has not been updated for Patch 7, and has no solid/official confirmation that it is compatible with Patch 7, uninstall those mods.
Side Note, Regarding "LoadLibrary failed" Errors:
Updated - 2 October 2024, 10:26PM
Regarding the Patch 7 Hotfix #27 update:
Native Mod Loader is unaffected by the new update (Hotfix#27) that Larian dropped yesterday (1 October 2024).
Updated - 18 October 2024, 12:15PM
Regarding the Patch 7 Hotfix #28 update:
Native Mod Loader is unaffected by the new update (Hotfix#28) that Larian released on 16 October 2024.
Updated - 25 November 2024, 12:26PM
Regarding the Patch 7 Hotfix #29 update:
Native Mod Loader is unaffected by the new update (Hotfix#29) that Larian released on 21 November 2024. The new update only applies changes to Console players, as mentioned on their Patch Notes.
Updated - 19 April 2025, 10:51PM
! NEWS ! Regarding the Patch 8 update:
I redownloaded and using the original mod files from the Main Files 'NativeModLoader Version 1', and both the 'bink2w64.dll' and 'bink2w64_original.dll' files from the archive are still working fine as advertised, with the new Patch 8 update (Steam; Manual installs). The renaming-method of the new 'bink2w64.dll' that comes with the Patch 8 update is not necessary, UNLESS you're having troubles getting NML to work for you, then try the renaming-method and if it works, hella nice. :)
So because Im a simple man and didnt get what to do to make this work at first: Here a step by step guide for the folks struggling to get this to work. You want the original bink2w64.dll which came with patch 8 AND the bink2w64.dll that came with this mod. To do so rename the original bink2w64.dll that came from patch 8 to bink2w64_original.dll and copy the bink2w64.dll to the same folder. Usually C:\Program Files (x86)\Steam\steamapps\common\Baldurs Gate 3\bin
1. locate the bin folder for bg3, usually C:\Program Files (x86)\Steam\steamapps\common\Baldurs Gate 3\bin
2. rename the original bink2w64.dll to bink2w64_original.dll
2. download this mod manually
3. copy only the bink2w64.dll from this mod into the bin folder
4. check if you have both a bink2w64.dll and a bink2w64_original.dll
5. done.
Download page:
They are the same location, just worded/phrased differently. The "bin folder" is located within the game's "root folder".
I just extracted the two files into the bin folder.
But I see the reasoning since when unzipped the two files are already inside a folder called bin so it could work both ways.
Just, description page said to extract the two files and not the bin folder they're in into the game's bin folder so I did by those words because it seemed most sure fire way to be safe.
Sorry, I'm bad at english and modding. Thanks for letting me know though. Seems everything is where it should be now
looks like patch 8 finally broke thisStill works if you take the new bink2w64 from the patch and rename it to bink2w64_original.dll (If you already had the native tweaks dlls in your files you might need to delete them and verify game files in steam to get the updated dll)
but wasd and some other mods are broken
BUT also, WASD and Native Camera Tweaks are not updated yet, so just send those modders some love and encouragement and be patient. =)
1 verify game files in steam before updating (using steam bg3 properties/Betas/realease_patch_7_hf3 )
2 delete old "bink2w64_original.dll "
3 update to patch 8
4 rename the new "bink2w64.dll" to "bink2w64_original.dll "
5 manually past "bink2w64.dll" of this mod in place of the new "bink2w64.dll", but do Not past "bink2w64_original.dll " of this mod.
TL;DR only use this mod's "bink2w64.dll" and Not "bink2w64_original.dll ", after renaming Patch8 new "bink2w64.dll" to "bink2w64_original.dll " ?
have done what you said, it doesn't work.
Nevermind, it works.(And I don't understand why it would - why would the game be "aware" of a different version of a file that it's not using? - if the fix is working for some it might be something about the verifying and repairing process, like the game has to know that the version 8 bink file has beren put into the folder? But it hasn't worked for me anyway.)
**************
Later note: I seem to have fixed it by:-
1) removing all the native mods I was using, i.e. I deleted the .dlls and log files for Native Camera Tweaks and WASD movement from the NativeMods folder in the bin folder (I retained only the .tomls which had my config tweaks, after checking in Notepad++ just to see if anything had changed in the .tomls for the update 8 versions of those mods),
2) deleting the bink2w64.dll from this mod that was in the bin folder (renaming the original bink2w64.dll - which wasn't from this mod, but was the one that came with update 8 on a verify and redownload - back to normal) and then deleting the SDL2.dll from WASD movement and replacing it with the update 8 version (which I'd also renamed to original).
3) checking that the game ran.
4) manually unzipping this mod, Native Camera Tweaks and WASD Movement and then renaming the original update 8 bink2w64.dll to bink2w64_original.dll, and putting the bink2w64.dll from this mod into bin, then taking the .dlls (only) from NCT and WASD and putting them in the NativeMods folder in bin.
5) all working
My suspicion is this: formerly WASD added its own SDL2.dll file to bin, the update 8 version doesn't. I think maybe where I went wrong was in confusedly retaining the older WASD version of SDL2.dll. For some reason this was creating an error related to Native Camera Tweaks (but probably nothing to do with it really, just an artifact of having the wrong file).
Yep, typically when a new Patch/update/hotfix is released, NML will usually only require a reinstall, while it's more probable (but not always) other mods that list NML as a requirement that can break and need updating (i.e. WASD, NCT, others).
EDIT - 19 April 2025, 11:05PM
After doing a complete/fresh reinstall of the game (Steam) for the Patch 8 update, nuking all associated game folders/files (including Hidden ones), as well as nuking all mods associated folders/files, I redownloaded+reinstalled (Manual installs only; I don't use Vortex/MO2) the four holy mods: Native Mod Loader, Achievement Enabler, Native Camera Tweaks, and WASD, and everything is working flawlessly for me (phew! Praise be Lolth, lol!). I should also make mention that I do not have BG3ScriptExtender, nor BG3ModManager installed, as of yet (but they will be eventually/at some point; need to do other testing of things without them installed for now).
Also, I did not have to do any of that "renaming" stuff that some have suggested. The original files from the Main File's 'NativeModLoader Version 1' downloaded archive ('bink2w64.dll' and 'bink2w64_original.dll') are still working fine, as advertised, with the new Patch 8 update. If some of you, for whatever reason, can't get NML's original mod files to work on your end, then give the renaming-method that some claim to work, a try. If that works for you, then hella nice. :)
Have an awesome weekend everyone! \o/ ♥ :D