Rick Jonk Posted February 1, 2022 at 12:45 PM Posted February 1, 2022 at 12:45 PM Hi, I was wondering whether It's currently possible to load a certain livery based on registration info e.g.: REG/PHHSJ (in rmks) or maybe with the selcal code? in this case JQ-LP. It would be great to know if there's any possibility of this right now, and if not, whether there are plans to implement it. Thanks, Rick Link to comment Share on other sites More sharing options...
Dace Nicmane Posted February 1, 2022 at 01:31 PM Posted February 1, 2022 at 01:31 PM There are thousands and thousands of real world aircraft registrations and you can't have a livery installed for each one of them, besides a VATSIM user can assign any registration number to any aircraft, so no, it's not possible. What about SELCAL, I didn't quite understand what you mean? Link to comment Share on other sites More sharing options...
Rick Jonk Posted February 1, 2022 at 02:00 PM Author Posted February 1, 2022 at 02:00 PM (edited) I understand It's not quite possible on a large scale, but It's definitely possible for a few airlines. (Which is what I intended) I thought about filtering the registration with the SELCAL you enter when connecting (*which is optional ofcourse), since that might be easier than having to filter it with the remarks. I read something about it on the pinned topics though, so might have to read into that. Edited February 1, 2022 at 02:01 PM by Rick Jonk Link to comment Share on other sites More sharing options...
Rick Jonk Posted February 1, 2022 at 02:03 PM Author Posted February 1, 2022 at 02:03 PM 2 minutes ago, Rick Jonk said: I understand It's not quite possible on a large scale, but It's definitely possible for a few airlines. (Which is what I intended) I thought about filtering the registration with the SELCAL you enter when connecting (*which is optional ofcourse), since that might be easier than having to filter it with the remarks. I read something about it on the pinned topics though, so might have to read into that. "First, I would expand the Connect window so that you enter not only your callsign and aircraft type code, but you can also enter an airline code and livery code. The airline code would be optional, of course, and you would leave it blank if you're flying a General Aviation aircraft. If you're flying an airliner, you would obviously enter the ICAO airline code in the airline box. This airline code would be used by other pilots' pilot clients (not just vPilot) for the purpose of selecting a model to represent your aircraft in the other pilot's sim. This will improve model matching not just for vPilot users, but also for other pilot client users when they are displaying aircraft flown by vPilot users. If you leave the airline code blank, and your callsign looks like an airline callsign (three letters followed by one or more digits and then optionally one or two letters) then the airline code will be set equal to the first three letters of your callsign. If you fill in the livery code, that code will be sent to other pilot clients to allow for more fine-tuned model matching. Since we don't have a standardized database of livery codes, this will primarily only be useful for people that build custom VMR files for their VA. Eventually, I would like to build up an "official" database of livery codes, and provide a list of those codes in a dropdown for the user to choose from. This list would be filtered based on the aircraft type code and airline code that was entered. This would allow pilots to specify that they are flying the "Mosaic" livery for JetBlue, or the Fox livery for Frontier, or the Shamu livery for Southwest, to name a few examples. We could also establish standard livery codes for GA aircraft in order to represent the colors in the paint scheme more accurately. When you fill in these fields, you will have the option of saving the aircraft details in your "hangar" for easy recall later. There will be a dropdown on the Connect window where you can choose a previously-saved aircraft. Note that the callsign would not be saved with the aircraft, as it is subject to change each time you fly any given aircraft, but vPilot will remember that last callsign you used with each aircraft and pre-fill that callsign when you select the aircraft from your hangar. I may also have vPilot remember which aircraft you selected for each flyable aircraft that you have installed in the sim, and then automatically select the appropriate aircraft from your hangar when you select an aircraft in the sim. If vPilot doesn't recognize the aircraft that you selected in the sim, the Connect window fields will be blank and you'll need to enter the data. vPilot will then remember the values that you entered for the next time you select that aircraft in the sim, even if you don't save the details as a new aircraft in your hangar. I might have vPilot pre-fill the aircraft type, airline code, and livery code if the aircraft you've selected in the sim is found in the model database." Link to comment Share on other sites More sharing options...
Dace Nicmane Posted February 1, 2022 at 04:52 PM Posted February 1, 2022 at 04:52 PM 1 hour ago, Rick Jonk said: This would allow pilots to specify that they are flying the "Mosaic" livery for JetBlue, or the Fox livery for Frontier, or the Shamu livery for Southwest I seem to recall XSB had an option to choose a special livery. Don't know how exactly it worked, though. As for SELCAL, I still don't understand your idea. As far as I can see, PH-HSJ doesn't have any SELCAL code assigned, same with many aircraft. So how would you filter anything by it when it's not entered or entered wrong? Link to comment Share on other sites More sharing options...
Ross Carlson Posted February 1, 2022 at 05:08 PM Posted February 1, 2022 at 05:08 PM In my opinion, we shouldn't rely on flight plan data for model matching, because not all pilot connections have a flight plan associated with them. Everything needed for model matching should be found in the "Connect" window. Here's the link to my proposed model matching changes (which Rick quoted from above): Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy Senior Controller, Boston Virtual ARTCC Link to comment Share on other sites More sharing options...
Recommended Posts