Jump to content

Recommended Posts

Posted

The FMM v1.0.4.2 runs perfekt on my Win7 64 System. After I switched to Win10 64 the FMM don´t launch MEA. I´d tried FMM v1.0.5.9 and it´s the same.

 

I forgot, NO it is not a pirate Version of MEA.

  • 2 months later...
  • Replies 41
  • Created
  • Last Reply

Top Posters In This Topic

Posted

With win10 build 1909 the latest FMM (1059) worked just fine. After windows update to build 2004 not any more. Symptome is like same as described above. FMM starts applying mods, launches MEA, then nothing happens.

In task manager MEA is running under FMM.

Fortunately 2004 could be undone, so with older version 1909 it works again.

Posted

 

 

at time of posting video may not work cause of SD processing of video is taking for ever

 

 

but since 2004 win10 update, frosty 1.0.5.9 not 1.0.5.7 will not correctly launch MEA, both worked perfect in 1909 with same game install and mods.

normal tricks to fix FMM do not work.

  • 2 weeks later...
  • 4 weeks later...
Posted (edited)

I am also experiencing this issue. It first started happening after I updated to Windows 10 build 2004. I rolled back to 1903, but the issue persists. I've tried all the typical tips online on how to fix it and nothing works. I tried the decrypt dll trick, uninstalling/reinstalling the game, etc. No good.

Edited by SireEvalish
Posted

I'm running Win10/64-bit, version 2004, Build 10.0.19041, and Frosty version 10.0.5.9 with no problems. Latest EA/Origin update also already applied. Still no issues...

 

But I'm only using .fbmod-formatted mods. :thumbsup:

  • 5 weeks later...
Posted

Here it stopped working in the last update from Origin.

 

The mod manager not launch the Me Andromeda...

Same here for me for Battlefront 2. I double checked to see if I had the dll issue mentioned early and I don't have that dll in my files.

  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...