bavella1 Posted March 1, 2020 Posted March 1, 2020 (edited) Just did a little test to find out Rmax and Rne from the AIM-120B at different heights. Two hornets at the same altitude head on with mach 1.0. The screenshot is at 40,000 ft and has an Rne of 7.1nm ... Isn't that a little weird? I thought it should be a lot further away ... Tested on Current openbeta 2.5.6.43931 Edited March 1, 2020 by bavella1 Tracfile added to thread
bavella1 Posted March 1, 2020 Author Posted March 1, 2020 Gave it another try and saved a trackRne_40kft_7nm.trk
Bunny Clark Posted March 1, 2020 Posted March 1, 2020 I do believe DLZs are currently bugged and not displaying properly. Oil In The Water Hornet Campaign. Bunny's: Form-Fillable Controller Layout PDFs | HOTAS Kneeboards | Checklist Kneeboards
ED Team BIGNEWY Posted March 1, 2020 ED Team Posted March 1, 2020 Hi, you are launching on a high speed target flying away from you, your range will be greatly reduced. Thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
mcfleck Posted March 1, 2020 Posted March 1, 2020 Isn't it a bit too fast marking this report as "no bug" 1. The OP stated right in the beginning, that the hornets flew head on. 2. The RWR information in the HUD shows that the other Hornet is spiking the OP (would not be possible in rear aspect) 3. The Vc is around 1300 knots... Clearly a head on engagement. I would rather guess it was a very fast judgements without even looking at the screenhot/description.
bavella1 Posted March 1, 2020 Author Posted March 1, 2020 That´s correct. Both planes were flying head on until the human-players hornet shot the AMRAAM as can be seen in the trackfile. However, I didn't want to report a bug at all. The topic was dragged over to the bug section by a moderator.
raelias Posted March 1, 2020 Posted March 1, 2020 Isn't it a bit too fast marking this report as "no bug" Shocking.... Win10 64, MSI Krait Gaming Z370, I7 8700K, Geforce 1080Ti FTW3 ,32 GB Ram, Samsung 980 EVO SSD Modules: Combind Arms, A-10C, F-86F, F/A-18, F-16, Flaming Cliffs, KA-50, L-39, P-51, UH-1, Christen Eagle II, Persian Gulf
nighthawk2174 Posted March 1, 2020 Posted March 1, 2020 Yeah even just look at the picture the closing V is 1330kts...
maxTRX Posted March 1, 2020 Posted March 1, 2020 Are you guys talking about Rmax or Rne? If the bandit turns around 180 and runs the difference in Rmax is going to be dramatic not so much in Rne since it assumes at any given moment the bandit starts turning and running like hell so the difference is the time it takes for him to turn around and accelerate. I think...:smilewink:
Fisu_MAD Posted March 1, 2020 Posted March 1, 2020 Rmax, wait 4 seconds more and you can use AIM9X or AIM9M. I was destroyed by SD10 launched at Angeles 5. I was at Angeles 25, and Rmax reached, 15mn??? and FOX3. RWR alert the SD10, 4 seconds and F18C destroyed. He lauched the SD at 5000 ft and have range before than me that was a 25000 ft??? The ranges for the AIM120 are shorter than before. YouTube Channel Update: MSI Z790 Tomahawk, i9 13900k, DDR5 64GB 640 MHz, MSI 4090 Gaming X Trio, 970 EVO Plus 1TB SSD NVMe M.2 and 4 more, HOTAS TM Warthog, Meta Quest Pro
maxTRX Posted March 1, 2020 Posted March 1, 2020 Rmax, wait 4 seconds more and you can use AIM9X or AIM9M. I was destroyed by SD10 launched at Angeles 5. I was at Angeles 25, and Rmax reached, 15mn??? and FOX3. RWR alert the SD10, 4 seconds and F18C destroyed. He lauched the SD at 5000 ft and have range before than me that was a 25000 ft??? The ranges for the AIM120 are shorter than before. Well, that doesn't sound good:noexpression: I've done only 3 BVR engagements (with AI) in 2.5.6. All against JF17's with SD10 at high altitudes. So far I was able to whack the AI with no problems every time. The only quirk I've seen was when launching in TWS on my first engagement... the "LOST" message (reported already) 3 runs are definitely not enough to notice possible issues... I'll do some more scenarios later.
bavella1 Posted March 3, 2020 Author Posted March 3, 2020 So may this be no bug at all, als BN statet? I thought Rne at 40k ft head on with 1300 knots v closure should be much more than 7 nm. Am I wrong?
NoJoe Posted March 3, 2020 Posted March 3, 2020 (edited) Looks like it might just be a bug in the Rne range indication. If the bandit's nose is about 30 degrees to my right, the Rne range indication increases out to around 14 or 15 miles, compared to about 7 miles if the bandit is head-on to me. It might be as simple as some confusion in the code between Navy and Air Force notations for bandit aspect that is messing up the math. In Navy planes a bandit that is facing straight at you is considered to be at 180 degrees aspect. But in Air Force planes it's considered 0 degrees. Or the other way... I forget. But the point is that they're opposite. Maybe the Rne code is expecting Air Force notation in the math. I'm attaching a short track that shows this. We start head-on at 40,000 feet and Mach 1. Then he turns off to my right. As he turns, the Rne range indication actually increases as he turns rather than decreasing as would be expected.Hornet Rne Test.trk Edited March 3, 2020 by NoJoe
ED Team BIGNEWY Posted March 3, 2020 ED Team Posted March 3, 2020 Rne issue is reported. thanks Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal
Recommended Posts