mmcmah

And as I recall, an older version also had a preference for larger airports within some radius. Maybe the same setting, but I also don't know if anything like it is still there.

It's also happened to me at WSSS recently

If this is the 2.1.7 update of a couple of days ago, the below is all that was changed: v2.1.7 – 06 April 2026 General Amphibian Users can now climb on the floats during preflight Visuals Exterior Fixed amphibian chock spacing Flight Model Fixed some erroneous exit definitions in the flight model configuration

That's not correct. En route weather is injected and you can set the time interval at which the weather is injected. There are tons of configuration options such as: for how long to keep the departure weather before changing it based on en route METARs, time interval for updating METARs online, time injection intervals, how to manage a change in weather if the destination weather is very different and you're in the approach, how quickly to transition between injections, etc. The only real downside is that you can't be flying and see a front in one direction or another because the weather that is injected is applied in a large radius around you. That is entirely the fault of MS/Asobo not allowing more sophisticated weather injection and limiting it to basically custom weather presets that change as you fly. Also, you can input a flight plan so that the system better manages the weather that it is injecting as you fly and can interpolate more accurately between METAR stations. This is not necessary, but can be helpful if you know your route.

There is also a setting in ASFS which allows you to make Cloud Density Adjustments. Here are two shots just a few seconds apart from the lowest setting, followed by the highest setting. I feel like the highest setting is generally more representative of the clouds I see in real life. https://imgur.com/a/fJBfgWy

Ryan, I know you say you don't use any of the after-market add-ons, but except for the fact that Active Sky doesn't show fronts due to the limitations of the sim weather injection, I have generally found ASFS to be MUCH better than the sim weather depiction. With your METAR information, I was able to get close in terms of the METAR that I could pull up and here is the weather depiction from the drone camera coming in over the lights into Runway 09 (your shot looks a bit different, so you might have some scenery that is different than the stock): https://imgur.com/a/EiQVD8E The METAR represented is: KDLH 021655Z 08021G30KT 1/2SM R09/3500V5000FT SN BLSN OVC008 M02/M03 A2989 RMK AO2 PK WND 07036/1609 SLP143 SNINCR 1/4 P0004 T10221033 $ Decoded textual weather for KDLH Wind: 080 at 21 knots gusting to 30 Visibility: 0.9 SM (1524 m) Clouds: Broken at 8427 feet Temperature: -2.0C Precipitation: Moderate snow Altimeter: 1012 mb (29.89 inches) This station includes complete surface weather information, interpolation disabled. Original metar of the stations: KDLH 021655Z 08021G30KT 1/2SM R09/3500V5000FT SN BLSN OVC008 M02/M03 A2989 RMK AO2 PK WND 07036/1609 SLP143 SNINCR 1/4 P0004 T10221033 $

Hi Nico, I know you are away, and this isn't urgent. A week or so ago I took a flight out of LFPO. Every time I opened RT and PSXT, PSXT would crash (the UI would close suddenly) and RT would remain open while still showing traffic. This happened multiple times. I quit the sim, restarted the computer and tried again,with the same result. Assuming that the issue was specific to LFPO, I took off and waited until I was close to the English Channel (destination was EGLL), and restarted PSXT. Everything worked fine from there. Today, I thought I would try again, and the same issue happened. I did notice that the file was showing a QF of 0 in the PSXT interface, even though it's not showing up in the TBLO folder. I have now looked at the log and can see the likely culprit. The LFPO file seems to be empty of parking spots. Here is the log output: And here is the file located in the 'airports\learned\thirdparty\jetstream\LFPO.xml' that the log says doesn't exist:

Thanks for posting this. So, full price for owners of the 2020 version? I didn't see the amphibious version listed, and after logging in to the SWS web site, I still see full price. What's really changed? The description seems to be pretty identical to what I remember of the 2020 description except for the walk-around features. Not sure that this will be worth the upgrade, especially at that price?

Yes, you can bring up Developer mode and the Camera Blend display to see the FoV as per the OP while using Chaseplane. I just did it based on this thread as I wanting to try it out. It's not pretty as the Developer Mode text hovers over everything, but you can see the FoV value while adjusting the Zoom in the camera position for the pilot/co-pilot/etc.

Me too. I used v2 for a long time and loved it. Experimented with other solutions and always came back to it. Then v3 came out and it has been a disaster for me since it did. I thought about going back to v2, but just decided to move on from the product altogether. So far, BATC is working well as a replacement. Nothing is perfect, but I find it to be working well enough and more enjoyable than flying without it. I also sometimes use it's traffic feature and sometimes use PSXT instead.

Simple isn't a requirement... 😉 Do they work?

Thanks. That's what I was afraid of. Guess I'll do the same and hope that they integrate it at some point, like SayIntentions (which I used to use).

I just decided to get BATC last night and had a hell of a time getting it working. Not exactly my fault or BATC's, since it was a network security issue. Once resolved, I got it to connect. So, I've used ASFS since it first came out and had been wondering this morning about how to use the two together and what limitations there were. Near as I can tell, BATC doesn't draw from ASFS, so they don't really work together? I sometime fly live and sometimes with historical weather for time shifting, and sometimes beyond the 24 hours the MSFS gives as an option. So, since I can upload weather to Simbrief from ASFS, that's what I do. Any pointers on how to use ASFS and BATF together, or what the pitfalls are?

I heard back from Balthasar, as I reached out to him about a couple of other questions as well. He has implemented a variable buffer to allow syncing. Currently in a beta version of the app.