0 of 0

File information

Last updated

Original upload

Created by

ffgriever

Uploaded by

ffgriever

Virus scan

Safe to use

Tags for this mod

251 comments

  1. ffgriever
    ffgriever
    • premium
    • 22 kudos
    Locked
    Sticky
    Since version 1.3.15, EFL supports launcher injection and along with it Mod Organizer 2. The plugin will be released at a later date, because it's just a very simple python plugin right now that requires some manual setting. If you want to test it, though, you can get it on our discord: https://discord.gg/UBrP6ME

    If the game doesn't start after updating or gives you errors at startup, make sure you've got up to date VC++ Redistributables installed.

    The most recent version is always available under the following link:
    https://aka.ms/vs/17/release/vc_redist.x64.exe
  2. salazar4
    salazar4
    • premium
    • 0 kudos
    Hi. Not sure what happened. Game was working perfect with all my mods then today, I crashed with "Microsoft Visual C++ Runtime Library error! This application has requested the Runtime to terminate it in an unusual way." 

    I disable all my mods and game works fine. If I enable this mod, it crashes again. 
    1. salazar4
      salazar4
      • premium
      • 0 kudos
      Versions 1.4.0 and 1.3.15 are not working for me. I have to use 1.3.13 for my game and mods to work. Any reason why?
    2. yohanesmaniac
      yohanesmaniac
      • member
      • 0 kudos
      Same Here, idk why it happen just now. i played smoothly a week before, i tried all solution i found for this issue on internet but still can't work, thx to you it works when i use old ext file loader 1.13.13, but just wonder why it happen just now?
    3. yHall
      yHall
      • member
      • 1 kudos
      .
    4. yHall
      yHall
      • member
      • 1 kudos
      Same Here, idk why it happen just now. i played smoothly 40 hours before.
    5. Xeavin
      Xeavin
      • premium
      • 136 kudos
      Verify your files with Steam. Disable all mods except EFL. Make sure that your mods were properly deployed (top right notification) in Vortex. Install the latest vc redist linked on the mod page. Restart your pc (fully, not just turning it off and on) and then check again. If it still crashes, go to "{game}/x64" directory and find the latest crash dump (should be several GB), put it in an archive (e.g. zip, rar, ...), upload it to something like WeTransfer and send us the link via a comment, private message, or the modding discord server. Just be aware that a crash dump can contain some personal information like Steam username, Windows username, what programs were open, etc.
    6. KingTom12
      KingTom12
      • premium
      • 0 kudos
      Ok - glad to hear this isn't just me! Same thing happening here, worked fine until today, 7/25/25 where 1.40 stopped working. I did a fresh install, the game works, I install the latest External File Loader and it gives the C++ Runtime Error when loading a save or starting a new game.

      EDIT - to all who find this. the reply above suggesting to use 1.3.13 is correct, switching to this version works! Uninstall 1.40, go to the Files section and download 1.3.13 instead, and you should be good to go.
    7. Xeavin
      Xeavin
      • premium
      • 136 kudos
      If you are going to downgrade, just keep in mind that the Lua Loader requires v1.3.15 or higher. Any older ones won't work. So if you are using any lua mods, that is not really a solution. And if you make the switch during a playthrough, it might break things even further. So be absolutely sure before you downgrade. I am sure this issue can be solved fairly quickly if anyone would be willing to share their crash dump. Without it, we cannot replicate the issue and therefore also not fix it.
    8. ffgriever
      ffgriever
      • premium
      • 22 kudos
      Hey. Sorry, I haven't been checking nexus for a few weeks. It's possible I've found a solution to this issue. If you want to test the new version early, find me on our discord server or PM me for a test version.

      NVM. Turned out it was the culprit. Update to 1.4.1 to solve the issue.
    9. Xansaibot7
      Xansaibot7
      • member
      • 1 kudos
      i am still getting this Crash Runtime error with 1.4.1
    10. Xeavin
      Xeavin
      • premium
      • 136 kudos
      We can't help you if you do not provide any useful information to replicate the issue. I have explained two times how to do that by now. Your issue might be completely unrelated. It is impossible to know without any info.
    11. Xansaibot7
      Xansaibot7
      • member
      • 1 kudos
      https://drive.google.com/file/d/1IW-W6y2ggiX098oGf12C4YyEtWoyEoLq/view?usp=sharing
    12. Xeavin
      Xeavin
      • premium
      • 136 kudos
      It looks like you are using Reshade. We have tested it with both the launcher and dinput.dll variants of this mod and they work just fine with it. Please fully remove Reshade and check again. Also test both variants (dinput.dll and launcher). Keep in mind that with the launcher, you need to start the game by using launcher.exe, not via Steam or manually with FFXII_TZA.exe. Also please provide more information about the crash itself. Does it hang with a white screen? How long until the game process closes? Or are you force closing it? Are you using MO2, Vortex or manually installing mods? Please also always test with all mods disabled except this one. If it still crashes, also send the new dump file. You can always also reach us on the modding discord if you want, where we can help much faster. Finally, also try things like updating Reshade or using the default configuration to rule out any issues caused by a specific Reshade config.
    13. Xansaibot7
      Xansaibot7
      • member
      • 1 kudos
      it seems that deleting reshade solved the problem. i will test more in a few days and say more about it. 

      And yes - i am using Vortex for mods

      P.S Sry for being annoying in another mod's comments page, didn't mean to be rude or anything....
    14. Xeavin
      Xeavin
      • premium
      • 136 kudos
      Good to hear that you can now at least play without crashes. As for the recent incident, it's all good. I have also already reverted the ban.
  3. sizeak
    sizeak
    • supporter
    • 0 kudos
    I had trouble getting this installed with Vortex on Linux (i.e. this applies to Steam Deck too) and found that the problem was that the default staging directory in Vortex was on a different partition to the game install, which forced Vortex to use symlinks instead of hardlinks. Symlinks don't work correctly with Vortex under Wine, this is why mods won't install correctly.

    So if you're on Linux / using a Steam Deck, make sure you check the Vortex settings that hardlinks are being used. If they are not and you cannot select them as an option, it's probably because you need to change the staging directory to one on the same partition! In my case, the "Suggest" button actually provided the correct path, but YMMV.

    The settings should look something like this for mod deployment to work correctly:
    1. Brianmac193
      Brianmac193
      • supporter
      • 0 kudos
      I know old thread, but how to give permission? Everytime I try it says error and retry loop. Like I'm not the administrator even though I'm on main account of deck.
  4. Brianmac193
    Brianmac193
    • supporter
    • 0 kudos
    Hello! FFgriever, I need your help. I have attempted EVERY possible installation construction I could find and I still cannot get this to work right. I followed the instructions on page 3 for manual installation, installed the 2015-2022 redist. file, have dotnet 6 desktop on the prefix for both Ffxii AND Vortex. (I have Vortex added as non steam game, with a separate prefix).

    I followed the instructions and when I looked at the hook.log file it was empty with 0bytes. 

    So is there ANY other way to manually install this? I've been modding for years, usually I inject files myself (placing them into the correct files/locations) so in not really sure what I'm messing up here. 

    Also, I knkw it's not your mod, but my Vortex, if I run. It trhough steam tinker launch doesn't register dotnet 6. But I can still use the native Vortex and manage the game but I can't get past the "file loader not detected" which is why I have tried manual install. 

    Please help!
  5. thalassios
    thalassios
    • member
    • 0 kudos
    From July 2025

    Took me a few hours to get this working on SteamDeck/ArchLinux with Vortex (I even got "The Planetary Age" running!). Using protontricks to install the latest  VC++ it has did not work for me.

    There are likely easier, simpler ways, but this is what worked for me and I hope it helps somebody.

    1.  Install the Latest ProtonGE from its github page (https://github.com/GloriousEggroll/proton-ge-custom)
    2. Install steamtinkerlaunch from the AUR
    3. Add steam Tinker Launch as a compatibility tool by running "steamtinkerlaunch compat add" in a terminal.
    4. Set "Proton-GE" as the Compatibility tool for FF12 in steam.
    5. Launch FF12 from steam once with no mods or anything done to it. (only need to get to the title screen and  then you can exit)
    6. Download LATEST VC++ Redistributables from MS here: https://aka.ms/vs/17/release/vc_redist.x64.exe
    7. COPY that "vc_redist.x64.exe" from downloads into the steam FF12 folder, specifically "~/.steam/root/steamapps/common/FINAL FANTASY XII THE ZODIAC AGE/x64/"
    8. Rename "FFXII_TZA.exe" to "REAL___FFXII_TZA.exe"
    9. Rename "vc_redist.x64.exe" to "FFXII_TZA.exe" and run ff12 via steam again. This will make steam/proton install the newest VC++ into the right container for FF12.
    10. DO NOT DELETE "REAL___FFXII_TZA.exe," Delete the VC++ exe that we named "FFXII_TZA.exe" 
    11. Rename "REAL___FFXII_TZA.exe" to "FFXII_TZA.exe" 
    12. Set "Steam Tinker Launch" as the Compatibility tool for FF12.
    13. Launch ff12 again, if this does not bring up the Steam tinker Menu, then exit as quickly as possible and Steam Tinker will bring up a window and ask "Retry With different settings", click that button.
    14.  From here click the "Game Menu" button
    15. In the new window it brings up Set:
    15a: Under "Gui Options" set "Requester Timeout" to 4
    15b: Under "Vortex Options", click the checkbox labeled "Vortex" and again set "Requester Timeout" to 4
    16. Click "Save and Play"
    17. A popup shoould come up that gives you 4 seconds to click "Start Vortex", click "Start Vortex"
    18. This will make "steamtinkerlaunch" install and launch Vortex using proton AND the VC++ we manually installed earlier.
    19. Set ff12 to managed in Vortex.
    20. Install mods through Vortex just like you would on windows.


    Once again some of this may not be necessary and there may be easier ways, but I hope this helps somebody and saves them the hours of debugging and research i did.




  6. yong50k
    yong50k
    • member
    • 0 kudos
    i can't apply this mod
    https://www.nexusmods.com/finalfantasy12/mods/332 by vortex
    i think i dun need to touch vbf file because of this mod. and author also said to.
    would you tell me what's the problem?
    1. ffgriever
      ffgriever
      • premium
      • 22 kudos
      What do you mean you can't apply it? As far as I see, it should work just fine with vortex.
  7. ancntastrnomer
    ancntastrnomer
    • supporter
    • 0 kudos
    Game is crashing on startup and I've narrowed it down to this mod, I've tried everything suggested in replies and bugs as well. Changing resolution and/or fps seems to get it to work for bout a minute, then crashes again. This started suddenly, bout 40 hours in. Only thing I can't seem to do is check if the VC++ is the correct version in steam prefix (I've searched google for help on this to no avail) however I am on windows 10 pro and downloaded and installed the version linked in your pinned comment but this didn't fix it either. Any help would be greatly appreciated!
    1. ffgriever
      ffgriever
      • premium
      • 22 kudos
      Like in you disabled all other mods and it still crashes? Disabling this mod alone doesn't prove anything, because it enables all other mods to work.

      If that's the case, then start with restarting (rebooting, not turning off and on again) your PC. Also make sure to verify your steam files.

      Then post contents of hook.log from x64 directory and check whether the game created a crash dump (there might be two of them, one in game's x64 directory, the other in %LocalAppData%\CrashDumps).
  8. DangerousDom
    DangerousDom
    • member
    • 0 kudos
    So i'm having trouble installing the EFL into the Open World Randomizer. I'm not using Vortex I have installed the randomizer manually then installing the rest through its launcher. When I try to install i get 'Failed to install the External File Loader, Expected files are missing'

    EDIT: I fixed it, i used an older version of EFL
  9. alann0610
    alann0610
    • premium
    • 0 kudos
    For those who are having issues on steam deck. 

    Starting with version 1.3.11 the below error occurs when launching on steam deck with launch option
    PROTON_LOG=1 WINEDLLOVERRIDES="dinput8=n,b" %command%


    71953.040:012c:0130:err:module:loader_init "DINPUT8.dll" failed to initialize, aborting
    71953.040:012c:0130:err:module:loader_init Initializing dlls for L"Z:\\home\\deck\\.local\\share\\Steam\\steamapps\\common\\FINAL FANTASY XII THE ZODIAC AGE\\x64\\FFXII_TZA.exe" failed, status c0000005


    I have to revert to 1.3.10 to be able to run this on steam deck.
    1. ffgriever
      ffgriever
      • premium
      • 22 kudos
      Replied in bugs as well.

      Update VC++ redistributables in the game's steam prefix. Also, if you installed the loader manually, remove vcruntime140_1.dll from x64
      directory.

      I'd say the easiest way is to add the installer anywhere and temporarily change game's exe in steam configuration, then launch the game. Once it's installed, just change it back to the original one. You might need to change proton version in compatibility if it doesn't install properly.

      Works just fine on steam deck. I'm using it myself.
    2. Souchyness
      Souchyness
      • member
      • 0 kudos
      Hey just wanted to thank you, my problem was exactly that, an old version of VC++ redistributables. Just updated it on the prefix and the game launched just fine.
    3. ffgriever
      ffgriever
      • premium
      • 22 kudos
      Great to hear. Although I'd recommend to use protontricks to do that. A few more steps to install it, but it's a tool that will definitely come in handy in the future :)
  10. OmegaPotion
    OmegaPotion
    • premium
    • 8 kudos
    Anyway to use this awesome mod without having to download Vortex?
    1. ffgriever
      ffgriever
      • premium
      • 22 kudos
      Yup. Just copy the dinput8.dll along with simple log and trampoline into game's x64, then the loader into modules folder.
    2. OmegaPotion
      OmegaPotion
      • premium
      • 8 kudos
      Awesome thank you
    3. RedSamurai7
      RedSamurai7
      • supporter
      • 0 kudos
      Where is the modules folder? I see one in the mod folder, I don't see anything in the games install. 
    4. ffgriever
      ffgriever
      • premium
      • 22 kudos
      It should be in game's x64 folder. If it gets created in mods folder, then you most likely have a very old vortex support plugin.
  11. Cryptghast11
    Cryptghast11
    • supporter
    • 0 kudos
    i know this alot to ask. but step by step manual install instructions for steam deck manual no vortex?
    1. ffgriever
      ffgriever
      • premium
      • 22 kudos
      Try minnou's comment (on the second page now, it seems that I can't link to a particular page now?).

      The difference is that now you have to use protontricks to update your vcredist.