Jump to content

Recommended Posts

Posted (edited)

I attach three tracks for your perusal.

Track 01 :  the behaviour I intended to report.  Things go very wrong at around 1017 as the missile plunges to its demise.

Track 01a: I unintentionally left the fuse set to OFF and I got a different (and unexpected) result; even with the fusing incorrectly set should it do this?  Around 1017 the missile doesn't make its last turn towards the target and gradually descends until it crashes into the sea.

Track 02: I amended the mission so that the target was nearer and this time it worked as expected.

I created this mission years ago, and this didn't happen at the time.  Maybe it's something to do with the range or that the missile is (mostly) flying into wind; but surely an in-range indication shouldn't appear if the FP to the target is outside of the missile's range.  Please ignore any mission failure, etc, messages, they are informational only.

Searching I found this post, from January(!), which seems very similar.  If it's the same issue, consider this a bump and an offer of additional information in the hope of encouraging a swift resolution.

 

Screen_250905_080923.png

track_01a.trk track_01.trk track_02.trk

Edited by Hippo
typos

System spec: AMD Ryzen 7 9800X3D @ stock, MSI GeForce RTX 5090 Ventus 3X OC 32 GB DDR7, Gigabyte X870 Gaming X, Corsair Vengeance LPX 32GB EXPO (2 x 16GB) DDR5 5300MHz C30, Samsung 980 EVO 500 GB NVME M.2 SSD (system drive), WD Black SN 850X 2TB NVME M.2 SSD (games drive), Thermalright Assassin Spirit 120 Evo Cooler, Asus XG43UQ Monitor, Oculus Quest Pro, Thrustmaster Warthog HOTAS, Thrustmaster Pendular Rudder

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...