mpo910

I bought ASFS and overall I like the Cloud formats and Weather layers etc. But, here is something I really do not like. I flew a Jet from Zurich to Nice. Startet with Historical weather with Snow and Overcast condition in Alps. Flew directly to the south, did not change anything in ASFS during flight. Download intervall was set to 15 minutes and smoothing rate 75% PRIOR firing up MSFS Clouds did disappear according to the MAP slowly and flew from Overcast conditions to clear skies as expected. Alps where covered with snow nicely When arriving in Nice (30 Min later), Clouds where gone es expected. BUT: Snow coverage all over in Nice. METAR showed 14 Degrees Celsius in LFMN Thats something I would not expect. @Damian Clark: Is this correct behavior? Does Snow coverage also fade away when temperatres and METAR do not report any snow at your place of destination for example like in my scenario? Regards Marcus

How to update my AIRAC in ASFS? Do you know this? I use Navigraph Subscription

Thanks a lot. That sounds good.

Thanks for this very usefull aditional topic!

Hy to ALL using ASFS. I am flying mainly Fenix A320 and i´m very well known with ActiveSky in P3D for several years. I have very good experiences with AxtiveSky, unfortunately due the restrictions in P3D, not with P3D as soon as volumentric clouds implemented in P3D. My questions are: Is ASFS good to use in Combination with Fenix A320? So, does Fenix handle the implemented weather well? Regarding: 1) Turbulence, Temps, Wind Requests for Climb, Cruise and Decent, Wind directions and Speed in PFD, Windshear (so, shows Fenix a normal behavior or overreacting on these wind and turbulance related topics)? 2) Is it possible to request ASFS METAR/TAF in Fenix EFB when using ASFS Live Weather? Or are these Fenix Functions INOP or are they even calling MSFS METAR/TAF? I would like to use ASFS as I think this Addon is the absolut specialist APP regarding Weather in a Flightsim. But if it is Suboptimal for me, with Addons like FENIX, then I would wait to plunge in till FENIX got updated. A feedback would be very welcome. Thanks in advance! Marcus

And if it has VR build in, I hope OpenXRToolkit will be too, or all functions integrated (which I doubt). Because only since using OpenXRToolkit, my VR looks stunning sharp. Things like Foveated Rendering are not implemented in MSFS yet, and this is needed for all users using High End Headsets....wihtout Foveated Rendering, Performance will drop signifcantly.

Mathijs Koks Signature text is interesting: Have fun. Be respectful. Criticize Ideas, never people. I would never use the approach to "Criticize Ideas". Every Idea is a free motivation from a "Customer or potential Customer" to share something. Why Criticzing on that? It is Off-Topic.......I know. It´s just something that I don´t like to read from a Manager.....

......2.84Mbits\s....... When is this going to get better dear ASOBO\MS?

Food=Good...... 😂

Food questions. I have equaled them (4%) in MSFS and MCDU

Maybe check the dead zone settings if they are high enough? And, also with MSFS I had heavy weather upload changing altitude and wind dramatically causing my AP to disconnect as well. Just some thoughts, although this must not be applicable to your situation.

The AutoLod is only increasing and maintaining TLOD if your set target fps is achieved. If this is the case, tlod could be high BUT if the sim is not well optimized then you still will suffer from stutters

Is this relyable or is this pure assumption from yourside? And what if it is "pressure"? What does this mean for you or Asobo (Time, Money, Reputation etc.)?

I do understand this very good. This will lead to the case, that when you start a flight, all is fine because the app will choose your "in MSFS" TLOD to start with. The downside is, that when decending, you get very high TLOD (when your Target FPS is not set to high and your machine is capable of), then when hitting the ground, the app will "fix" the last TLOD value, which was present "at" the moment you hit the ground, this is a high value, in the most cases, to high for smooth taxiing. Yesterday I got, till landing TLOD values >200, and after I touched down it reduced quick to 105. So 105 would be the right value to maintain my "target FPS, which was 45 set by me in the app). With the newsest version this "105" will be around "200". That will cause stuttering. That´s why I asked about the "fix TLOD GRound Value" set by the user.

@Reset XPDR For AutoFPS It would be nice to have the possibility to set a ground TLOD value in the app (0=x, like 0=125). The value x can be set by the user and the "0" is fix. When loading into the flight that x value is chosen, when climbing the fps target is leading, when decending also, when touching down after decending (=ground) the set ground value is set once by the app. Ground value works the same as in dynamic lod reset app.