[Released] EMF v1.0.3a (BMS 4.34)
-
East Mediterranean Front (EMF) v1.0.3a
BMS 4.34Installation
1. Download EMF v1.0.2 from Direct Link or MediaFire .Unzip the file and place the Add-on emf folder into C:\Falcon BMS 4.34\Data. Place the EMF Settings.cfg wherever you want.
Go to C:\Falcon BMS 4.34\Data\TerrData\TheaterDefinition and open theater.lst with notepad. Add the following line: Add-On emf\theaterdefinition\emf.tdf Save the file. If you have,already, downloaded and installed EMF v1.0.2, then proceed direct to step #2.2.Download EMF v1.0.3 from Direct Link or MediaFire. Unzip the file, and copy & paste Add-on emf folder to C:\Falcon BMS 4.34\Data. Allow to overwrite files. Also, copy & paste the new EMF Settings.exe over the old one (from EMF v1.0.2).
3.Download EMF v1.0.3a hotfix from Direct Link. Unzip the file and copy & paste Add-on emf folder again to C:\Falcon BMS 4.34\Data. Allow to overwrite files. This fixes the elevation issue in airbases and airstrips. Upon successful installation, you will see “East Mediterranean Front v1.0.3a” in the main UI screen, when you launch BMS 4.34.
Enjoy!!!
EMF v1.0.3 Changelog
1.Fix of emf.thr. You don’t have to press “nuke all” or “clear all” button in TE window anymore. Thus, the TE_Creation.pdf shipped with EMF v1.0.2 becomes obsolete.
2.Remove around 2.000 non essential bridges. Now, theater’s loading time has been reduced noticeably.
3.Improve of tiling in Libya (thnx Nuno Santos).
4.Various improvements in te_new.tac.
5.Correction of Nea Anchialos town.
6.RIM-7 correction of Max Gs.
7.Correction of TWR not clear you for departure on time in some airbases.
8.Add ILS at Konya Airbase.
9.Fixing Noname issue in various objectives.
10. Ability to choose between two (2) Maps in UI. Plz check EMF Settings.exe
11. New splash pictures and Theater main title.
12. Removal of EMF v1.0.2 campaigns at the moment. Will be added in next update, due to emf.thr overhaul.***Caution*** Missions (.tac) created with EMF v1.0.2 will NOT work with EMF v1.0.3a. ***Caution*** It is advised to create new logbook for 128seg theaters like EMF, or at least to import only the .lbk file, without the callsign.ini file.
-
Great work, once again!:thumb::thumb:
Cheers!
-
Thx on this great theater!!
Hope new campaign will come soon…1-2 weeks:D -
About the logbook, does it affect and viceversa?
Meaning if you create your logbook when in 128seg and then switch to 64seg will it cause trouble?
What if no logbook creation take place and you use the stock vanilla one? Will it also have trouble?Sent from my SAMSUNG-SM-T818A using Tapatalk
-
Hello Mystic_J, thanks for your effort to bring back and support this nice theatre.
Do you plan to expand the map to the North - with Bulgaria, Romania and Crimea?
-
About the logbook, does it affect and viceversa?
Meaning if you create your logbook when in 128seg and then switch to 64seg will it cause trouble?
What if no logbook creation take place and you use the stock vanilla one? Will it also have trouble?Sent from my SAMSUNG-SM-T818A using Tapatalk
It works vice versa. No problem with 64seg theater. You can use stock or even an old one. But some people experience problems if they improperly import their old 4.33 logbook. So, in order to be on the safe side and cover greenhorners as well, I’ll stick to the create a new logbook and don’t import an old one.
-
Hello Mystic_J, thanks for your effort to bring back and support this nice theatre.
Do you plan to expand the map to the North - with Bulgaria, Romania and Crimea?
Next will be Syria.
-
Thanks for the update!
Can I load a TE from 1.0.2 into the TE editor in 1.0.3 and save it there in order to “convert” it or will I have to use Mission Commander for this?
All the best, Uwe
-
Try with MC, although I don’t think it will work.
-
Thanks for the update!
Can I load a TE from 1.0.2 into the TE editor in 1.0.3 and save it there in order to “convert” it or will I have to use Mission Commander for this?
All the best, Uwe
No saving with TE editor will not work. TE editor will save the file with version 73 and not version 100.
Plenty of things will be missing from the file.Old files need to be converted with MC if you want to use them.
Gr Falcas
-
Great work. I am waiting next update in excitement thank you
-
A big thanks for this big effort. Be well Mystic!
-
I hope this is the correct thread to report issues. Landing at Souda (RW 11) I found what looks like some “flattening” issues with the RW, the underlying ground flickered through over the entire runway length (see attached).
All the best,
Uwe
-
i had the same in souda and kalamata
-
Can’t reproduce it. Could you increase your anisotropic and MSAA values a bit and check again?
-
had almost the same issue in Anchialos. some tiles on the taxiway (330sq) and beginning of runway 26 appeared like grass.at first i thought it was my graphics but my wingman had the same issue
-
Mystic, something has gone wrong somewhere with the ATC folder - EMF installs all the .dat files into the Korea directory but worse it overwrites the airbase.lst file and seems to have screwed the Korea theater.
Easy to fix manually thanks to a backup of the install, but you may want to take a look at the installer. Not sure if this has happens before or after 1.0.3
-
Hi Malc,
That’s impossible because all the subfolders lie underneath Add-on emf folder, including ATC folder (EMF v1.0.3\Add-On emf\Terrdata\ATC)
Could it be, that you accidentally copy & paste emf ATC into stock KTO one?
-
Hi Malc,
That’s impossible because all the subfolders lie underneath Add-on emf folder, including ATC folder (EMF v1.0.3\Add-On emf\Terrdata\ATC)
Could it be, that you accidentally copy & paste emf ATC into stock KTO one?
No copy/pasting here, only extracting the distribution files.
-
Well, I don’t know what went fubar in your case. I’ve checked again that all subfolders are under master Add-on emf folder.