@RUSHER0600 said in Israel Theater of Operations for BMS 4.37:
@ricnunes 3-4 falcon days
And what’s a Falcon day??
All I know is that a Falcon day is shorter than a DCS one
@RUSHER0600 said in Israel Theater of Operations for BMS 4.37:
@ricnunes 3-4 falcon days
And what’s a Falcon day??
All I know is that a Falcon day is shorter than a DCS one
Is there any forecast to when will this theater be updated in order to be compatible with update 3 (4.37.3)?
@DUSTOFF17,
Well yes, during the flight after takeoff and before getting close to the CAP location, I did use autopilot (both ATT and ALT) and I really disengaged it with the paddle switch.
I will try not to use the autopilot and/or not using to paddle switch to disengaged it and will report back, as soon as possible.
EDIT:
I can now confirm that the culprit of this issue is what DUSTOFF17 said:
I made two sorties, both starting from the ramp where in the first one I never used the autopilot and in the second, I used the autopilot but didn’t disengage it using the paddle switch (instead I used the autopilot switches in the cockpit) and I could fire my missiles without any problems!
No problem tiag!
I’m glad to be helpfull.
I could try to load a full AIM-120B or a full AIM-120C loadout (but I can only do this tomorrow). But to be honest I’m a bit skeptical because like I said earlier, I was able to fire an AMRAAM missile (at a friendly aircraft for test purposes) early just after I take off but not later on against enemy aircraft.
Hi all,
I will try to reply to all questions in this post:
No, I didn’t over-G. I simply took-off, did gentle turns after taking off towards the BARCAP station/waypoint and locked and tried to shoot at incoming enemy Migs without making any noticeable hard turns.
This situation happens to me all the times during the campaign that I started. I’ll send a link below with one of my campaign savegames:
https://drive.google.com/file/d/1vtQx1zO6tBzqokIZcWf77h0mnz-ZRXjz/view?usp=sharing
Everytime I fly one of the first missions (F-15C squadron from Gunsan) - for instance the 1st of 3rd which are BARCAPs - this issue always happens. Anyway, this is definitely not a “one off” situation.
Autopilot is always off when this happens.
I never mess with the msl slaved or BORE setting. Actually and to be honest with you, I don’t even know where that is changed, LoL. So that setting must be set to the “default setting”.
Where’s the “blinking FPM” light?
First of all, I want to say that the new F-15C which comes with Update 3 (BMS 4.37) looks awesome and it’s great to finally to have a “completely new aircraft” in BMS (with completely new and different avionics and sensors from the F-16, I mean).
As such I decided to play a campaign in the stock Korea theater (Rolling Fire) playing with the F-15C squadron (flying from Gunsan) but now I’m having the following issue there:
This is strange because when playing the “F-15C_Scramble” mission in TE or when trying to fire against a friendly target in a campaign mission (mentioned above) just after taking off (early), I have no problems in firing any missiles.
It almost seems like the missiles become “broken” after flying for a considerable period of time and therefore can’t be launched anymore.
@pgk007 said in SA10 vs SDB or JSOW:
Actually TB2 is not good example of hard target. Over 20 was lost in Ukraine and this equipment is really overrated . It can operated only in area without ECM coverage and without basic AD.
Well, losing 20 (or a bit more) slow but not so small TB2 UAVs during a full year of conventional war against an enemy (Russia) well equipped with Air Defence Systems is IMO not that bad. Not bad at at all.
A clear situation that shown that even something like the TB2 is not that easy to be shot down was during the battle for the “Snake island” where Ukrainian TB2s were able to destroy SA-15s and Pantsir Air Defence Systems thus paving the way to subsequent manned fighter aircraft attack (like for example Su-27s) and later on, allowing the Ukrainians to retake the island.
Of course and obviously a JDAM is much, much harder to be shot down compared to a TB2 UAV.
@pgk007 said in SA10 vs SDB or JSOW:
I didn’t mention JDAM bombs because they are relatively easy to shoot down with modern short range systems and it was not related to this topic.
Actually there’s nothing that indicates that JDAM’s are relatively easy to be shot down.
Flying slow does and can present an extra challenge for a radar to lock on as it can be seen over Ukraine where even the most advanced Russian Air Defence Systems have had a harm time to shot down even something like a loitering Bayraktar TB2 UAV which has a quite larger RCS than a JDAM.
Moreover the RCS of a JDAM is very small since we are talking about a “cone-shaped” with a relatively small diameter coming directly but not so fast (presents a challenge to pulse-doppler radars).
On top of this, many (or today most) Air Defence Systems also use other means of detection, namelly IR sensors and here (in the IR spectrum) the JDAM is far more stealthier than any missile (due to having much less heat).
SDBs and JSOWs are obviously even harder to be detected and shot down by enemy Air Defence Systems than JDAMs (due to lower RCS).
@janjan
Actually I haven’t tried that fix/setting and the reason is simple: I want to keep playing with 4.37.0 instead of updating it to 4.37.1, this in great part because of this Rampage issue (I enjoy playing in the Israel theater).
But if you (or anyone else) teach me out to be able to revert from 4.37.1 to 4.37.10 without uninstalling BMS completely and installing it again then I would definitely try that “Time To Go Active to -1.00” setting.
@janjan,
Yes, they completely miss the target (and always).
Actually if you notice, it was me who created this thread and reported the issue (initially).
Is there any news or update about this Rampage missile issue with 4.37.1?
Yes, you’re right. I really wasn’t understanding but now I get it.
Thanks for the reply and explanation
@Mav-jp said in 4.37 Update 1 “messed up”/broke Rampage missile and “autojammer”:
@ricnunes said in 4.37 Update 1 “messed up”/broke Rampage missile and “autojammer”:
@Leech
Thanks for the reply and explanation!I though that dispensing (either in SEMI or AUTO) was based on the dispensing program selected (1 to 4) and not on RWR threat sensing?
Yep that’s not implemented yet , for now it uses the selected man program
I must admit that I’m really confused right now since that’s how it’s already implemented in BMS 4.37.0 (without update 1) when commanding countermeasure dispense (CMS forward) it will dispense the amount of Chaff or Flares specified in selected program (1, 2, 3 or 4).
@Leech
Thanks for the reply and explanation!
I though that dispensing (either in SEMI or AUTO) was based on the dispensing program selected (1 to 4) and not on RWR threat sensing?
@Mav-jp
That’s strange. What would be the purpose of the CMDS AUTO setting versus for example SEMI, then?
I always thought that AUTO had exactly the purpose of automatically turning the jammer on (together with releasing chaff and flares automatically) whenever needed while with SEMI the ‘consent’ must be given?
Note that I’m not doubting what you’re saying. Just wish to know what’s the diference between SEMI and AUTON then?
Anyway, the main purpose of this thread was to alert about the Rampage missile. Something clearly when wrong with it with the latest update. BTW, can someone else confirm this?
Recently I installed Update 1 for BMS 4.37 but unfortunately I was “surprised” that the Rampage missiles (Israel Theater) always missed their targets where previously there wasn’t such problem.
I even followed the Rampage missile flight (via weapon camera) and noticed a very awkward behaviour in which the missile climbed “almost to space” (more than 65,000 feet) and then when near the target dived almost at a 70-80 degree angle towards the target but always missing (short) the intended and designated target - BTW, the targets were designated using the Radar - where previously the Rampage missile flight was clearly ballistic like as expected from a ballistic missile and it hit the intended and designated target without any problems.
I found this to be very strange and then I remembered that I recently updated BMS 4.37 to Update 1 (4.37.1), so what I did was to uninstall BMS 4.37.1 and install it again without updating it and tested the Rampage missile again (now with 4.37.0) and without surprise (I admit) the Rampage missile worked just as expected.
I also found another issue with BMS 4.37.1 (Update 1) which is when you set the countermeasures/CMDS mode to Auto and when the player’s aircraft was tracked by a radar, the jammer didn’t automatically turn ON like it always did. Again with BMS 4.37.0 (without Update 1) the jammer turns automatically ON as expected.
For example you can test this using for example the following mission:
https://drive.google.com/file/d/1vElM64Qu7VCNNlHtjJjkMh1a111f6ULv/view?usp=share_link
@LorikEolmin
Oh, I see! Thanks for the reply
BTW, how can I change the database for this campaign?
Sorry, for the ‘noob’ question but and while I’ve been playing Falcon BMS for quite awhile, I never edited anything in the sim except for TE scenarios.
Just installed this theater and from what I’ve seen it looks great. While I still didn’t have time to test it in detail, I noticed the following in the Operation Desert Storm campaign:
@Ironman53rd and @AlehandroGTI
Please note that I don’t have much of a problem “killing” a SA-10 site with other weapons and tactics.
For example, I can use pop-up tactics successfully like you (Ironman53rd) said and for example the SDB is a great weapon for this.
Or for example like AlehandroGTI said, the Rampage missile is also a great weapon for this effect specially if we already know beforehand the exact coordinates or location of the SA-10 radars.
So yes, either by using the SDB or Rampage (or both) I can inflict severe damage to a SA-10 site and knock out its radars and basically everything else.
However, please note that this is not the purpose of this thread. This thread is basically to report a bug where the Delilah missile can be (easily) detected by the SA-10 radars (I imagine that this might also be the case with other Air Defence systems) when it shouldn’t because the Delilah missile is flying on the other side of a mountain/hill.