MPPRE for JDAM, JSOW, Harpoon waypoints, buddy data link guidance?
-
So can any BMS DEV confirm if they are planning to include those features?
For me it seems to be important feature and also very useful thing.And what’s up with IFF? Are they planning IFF interrogation? Would be cool and even more useful.
-
So can any BMS DEV confirm if they are planning to include those features?
For me it seems to be important feature and also very useful thing.And what’s up with IFF? Are they planning IFF interrogation? Would be cool and even more useful.
Well, for discussing new features, the general rules is this :
https://www.benchmarksims.org/forum/showthread.php?22205-BMS-Release-Date-QuestionsSo wait and see in 3-4 weeks.
-
oh dont get started on IFF lol…do a search and you will see if and when IFF will be implemented.
-
Yeah basically when it comes to IFF, BMS is the type of group that doesn’t like to half-ass things so they would want a full transponder system not just the Mode 4/5 interrogation. Even if they would implement just the part that would need for interrogation the counter-debate is that really even that encrypted Mode 4/5 part is shut off on fence in IRL so it wouldn’t be that useful, every thing past the FLOT or so wouldn’t be interrogatable anyway.
-
It would be interrogatable. You can interrogate fast enough cars and trains for that matter.
Expecting a reply might be pushing it though.
Sent from my SM-N910G using Tapatalk
-
So why they turning mode 4 off when fencing?
I know they turning off modes 1, 2, 3A and C because they actually tells enemy that you are here.
Mode 4 is different kind of dog, it responds only to properly encrypted challenge. So when enemy sends (improperly encrypted) challenge it simply does not responds to do not alert enemy that u are there. When mode 4 receives wrong improperly encrypted challenge it also warns the pilot about this fact generating “IFF” Betty.And we already have option to input codes for transponder and turn modes 1, 2, 3A and C on and off on IFF page of DED. So just implement mode 4 switches on the panel and the logic for transponder and IFF.
-
Hi,
MPPRE - Basic code is already included to support up to 8 STPTs for JSOWs, However there is no implementation to actually use that part of the code, I didn’t bothered back then because really had no intentions to implement JSOWs STPTs in the UI map. Using WDP is IMHO the ultimate way to do it. Maybe someday I’ll implement the rest of the needed code to fully support but TBH this is currently VERY low priority on my todo list.
Harpoon STPT support - Harpoon STPT support will not be implemented unless someone will find detailed documentation on Harpoon STPT that is available publicly.
Mutual DL guidance - That is something that I wanted to do yes but again low priority on my todo list.
-
So why they turning mode 4 off when fencing?
I know they turning off modes 1, 2, 3A and C because they actually tells enemy that you are here.
Mode 4 is different kind of dog, it responds only to properly encrypted challenge. So when enemy sends (improperly encrypted) challenge it simply does not responds to do not alert enemy that u are there. When mode 4 receives wrong improperly encrypted challenge it also warns the pilot about this fact generating “IFF” Betty.And we already have option to input codes for transponder and turn modes 1, 2, 3A and C on and off on IFF page of DED. So just implement mode 4 switches on the panel and the logic for transponder and IFF.
Debated to death multiple times already, just search IFF on the forum.
-
For specifically the Mode 4 answer try searching this thread, I brought up specifically just Mode 4 and got the answer it still gets strangled fence in or pretry close to it:
https://www.benchmarksims.org/forum/showthread.php?23833-ff-you-could-have-one-thing-in-the-next-update-it-would-be&highlight=Iff -
My idea for IFF implementation is following:
-Switches in cockpit would control mode 4 behavior (A, B, OUT and audio warning).
-Code for mode 2 would be set in loadout screen (just like code for bomb laser).
-IFF page on DED would control other codes and modes transmitting.
-There would be a text file where positions of aircrafts, respective codes and altitudes would be saved periodically. OFC it would be depended on transponder modes used so altitude would be saved only with more C on.
-AI would not interrogate humans (to simplify the code).
-Humans would be able to interrogate AI and other humans.
-Mode 4 crypto codes (A and B) would be readed from text file (it would be local to every player). Text file would contain 2 numbers simulating crypto keys for A and B.
-Crypto keys used by AI would be in text file inside campaign folder, they would be readed by server. OFC file would contain codes and time periods for the codes.
-There would be configurable chance of IFF failure for AI so some percent of AI aircraft would have non working IFF.
-AI would set the mode 1 code depending on mission type.
-AI would turn off transponder when fencing. -
My idea for IFF implementation is following:
-Switches in cockpit would control mode 4 behavior (A, B, OUT and audio warning).
-Code for mode 2 would be set in loadout screen (just like code for bomb laser).
-IFF page on DED would control other codes and modes transmitting.
-There would be a text file where positions of aircrafts, respective codes and altitudes would be saved periodically. OFC it would be depended on transponder modes used so altitude would be saved only with more C on.
-AI would not interrogate humans (to simplify the code).
-Humans would be able to interrogate AI and other humans.
-Mode 4 crypto codes (A and B) would be readed from text file (it would be local to every player). Text file would contain 2 numbers simulating crypto keys for A and B.
-Crypto keys used by AI would be in text file inside campaign folder, they would be readed by server. OFC file would contain codes and time periods for the codes.
-There would be configurable chance of IFF failure for AI so some percent of AI aircraft would have non working IFF.
-AI would set the mode 1 code depending on mission type.
-AI would turn off transponder when fencing.Similar implementation has been suggested, plus the rest of the transponder ATC functions, but that a is lot of work for very little return in mission. For the amount of coding time, implementing Link 16 (if you can get enough unclassified info on it) would probably be a better return on time investment.
-
Yeah, Link 16 would be a cool thing.
Imagine AWACS datalinking boogeys to you. Much better than just voice comms between AWACS and you.But i will not agree that IFF is non important. My implementation idea seems to be not so much complicated. It can be even more simplified by in example removing the “crypto key” files and making just 2 codes. A and B and making AI always respond as friend. But it would be a little too simplified.
I was trying to do some basic IFF system for ArmA 3. But then i realized that there is no sense in improving it leaving it in pre alpha state (it has never been released). It was simple interrogator in mode 4 (with A and B codes + OFC out option and zeroize) and there was also a way to input mode 1,2 and 3 codes. Mode C was also implemented but was not so much realistic. I did it to play with Stinger IFF but i never found sound samples for the Stinger IFF interrogator unit.
-
Yeah, Link 16 would be a cool thing.
Imagine AWACS datalinking boogeys to you. Much better than just voice comms between AWACS and you.But i will not agree that IFF is non important. My implementation idea seems to be not so much complicated. It can be even more simplified by in example removing the “crypto key” files and making just 2 codes. A and B and making AI always respond as friend. But it would be a little too simplified.
I was trying to do some basic IFF system for ArmA 3. But then i realized that there is no sense in improving it leaving it in pre alpha state (it has never been released). It was simple interrogator in mode 4 (with A and B codes + OFC out option and zeroize) and there was also a way to input mode 1,2 and 3 codes. Mode C was also implemented but was not so much realistic. I did it to play with Stinger IFF but i never found sound samples for the Stinger IFF interrogator unit.
I’m not saying the implementation is a bad idea, BMS is saying IFF and even just Mode 4 interrogation is a lot of work for something you will end up and rarely use in combat. Unless you can prove that modern operational procedures in the symmetric air to air portion of a conflict would use Mode 4 past fence in or even past the FLOT, it is of little use in BMS is their opinion. They would rather build a whole Mode 3/C system first and even then it is debatable if it would be of real value right now. IFF interrogation has more purposes like national ADIZs that would not be used in BMS.