Yep, lack of loft + maybe some wierd behaviour at very low alt in that it wont maintain alt
Did you try pitching up when you loosed the missile? It seems to be working for me.
No, I didnt.
Even at ~50m, pitching up as it comes off the rail seems to get it tracking fine without the dropping alt issue
My friend and I tested the PGM-2000 in custom battles. When launching the PGM and dropping a dumb bomb simultaneously from a high altitude (about 7000 m), the bomb arrived about 4 seconds earlier.
Yeah, manually lofting does work quite well, so the fix is definetly give them lofting code
That actually kinda makes sense.
Assuming the bomb is dropping vertically and the PGM is coming in at an angle. (and not that the PGM was fired straight down) Then the bomb has less distance to cover, whilst the PGM does have a rocket motor, its not really a missile, but rather a powered glide bomb, the motor is just keeping it aloft
Found extended launches at low alt still drop out the sky with manual lofting. But kind of didn’t expect a 25km launch to work out at 50m above sea level. Unless martel is more advanced than I am aware, which is entirely possible.
Especially when their max range (iirc) is about 30km anyway when launched from about 7500ft I think. at least going by Flames bug report. But maybe Im misreading it
https://community.gaijin.net/issues/p/warthunder/i/Y5BrZ6gGHVXX
Bug report reminds me that we’re stuck with a DL pod and none of the functionality that should facilitate.
Yeah, whats funny is that I think… though could be entirely wrong… we should only be able to fire and guide one at a time. Not 3 like we can currently… :D
An acceptable price if we got man in the loop.
Yeah it would.
Where my 60 scan zone?
"scanPatterns": {
"search60": {
"type": "pyramide",
"azimuthLimits": [
-180.0,
180.0
],
"elevationLimits": [
-10.0,
90.0
],
"yawStabLimit": 180.0,
"pitchStabLimit": 10.0,
"rollStabLimit": 10.0,
"period": 0.8,
"width": 7.5,
"barHeight": 1.5,
"barsCount": 41,
"rowMajor": false,
"barsOneWay": false,
"isSmoothMajor": true
},
"search360": {
"type": "cylinder",
"azimuthLimits": [
-180.0,
180.0
],
"elevationLimits": [
-10.0,
90.0
],
"yawStabLimit": 180.0,
"pitchStabLimit": 10.0,
"rollStabLimit": 10.0,
"period": 1.0,
"barHeight": 15.0,
"barsCount": 1,
"rowMajor": true,
"isSmoothMajor": true
},
"searchVertical": {
"type": "pyramide",
"azimuthLimits": [
-180.0,
180.0
],
"elevationLimits": [
-10.0,
90.0
],
"yawStabLimit": 180.0,
"pitchStabLimit": 10.0,
"rollStabLimit": 10.0,
"period": 0.75,
"width": 47.5,
"barHeight": 1.5,
"barsCount": 1,
"rowMajor": false,
"centerElevation": 37.5
And where custom and 120?
1 Like
The flight path for the gliding bombs (plus a loft) would be perfect for the Martels.
Anti clutter would be nice… Still wobbles like an OAP in an egg an spoon race locking helicopters atm.
The only parts of the report i did that got actioned are IFF and vertical scan. Rest was not actioned yet.
1 Like
Yet… One can hope
https://community.gaijin.net/issues/p/warthunder/i/eqmrXuDGDIta
Got bored and made a bug report for the Challenger 1s underwhelming neutral steering
Nah, the Neutral steering on the CR1 is already very generous.
The drive for the neutral steering on the CR1 was too thin to apply full torque of the engine or it would shear the drivetrain for the neutral steering.
This means it could only really be used on very firm, flat ground or it would completely break the tank and result in a very problematic repair.
I personally wached this happen to the privately owned CR1 during War and Peace Revival, Hop Farm in 2018. They tried to perform neutral steering on rough/uneven ground, broke the tank and it needed to be recovered/towed from the show grounds as it could not move on its own power.