BMS Other Fighters Mafia (BMSOFM) Journal

[Trigger]

I thought I fixed the Cockpit issue with the F-18 but somethings missing from my rampstart. In a TE when the plane is already set up for me I don’t get the canopy light warning.

As for the F-22 stabilizer I’ve narrowed down the issue to the actual model. It’s not in the .dat .txtpb or the parent. It’s not in the editor either it’s something to do with the model or .bml and I don’t have the skills for that yet.

[Scorpion82]

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

I thought I fixed the Cockpit issue with the F-18 but somethings missing from my rampstart. In a TE when the plane is already set up for me I don’t get the canopy light warning.

As for the F-22 stabilizer I’ve narrowed down the issue to the actual model. It’s not in the .dat .txtpb or the parent. It’s not in the editor either it’s something to do with the model or .bml and I don’t have the skills for that yet.

There is an entry in the .dat/.txtpb files called something like “canopy handle” set this value to 0 and the “locking/unlocking” is not required.

That the stabiliser issue in the F-22’s cockpit wings model is a model problem has been discussed in the past already.

[Trigger]

@Scorpion82 I know, Airwolf just asked if I could look into it after i found a work around for the landing gear and I was only able to narrow it down to the model but I don’t have enough experience with that to go further.

EDIT: Dang I was hoping that would fix it come to find out its already set to 0 and the light is on. Only at 24,000 and higher. I don’t see a negative side effect occurring but the master caution going off every sudden dip in altitude a bit jarring sometimes.

[drtbkj]

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

EDIT: Dang I was hoping that would fix it come to find out its already set to 0 and the light is on. Only at 24,000 and higher. I don’t see a negative side effect occurring but the master caution going off every sudden dip in altitude a bit jarring sometimes.

Hi, @Trigger . I’ve been trying to repro your canopy light issue without success.
It looks like I’ve found that the command you @Scorpion82 and you were mentioning , canopy handle method( line 1203 in f-18E.txt). It’s 0 in mine , and I confirmed it’s 1 in a Viper.
I also checked art/ckptart/F-18E-Type . I don’t have anything mapped to HOTAS, so I’m using the in-pit hotspot which has AFCanopyOpen -1.12040 -1.123762 -1.598873 20 322 1
AFCanopyClose -1.12040 -1.123762 -1.598873 20 322 2
Have you seen this issue in other OFM Theaters? How about in the F-18C?
mapped to it.

[drtbkj]

Good Day, All. We have have been testing the OFM Theaters for U8 compatibility and so far haven’t found any bugs. Here is a good place to let us know if you find issues.
Brother Tomcat2 has informed me that our sound files need to be updated for new AWACS functionality. We are working on that.

[drtbkj]

Good Day, All. Here’s an update on the new U8 AWACS messages. It turns out the sound files are Theater-specific, so we can’t do a simple Universal Updater. We’re working on getting the changes to you. Thanks as always to Brothers @Scorpion82 and @Tomcattwo

[drtbkj]

One more update for today… We’re in the process of testing the sound files updates. It will be a simple hotfix, just drop some files into x/4.37.8/data/the specific OFM Theater/sound, replacing what is there. We’ll be posting them in each Theater’s Forum Tread. Nevada will be first, probably tomorrow

[Trigger]

Hello Mafia

The AIM-260 does not have a clearly labeled .dat file. Which one is it using?

Edit: Where are weapons tied to .dat files? Like how do the new weapons created know which .dat file to use? Like AC are tied in the AC data section of the CT record.

Thank you

[drtbkj]

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

Hello Mafia

The AIM-260 does not have a clearly labeled .dat file. Which one is it using?

Edit: Where are weapons tied to .dat files? Like how do the new weapons created know which .dat file to use? Like AC are tied in the AC data section of the CT record.

Thank you

Hi, @Trigger . With thanks to Brother Scorpion for the info, here is the Scoop.
The AIM-260 uses the AIM-174B misdat. I found that with the Editor under the Weapons/Sim WeaponData tabs. The sixth column over is Missile/Bomb PTR.
You can also find a list of ptr’s in data/Theater/sim/misdata/MisTypes.LST.
In that file the ptr is the file line number minus 2. So. the AIM-174/260 in line 228=ptr 226
On to sound file testing…

[Trigger]

@drtbkj Thank you! And @Scorpion82

[drtbkj]

Good Day, All. We have completed, thanks to @Tomcattwo , the bulk of the u8 sound updates for the OFM Theaters. The procedure is pretty simple.
Step 1- Copy/paste set g_bAwacsGameplayMessages 1 into your BMS/User/Config/BMS User.cfg
Step 2- Go to here https://www.mediafire.com/folder/1k76i68fspa00/BMS4.37.8+OFM+Sound+File+Updates select your Theater and download the zipped folder.
Step 3- Unzip and copy the files to BMS/data/ your OFM Theater ver. 2.6./Sounds , overwriting what is there.
This will give you the new AWACS messages such as Station time commence, etc.
As for OFMKTO, I believe that draws off the base BMS, and I am checking on the status of OFM Balkans and OFM-MidEast 128

UPDATE: It’s confirmed that OFMKTO is functional as is. Also, we are checking the status of OFM-Balkans,OFM-Israel, and OFM MidEast128

[Jackal]

@drtbkj
Hi there, Fra’, how you going?
Seen that, I volunteer to test Nevada then, if you like it.
Please let me know.

With best regards.

[drtbkj]

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

@drtbkj
Hi there, Fra’, how you going?
Seen that, I volunteer to test Nevada then, if you like it.
Please let me know.

With best regards.

Hi, Compadre, You’re input is always welcome

[Jackal]

@drtbkj
Thanks, Joe - don’t think I’ll take too much time for this. I’ll keep you updated about the results, but I think all will be fine.

To soon.

[drtbkj]

Good Day, All,
The sound updates fir OFM-Balkans, OFM Mid East 128, and OFM Israel are done , Please see the post from 3 days ago for link and instructions.
Note on OFM-B and - Although the file names say 2.5.8 , it has been tested for stability in the 2.6 version

[drtbkj]

As I was doing the sound file releases I noticed some of the OFM - Theaters threads have been around awhile, and perhaps confusing to newer BMS Members. So. here’s a bit of " refresher training" for our Theaters.
The latest full Installer versions of our Theaters is 2.5.8, except Nordic which is 2.5.9. On top of that , there has been a 2.6.0 Universal Updater, and a later Hotfix.
Also, some of the Theater threads may be listed for earlier versions of BMS , but all have been tested in BMS 4.37.8
All the files can be found at…
https://discord.com/channels/797936162638659594/1021169991367806976

[Jackal]

@drtbkj
Good morning, Joe.

Tests - successfully, no wonder that - completed.
Please see my full report at OFM Nevada theater page.

With best regards.

[Trigger]

Hello Again Mafia

Back with yet another question. So I did a thing and made a weapon go ugh… really fast. Said weapon is fired from Seoul and hitting an A-50 over Pyongyang in about two and a half minutes. This weapons is strictly for test purposed and will stay in the depths of hell, BUT this demon tracks the A-50 with relative ease no problem maintaining lock as per usual FOX 3’s in BMS. Now fighters specifically the SU-35 whos jamming and a MIG-21 are all singletons over Pyongyang same as the A-50. Missile losses DL everytime but does go HPRF then MPRF but DL (Datalink) is lost and the target is missed often flying right by the fighters canopy by a mile or so. My question. How do I get this test weapon to track and kill fighters the same way it does a bomber at that extreme range. I tried messing with the .dat and couldn’t seem to find it so is this something that’s locked behind BMS Code? This missile can kill fighters but only if the shot is taken around 80 Miles or less then it will track and kill them in seconds. I’m leaning towards this being a code thing as I tried the default OFM AIM-174B and AIM-260 both can track and sometimes kill the A-50 but the fighters it goes right past them the same way the demon missile does just much slower only becoming viable near 80 miles.

Thank you for any assistance.

[drtbkj]

Hi, @Trigger . Your shot from Seoul to Pyongyang of 120miles is reasonable. The Navy has confirmed a range of “at least 130miles” for the AIM-174. As for guidance…Way back in the early 120D testing I remember testing and seeing what you’re seeing. The missile flies right by the targeted fighter. My supposition was that when the missile lost DL a fighter had enough time to get out of the missile’s seeker FOV but A-50’s doesn’t
Unfortunately, the person that did the file work is not with us at present. I’ll pass your along to the Mafia Tech Brains

[Trigger]

@drtbkj still testing appreciate the response and future guidance