Fallout 4

Fallout 4

View Stats:
Extended Dialogue Interface Mod issues
for some reason my XDI has stopped working even after I've updated my F4SE, and all the other mods that use F4SE are working just fine. It keeps saying that the XDI.dll can't be found and gives me this directory path to go and look for it: DATA \ F4SE \ PLUGINS directory, but I don't know what else to do to try and fix this annoying issue; I've already uninstalled and reinstalled XDI but that didn't work at all.

Can someone please help me out in trying to fix this bug.
Originally posted by Ilja:
So, not the issue I expected it to be.

NMM is buggy. Manual installation might solve the issue.

Other option is that file is set as Read Only. Right click the DLL-ile and make sure it is not set as "Read Only" by Windows.

If it was and problem continues, then it is possible that Windows keeps setting it as Read Only for some reason. Some security application might also be blocking it.
< >
Showing 1-8 of 8 comments
Ilja Oct 7, 2018 @ 10:58am 
Which mod manager you are using?
Ryusniper10001 Oct 7, 2018 @ 10:58am 
Originally posted by Ilja:
Which mod manager you are using?
NMM
s.turner3030 Oct 7, 2018 @ 10:58am 
Not much help here but I just get the missing file for xdi.esm when trying to load saves, like yourself everything has been updated as well.

Though when you check is the dll actually there?
The author of this thread has indicated that this post answers the original topic.
Ilja Oct 7, 2018 @ 11:02am 
So, not the issue I expected it to be.

NMM is buggy. Manual installation might solve the issue.

Other option is that file is set as Read Only. Right click the DLL-ile and make sure it is not set as "Read Only" by Windows.

If it was and problem continues, then it is possible that Windows keeps setting it as Read Only for some reason. Some security application might also be blocking it.
Ryusniper10001 Oct 7, 2018 @ 11:04am 
Originally posted by s.turner3030:
Not much help here but I just get the missing file for xdi.esm when trying to load saves, like yourself everything has been updated as well.

Though when you check is the dll actually there?
The things that're inside the Plugins folder is as follows:
[Folder] F4EE
f4ee.dll
f4ee [config settings]
mcm [symlink]
place.dll
place_example [config settings]
place_ini_help [text Doc]

these are the only things that're listed inside of the Plugins folder, so no I don't see the DLL file for the XDI :(
Last edited by Ryusniper10001; Oct 7, 2018 @ 11:07am
Ryusniper10001 Oct 7, 2018 @ 11:17am 
Originally posted by Ilja:
So, not the issue I expected it to be.

NMM is buggy. Manual installation might solve the issue.

Other option is that file is set as Read Only. Right click the DLL-ile and make sure it is not set as "Read Only" by Windows.

If it was and problem continues, then it is possible that Windows keeps setting it as Read Only for some reason. Some security application might also be blocking it.
thanks for letting me know that NMM was bugging out and was the issue, I did what you said and manually installed the mod and that fixed all of the issues, THANK YOU!
Ilja Oct 7, 2018 @ 11:21am 
Good to hear that you got this sorted out.

NMM is no longer officially supported by Nexus. It is breathing on community support, but this is exactly the sort of issue they haven't managed to solve. NMM was derived from old Fallout mod manager. Code is old and badly tangled. Nexus abandoned the application and will officially move to Vortex within weeks rather than months (estimate from staff comments in Discord.)

People are moving to use either Vortex or Mod Organizer 2. I am using latter. NMM can bug out with mod installations and it can sometimes be hard to figure out which file is failing. :/
Last edited by Ilja; Oct 7, 2018 @ 11:21am
Ryusniper10001 Oct 7, 2018 @ 11:30am 
Originally posted by Ilja:
Good to hear that you got this sorted out.

NMM is no longer officially supported by Nexus. It is breathing on community support, but this is exactly the sort of issue they haven't managed to solve. NMM was derived from old Fallout mod manager. Code is old and badly tangled. Nexus abandoned the application and will officially move to Vortex within weeks rather than months (estimate from staff comments in Discord.)

People are moving to use either Vortex or Mod Organizer 2. I am using latter. NMM can bug out with mod installations and it can sometimes be hard to figure out which file is failing. :/
thanks for letting me know. I guess for the time being until I get some more games that I can mod that I haven't already installed through via the NMM I'll just have to continue using the NMM because for me to try and convert all the mods from one organizer to another would be a huge pain in my ass, especially since I've got over 100s of mods for multitude of games already.
< >
Showing 1-8 of 8 comments
Per page: 1530 50

Date Posted: Oct 7, 2018 @ 10:52am
Posts: 8