Rinz1er Posted November 1, 2022 Posted November 1, 2022 (edited) According to @IronMike, ED controls the functionality that would correct a bug in the current AIM54C that is preventing the "Target Size Switch" from being functional. Currently the missile always goes active at the same time/distance from target regardless of the target size switch position. In patches prior to this one, the target size switch position would change at what distance/time the AIM54C went active on the target. Note: The AIM54A is affected properly by the target size switch. This only appears to be a problem with the AIM54C-MK60 & AIM54C-MK47 Edited November 1, 2022 by Rinz1er Adding Note
IronMike Posted November 1, 2022 Posted November 1, 2022 It is not a bug. It is simply how active missiles are modelled. The A is different as in not being treated like an active missile all the time, which is why the target size switch works. This is not possible to do with the C. It is not an ideal way to do it with actives, we agree, but it is not a bug per se. Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/
DSplayer Posted November 1, 2022 Posted November 1, 2022 Well the reason why only the AIM-54Cs are affected and not the AIM-54As is because the 54Cs go active on their own utilizing the go_active_by_default value (which is set to 1 on the 54Cs and 0 on the 54As). This causes the 54Cs to default to the active_radar_lock_dist value (which is 10nm). This is a limitation of the current API/schema that the AIM-54s currently use. I would also like to point out that ED hasn't been able to do a similar target active distance thing with their AIM-120s yet even though Deka's SD-10 was able to do so when they were on the same API/schema. Discord: @dsplayer Setup: R7 7800X3D, 64GB 6000Mhz, Saitek/Logitech X56 HOTAS, TrackIR + TrackClipPro Resources I've Made: F-4E RWR PRF Sound Player | DCS DTC Web Editor Mods I've Made: F-14 Factory Clean Cockpit Mod | Modern F-14 Weapons Mod | Iranian F-14 Weapons Pack | F-14B Nozzle Percentage Mod + Label Fix | AIM-23 Hawk Mod for F-14
Rinz1er Posted November 1, 2022 Author Posted November 1, 2022 17 minutes ago, DSplayer said: Well the reason why only the AIM-54Cs are affected and not the AIM-54As is because the 54Cs go active on their own utilizing the go_active_by_default value (which is set to 1 on the 54Cs and 0 on the 54As). This causes the 54Cs to default to the active_radar_lock_dist value (which is 10nm). This is a limitation of the current API/schema that the AIM-54s currently use. I would also like to point out that ED hasn't been able to do a similar target active distance thing with their AIM-120s yet even though Deka's SD-10 was able to do so when they were on the same API/schema. Deka seems to not use the "go_active_by_default = 1"...They instead use "active_dist_trig_by_default = 1". Not entirely sure how they are changing the distance in code but there is a forum post about it here from Deka
Recommended Posts