It recommends a system restart (maybe optional, but I did). Use option 4 and follow prompt until the bat file closes itself. Run the bat file, reading carefully as you go so you know how to disable or change modded games. So, paste the pastebin contents into notepad, name it what you like but with extension bat, e.g eaMods.bat. If not you probably need to run Frosty as Admin and then launch the game through Frosty first. I added some lines to the pastebin to make the batch file work for ME:A as well īefore running the bat be sure that your ModData folder is showing up in (default C:\Program Files\EA Games\Mass Effect Andromeda). The second batch file is exclusive to Battlefront 1-2 but support for other frostbite games can be added This NEEDS to be disabled before launching any other EA game as changing the env variable affects all frostbite games. Paste the pastebin code into notepad or text editor of your choosing and save as "anything".bat. Frosty Mod Manager/Editor uses a command line argument to change the game's datapath to the modded one when launching the game through that, which does not work with EA Desktop This is because EA Desktop does not support launching a game with CMD line arguments (which causes issues outside of modding EA games). Me and a couple other modders made another batch file which uses environment variables to set the modded datapath. This 'patch' is adaptable to other Frosty games, but you would need to add a few lines to the batch file (mostly paths and variables) to add support for each game.īut here's the essential reading/instructions from user Dulana57 This batch file will let you use FMM mods with Mass Effect: Andromeda but also SW: Battlefront 1 and 2. I highly suggest Frostbite engine mod users check out the readme for Frosty Fix and use that instead: Update: The below method is outdated, since Dulana57 created and shared a utility to do the same thing quicker.
0 kommentar(er)
