Hello there!
Thank you for your feedback and for taking the time to try and test RedGriffin ATC. I am glad you appreciate my addon.
scarymovie wrote in Thu Nov 19, 2020 3:55 am:1. Not able to communicate with arrival airport even when nearing it and in range. At times when it finally works, the communication breaks when the radio detects another nearby airport. This happens many times especially when I am flying around "undeveloped" areas in FG (eg. South-east Asia).
Can you please provide me the aircraft you used, the airport code and area in which you experienced this bug? That would help me to personally test this condition and possibly fix the bug.
Please consider RedGriffin ATC assigns to every airport (and hence its radios) a particular range and according to airport size. This also applies to CTR management: the bigger the airport, the wider the CTR area.
scarymovie wrote in Thu Nov 19, 2020 3:55 am:2. Every so often, the ATC changes her mind about eg. departing runway, landing runway during approach etc. This could be due to the sudden change of wind direction.
Yes, I noticed that too and I am trying to figure out what could be the best option for this. Runway is assigned according to wind direction and in case it changes, I am struggling with the best thing to do. You could stay on the assigned runway but, as the wind direction has changed, maybe it is better to use a different and more appropriate runway. Or it may be simply ignored and use the runway determined at the first radio contact but wind direction could be not appropriate for that.
I am still thinking about this issue and the best thing to do. Any idea?
scarymovie wrote in Thu Nov 19, 2020 3:55 am:3. Incorrect weather report. It gives a different info eg. the live weather says wind direction: 160 while info given by ATC is 227.
RedGriffin ATC uses METAR information passed by FlightGear. I will however check this again.
scarymovie wrote in Thu Nov 19, 2020 3:55 am:4. ATC directs me to a departing or landing runway that doesn't make sense because of very strong tailwind.
Like I said, take off and landing runways are determined according to wind direction and I guess it is working right, although it could also be the case there is a bug or specific conditions should also be considered.
Can you give me a proper example on how take off and landing runways should be chosen according to very strong tailwind?
Squawking is something I am thinking about since the very beginning of RedGriffin ATC development. There are many things to be considered, including the well known "special codes" (7500, 7600, 7700) as well as the specific area of the world as the squawk code also depends on that.
I thought about simply assigning a "random code" at the very moment of departure request from the pilot, but I know there are many exceptions according to the area of world and sometimes there are special codes to be properly managed in each case and/or airport.
I would also like to "simulate" the cases in which the pilot sets squawk codes to 7500, 7600 and 7700 and to handling them properly. (not much to to with 7500 and 7700, but in case of 7600 ATC could provide assisted approach and landing, although in case of 7600 they usually give light signals)
As a matter of fact (and as far as I know) FlightGear does not support squawking and there are no properties associated to this. I could however assign a random squawk code (excluding the special ones, of course) and just use that. In such a case, implementing squawking would be super easy and done in one minute.
It is not also clear to me whether the squawk code is assigned by the initial ATC (the departure ATC) and you stay with that squawk code for the whole duration of flight or it can be reassigned by other ATCs in case of CTR transition.
Of course, in order to properly have a "real" squawk code, we also need to consider VFR squawk codes and this changes according to the specific area of the world.
Thank you very much indeed for your feedback.
Enjoy RedGriffin ATC!