GallowsGrip Posted October 1, 2017 Share Posted October 1, 2017 So I've been using Frosty Mod Manager to load my mods (I have around 14 or so) and it's been working wonderfully... up until I tried to travel to Havarl or Voled. The game launches completely fine, and lets me click resume, but i get stuck on the loading screen and can't even play the game. It starts to load and gets around 4/5 to the end, but then it just stops. The game doesn't crash or anything, it just stays on the loading screen. It works fine if I launch it without mods, but I really wanted to make my Ryder look awesome :( I've tried checking the DLLs, uninstalling Frosty and reinstalling, starting a completely new save game, loading back to a previous save game, and repairing mass effect on origin. I don't know if its just a certain mod I have or something else. I've yet to uninstall and reinstall Mass Effect itself because i wasn't sure it would help and didn't want to wait for it to download again, but at this point, I'm willing to do pretty much anything just to play with mods. Link to comment Share on other sites More sharing options...
JimmyRJump Posted October 4, 2017 Share Posted October 4, 2017 Most probably a mod issue. Try loadng a save from right before going to either Havarl or Voeld, but load that save through FMM without any mods active (Frosty Mod Manager doesn't alter any core game files, it applies the mods everytime the game starts) and see if this way you can reach any of the two planets. If you do get there, save when on the surface of either planet, quit the game, re-apply the mods and try loading the last save. Another way is to de-activate all mods and re-apply them one by one. Time consuming, sure, but it's about the only way to get to know which mod doesn't want to play nice... Link to comment Share on other sites More sharing options...
femshepping Posted October 8, 2017 Share Posted October 8, 2017 Iâve seen quite a few people on tumblr having this issue after updating to latest FMM. After updating, the game wonât even launch from FMM for me despite installing properly and having the same mods so Iâm not too sure whatâs even going on :( Link to comment Share on other sites More sharing options...
JimmyRJump Posted October 8, 2017 Share Posted October 8, 2017 Iâve seen quite a few people on tumblr having this issue after updating to latest FMM. After updating, the game wonât even launch from FMM for me despite installing properly and having the same mods so Iâm not too sure whatâs even going on :sad:I've had the issue with an update from FMM v1.0.2b to v1.0.3a3. Game wouldn't launch even after having reverted back to v1.0.2b. After having deleted FMM and then installed a back-up install of Andromeda and again installing FMM v1.0.2b, everything worked again... In my case, FMM is installed on a different drive than the game. Link to comment Share on other sites More sharing options...
GallowsGrip Posted October 9, 2017 Author Share Posted October 9, 2017 Most probably a mod issue. Try loadng a save from right before going to either Havarl or Voeld, but load that save through FMM without any mods active (Frosty Mod Manager doesn't alter any core game files, it applies the mods everytime the game starts) and see if this way you can reach any of the two planets. If you do get there, save when on the surface of either planet, quit the game, re-apply the mods and try loading the last save. Another way is to de-activate all mods and re-apply them one by one. Time consuming, sure, but it's about the only way to get to know which mod doesn't want to play nice...I tried deactivating all of my mods through FMM and launching it, and it loaded fine. I then tried to travel to Havarl and Voeld, and experienced the same issue. I have absolutely no idea why it's doing this. I'll try reinstalling Andromeda and see how that works, but for now I guess no mods for me :( Link to comment Share on other sites More sharing options...
JimmyRJump Posted October 9, 2017 Share Posted October 9, 2017 Most probably a mod issue. Try loadng a save from right before going to either Havarl or Voeld, but load that save through FMM without any mods active (Frosty Mod Manager doesn't alter any core game files, it applies the mods everytime the game starts) and see if this way you can reach any of the two planets. If you do get there, save when on the surface of either planet, quit the game, re-apply the mods and try loading the last save. Another way is to de-activate all mods and re-apply them one by one. Time consuming, sure, but it's about the only way to get to know which mod doesn't want to play nice...I tried deactivating all of my mods through FMM and launching it, and it loaded fine. I then tried to travel to Havarl and Voeld, and experienced the same issue. I have absolutely no idea why it's doing this. I'll try reinstalling Andromeda and see how that works, but for now I guess no mods for me :sad: Provided you have the drive space, after having re-installed the game, first make a back-up of it before activating FMM again. It'll save you from having to download the whole kaboodle again in the future. Link to comment Share on other sites More sharing options...
DankRafft Posted October 10, 2017 Share Posted October 10, 2017 Most probably a mod issue. Try loadng a save from right before going to either Havarl or Voeld, but load that save through FMM without any mods active (Frosty Mod Manager doesn't alter any core game files, it applies the mods everytime the game starts) and see if this way you can reach any of the two planets. If you do get there, save when on the surface of either planet, quit the game, re-apply the mods and try loading the last save. Another way is to de-activate all mods and re-apply them one by one. Time consuming, sure, but it's about the only way to get to know which mod doesn't want to play nice...I tried deactivating all of my mods through FMM and launching it, and it loaded fine. I then tried to travel to Havarl and Voeld, and experienced the same issue. I have absolutely no idea why it's doing this. I'll try reinstalling Andromeda and see how that works, but for now I guess no mods for me :sad: If this issue appears by loading Andromeda through FMM (with deactivated mods) and otherwise it would run fine, when you start it through Origin you could try to use another version of FMM. Some mods only run with the newest version of FMM, some can be run with older versions, too. I haven't had any issues since I've upgraded to v1.0.3alpha3. By the way, reinstalling the game doesn't change anything which couldn't be solved by just deleting the ModData folder in the game's main folder since FMM doesn't change the vanilla game files.. Link to comment Share on other sites More sharing options...
JimmyRJump Posted October 10, 2017 Share Posted October 10, 2017 If this issue appears by loading Andromeda through FMM (with deactivated mods) and otherwise it would run fine, when you start it through Origin you could try to use another version of FMM. Some mods only run with the newest version of FMM, some can be run with older versions, too. I haven't had any issues since I've upgraded to v1.0.3alpha3. By the way, reinstalling the game doesn't change anything which couldn't be solved by just deleting the ModData folder in the game's main folder since FMM doesn't change the vanilla game files.. I'm still using v1.0.2b of FMM and each and every mod (old and recent) run perfectly through it. Before installing my Andromeda back-up, deleting the ModData folder didn't make the game work again... Installing the back-up did, so, there you go... Link to comment Share on other sites More sharing options...
DankRafft Posted October 10, 2017 Share Posted October 10, 2017 If this issue appears by loading Andromeda through FMM (with deactivated mods) and otherwise it would run fine, when you start it through Origin you could try to use another version of FMM. Some mods only run with the newest version of FMM, some can be run with older versions, too. I haven't had any issues since I've upgraded to v1.0.3alpha3. By the way, reinstalling the game doesn't change anything which couldn't be solved by just deleting the ModData folder in the game's main folder since FMM doesn't change the vanilla game files.. I'm still using v1.0.2b of FMM and each and every mod (old and recent) run perfectly through it. Before installing my Andromeda back-up, deleting the ModData folder didn't make the game work again... Installing the back-up did, so, there you go... And the backup had the exact same version of the game? If so, maybe your game files were corrupt but that doesn't have anything to do with FMM. Repairing the game through Origin should have the exact same result as reinstalling. Link to comment Share on other sites More sharing options...
JimmyRJump Posted October 11, 2017 Share Posted October 11, 2017 If this issue appears by loading Andromeda through FMM (with deactivated mods) and otherwise it would run fine, when you start it through Origin you could try to use another version of FMM. Some mods only run with the newest version of FMM, some can be run with older versions, too. I haven't had any issues since I've upgraded to v1.0.3alpha3. By the way, reinstalling the game doesn't change anything which couldn't be solved by just deleting the ModData folder in the game's main folder since FMM doesn't change the vanilla game files.. I'm still using v1.0.2b of FMM and each and every mod (old and recent) run perfectly through it. Before installing my Andromeda back-up, deleting the ModData folder didn't make the game work again... Installing the back-up did, so, there you go... And the backup had the exact same version of the game? If so, maybe your game files were corrupt but that doesn't have anything to do with FMM. Repairing the game through Origin should have the exact same result as reinstalling. That's the reason I keep a back-up; to have the exact same version of whatever working game version I'm playing at any given time, everytime. Repairing the game "should" have the same effect?. Why start to speculate? Especially in the knowledge that a repair keeps the game's roots in place while a delete and re-install doesn't. Also, in my case, a repair would let me end up with a game version I don't want. Remember that no two computers are alike and that different configurations will have different results, whatever one does. Link to comment Share on other sites More sharing options...
Recommended Posts