TAW_Impalor Posted February 23, 2015 Posted February 23, 2015 (edited) Hello, I think there is a bug with "Request Azimuth". I am trying to land after Quick Dogfight, for example. I call the nearest tower. It replies "Krymsk-ADF, your heading 139". A minute later I ask again, it gives reciprocal course "heading 319". And so on. I cannot see the airfield from that distance, and I don't want to use the map. In reality Krymsk is 18 km away with bearing 215. What's going on here? Thanks! Vlad Edited February 23, 2015 by impalor 12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR
WildBillKelsoe Posted February 24, 2015 Posted February 24, 2015 the P-51D modeled relies heavily on using a map. no ADF equipment is modeled. Its strange I know but get used to it. AWAITING ED NEW DAMAGE MODEL IMPLEMENTATION FOR WW2 BIRDS Fat T is above, thin T is below. Long T is faster, Short T is slower. Open triangle is AWACS, closed triangle is your own sensors. Double dash is friendly, Single dash is enemy. Circle is friendly. Strobe is jammer. Strobe to dash is under 35 km. HDD is 7 times range key. Radar to 160 km, IRST to 10 km. Stay low, but never slow.
TAW_Impalor Posted February 24, 2015 Author Posted February 24, 2015 (edited) I am not talking about ADF equipment, I know it is not modeled. The tower should have me on their radar and give direction via radio. Here is another example - the tower gives me bearing perpendicular to the glissade, but not to its entry point! If I don't know where to look for the airfield, I'm screwed... Edited February 24, 2015 by impalor 12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR
Gunrun_KS Posted February 24, 2015 Posted February 24, 2015 Terrain association! [sIGPIC][/sIGPIC] I7 4790K / EVGA 1080ti SC / 32GB DDR3 / 1TB SSD / Oculus Rift S / X-56 / MFG Crosswind V2 / ButtKicker + Simshaker for Aviators
TAW_Impalor Posted March 8, 2015 Author Posted March 8, 2015 Thanks. That's what I do. But still a bug... 12900KF@5.4, 32GB DDR4@4000cl14g1, 4090, M.2, W10 Pro, Warthog HOTAS, ButtKicker, Reverb G2/OpenXR
Diplocaulus Posted March 8, 2015 Posted March 8, 2015 I noticed the same thing from the Mustang. Request an azimuth and you get weird, sometimes contradictory vectors. I wasn't sure if this was a bug or approach was trying to vector me into a specific approach pattern. Windows 10 64bit / Intel Core i7-5820K Haswell-E 6-Core 3.30 GHz / 32GB RAM / GeForce GTX 1080 8GB / Dell UltraSharp 27 QHD U2715H 2560x1440 / Saitek X52 Pro Flight System / TrackIR 5
Recommended Posts