mikeklimek

Any insight into how the turbulence settings in AS dovetail with the turbulence settings in FSRealistic? Do they double up or does one overwrite the other?

I really enjoy seeing local weather in the distance, but I have to admit, the better looking sky with different cloud types using AS makes it feel like a new sim and I find myself not missing the local weather in the distance so much--especially with the transition rate set to a slow, smooth transition.

In previous versions of Gaist I also added a few regional route folders (e.g., North American/Caribbean) to my community folder. Are those even still necessary with this new version?

Thanks for the tip! In my case uninstalling and then reinstalling both the connector and AS itself didn't create the correct entry in the exe.xml file (Steam user here). So I thought "well if AS won't do it, maybe I can just manually put that entry in myself." I did, and now it successfully connects when booting up MSFS. If anyone else runs into this issue (i.e., manually having to start 'ActiveSkyUtils.exe' for it to connect), this is what I did: 1) Ensure you have the 'ActiveSkyUtils.exe'. Should be in C:\Users\(name)\AppData\Roaming\HiFi\AS_FS\AddonFolder 2) Navigate to your exe.xml file. For Steam, it's here: C:\Users\(name)\AppData\Roaming\Microsoft Flight Simulator 3) Open the the exe.xml file with notepad and add the following entry: <Launch.Addon> <Name>Active Sky</Name> <Disabled>false</Disabled> <Path>C:\Users\(name)\AppData\Roaming\HiFi\AS_FS\AddonFolder\ActiveSkyUtils.exe</Path> </Launch.Addon> Note the line above bracketed by 'path' should be one line (it's just wrapping here in this post). Save the file of course. Thanks again RALF!

I've noticed that in order for AS to connect, I always have to manually click on ActiveSkyUtils.exe in the addon folder in my C drive after booting up MSFS. This .exe is excluded in my antivirus and I've removed all extra toolbar mods. Isn't this .exe supposed to run automatically? FWIW, I have MSFS (and AS itself) installed on my D drive, with this Appdata/Roaming/...addon folder in my C drive. Not sure if that makes a difference.

Quick question (forgive me if the answer is obvious and I'm just missing it): Let's say I have the update intervals and smoothing set the way I like it and the last update occurs just prior to entering my arrival airport's airspace, i.e., a metar prior to the arrival airport. When I make the approach to the arrival airport, will that airport's conditions reflect the last metar the app updated to, or the actual arrival airport's metar? Put another way, will I be landing with winds from the last metar update or the airport's metar?

Agree with this and others who mention the importance of weatherfronts. Going to a metar to metar transition seems like a step back and similar to REX. If ActiveSky solves this, I'm in for sure.

Think of it this way: the value you enter is only going to apply for the configuration that is displaying in the app at that moment based on what the app is "sensing" your configuration to be. So if you want to ENSURE you're entering/using a specific fps for when you're using FG (i.e., double your "true" frame rate), the app needs to be displaying 'Target FG FPS' within the app's 'General' section---and you enter your value for that. If at any time you're seeing 'Target PC FPS' in the app and enter a value, that value will only apply/be used when you're NOT using FG or VR. The example I used above about loading into airport and sitting in the cockpit was only because that's when I'm always acutely aware and reminded I'm using FG, and that label appears in the app. But forget about WHEN you enter the value, i.e., sitting in the cockpit, whatever. It's really WHAT is appearing in the app at that moment that will use the value you enter for it. So if I open the app and see 'Target PC FPS' displaying, that is what it will use when I've got FG turned off or not using FG. If I see 'Target FG FPS' displaying, then I've got FG active and it's using the value I've entered for that setting. So I theoretically if I wanted to, I could enter 25 fps for 'Target PC FPS' that it will use when I have FG turned off, and I can separately enter 40 fps for 'Target FG FPS' for when it sees I have FG turned on.

For those slightly confused around the 'Target FPS' setting, here's how I think about it (maybe this will help): The 'Target FPS' setting is one that can hold, remember, and use three different values depending on how you are using your sim: Target PC FPS - for users who have FG and VR turned off (default). Target FG FPS - for users who have FG turned on. Target VR FPS - for users who have VR turned on. The app will automatically "sense" how you are using your sim and automatically switch to that "mode" or value that you can use (and change to your preference) when in that mode. Examples: Let's say I open the app but have MSFS closed. The app will default to 'Target PC FPS' because it doesn't "sense" any use of FG or VR (which makes sense because MSFS is closed). I could set this to value to 30 fps which is what it will use when FG and VR isn't turned on. Now let's say I open MSFS and load into an airport, sitting in the cockpit ready to go--since I'm not using FG or VR, same thing: 'Target PC FPS' is used (and can be changed to my preference). Now let's say I'm a user that decides I want to turn on and use FG. I load into an airport and am sitting in the cockpit ready to go---the app now senses I'm using FG, so it'll switch to 'Target FG FPS'. Since I'm now using FG, I would go into that field and enter 60 fps because that's double my 'real' framerate, and what I want the app to maintain when I'm using FG. Same principle when turning on VR. The app will remember what values you entered for all 3 scenarios and auto-switch to those modes/values when it sees what you're using (FG, VR, or neither).

I would also willingly donate, this app is phenomenal! Between this app, the smoothness of the beta, and frame generation, I'm in flight sim nirvana.

I generally use PSXT, but with the server issues Real Traffic is having resulting in weird behavior, planes randomly appearing/disappearing at multiple airports, etc., it just breaks the immersion so I can't see myself using it again until the server issues get resolved. I like FSLTL, but sometimes it seems like it's not grabbing ALL the airliner traffic. So in the meantime, I'm now using AIG's Traffic controller with all its flightplans. May not be "live" but the flightplans are based on real life historical plans so they work great. With AIFlow and AIGround (and the ability now to set arrival and departure runways with those), the AI behavior is greatly improved over default. Throw in a GA Traffic mod and I'm set for now. Definitely not as immersion breaking.

I don't have an issue with the KBNA feelthere airport and kind of like it myself. That's my home airport and having tried all the different versions out there, this is the one I've settled on personally. They released an update a few days ago that I believe fixed the taxi intersection referenced by RandllR as well as a few other additions.

Sometimes when certain functions don't work on one peripheral, I found that function mapped and active on another, causing a conflict. You may want to check and see if items such as throttles, parking brakes, etc. aren't mapped and active on a different device. Just a thought.

Anyone recall why a change was made in the first place that took us down this road? If it was working fine before, why mess with the RT servers? Was it a forced thing?

So I've spawned into a few airports now where the traffic looks good in the air, taking off, landing, etc. But taxing is a different story. In many instances, you don't see the planes until they they've already taken off. In other instances, the taxing planes are injected, but just sit there, or they start moving, and then stop and sit there. After a few moments, they disappear, and then later, you see them reappear when about 50 above the runway on takeoff. From what I understand, this is a RT server issue, and they're apparently looking to get new or improved servers? If so, any word on when this might occur?