By Christoph Reule 1379750
#523489
Ross Carlson 887155 wrote:
Christoph Reule 1379750 wrote:Reading the ATC MODEL var should be an option, not a must, IMO.


Even if it's only read if it contains a valid ICAO type code? Why do you say that?


Disregard my suggestion about the ATC MODEL var. It was shortly after coming home from night shift when I read this, and unfortunately mixed few things up lol. :shock: :roll:
By Trevor Hannant 1240481
#523498
Ross Carlson 887155 wrote:That's why I'm thinking it should only prefill if the value in the ATC MODEL var is a valid type code.


Fair points. I'd go with the above:

- Valid? Pre-fill
- Invalid? Leave blank and use previous option of showing options as user types code in
By Ross Carlson 887155
#523514 Beta version 2.1.15 is now up, which adds the free text search capability on the connect window when typing into the type code field. You can type some or all of manufacturer, model name, and/or type code and it'll show all matches found in the ICAO database. If you type an exact type code, it 'll only show those matches.

I'll have it prefill the type code box from the ATC MODEL SimConnect var later.
By Ross Carlson 887155
#523595 Thanks Luke, looks like I have an older copy of the ICAO doc. I'll get it updated.

Where did you find A35X as a code? I don't see it on the ICAO site. Did you mean A35K?
By Christoph Reule 1379750
#523597
Ross Carlson 887155 wrote:Thanks Luke, looks like I have an older copy of the ICAO doc. I'll get it updated.

Where did you find A35X as a code? I don't see it on the ICAO site. Did you mean A35K?


I suppose it's A35K (Airbus A350-1000).