Jump to content

truthknown

Members
  • Content Count

    104
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

4 Neutral

About truthknown

  • Rank
    Member

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    VATSIM
  • Virtual Airlines
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Absolutely! Support here is tremendous and I have thrown him a bone!
  2. Ahh yes. I had this set correctly for P3D. Forgot to change these for MSFS... Looking much better now! Thank you so much for these changes, the regional jet solution is really elegant. Doesn't require much work from us at all. I was doing too much! LOL! I have one livery where PSXT doesnt seem to want to take the registration code N744P. This code is in the dbase file with the correct airline and aircraft type, although it's not the full 6 character code that would be expected. When PSXT runs, it does not put the regcode for this livery into the AI_Liveries file. Since it is a special livery, I have the code in the specials list, but because its not adding the regcode, its spawning them randomly as static aircraft.
  3. Ok, i'm getting somewhere. Now I am getting a few weird matchings for static aircraft. These all have liveries assigned, yet are matching incorrectly. Also, for this livery, the registration used to be owned by Dow Chemical and now is American Eagle operated by Skywest. So I get why the livery was placed as SKW. Therefore I added it to the specials list so it wouldn't be used for static aircraft, yet it still spawned in place of an American Eagle Skywest livery: SKW51_ SKW CRJ7 =2= AIGAIM_Dow Chemical Bombardier Challenger 870 - N872DC
  4. Ok, so i tried some stuff and it seems i'm making things worse. This is relating to static aircraft loading. I am getting tons of random liveries for planes spawning (using KORD as a test bed). One issue I see is the following: I placed the registration codes into the aircraft.cfg as you suggested, but if I have multple reg codes on a regional aircraft livery, it does not end up converting the airline to the right regional carrier For example, there are 2 liveries for the Skywest United Express. I placed the long registration list on the first one. These are the results in the AI_Liveries.xml Notice the first one was never changed from UAL to SKW but the second one was with only a single regcode. This is happening to all of the regional carriers with multiple regcodes. I tried flipping them, moving the reg codes to the 2nd livery and the same thing happened to the 2nd livery while the 1st one was changed to SKW. So first question - why is this happening? Second question, do I even need to keep doing this with your dbase.xml? Third, how do I get the right liveries to show up with static aircraft? Thanks!
  5. I've always made changes in the AI_Liveries.xml file to add custom atc_id fields. For instance: <livery airline="SKW" type="CRJ7" folder="1" cargo="false" title="AIGAIM_American Eagle Bombardier CRJ-700 - opb Skywest" atc_id="N745SK,N374CA,N606SK,N611SK,N613SK,N614SK,N63*SK,N65*CA,N70*SK,N70*EV,N71*SK,N71*EV,N72*SK,N72*EV,N73*SK,N73*EV,N74*SK,N74*EV,N75*SK,N75*EV,N76*SK,N76*EV,N761ND,N77*SK,N870DC,N872DC" regcode="N745SK" /> Where am I supposed to do this? In the aircraft.cfg? Can the atc_id field of the aircraft.cfg take all of that? I am also afraid that the aircraft.cfg changes would also get overridden in an AIG OCI update. Not sure how best to manage this.
  6. Thanks for all the changes! I am still trying to understand all of the changes and grasp how to best use them. However one thing is driving me crazy and that is the automatic regeneration of the liveries file each time we load PSXT. It is overwriting all of my customization in the file (registration codes for special liveries and regional jets, etc. that I manually put in the atc_id fields). Also do not know how the reg_code field is being used. I also delete a few liveries that I do not want in the file (ex. an FLai model that I would rather only have the AIG version of). Maybe there is a better way of doing this that I am not aware of.
  7. Thank you! Another request if you are making changes to parameters in the livery file. From the manual: Special case If you add the word special (all lowercase) to a livery title and add a single registration code to the atc_id key, that livery will only be matched upon registration code. Thus it will only show as live aircraft and not (multiple) times as static parked aircraft. Can we make this a parameter in the livery file as well? I would prefer a solution that did not require modification of the aircraft.cfg titles. This way the changes are contained to PSXT files. Also: 10.5.4 registration code added to title LIG will add the registration code of the livery, defined with atc_id=regcode, to the title of the livery (if not already present). Can we have a parameter created in parameters.xml that prevents that from happening. Again, do not want to have the aircraft title in the aircraft.cfg modified. I'm all good with the other automatic repairs as it doesn't modify the titles. And the registration code can just be placed in the livery file parameter. Reason I am asking is that the AIG One-Click Installer tool manages all of the AIG Aircraft files and when the aircraft.cfg livery titles are modified, it sometimes confuses the OCI tool. The tool then reports that various liveries are not installed when they are, or if you run a verify setup, it then re-adds the liveries which titles didn't exactly match what the tool installed, the latter causing duplication of livery titles when the livery generator goes in and finds those liveries and adds the registration code to the title again. That was a real PIA to clean up when it happened to me (in generates pop errors in P3D that all have to be cleared before the sim will start...) Thanks, Chris
  8. I for one would love this solution. Another advantage is that changes to the AI files wont just get overwritten when we run updates using the AIG OIC tool. Thanks for considering this! I know its a very localized problem but I tried everything I could given what we had available to solve this personally but I couldn't resolve this one issue. Chris
  9. Oh, and for AIG aircraft, it will never work because they do not put the airline code in the title of the aircraft, only the full spelled out name of the airline - "American Airlines" instead of "AAL" Having a parameter we could set would work much better...
  10. I see what you did. Partial solution but does not work everywhere. In KORD for example, the FSDT version 2 has 3 code in the airls field for the G gates: <parkpos id="G10" airls="AAL,JBU,KAP" /> While what we are looking for in this case is "AAL", based on your implementation, it wont even try here because it has more than 1 airline code listed... Same in the E Gates: <parkpos id="E1" airls="ACA,ASA,DAL" /> where we want "DAL" I also notice that the AFCAD just has wrong airline codes at many gates which you cannot do anything about, and the afcad section is not even in the parked_updates version of the KORD.xml, only the one in the airports folder. I just wish there was a more full solution. Thanks, Chris
  11. Hi, Wanted to bring up a thought on regional airlines with PSXT. At least in the US, but likely elsewhere, regional carriers fly for numerous airlines. Now while we can specify registration codes to various liveries that somewhat allow the right livery to appear for a given regional flight (take Skywest or Republic for example who flies for American, United, Delta, and I think Alaska as well), this doesn't work so well for spawning parked aircraft. So at KORD for example, pier G should all be American Eagle liveries on the regional jets that park there, but I get a mix of American Eagle, Delta Connection, and United Express. Could we have a means in which the correct livery gets parked at a gate where the regional carrier covers multiple carriers? So in the previous example, the afcad likely shows "AAL" as the airline for those gates, but because the airline for the aircraft is "SKW" or "RPA" or "ASH" or "ENY" or one of the numerous regional carrier that serve the big US carriers, it doesn't match the "AAL" and so it randomly picks a livery from the set available in the xml file for that specific plane and airline. If there was another field, say "operatedfor" or "opf" or something, that would then specify the mainline carrier, "AAL", then PSXT could match the correct livery option for that aircraft as it spawns as a parked aircraft. Is something like this possible? So many airports across the US are affected by this. The reverse occurs too with AI aircraft. Flai puts different liveries all under Skywest "SKW", while AIG puts liveries under the mainline carriers "AAL" and specifies in the livery title that it is "obp Skywest". I would love to hear thoughts on this. Thanks, Chris
  12. Also, learner will continue to move to the next airport if using the * in the airport code field, yet RT will stay at the last airport it was on when the error occurred and remain frozen. Even restarting RT doesnt help Learner. I have to restart learner to get it going again.
  13. I have this same problem. I see it particularly with Learner as I have that running all the time. It happens with PSXT in flight as well on long hauls. It takes some time before this happens, but for learner its particularly annoying as once it does, then the functionality of learner stops. It could be an entire day before i realize it and all that time is wasted. Chris
  14. i am using 19.4. Does it automatically convert the whole file or do I need to trigger something to have it converted? Just sitting at the airport in the sim does not do anything to convert the file. Its too much to do manually and I would hate to start from scratch. A lot of time was spent having those files built up. Chris
×
×
  • Create New...