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.

kiek

Members
  • Joined

  • Last visited

Everything posted by kiek

  1. Hi Devin, The next version will change that raw model into E55P Nico
  2. The method is still the same, but instead of once in 3 seconds, PSXT checks 10 times per second if there is another live aircraft close to the "stuck" one. So more chanse of detecting the collision.... EDIT could it be that the aircraft you mention were not stuck but still alive?
  3. If you are happy, I'm happy.
  4. QID is wrong in my dbase, it must be RCH. But that should not matter for matching based on regcodes. Your log does not show how your liveries were processed, because restart had happened. Please exit PSXT. Then run PSXT, and push Liveries scan. Then do some matchings and afterwards post the Log.txt
  5. C means cargo Will look at the Log later, i am not at home now.
  6. I found the counting bug in reporting the number of regcodes per livery title. I've updated 15.7.4, so if you already are at that version, re-download from my website.
  7. log0.txt is the previous version... (from your previous run of PSXT) Just give me the complete log.txt from a session where suspicious matching (according to you) takes place, so I can see lines like this: AAL396* N316RK AAL B38M. =1= AIGAIM_American Airlines Boeing 737 MAX 8 AAL1543* N163US AAL A321. =1= AIGAIM_American Airlines Airbus A321-200 - CFM AAL2840* N567UW AAL A321. =1= AIGAIM_American Airlines Airbus A321-200 - IAE N704US* N704US AAL A319. =1= AIGAIM_American Airlines Airbus A319-100 - CFM AAL2718* N832NN AAL B738. =1= AIGAIM_American Airlines Boeing 737-800WL UAL1210* N37504 UAL B39M. =1= AIGAIM_United Airlines Boeing 737 MAX 9 - OC UAL747* N14230 UAL B738. =1= AIGAIM_United Airlines Boeing 737-800SSW - OC GATE G11 : no static parking for ASA538, live aircraft JBU805 is adjacent at GATE G13, possibly colliding AAL2434* N987AM AAL A321. =1= AIGAIM_American Airlines Airbus A321-200SL N756US* N756US AAL A319. =1= AIGAIM_American Airlines Airbus A319-100 - CFM UAL602* N76508 UAL B738. =1= AIGAIM_United Airlines Boeing 737-800SSW ACA525* C-GROV ACA BCS3. =1= AIGAIM_Air Canada Airbus A220-300 - Wifi dome GATE H18 : AAL396* parked UAL787* N14563 UAL A21N. =2= AIGAIM_United Airlines Airbus A321-200neo GATE H16 : AAL1543* parked UAL651* N17550 UAL B39M. =1= AIGAIM_United Airlines Boeing 737 MAX 9 GATE H15 : AAL2840* parked UAL785* N872UA UAL A319. =1= AIGAIM_United Airlines Airbus A319-100 GATE H12 : N704US* parked UAL353 N24508 LAX->ORD UAL A21N. =1= AIGAIM_United Airlines Airbus A321-200neo GATE H10 : AAL2718* parked UAL1672* N53442 UAL B739. =1= AIGAIM_United Airlines Boeing 737-900ER SSW
  8. It is only feedback for you to check your file is (syntactically) correct. It has no furher impact. But it looks like my feedback is sometimes wrong. Will look at it. Could you mail me the contens of your my_regcodes folder?
  9. Processing 'input/my_regcodes/C5MGalaxy.txt' 1 livery title with 1128 regcodes, read from input/my_regcodes/C5MGalaxy.txt Is that correct? EDIT: I'm also still interested in the Log part that shows the matchings... EDIT: and also pay attention to this part of the LPG.txt: No license found in 'C:/Users/icroo/AppData/Roaming/InsideSystems/RealTraffic.lic'. Problem: [json.exception.parse_error.101] parse error at line 1, column 71: syntax error while parsing value - invalid literal; last read: and so on
  10. Hi, My new logging of reading your my_regcodes file is still not correct. But that's not the main problem. The main problem is that it has not found any livery in your MTL folder... ? That's why the helicopters and fighter jets checkboxes are disabled. I have the same here now. Thats fine, so it is easier for me to check what is happening. Just wait pls, Nico
  11. Hi, Please re-download 15.7.1 from my website and re-install. I've improved the logging of the processing of your files in my_regcodes. Als added recognition of your UH-1H aircraft type, and converted it to the ICAO code: UH1 Then do a run until you see a wrong match. Then post the Log again. Nico
  12. Hi Ian, The complete Log.txt please with the matchig lines... Nico
  13. The Log shows the matchings, post it here then I can have a look.
  14. EDIT: it should say 15 new regcodes added ... or something like that
  15. The regcodes in your \input\my_regcodes\100ARS.txt are all mapped to the livery with title IVAO_K35R. Hence, if such a regcode is detected in RT data, PSXT will match that aircraft with that livery. EDIT: In the Log you must see something like this (example): Processing regcodes file 'input\my_regcodes\test.txt' 2 liveries read from input\my_regcodes\test.txt
  16. I have not done anything on the QNH issue.
  17. I've checked that now (with stock KEWR 22R), but all planes take-off. Yes, they need the whole runway, but that's okay. What airport addon are you using? Could it be that the layout of the runways is not sync with real live?
  18. It is indeed easier what Dave said, define your own regcode file as desribed in the Manual Appendix (then you do not need to edit aircrfat.cfg files): In the input\my_regcodes folder, you may put one or more text files. The name is not relevant, but it must be unique, with extension .txt. In the file one should specify the (exact) title of the livery followed by a semicolon, followed by a list of registration codes separated by commas. A livery title may not appear on more than one line. Liveries that have just one registration code in an offline file, will be treated as being special, they will only show up as live aircraft, not as static parked aircraft. If you add ;# to a line, all registration codes will be treated as special, for example: AIGAIM_easyJet Europe Airbus A320-200SL - Europcar;OE-IVC,OE-IVT;# If you specify only a livery title, with no registration codes, PSXT will treat it as a “don’t use” livery.
  19. Your log stil does not prove double parking. GATE E1 : JBU2924* parked in between is the interval end with new parking. JBU294* could have been removed for live with static collision avoidance ... GATE E1 : JBU2924* parked Pls download 15.7.0 from my website. I've just add logging of static removal because of collision avoidance. EDIT: what is also strange: if PSXT would have parked twice they would have been exactly at the same place, not like you showed.
  20. If RT (you mean the App I guess) reports the correct QNH, then PSXT should have the same. If not, there is a bug... Can you give me location, utc date/time, then I can check. What does RT Direct tells you?
  21. I've composed a heuristic, try 15.7.0
  22. Please give Zulu dates and times, otherwise It cannot check it.
  23. I've checked LSZH, only a few aicrat slow down, which is caused by bad RT data. I cannot do much about it.

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.