mikeklimek

I agree with this. I periodically lurk in the forums to keep up with the latest, and I'm perfectly happy to wait until they get the majority of issues sorted, even if it takes a year or longer. To me, the time spent troubleshooting and frustration isn't worth the shiny new object just yet. More power to those who don't mind it.

Strange question here, but does anyone know if AI traffic navigation lights, beacon lights, etc., are cpu "intensive" or controlled? The reason I ask is that when using FSHud, I notice several of the AI planes are not displaying those. Whereas other traffic solutions don't have that issue (for me). If the AI traffic lights are cpu bound, and FSHud is cpu heavy, then that might explain it, i.e., FSHud is using enough cpu that there isn't headroom left over for all AI traffic lights. Minor issue, I know, just curious is all.

As long as the user disables the FSLTL separation control when using AI Flow and AI Ground, there are no ill effects, at least none that I've encountered. What I like about AI Flow and AI Ground is that one can designate arrival and departing runways for the airports, so if the game's ATC is controlling the AI planes, it'll instruct them to use the runways you've specified.

This. If using FSLTL, using AI-Ground and AI-Flow are a must.

Long-time P2ATC user here, been testing FSHUD, and now BATC. FSHUD is decent, but for some reason when it injects the traffic, it's disabling most of the AI traffic's strobes and nav lights on my system (not sure what that's all about). Checking out BATC, I like it! So far no major issues and very smooth (as another said, gate to gate). Certainly no more or less "on rails" than P2ATC. Right now P2ATC has that extra touch of warning the user of nearby traffic, but I can see BATC catching up to that, especially once it starts injecting its own traffic. BATC, of course, has the awesome voices and UI. Even the basic voices sound great to me and I like having the option of using (or not using) premium voices. I think I'll stick with this and see how it goes.

Is there value in downloading the newest version if no interest in the GPU load feature?

I've noticed the same, will try 20 as well.

I'm really enjoying this app. While we all would prefer local weather, the variations in cloud types and layers more than make up for it, for me anyway. Not to mention the adjustable smoothing rate is really good. FWIW, I was doing a flight from KBNA to KDCA at FL 410 yesterday with overcast clouds below me and still had a thin layer of clouds above me. But yeah, let's just use what works best for us and what we enjoy, and have fun!

So in the regular 'Active Sky' threads, I've noticed a few posts mention that Active Sky and RealTurbulence seem to work well together. For those who have both, can you expand on that a bit? Any insight on how the turbulence settings in AS play dovetail with RealTurbulence? I assume they don't double-up on each other as that might make it unrealistic, is that an accurate statement? Or is RealTurbulence even really needed if using AS? The reason I ask is I would like to get what is considered "realistic" turbulence, but I'm unclear how using both affects "realism", or if both aren't really needed and AS alone is sufficient. Hope that makes sense. Thoughts?

I'm a little confused with this: - Added new option: Use periodic theme reloads. Default On. Enable this option to have the weather theme rebuilt periodically, approximately every 7 minutes, to provide updates and variation to the weather as you fly. Without this option enabled, updates will occur only as per your download interval setting. What's the difference between updates that occur based on regular download intervals vs. "periodic theme reloads"?

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?

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?

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.

Thanks for the reminder. When I tried it earlier, I checked for updates within the application itself, and it told me I was still current. After seeing your message, I went straight to the website, and sure enough, there's a new version. Will install it and give it another go.

Yes, same here, seems to be injecting weather based on metars from 3 days ago. This is really frustrating and I wish Asobo would get their act together. Even my standby, REX Weather isn't injecting clouds at the moment either. Very strange.

When you say "loaded into the sim", are you referring to the main menu for example, or when loaded into the airport?

Yep, I've seen that too.