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.

jcuellar

Members
  • Joined

  • Last visited

  1. No more slow-motion effect with version 15.7.0. Thank you so much, Nico. Tomorrow I'll test MMMX to see if the QNH mismatch has been corrected also, I'll give you my feedback. Cheers Jaime Monterrey, Mexico
  2. No worries, I can live with that. I have one more thing, different to this subject. It is possible to have an option to manually enter the QNH when we have a QNH mismatch? I'm having this issue for a long time ago in MMMX (Mexico City). Everything starts great and after a few minutes the QNH jumps drastically, but RT reports the correct QNH. Mexico City most of the time has a very high QNH 1020+ and suddenly jumps to less than 1010 making arrival traffic to land on the streets, in some cases almost 1 km before the threshold. It would be nice to have a parameter to enter manually the right QNH value to avoid that behavior. Jaime Monterrey, Mexico
  3. Hi Nico, Unfortunately the slow motion effect is back, I'm spotting right now (0547z) at LSZH. All departures have this behavior. If I can help with some testing, I'll gladly do ti. Jaime
  4. Hi Nico, I think data is normalizing now. Last night I spotted LSZH for a couple of hours without issues.
  5. Hi Nico, I continued testing, this time at KSFO and KSAN. In SFO the departure traffic never took off, there was no rotation, and it was running into the city. At KSAN they took off, and immediately the slow-motion appeared. If you need more testing, I'll gladly help to find the issue. Cheers! Jaime Monterrey, Mexico
  6. Yep, no problems at all at EHAM. A few hours ago I tested at KSEA and saw the slow-motion effect over there. As you said, this must be bad data from RT.
  7. I'll also test EHAM for just one hour; it is late here in Mexico. I'll give you my feedback. Jaime
  8. With version 15.6.5, the strange slow motion appears 3 seconds after takeoff.
  9. Hi Nico. Not sure if this is related to PSXT or RealTraffic, but I'm experiencing a slow-motion effect seconds after takeoff of any aircraft. Also, I see that most aircraft are not banking on turns. All this is with version 15.6.4. Thank you Jaime Monterrey, Mexico
  10. I just tested as instructed, and now it is working as usual. Thank you, Nico. Jaime
  11. Hi, Nico. Sure, here is the log.txt: Fri Dec 05 05:14:16 2025 (utc) PSXT version 12.2.0 for MSFS 2020/2024 MAIN_WINDOW_X=400 MAIN_WINDOW_Y=48 ********************************** parameters ********************************** from 'C:\Users\jcuel\AppData\Roaming\PSXT\parameters.xml' ALWAYS_ON_TOP=false OBJECTID_LIST=false NAV_LIGHTS_WHILE_PARKED=true GUID_CHANGES=true SIM_TIME=false KEEP_SIM_TIME_PAR=false SCAN_LIVERIES=false LIG_AUTOMATIC=true LIG_PRIORITIZE=true SCAN_AIRPORTS=true LIGHT_AIRCRAFT=true HELICOPTERS=false HIGH_PERF_AIRCRAFT=false AUTO_RANGE=true AIRBORNE_ONLY=false COLLISION_USER_GND=true COLLISION_USER_AIR=true COLLISION_LIVE_PARKED_GND=false STRAIGHT_PBS_ONLY=false INITIAL_LOAD_ONLY=false WEEK=false PARK_SOFT=false RT_PARKTRAFFIC_ONLY=false MAIN_WINDOW_X=400 MAIN_WINDOW_Y=48 LAST_EPOCH_TIME:=0 CUSTOM_PARKING_PERCENTAGE=-1 HOLDING_THRESHOLD_METERS=250 MAX_HOLDING_MINUTES=20 AIRP_HEIGHT=18000 MAX_FIT=47 MATCHING_DEPTH=4 RANGE=40 AR_ABOVE_HEIGHT=48000 MAX_PARK_SEL=500 MAX_LIVE_SEL=500 AIRP_RANGE=20 AIRP_HEIGHT=18000 TIME_SHIFT_DAYS=0 TIME_SHIFT_HOURS=0 TIME_SHIFT_MINS=0 PROGRAM_VERSION="12.2.0" MSFS_INSTALL_PATH="" lfolder0="" lfolder1="" lfolder2="" lfolder3="" lfolder4="" lfolder5="" lfolder6="" lfolder7="" lfolder8="" lfolder9="" AIG_VERSION="12.0.1" DBASE_VERSION="12.0.56" AIRPORTS_VERSION="12.0.0" LIV_SCAN_VERSION="0.0.3" ADDONS_SCAN_VERSION="1.0.26" MYSIMADDON24_VERSION="" MSFS_2024_INSTALL_PATH="D:\zzzMSFS2024" AI_PACKAGE_SELECTOR="AIG, FSLTL, JF, MTL" DESTINATION="" BLOCK_CALLSIGN="" SIM_CHOICE="MSFS 2024" ******************************************************************************** Your RealTraffic license was taken from 'C:\Users\jcuel\AppData\Roaming\InsideSystems\RealTraffic.lic' msfs program version at web = 12.2.0 msfs version up-to-date airports version up-to-date aig version up-to-date liveries version up-to-date addons version up-to-date dbase version up-to-date 2630 ICAO model codes 7 prefixes 6965 ICAO airline codes 92 cargo operators 788 publishers 148 fixes 133 simaddons24 61851 dbase records read 7968 airports read 11630 liveries read from output\LiveriesScanned.xml 159 in-line regcode clashes, see 'output\errors\InlineRegcodes.txt' 5945 liveries read from AIG-regcodes.xml Offline regcode files processed, results can be found in 'output\info\OfflineRegcodes.txt' 3266 special liveries 3172 unique liveries 32252 registration codes 1467 airlines, 182 pax aircraft models and 66 cargo aircraft models 292 similar model definitions Category Light: 478 pax liveries and 39 cargo liveries BE36,C140,C150,C152,C170,C172,C177,C182,C185,C206,C208,C210,C414,C82R,DA40,DR22,DR40,F406,LJ25,P210 P28A,P28R,P28S,P28U,PA31,SR20,SR22,SW3,SW4,TBM7,TBM9,TRIS,VL3 Category Buzjets: 3147 pax liveries and 47 cargo liveries B350,BE10,BE20,BE40,BE99,BE9L,BN2P,BN2T,C25B,C25C,C402,C404,C421,C441,C510,C560,C56X,C680,CL30,CL35 CL60,CRJ2,DA62,E135,E145,E45X,E545,E55P,F2TH,FA20,G150,GALX,GL5T,GL7T,GLEX,GLF4,GLF5,GLF6,H25B,LJ31 LJ35,LJ40,LJ45,LJ55,LJ60,LJ70,LJ75,P212,PC12,PRM1 Category Large: 5487 pax liveries and 496 cargo liveries A19N,A20N,A21N,A318,A319,A320,A321,AJ27,AT43,AT44,AT45,AT46,AT72,AT73,AT75,AT76,B190,B38M,B39M,B712 B721,B722,B732,B733,B734,B735,B736,B737,B738,B739,BCS1,BCS3,CRJ1,CRJ7,CRJ9,CRJX,CVLT,D328,DC91,DC93 DH8A,DH8B,DH8C,DH8D,DHC6,E110,E120,E170,E190,E195,E290,E295,E35L,E75L,E75S,F100,F27,F50,F70,FA7X FA8X,J328,JS41,MD81,MD82,MD83,MD88,P8,SB20,SF34,SH36,SU95,WW24 Category Heavy: 1366 pax liveries and 570 cargo liveries A124,A306,A30B,A310,A332,A333,A337,A338,A339,A342,A343,A345,A346,A359,A35K,A388,A3ST,B742,B744,B748 B74S,B752,B753,B762,B763,B764,B772,B773,B77L,B77W,B788,B789,B78X,BLCF,C130,C30J,MD11 Category HighPerf: No livery found Category Rotorcraft: No livery found 53 models have a generic livery A20N,A21N,A306,A30B,A319,A320,A321,A332,A333,A343,A346,A359,A388,AT45,AT46,AT75,AT76,B350,B733,B734 B737,B738,B739,B744,B748,B763,B772,B77L,B77W,B788,B789,B78X,BCS1,BCS3,BE36,C152,C172,C208,C25C,CRJ7 DA40,DA62,DH8C,DH8D,DR40,E170,E190,LJ25,MD11,P28A,SF34,SU95,TBM9 ++++++++++++++++++++++++ airports scan automatic starts +++++++++++++++++++++++++++++ The scan will search 2 folders ==> SimConnect_Open (PARKING_DATA_RDR) FAILED hr=0x80004005 Error 779: MSFS must be connected to get addon airport data via SimConnect Exiting: SYSTEM ERROR Fri Dec 05 05:14:28 2025
  12. Hi Nico, This latest version, 12.2.0, is getting stuck with the message "Scanning for streamed airports..." Jaime, MEXICO.
  13. I just opened RT to compare the QNH METAR., then closed RT and opened PSXT to see the QNH. Most of the time in MMMX that discrepancy exists, not always, but it is very recurrent.
  14. Hi Nico, I have a QNH discrepancy. PSXT is showing a QNH of 1014 instead of 1025 for Mexico City Intl. Airport (MMMX). RealTraffic METAR shows the correct QNH, according the the current METAR, 30.27 this is 1025 hpa. This issue makes the aircraft land a lot before the airport, as shown in the images. Thank you Jaime. Monterrey, Mexico. https://drive.google.com/open?id=1F04FUFOCV2vpW4ptgKuejGr3LaZlXsKx&usp=drive_fs https://drive.google.com/open?id=1FJT376p4pYjuNa_hYlygR-m9aUoLg5gg&usp=drive_fs
  15. Same here, I just made a "Scan for liveries" and "Scan for addon airports" and the error has been fixed. With the exception that is not recognizing the payware airport, it is using the stock one. In my case, Cancun, Mexico, MMUN.

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.