-
Anyone still use the map enhancement tool?
pict I don’t see anywhere on my interface this adjustment Here is what I see when I open the app. I’m running the pro version. mike
-
Anyone still use the map enhancement tool?
is this for 2024 only I’m running 2020 - V9.6.2 and I don’t have that window on the bottom. How do you open that? mike
-
Anyone still use the map enhancement tool?
where is that set? I don't see it in settings mike
-
mike stryczek started following RT turns yellow , Anyone still use the map enhancement tool? , LiveriesScanned_MSFS2020.XML no there and 2 others
-
LiveriesScanned_MSFS2020.XML no there
thank you, Nico It’s highly appreciated mike
-
LiveriesScanned_MSFS2020.XML no there
no, that didn’t work It’s a pity that from just adding one line to LiveriesScanned.xml file I have to do some gigantic maneuvers, which are not working, and on top of it. I have to add Files and extent SIM loading. I really don’t understand what was wrong with me being able to do some adjustments and then simply rebuilding LiveriesScanned.xml file after update it take me 30 seconds, and now I really don’t see what improvement there is in model matching. For me personally, it is deterioration I do realize that I’m maybe the only one flying GA's and observing them and there is no point catering to such a minority… mike
-
LiveriesScanned_MSFS2020.XML no there
But maybe Dave can give an example file that didn’t work for me I copied a folder named IVAO_R22 inside of which aircraft CFG had a section like that [GENERAL] atc_type ="R22" atc_model ="R22" Category = "Airplane" performance ="" editable = 1 wip_indicator = 1 icao_type_designator =R22 icao_manufacturer =ROBINSON icao_model =R22 icao_engine_type =Piston icao_engine_count =1 icao_WTC =L icao_generic=0 I renamed the folder IVAO_R22-H300 and inside I change in the file aircraft CFG to this [GENERAL] atc_type ="H300" atc_model ="H300" Category = "Airplane" performance ="" editable = 1 wip_indicator = 1 icao_type_designator =H300 icao_manufacturer =ROBINSON icao_model =H300 icao_engine_type =Piston icao_engine_count =1 icao_WTC =L icao_generic=0 I restarted it PSXT and the new LiveriesScanned.xml file did not include H300 but it does include R22 mike
-
LiveriesScanned_MSFS2020.XML no there
I don’t understand how you do that Can you give a step-by-step or an example? TH mike
-
LiveriesScanned_MSFS2020.XML no there
throughout the history of the program at first, there was non-scrambled file that show the similar selections That will force models of similar look to in case there wasn’t one available for example commonly available P28A model can be representative of low wing models like RVs and M20... R22 for small helis - H300 or gyrocopters - CDUS, CLON .... Because there also always have been Liveries file accessible I have many times adjusted details like specific registration "N" # for a plane that I would follow It also allows me to confirm that I didn’t make any mistakes creating custom models Also, there is many new Plane Type ICAO that I would see on radar 24 but they were not showing as there were new plane codes, but by adding the new codes manually, they will appear closer represented. Having the Similar and Liveries files back, readable, accessible, and customizable locally will let crazies like me set up the program the way we like it mike
-
LiveriesScanned_MSFS2020.XML no there
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
-
drastic improvements
I am observing quite drastic improvement in aircraft behavior in the air and on the ground There used to be big problem of aircraft pumping up and down, extremely annoying. The way I understand it was because of low quality of data coming from RT. In V14 I haven’t yet seen that behavior so I’m suspecting that Niko has put a lot of time in smoothing out data points or RT quality have drastically improved. It used to be very immersion killer, seeing aircraft, jumping up and down on a descend or even in level flight and now it almost is as good as it used to be in the beginning . Congratulation, Niko and highly appreciate it how you’re constantly making an effort to improve the experience mike
-
RT turns yellow
TH Niko mike
-
PSXT and LiveATC
PSXT and LiveATC is my favorite combination. I have tried all kinds of other injectors and ATC simulations, and all of it is extremely unreliable and frustrating PSXT is untouchable for injection and if I want life interaction Vatsym is the only way. As a fly, mostly GA's, I can slot myself into the real world traffic, listening to lifeATC and observing aircraft out of the window. For now that’s the best way.
-
PSXT and LiveATC
30s
-
RT turns yellow
When I first start PSXT, everything is green, but after sometime RT turns yellow yet everything seems to be continuing working. RT stays yellow I did notice in the log some errors, but I don’t know what they mean and how to fix it if it’s needed Attaching log file TH mike
-
The Traffic Reader has stopped with an error
new log with version 11.11.1