- HOW TO USE FROSTY MOD MANAGER 1.0.4 HOW TO
- HOW TO USE FROSTY MOD MANAGER 1.0.4 INSTALL
- HOW TO USE FROSTY MOD MANAGER 1.0.4 PATCH
- HOW TO USE FROSTY MOD MANAGER 1.0.4 MODS
- HOW TO USE FROSTY MOD MANAGER 1.0.4 CODE
HOW TO USE FROSTY MOD MANAGER 1.0.4 MODS
Re-launch the game with the mods through FMM, this time the game will open with mods launched.
Game might launch tho (mods still won't be working), close the game (task manager if necessary), and on to my next last step Now that the mods are properly loaded (but EAPlay won't recognize them), close MEA and open FrostyFix 4, check EAPlay, select the game, the folder, and launch with mods. Launching the game like that won't work yet, it might launch the game but with no mods (that's what happened with me) Create ur mod list, activate them, all standard the way they should be (with administrator on in everything), launch the game through Frosty (I have downloaded the bcrypt.dll from nexus and pasted it in the ThirdParty folder inside the folder where FMM is located - don't forget to delete the cryptbase.dll) You probably should delete the moddata folder to start the process as if it was from the beginning I have tried EVERYTHING out there and I gave up until MEA came to EAPlay, and I decided to try once more. The only thing you should have to do to get this batch and program working after installing the game is launching ME:A from Frosty (with Admin permission) to build your ModData folder, and then using the program or batch to enable mods. I never touched any of those files, so if you did a reinstall of ME:A might help. My only other guess might have to do with a potential solution that I think used to work to get Frosty mods working- some users in the past suggested deleting bcrypt.dll or making other changes to game folders to have ME:A launch with mods.
HOW TO USE FROSTY MOD MANAGER 1.0.4 INSTALL
Unfortunately I'm at a loss of how else you could fix this, since the only thing I added to the original batch file was finding the install directory of ME:A and setting the gamepath to ModData- and it looks like you said that all looks good. Have you tried the program I updated the top of the post with? Functionally it should be doing the same thing as the batch file, so it might not work for you too, but it might be worth a try. You mentioned permissions, but just to confirm, that means your ModData folder shows in the ME:A install directory? If you've checked the registry path and it matches with the value for install directory (as you've said) then %minstalldir% is filling that in, so there shouldn't be any problems with that path. Sorry to hear it's not working for you, and thanks for listing the steps you took.
HOW TO USE FROSTY MOD MANAGER 1.0.4 PATCH
Thanks to those from Battlefront Discord that worked on the SWBF1+2 patch and to Dulana57. After starting up my PC I ran Frosty Mod Manager and launched through Frosty with mods enabled. It recommends a system restart (maybe optional, but I did). Use option 4 and follow prompt until the bat file closes itself.
HOW TO USE FROSTY MOD MANAGER 1.0.4 HOW TO
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.
HOW TO USE FROSTY MOD MANAGER 1.0.4 CODE
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)
