16 hours ago16 hr LiveriesScanned_MSFS2020.XML has been removed. That was the only place that I was able to customize non existing codes.Here is an example that I used to add to LiveriesScanned file with good results <l a="ZZZ" m="RV6" t="FSLTL_GA_HTAI_P28A_ZZZZ" /> <l a="ZZZ" m="RV7" t="FSLTL_GA_HTAI_P28A_ZZZZ" /> <l a="ZZZ" m="RV8" t="FSLTL_GA_HTAI_P28A_ZZZZ" /> <l a="ZZZ" m="RV9" t="FSLTL_GA_HTAI_P28A_ZZZZ" /> <l a="ZZZ" m="RV10" t="FSLTL_GA_HTAI_P28A_ZZZZ" /> <l a="ZZZ" m="RV12" t="FSLTL_GA_HTAI_P28A_ZZZZ" /> <l a="ZZZ" m="RV14" t="FSLTL_GA_HTAI_P28A_ZZZZ" /> <l a="ZZZ" m="M20" t="FSLTL_GA_HTAI_P28A_ZZZZ" /> <l a="ZZZ" m="SR20" t="FSLTL_GA_DA40-NG_ZZZ" /> <l a="ZZZ" m="SR22" t="FSLTL_GA_DA40-NG_ZZZ" /> <l a="ZZZ" m="R44" t="UH1ZZZ" /> <l a="ZZZ" m="R66" t="UH1ZZZ" /> <l a="ZZZ" m="EC" t="UH1ZZZ" /> <l a="ZZZ" m="H300" t="R22ZZZ" /> <l a="ZZZ" m="CDUS" t="R22ZZZ" /> <l a="ZZZ" m="CLON" t="R22ZZZ" /> <l a="ZZZ" m="H25B" t="FSLTL_GA_HTAI_LJ25_ZZZZ" /> <l a="PVT" m="C150" t="GAmodC152_1" r="CESSNA" /> <l a="PVT" m="BEAR" t="GAmodC152_2" r="AS-JTP2" /> <l a="ZZZ" m="PA27" t="BE58ZZZ" /> <l a="PVT" m="P51" t="PC12 AI2" r="AS-STP3" />Is there any place that LiveriesScanned still exist to be accessible?I understand that you’re file of "similar" has been scrambled for some reason and I respect that but let’s have some access to customize LiveriesScanned locally please mike Sim,PC, monitor,prescription glasses, chair.
2 hours ago2 hr I concur with this - the xml file was a useful thing to check which liveries I have before installing new ones or for deleting defunct special liveries or even whole airlines.Could we have it - or something like it - back, please?
1 hour ago1 hr Hi mike,13 hours ago, mike stryczek said:LiveriesScanned_MSFS2020.XML has been removed. That was the only place that I was able to customize non existing codes.Is there any place that LiveriesScanned still exist to be accessible?It has been removed because it is no longer necessary. Scanning and processing liveries is now done in one go, with no disk access required. Fast and secure...Note that LiveriesScanned.xml was never intended to be edited manually. It was a file used for machine-to-machine communication. There was even a warning about this in the documentation...It looks like you were creating your own similar-type definitions. That's rather tricky, both because of the risk of typos, misinformation (I mean CESSNA as regcode?) and because LiveriesScanned.xml was overwritten every time a new livery scan was performed.Maybe I could add a separate user-defined file for this, which PSXT could use as input?As I understand it, all you need is a way to specify that if an RV6, RV7, RV8, RV10, RV12, or RV14 is required for matching but none is available, you are happy to use a P28A instead.I'll have to analyse whether and how that could fit in with the similar-type definitions that are already in my database.The work on PSXT never seems to end... ;-) Edited 1 hour ago1 hr by kiek
1 hour ago1 hr 59 minutes ago, romeocharlie said:I concur with this - the xml file was a useful thing to check which liveries I have before installing new ones or for deleting defunct special liveries or even whole airlines.Could we have it - or something like it - back, please?I could write the file as an option, but it would be useless for your purpose because it is no longer used as input. So, any changes you make to it would have no effect.
Create an account or sign in to comment