Search the Community

I don't think this is intended behavior, but I could be wrong Steps to reproduce: Switch to A-G master mode Set FCR to GM Set FCR to NORM mode With azimuth set to 60, observe time it takes to scan: roughly 2.5 seconds With azimuth set to 30, observe time it takes to scan: roughly 1.5 seconds With azimuth set to 10, observe time it takes to scan: roughly 0.5 seconds This seems normal, there's a smaller area to scan so it takes less time Switch to EXP, DBS1 or DBS2 mode With azimuth set to 60, observe time it takes to scan: roughly 5 seconds With azimuth set to 30, observe time it takes to scan: roughly 5 seconds With azimuth set to 10, observe time it takes to scan: roughly 5 seconds Observed result: When changing the scan area, the time it takes to scan stays the same. Expected result: The same as NORM mode. The scanned area is smaller between azimuth set to 60, 30 and 10, so it would make sense that 30 updates quicker than 60 10 updates quicker than 30 ground_radar_bug.trk

Often, the cannon will appear to move erroneously on its own, and in unnatural ways. This mostly happens when lasing beyond its range, but even so the behavior is odd. It can be observed doing similar behavior within range though as well, though not to such an extreme. Uploaded a video showing the behavior here:

Add option to ask ATC "where am I relative to field" or have ATC volunteer this info. Example. Called "Inbound" west of Batumi (see image), it directs to rwy 13. It gives contra course, which might seem odd. What is happening, I believe, is that anytime I call "[F1] Inbound", or keep calling "[F2] Request Azimuth", it keeps directing me to a point outside of the field in the runways extension (for runway 13, extension is to about 9 nm NW Batumi I surmise looking at F10 map). As experiment I kept calling "[F2] Request Azimuth" (Navigation assistance), it kept giving me any and all directions 75, 250, 179, 56 ... whatever (because I kept passing the point it directed me too). In daylight, you can ignore this and just keep heading for the field until it calls "cleared for visual, contact tower". In pitch black night time on the other hand ... you can keep running around forever getting new directions, never seeing the field or even being told you should see the field. One can infer I guess, if one keeps getting contradictory directions but remembering it's for rwy 13, that must mean you are NW of Batumi. One could then steer 130 hoping to see the rwy and getting the "cleared for visual, contact tower". It would be a help, especially at night, if ATC actually told you where you are relative to the field: "you are NW Batumi" followed by "steer 297" (or whatever) for "landing inception point". If ATC AI was really intelligent, of course, it would never say "297" in this situation, it would suggest a course (and altitude?) that asymptotically approaches the correct RWY approach. But adding human judgement to ATC AI is extremely complicated and will not happen. But adding an option to have ATC AI volunteer where you are relative to the field or adding an option to straight up ask "ATC where am I relative to the field?", that could be done. Following real world vocabulary of course. This brought about because I've never seen RWY lights in multiplayer ever, that I can remember so I tried an night offline mission. Yes, the RWY lights do come on when calling inbound (and goes off if you call abort landing). So then I tried some pitch black navigation and discovered I can run around forever, never seeing the field, if I keep following "[F2] Request Azimuth" directions.