- Thu Apr 26, 2018 9:52 am #523489

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.

- Thu Apr 26, 2018 1:53 pm #523498

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

Trevor Hannant
VATSIM Network Supervisor

- Fri Apr 27, 2018 4:03 am #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.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy
Senior Controller, Boston Virtual ARTCC

- Tue May 01, 2018 1:22 pm #523593 Hi Ross,

Excellent new feature, however...

Just did a quick test of the list that is provided. Certain codes, certainly those for newer aircraft don't appear e.g.

B38M
A35X
B788

- Tue May 01, 2018 4:20 pm #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?

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy
Senior Controller, Boston Virtual ARTCC

- Tue May 01, 2018 5:14 pm #523596 I've updated the type data file, and released Beta 2.1.16, which is necessary to read the new data file.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy
Senior Controller, Boston Virtual ARTCC

- Tue May 01, 2018 5:24 pm #523597

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).

- Wed Aug 29, 2018 9:37 pm #526744

1. Recognise helicopters and assign a default heli when the type code is incorrect or matching has been unsuccessful?

Unfortunately, the only way for vPilot to know that a user is flying a helicopter is for that user to enter the correct type code when connecting to the network. That is the only piece of data that is transmitted to other pilots which contains any information about the type of aircraft you are flying. In other words, there is no field in the transmitted data that indicates if the user is flying a prop, a jet, a sailplane, a blimp, a helicopter, etc. There is only the type code that the user enters.

That being said, vPilot does have a list of type code aliases which it uses to correct for invalid type codes. So if you are regularly seeing someone connect with an invalid helicopter type code, I could add entries to this list that would correct their type code before looking for a matching model. Let me know if you have any such invalid codes to add to the list.

2. Read a bespoke libary for model matching rule set, that links to a AI model matching pack?

Yes, you can load custom model matching rules into vPilot, which map type codes to your models. Documentation is here:

http://vpilot.metacraft.com/Documentation2.aspx

Hi there,

Sorry for the late reply

So can check my understanding here: is the AgustaWestland / Agusta-Bell AW139 = A139?

- Thu Aug 30, 2018 3:29 pm #526752 According to this page, yes...

http://www.flugzeuginfo.net/table_accodes_en.php

Cheers,
-R.