DaveS

so now comparing it to the 800 I can honestly say I don't see any difference in the detail other than maybe the rivets being a little more noticeable on the fuselage. I feel like the high detail part of this update is missing

I'm not a Pmdg hater by any means but to me I don't see much of a difference. The cockpit is exactly the same as the others. I use borisn for sounds so never even heard what their updated ones sound like.

where is the high detail update? Just loaded it up and it's the exact same textures as the other variants

I agree we probably are haha. Thanks as always for all the hard work

Do these lower QF's then affect real parking? I don't like to use soft parking since its not accurate. It's disappointing to see large airports that were filled with real parking now have such low QF's. Example flightbeam KSFO is only 28 and KMSP is 18. MK studios KLGA only 22 many others as well

This sounds great! thanks!

I am still seeing this issue. I know you were going to do some tests but just wanted to point out what others might being seeing. The plane ahead of me was actually much closer at one point. This is just when I remembered I should probably take a screenshot. This is with the Fenix Airbus. Had this TCAS alert going until I could figure out what flight it was and blocked it. I also flew right through an aircraft in the PMDG 777 on file to KMEM the other day. I confirmed the check box user air was checked under collision avoidance.

Just to update. I emailed Balt and he advised that some of the data providers do not provide the hex id and the fallback is to match by callsign which has resulted in the mismatches. He made some changes on the backend to hopefully improve this but he did state it is possible to still seen an occasional mismatch. He did state that anyone seeing these to report it to him

I noticed same thing. Leaving KMKE the other day. Skywest flight from MKE-ORD was showing in the sim as a qantas link dash-8 EC-NIG VH-QOK BOG-> respawns EC-NIG VH-QOK BOG-> QLK DH8D. =1= AIGAIM_Qantaslink Bombardier Dash 8-Q400 JIA5532 VH-QOK ORD->MKE respawns JIA5532 VH-QOK ORD->MKE QLK DH8D. =1= AIGAIM_Qantaslink Bombardier Dash 8-Q400 SKW5502_ is a ghost and will be removed, continue with SKW5502

I noticed the latest archive txt has my home airport of ini KMKE only having a qf of 22. In previous weeks it was always much higher in the 40's. Is there a way psxt can not override a file if the QF is better in an earlier week? I have noticed this with other airports as well. Glipeslope/BM World KMEM has always had pretty poor data but had a qf around 30 or so at one point. Now it is only 5 thanks,

I believe it is here AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community\fnx-aircraft-320\SimObjects\Airplanes\FNX_32X\common\config In there is the aircraft.cfg [SERVICES] FUELTRUCK =0 BAGGAGE_LOADER =0 CATERING_TRUCK =0 BOARDING_RAMP =0 GROUND_POWER_UNIT =0 PUSHBACK =0 SMALL_PUSHBACK =0 MARSHALLER =0 JETWAY =1 change pushback=1 to 0

I agree I just moved to MSFS2024 from 2020 and could not figure out why my performance was so bad one flight would be fine the next a stutter fest. I decided to lock to 30 and 2x since I only have 4070ti. Using autofps my frames are always at 60 now and as smooth as can be.

great thank you!

does anyone know if this effects any 3rd party airports? I have pretty much all the ones airlines fly to lol

It's in each airports folder in the community folder or wherever you keep your scenery folder. You should see a layout json and manifest json file. Open the manifest with text editor and ensure that it matches the version number for the airports in the archive file found at www.lekseecon.nl/downloads/docs/msfs2024_archive.txt If it doesn't match change the version number in the manifest file to match and it should recognize the airports properly next time you do a scan