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.

Dave_YVR

Members
  • Joined

  • Last visited

Everything posted by Dave_YVR

  1. Xnconvert will do it as well but with less artifacting when saving. Plus you can mass convert/save hundreds of textures in a few seconds.
  2. If you are getting weird airlines that shouldn't be there then it's your own settings in PSXT. What are they set to?
  3. Do you save your custom bindings and assignments to your own custom named profile?
  4. The majority of painters are painting on the models that are currently most widely used even if most of them are between 2-15+ years old. They aren't painting on the old models that have been replaced 2 or 3 times already because why would they? No one is forcing anyone to move to MSFS2024, most AI models and paints will work from FSX right through to MSFS2020. I know personally moving from P3d and also MSFS2020 to 2024 that I lost quite a few AI models that haven't been converted and I haven't seen anyone complaining about it even when the majority of simmers are using 2024, it's just the way it is as it's that much better overall. Just my 2 cents anyways. As for a lack of spot views etc. It's just different than what you are used to. The camera system in 2020 and 2024, you just get used to using it. Personally I use the drone cam connected to a spare PS4 controller all of my spotting and it's awesome, far better than what I ever had from FS9 through every P3d. There are other options as well with a selection of different camera addons many offering the ability to cycle through AI aircraft etc.
  5. All of those idents are in the log except for CSN326 and JST952. VOZ414 was just rolling as you loaded up, maybe you missed it. MATCHING_DEPTH=7 and max fit 47? That's just asking for a mish mash of various aircraft with not much in the way of accuracy. Those that are subbed in are because you are using FSLTL which has a fairly limited selection of liveries or types. So some of those that are missing were mostly there, but because you aren't supplying the liveries, PSXT is using what it can find. Fwiw, I loaded in to roughly 10 mins before you did and the only ones I was missing out of your list were the departing flights that hadn't yet turned on their transponders prior to or during the pushback because it was still 20 minutes early. Once that time came, they were there as expected.
  6. What are your settings? Soft shouldn't be checked here for sure, otherwise I could definitely see getting some cross traffic from OTHH. The only airline traffic I might get at OTBD in my sim is some QTR VIP or training flights, other than that it's pretty quiet as expected, some military trainers, helicopters and VIP stuff. Do you have specific types and liveries in your collection that you might expect to be there for PSXT to inject?
  7. It has to be one of your models or repaints. I can't see how PSXT itself would cause the sim to CTD. I get the odd ctd myself, but I also have nearly 20,000 liveries in my setup, only 8500 or so from AIG the rest are custom manually installed. I'd suggest something simple like disabling your lower ai-package and see if you can repeat the ctd.
  8. The point was more to check and see for yourself and your system. Just because it says that it is a VRAM issue doesn't mean that it is. In the case of the OP with a 6gb card, it probably is, but it's still good to look to see if there are other weak links in the system.
  9. Check for yourself and use the display FPS option within MSFS2024. I too thought that I had a VRAM issue as that is what the sim was telling me. I was wrong. I USED to get this warning ALL of the time with my 16gb RTX4080 so I enabled the display fps to see what was going on and the VRAM WAS NOT anywhere close to being exceeded. The system ram however WAS exhausted. I Had 32GB of DDR4 and was nearing near zero headroom with my sim running left so I pulled the pin and moved over to 64gb of DDR5 and it has NEVER come back once since. I was previously quite reluctant to upgrade ram thinking that it wouldn't make much difference, I was so wrong. The smoothness increase in the sim was night and day compared to before. I definitely paid through the nose for the ram and it has since then increased in cost by another 40% but it was one of the best purchases for the PC that I have ever done in the 25+ years of simming and building pc's. The important thing though is to check for yourself with the display FPS function and see what's going on inside.
  10. Lol.. Finding work arounds for when it doesn't work as planned. ;)
  11. I also prefer to not scan as I have a few airports that still don't get seen by the scan (old marketplace purchases) so I have manually made my own my_thirdparty files for them and they work great, until the next airport scan.
  12. The IVAO MTL models I find are VERY finicky if you mod them. Some work and some do not and I'm not sure why. But you also didn't conform to proper ICAO in the entries. The H300 isn't a Robinson and the H300 isn't an icao type. Try something like this. [GENERAL] atc_type =H269 atc_model =H269 Category = Helicopter performance ="" editable = 1 wip_indicator = 1 icao_type_designator =H269 icao_manufacturer =SCHWEIZER icao_model =300 icao_engine_type =Piston icao_engine_count =1 icao_WTC =L icao_generic=0 Also, did you edit the cfg entry for the actual aircraft under [fltsim.0] as well?
  13. Sure no worries. Take the 737 Max 10 as an example. I take my AIA 737 Max 9, copy it and rename it AIA_B737-MAX10 FAKE. Then in the aircraft.cfg and under the [General] section simply change what is needed to conform to ICAO so that PSXT thinks that it's the type that you want. icao_type_designator=B3XM icao_manufacturer=BOEING icao_model=737 MAX 10
  14. Thanks Nico! It's more appreciated than you know!
  15. I'd love to have the liveriesscanned file back as well. I use it multiple times a day EVERY day. It was an awesome feature to have imo.
  16. I add fake model types to fill in missing gaps by copying a particular model that I think will be a reasonable addition and simply editing the [General] section of the aircraft.cfg to conform with ICAO model, type and Manufacturer etc and it works great! I've probably done this for upwards of 40-60 new types that we don't have models for. Super simple and doesn't get overwritten by a new livery scan.
  17. It's just the log.txt in your main psxt folder.
  18. Nope. That will not be it at all. Steam or Xbox/MS store doesn't make a difference when connecting to the MS servers. Mine is through Steam as well and I'm on the West Coast of N. America and have had ZERO issues starting and running the sim today or yesterday.
  19. https://www.alpha-india.net/2026/05/10/oci-basepack-release/
  20. I'm pretty sure that the conversion team at AIG have looked at everything they can on their end. It also didn't used to be this bad, Asobo reduced the lod distance to improve performance for the console users. They could fix it near instantly if pushed hard enough.
  21. Yeah it's the same for everyone, complain to Asobo as they are the ones able to fix it.
  22. Westjet also has a number of their own RNP approaches into various Canadian airports. The best ones being in the mountains of British Columbia very similar to around PAKT.
  23. The GL5T is a valid ICAO icao for the Global 5000 and 5500.
  24. There is no GL6T icao code, it's a GLEX. If you can change it in the aircraft.cfg, then try it and see.

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.