@Trigger said in BMS Other Fighters Mafia (BMSOFM) Journal:

Hello Community

How if possible does one just revert the avionics to that of the viper? For instance the the F-35’s? They have the F-18 FLCS and avionics. I’m just not a fan of it and cant find documentation on its use I’m just pressing buttons on the OSBs and praying.

Thank you

Hi, Trigger, Another option is to paste set g_bEnableWIPF18Avionics 0 into your BMS User Config file. This “turns off” the new F18 avionics

Hi, @Jackal . One of the specific things we had tested were your TE’s. I didn’t see any issues, either.

Good Day, All.
We have been testing for U7 compatibility with the OFM 2.5.8 Theaters with the 2.6.0 UniUps, and am happy to report no issues.
We’ve tested compatibility with new and old campaign and TE’s in at least 3 different Theaters, so we feel pretty secure.
Let us know if you find and issues in an OFM Theater

@Trigger said in OFM-Balkans for BMS 4.37.4:

@drtbkj Hey are the airports purposefully not the same as the Stock Balkans theater? For example Aviano airbase in the stock is more realistic different from the OFM theater, Brindisi Casale airport also. Just wondering if this is a mix up on my end or intended?

Hi, Trigger.
Yes, @cougar56th and the Balkan’s Team use their own Objective data. And yes, it is more realistic. I believe we did that to be more consistent with our other Theaters’ database and we didn’t want to usurp the BT’s work

Hi, again. One more update for today…

Even way back in the AIM-120D days, we sometimes release something even before it is refined. That is purely to get input from the BMS Group. We “enlist” you all as testers.

Good Day, All. Some things came up in another thread that bear repetition here…
1)The OFM is a group of BMS enthusiasts, but not the BMS Dev’s. Our work is our own, and the BMS Dev’s have no responsibility for it. We don’t have BMS hard code access. So, we do what we can with what we have. We never claim perfection, either. But, you’ll always get our best.
2) The OFM goal has always been is to give people options. So, with things like the AIM-174,AIM-260, AGM-184, etc., we try to “tread softly” in how broadly we equip the jets. We know not everyone will want to use them, and we are completely fine with that. You can add them to your jet of choice with the BMS Editor
3) We are not, or have ever claimed , to be the only third party developer. I feel confident that we have been very vocal over the years with our gratitude towards the contributions of people like Radium, Cougar from the Balkans Team, and others. Nor do we claim to make all the newer weapons in BMS. In fact we try , in every release note, to credit everyone’s contributions.

@Logic said in EZBoards - Generate kneeboards (flights, comms, stpts, weather) from briefings:

@drtbkj Hi, you need to run Ezboards as the last step of this. Just before committing to 3d.

Thanks for the reply. Running BMS in windows, “minus’d” out and ran ezboard. Got the “success” and that it wrote to dds7892 and 1403. Unfortunately, that didn’t work.
EZwatch isn’t working either.
BTW, I didn’t do this for testing ezboard, but if you were to also set up WDP, which would overwrite the other?

@Logic and Group. My EZ Boards has recently stopped working. I would appreciate any input on my efforts to troubleshoot.
I have…

1. redownloaded version 14 and the net core
2. The 2 config entries are correct
   3)I run ezboard.batch, get the “success, hit any key” and hit enter
3. In 2D, I save the Link16,HARM, and COMM plans then the DTC
4. Go into Briefing hit click on Print.
   Ezboard does display but not the current mission. In fact, and I’m going to further test this, is it seems to display the previous mission

@Scorpion82 said in BMS Other Fighters Mafia (BMSOFM) Journal:

@oakdesign

the OFM DB is standardised across theaters. It has its pros and cons. At some point it may become a mess, if there are too many additions over a long time.

Anyone who has followed the thread for awhile know that back around the holidays we lost a key member of the OFM Team. We hope he is back soon. As we move forward @ccc1tw( as always) and others have been steadily “behind the scenes” giving us great material ,and @Scorpion82 has really stepped up to the plate. The 2.6.0 UniUp was his work.
As much as we miss Eddie, I am at least grateful for the timing. Our goal, considering 4.38 was/is somewhere on the horizon, was to get a .37 version of all the OFM Theaters out. So, we spent a lot of months releasing Theater-specific updates. .Then redoing them as new material was available, on and on. We finally achieved the final version (2.5.8) of all the OFM Theaters. So, at least for now, we are refining them with THE 2.6.0 UniUps.

Good Day, All.
Here’s a little present for you, CVN 65 and IFLOLS skins.
Copy them to Falcon BMS 4.37/data/any OFM Theater/Terrdata/objects/Korea objects.
https://www.mediafire.com/file_premium/67ryjcyythid83s/CVN_65_skins.7z/file

Good Day, All.
Just to clarify Scorpion’s and my conversation from this morning, He’s right that the 2.6.0 UniUp does not have the 120D. However, the hotfix corrects that… https://www.mediafire.com/file_premium/w2ib4gvicay25i7/OFM_UniUp_2.6.0_Hotfix.zip/file

@Scorpion82 said in BMS Other Fighters Mafia (BMSOFM) Journal:

@drtbkj

have to correct you here, the D is not enabled with 2.6.0. It would be in a future release.

HHHmmm, it is in mine. Let’s get together, maybe we need a 2.6.1 ?

@dawgboy said in BMS Other Fighters Mafia (BMSOFM) Journal:

@drtbkj …If I make this change in the Editor to add AIM120Ds, do I have to make this edit each time y’all upgrade the theater? TIA!

Hi, @dawgboy . Actually, with the 2.6.0 Uni Up the 120D’s are already activated. And, the current plan is to continue to do so in the future. Plus, Brother Scorpion makes a good point. When we were pre-release testing 2.6.0 we found that the 2.5.8 120D on/off files were borking things. So, without making new on/offs each time, which is not our current plan, you should proceed carefully. The simple way to protect yourself is to backup your Falcon BMS/data/OFM Theater/terrdata/objects/xml files.

Hu, @Trigger
First, let me give some more feedback on your earlier question about the AIM-120D. I did some testing in the Viper, which currently carries the 120C. The most noticeable difference at closer range is that the Bandits are significantly less able to go cold and out run the missile.
The reason we didn’t set up the Viper with the D is that we are aware that not everyone wants it. You can add it to the Viper in the Editor by adding to Squadron Stores , then appropriate hardpoints.
Now, on to your latest questions…

1. Yes, Low Observability is modeled in the F-35(B and C , at least) ,the Raptor, and I believe the J-20. The most work was done to the 35C. The F-35A has been a problem child for us, causing some CTD issues in the past.
   What we did was take real world RCS values and plugged them it as well as we could. RL RCS changes with aspect, but BMS only has one RCS value. What we did was use RL frontal aspect RCS values. Once again, what we’ve tried to do is produce Theaters that please the most people.
2. Yes, AI does want to load in Beast Mode. And, I believe that the RCS if weapons and racks are not modeled, though we’ve never been able to get verification on that. When I fly the Panther on Stealth strikes, I use " the honor system" and only carry AIM-9 or -132’s on the wings.
3. My personal loadouts are not quite stock, affectionately known as AWAS( Airwolf’s Wild Ass ,Stuff ) but I believe the 35C are set with A_G- weapons in the outer bays. The inner bays are AAM only, as in RL . You’re not seeing any?

VERY nice.

@Quasi_Stellar said in Wheel Brakes key command not working:

@drtbkj Make for certain something isn’t bound to the brake axis. That will override the KB command at times.

Hi, Quasi. Thanks for that reminder. The Op had an axis set.

@Trigger said in BMS Other Fighters Mafia (BMSOFM) Journal:

I noticed the 120D is not in the TacRef? Is there any documentation on it so I can see its differences between the 120C for weapon employment etc…?

Hi, @Trigger . The HUD DLZ for the 120D is fairly accurate. The difference is employment from the C is simply a function of range. I’ve shot at a/c such as A-50’s at 60+ miles and gotten hits. Against fighters, especially given the AI’s tendency to go cold when you shoot, 40 miles is a fairly safe engagement range for hot targets. In a pure tail chase engagement against fast jets 20 miles is a good range.
Tbh, It’s been over a year since I’ve done real testing. We’ll do some and I’ll give you more specifics later.

Good Day, All,
I am helping a friend set up his HOTAS. He does not have toe brakes, and the K key command is not working. Is that still an active callback?

Good Day, All.
We found a small bug with the F-22 when the AIM-120D is enabled.
Here is a Hotfix.
https://www.mediafire.com/file/w2ib4gvicay25i7/OFM+UniUp+2.6.0+Hotfix.zip/file
Just unzip and copy/paste the files to x/BMS 4.37/data/OFM Theater/Terrdata/objects, AFTER doing the 2.6.0 UniUp.
Speaking of the AIM-120D, we’re going in a slightly different route with that. Rather then the On/off files we’ve included for quite awhile, we’ve decided to do future releases with them enabled.
If you don’t want the 120D in your Theater, simply go it the BMS Editor under squadron stores and zeroize the value.

Good Day, All.
We found a small bug with the F-22 when the AIM-120D is enabled. There is now a link in the first post above for the Hotfix.