Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

DaveS

Members
  • Joined

  • Last visited

Everything posted by DaveS

  1. 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
  2. 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.
  3. where is the high detail update? Just loaded it up and it's the exact same textures as the other variants
  4. I agree we probably are haha. Thanks as always for all the hard work
  5. 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
  6. 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.
  7. 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
  8. 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
  9. 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,
  10. 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
  11. 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.
  12. does anyone know if this effects any 3rd party airports? I have pretty much all the ones airlines fly to lol
  13. 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
  14. I think I may have found a solution. Check your manifest file for your airports. I went through the one's that were in my tblo folder and many were showing a different version number than what the archive.text has despite my sceneries being the latest version. I am not sure why those did not change whenever I downloaded an update but by making sure the version number in the manifest file matches what is in the archive, all those now work properly and with the correct qf.
  15. there seems to be something related to version numbers. For example FB KSFO was generated. I have version 1.2.1 but the archive.txt says 1.2.2. I downloaded via the contrail app and there is no version 1.2.2 only 1.2.1
  16. @kiek I definitely think something might be off the with data lately. For example I just ran a scan with all my airport addons activated and I get a tlob folder with 25 airports many of which are very popular and are listed in the archive.txt. For example MK-Studios KLGA and KSEA are in there. I'll email the folder but those airports have never been an issue and all of a sudden it's like PSXT is seeing them for the first time
  17. Thanks. Wonder why someone would have a complaint about 1 file for an airport?
  18. ok thanks. Is that something you can fix when the next update comes out?
  19. Just following back up on this. I have completely uninstalled MSFS2020 so only using 2024 There is a native 2024 version of Tropicalsim KMCI which I downloaded and installed. When I do the airport scan I get this: Fac: C:\Users\dschl\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalCache\Packages\Community\tropicalsim-kmci\scenery\world\scenery\KMCI-scene.bgl airport has code 'KMCI' in BGL path publisher: TropicalSim thirdparty TropicalSim KMCI does not exist Generated KMCI.xml: 56 positions However, there is no xml file in my third party so I am at a loss. Any ideas?
  20. ok I think I might have discovered what could possibly be the issue. I recently installed MSFS2024 and have been testing with it. I had airports for both sims linked via addon linker. I just uninstalled 2020 and now the QF for the 2024 version of X-Codr KDEN is at 52 so all good there. I still can't figure out SMF and KMCI even in 2024 they just show stock file. I'll do more testing when I can
  21. Ok so for KMCI there is nothing in my_thridparty for it. It does not exist in the tblo folder either. What is intersting is KDEN is in the tblo folder. Here is the log file for KDEN here you can see the qf is 19. I suspect it went up a bit as it made updates Airport file read from 'airports\my_thirdparty\KDEN.xml' for Denver Intl publisher : X-Codr Designs version : 1.2.2 altitude : 5351 ft num_parkpos : 344 Facilities : true quality factor : 19/ 0 RT traffic week : 0 For KSMF, it shows I have version 1.0.0 installed but again nothing in airports/my_thirparty. It's not in the tblo. Here is the log for that Airport file read from 'archive/stock/KSMF.xml' for Sacramento Intl publisher : stock altitude : 24 ft num_parkpos : 91 quality factor : 52 RT traffic week : 2
  22. thanks. I didn't even realize I had a saved signature haha. I had the signature option turned off so I never saw it
  23. Here is the airport scan. Both show the airport doesn't exist. When I load into TS KMCI it only loads the stock file with a qf of 7. Same with Orbx KSMF only stock file loads Kind of separate issue but is something off with the latest learned data? For example, X-Codr KDEN always had a qf in the 50's and even shows qf of 52 in the last archive.txt but loading in there and it's now only 15

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.