I mean it will work like a HARM and not how the Alarm should work.
It will track Radar signals but not have it’s unique function. Smin said as much
I reckon Meteor is just going to be the same, They can barely get lofting to work properly, let alone variable thrust ontop, and most of hte time (with current map sizes especially) you probably want it to just go at max speed, the loss in range is not going to be that noticable I reckon.
1 Like
It doesn’t do that IRL
1 Like
It actually seems fairly complex:
Spoiler
"propulsion0": {
"fireDelay": 0.75,
"impulse0": {
"time": 3.5,
"force": 104785.0,
"massLost": 163.0
},
"impulse1": {
"time": 0.0,
"force": 0.0,
"massLost": 32.0
}
},
"propulsion1": {
"impulse0": {
"massFlow": 2.2,
"isp": 14500.0,
"massLost": 110.0,
"factorIndex": 0
}
},
"propulsionFactor0": {
"MaxThrottleByAirflow0": [
40.0,
0.1
],
"MaxThrottleByAirflow1": [
60.0,
0.15
],
"MaxThrottleByAirflow2": [
400.0,
1.0
],
"MaxThrottleByAirflow3": [
600.0,
1.5
],
"ThrustByMachThrottle2D0": 1.4,
"ThrustByMachThrottle2D01": [
1.0,
0.05
],
"ThrustByMachThrottle2D1": 1.6,
"ThrustByMachThrottle2D11": [
1.0,
0.65
],
"ThrustByMachThrottle2D2": 2.0,
"ThrustByMachThrottle2D20": [
0.1,
0.7
],
"ThrustByMachThrottle2D21": [
0.2,
1.0
],
"ThrustByMachThrottle2D22": [
0.3,
0.93296087
],
"ThrustByMachThrottle2D23": [
0.4,
0.8743017
],
"ThrustByMachThrottle2D24": [
0.5,
0.8324022
],
"ThrustByMachThrottle2D25": [
0.6,
0.7960894
],
"ThrustByMachThrottle2D26": [
0.7,
0.76536316
],
"ThrustByMachThrottle2D27": [
0.8,
0.7430168
],
"ThrustByMachThrottle2D28": [
0.9,
0.7122905
],
"ThrustByMachThrottle2D29": [
1.0,
0.6955307
],
"ThrustByMachThrottle2D3": 3.0,
"ThrustByMachThrottle2D30": [
0.1,
0.65
],
"ThrustByMachThrottle2D31": [
0.2,
0.9134078
],
"ThrustByMachThrottle2D32": [
0.3,
0.8910614
],
"ThrustByMachThrottle2D33": [
0.4,
0.8603352
],
"ThrustByMachThrottle2D34": [
0.5,
0.83798885
],
"ThrustByMachThrottle2D35": [
0.6,
0.8156425
],
"ThrustByMachThrottle2D36": [
0.7,
0.7849162
],
"ThrustByMachThrottle2D37": [
0.8,
0.76536316
],
"ThrustByMachThrottle2D38": [
0.9,
0.74860334
],
"ThrustByMachThrottle2D39": [
1.0,
0.7290503
],
"ThrustByMachThrottle2D4": 4.0,
"ThrustByMachThrottle2D40": [
0.1,
0.6
],
"ThrustByMachThrottle2D41": [
0.2,
0.7290503
],
"ThrustByMachThrottle2D42": [
0.3,
0.7681564
],
"ThrustByMachThrottle2D43": [
0.4,
0.76536316
],
"ThrustByMachThrottle2D44": [
0.5,
0.75977653
],
"ThrustByMachThrottle2D45": [
0.6,
0.74860334
],
"ThrustByMachThrottle2D46": [
0.7,
0.73463684
],
"ThrustByMachThrottle2D47": [
0.8,
0.7206704
],
"ThrustByMachThrottle2D48": [
0.9,
0.7094972
],
"ThrustByMachThrottle2D49": [
1.0,
0.6955307
]
},
"propulsionAutopilot": {
"propulsion0": {},
"propulsion1": {
"startTimeMin": 4.25,
"cruiseVelocity": 3960.0,
"cuiseVelocityDiffMax": 1000.0,
"PidControllerCruise": {
"prop": 0.05,
"intg": 0.5,
"diff": 0.01,
"intgLim": 1.0
}
}
},
Most boost sustain missiles in game just have 6 lines of code for their motor (thrust, burn time, fuel usage for each stage)
8 Likes
I thought it did, is it just gravity then that drives it to the target
AFAIK it has two modes: regular and loiter. Additionally it has a two-stage solid-fuel rocket motor.
If the loiter mode is used, it flies high, discards its first stage, ignites the second stage and comes top-down onto the target radar. If the radar stops sending before the second stage is ignited, it deploys its parachute and waits until the target radar sends again to discard the parachute and ignite the second stage.
1 Like
That is where my confusion lies, thanks
That will be incorrect, it does not have 2 pulses (what you are describing here). It has a booster, and then a long sustainer, that ignites instantly after the booster. After it burns out, it can’t reignite.
We’re still talkin about the ALARM, right?
Yes
Then the propulsion of this missile is everywhere described as “two stage solid fuel rocket motor”. It also wouldn’t make sense for it to have a parachute if the second stage gets ignited no matter what, because if both stages burned out and the parachute is deployed, it has no means to reach the target afterwards.
Yes. I’ve not seen any reliable evidence for ALARM re-igniting it’s motor, it seemingly just drops onto the target under gravity after the parachute is cut.
It seems they might have considered re-igniting the motor early in development, but it likely proved too difficult (it is known ALARM’s original Royal Ordnance motor was cancelled and replaced by a Bayern Chemie motor during development).
1 Like
It wouldn’t be a reignition. It would be an ignition of the second stage. Such missiles with mutiple stages have programmable ignition points.
2 stage means booster sustainer.
So short burning but stronger booster, with longer boosting but weaker sustainer.
2/Dual pulse means it gets ability to fire motor pulses, independent from eachother sections, that missile computer can ignite on demand.
And there is no evidence the motor does that. It is a standard boost-sustain motor.
Two stage doesn’t always mean that. It can also mean that the single stage looks like this (different profiles at different lengths of the single stage):
Boost + Sustain = Single Stage (no control over the ignition)
Solid rocket (which could also be Boost + Sustain) + Another solid rocket (which can be Boost + Sustain too) = Two Stage (control over the ignition)
Yes was pointing out that a previous pilot who has used the Alarm system used the term free fall.
Interesting to confirm that, what altitude does Alarm climb too when loitering?
1 Like
No, you are mistaking it now once again.
So let’s get this straight.
This is a dual stage missile
The stage means there is a separate part that detaches.
Then you have dual burn/thrust, that are commonly called 2 stages. They present different “stages” with different burns, just inside one motor, instead of having a separate section that falls off.
And you have dual pulse, that has 2 separate propelant compartments, that can be ignited on demand by the missile.
Now when it comes to ALARM, there is no 2nd stage
