Leadnap Posted January 3, 2019 Posted January 3, 2019 (edited) So with the posted wind issues on the BK90 today I was running tests and noticed that regardless of my inputs for the altitude (91 block) the BK90s consistently flew at and released at the same ~130m altitude, set for 30, 50, 100, 500, and the "standard" (60m). I wouldn't think 500 would work due to the ceiling of the release envelope, but input anyways. Also, since we're on the topic - is the 91 block code 91 then 4 digit #### altitude or just 91 then 3 digit ### altitude? A) 91 0100 for 100m or B) 91 100 for 100m (thus ignoring the last of the 6 digits on the CK37)? (The answer to the question is irrelevant to my testing, tried 91500 and 910050 for 50m for example) Edited February 7, 2021 by RagnarDa --- AJS37 Viggen, F-16C Viper, Adobe Premier. X56 HOTAS, Ryzen 7, GTX 2070S youtube.com/leadnapgaming
ShagrathBG Posted January 3, 2019 Posted January 3, 2019 As far as I remember, they disabled those options since the new implementation of the BK-90.
QuiGon Posted January 3, 2019 Posted January 3, 2019 As far as I remember, they disabled those options since the new implementation of the BK-90. Haven't heard anything like that, but if so, are they planning on enabling them again? Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
frosen Posted January 3, 2019 Posted January 3, 2019 I also fiddled around with the approach altitudes (60-500 m) and could not see any difference. Would be a pity if the disabled the VALB functions but that explains it then. Hope they reintroduce it soon. i7-7700K @ 4.9 GHz | Gigabyte Aorus Geforce GTX 1080 Ti | 32 GB DDR4 Corsair Vengeance @ 2400 MHz (2800 OC) | Asus Strix Z270E Gaming | Samsung 970 EVO M.2 SSD 1 TB | Samsung 960 EVO M.2 SSD 500 GB | WD NAS Red 2TB SATA3 | Corsair Cooling Hydro Series H80i v2 | Thrustmaster Hotas Warthog | Saitek PRO rudder pedals | Valve Index
Leadnap Posted January 3, 2019 Author Posted January 3, 2019 As far as I remember, they disabled those options since the new implementation of the BK-90. What would be the purpose of disabling a critical feature of the weapon? Last month release altitude worked - I know because I was doing some other testing on release characteristics and there was a definitive difference. Eliminating the feature restricts attacks to very specific parameters, since no longer can terrain features mask you from the target. --- AJS37 Viggen, F-16C Viper, Adobe Premier. X56 HOTAS, Ryzen 7, GTX 2070S youtube.com/leadnapgaming
johnv2pt0 Posted January 3, 2019 Posted January 3, 2019 Pg. 343 of the manual: "The attack altitude is always 60m." The address 91 is for the ingress (approach) altitude.
frosen Posted January 3, 2019 Posted January 3, 2019 (edited) Pg. 343 of the manual: "The attack altitude is always 60m." The address 91 is for the ingress (approach) altitude. That's true but at least my comment was about approach altitude. I don't see any change when I try different codes (910300-915000). Please feel free to try it out and see if you have the same issue. Edited January 4, 2019 by frosen Typo i7-7700K @ 4.9 GHz | Gigabyte Aorus Geforce GTX 1080 Ti | 32 GB DDR4 Corsair Vengeance @ 2400 MHz (2800 OC) | Asus Strix Z270E Gaming | Samsung 970 EVO M.2 SSD 1 TB | Samsung 960 EVO M.2 SSD 500 GB | WD NAS Red 2TB SATA3 | Corsair Cooling Hydro Series H80i v2 | Thrustmaster Hotas Warthog | Saitek PRO rudder pedals | Valve Index
johnv2pt0 Posted January 3, 2019 Posted January 3, 2019 Roger. My fault, wasn't thorough on my read of this one...I had just replied to another thread about the altitude and basically copied here. It's probably just a typo, but just so there's no confusion for others, if you wanted an approach altitude of 30m it would be 910300 (not 913000).
Leadnap Posted January 4, 2019 Author Posted January 4, 2019 It's probably just a typo, but just so there's no confusion for others, if you wanted an approach altitude of 30m it would be 910300 (not 913000). Thanks for clearing that up. That's true but at least my comment was about approach altitude. I don't see any change when I try different codes (910300-915000). I understand the rationale of removing the [sub-munition] release altitude over ingress altitude - but neither currently works. The feature is very important because ideally terrain should mask your approach but that means you have to assign an ingress altitude to clear said terrain. To the reddit post which mirrors all the wind BK90 posts here the issue remains as well - a default of 120m means that the release envelope must calculate for the higher AGL which shortens the envelope dramatically and reduces the lowest altitude you can release from, but further more introduces a greater degree of wind disruption to a munition that has no ability to induce velocity. --- AJS37 Viggen, F-16C Viper, Adobe Premier. X56 HOTAS, Ryzen 7, GTX 2070S youtube.com/leadnapgaming
Recommended Posts