jabloomf1230

Thanks. My updates are not specific to which 3rd party addon is being used and are updated on a regular basis.. The SI Taxi Tuner has over 2000 airports updated by the SI community but if one is.missing, the user has to use the SI Taxi Tuner app which requires work in researching airport changes.

I have created a number of revised default MSFS 2024 airports that are available for download. The thread is located here (with a Discord server invite): https://discord.gg/skY3r4NyC The airports have real world, up to date (based on Navigraph Charts) taxiways, runways, taxi signs, taxi designators, painted lines, gate numbers and airline codes. These airports are designed to work properly with a 3rd party ATC app (BATC, SI, FSHUD, AIG TC, etc.). There was no attempt to revise terminals, hangars or other airport buildings, unless a terminal was modified in the real world airport. All editing was done with MSFS 2024 Developer Mode. The main purpose was to allow AI traffic to traverse the taxiway network without becoming stuck. The secondary purpose was to match the real world airport chart as much as possible. If you notice any errors report the issue on the Discord Server. These airports represent the larger facilities by enplanements, except for the largest in each world region. The reason for not including the largest airports is that there are excellent commercial 3rd party versions available for MSFS 2024. You may also further modify these airports for your own personal use. However, if you revise them and post a revised version online, just give credit to "JAB-Flightsim".

What on earth is @fl95 talking about? FR24 makes money by subscriptions (which I have as it's a valuable service), but it also partners with airlines and aircraft manufacturers. It was just a matter of time before FSLtL was going to be prevented from using FR24 data for free. When a private equity company bought about a one third interest in FR24, there probably was some internal examination of areas where potential income was being lost. Also, I don't know how much of the flight sim community knows this, but FSLtL uses freeware models without permission from the authors. I guess the best way to keep your product free is to use other people's intellectual property.

I think that you more or less answered your own question. However, I own multiple 3rd party ATC add-ons, but unfortunately I can only guess at what happened to you at LAX. The add-ons like BATC have runway ops for airports with multiple runways and usually the low (or calm) wind runway(s) is specified. Low wind is usually considered to be 0 to 5 Kts. The problem is that this creates a discontinuity at 5 to 6 Kts where the active runway could hypothetically switch. In the real world, the airport's chief AT controller doesn't keep changing the active runways every time the wind speed goes from 5 to 6 kts. Generally, real world runway shifts are kept to a minimum during a given day and are only mandated after frontal passages that cause drastic changes in wind speed and direction. Another issue is the timeliness of the weather data and how often it is updated in the ATC app. Each ATC app (and the sim for that matter) uses a slightly different approach to obtaining and updating weather data. Also, I noticed you mentioned crosswind runway use. This is commonly only important for GA and other light aircraft, at least for wind and wind gust velocities normally experienced at most real world airports. This doesn't mean that crosswind runways are never used. They can also used by mid-sized commercial jets when the crosswind or tailwind component exceeds the design spec for that aircraft model. A crosswind runway might also be used to ease separation bottlenecks. It also could be used if its taxiway locations provide a shorter path to either the stand or the FBO apron. In any case, if you are piloting either a B737 or an A321 in the sim, the active runway will be either the calm wind runway or the non-crosswind wind runway best aligned with prevailing wind direction. At least it should be. One last real world consideration is for night ops, often 2300 ± to 0500 ±. Noise abatement procedures may dictate that certain runways should not be used at night, since the flight path take the low flying aircraft over heavily.populated areas. Takeoffs are more critical because they generate more noise than landings.

Alex spent some time trying to figure out the changes to the Airport BGL file format, but in the end he just used API calls to decipher airport structure in MSFS 2024. This approach requires that MSFS 2024 be running at least once, so that LNM can create its airport database.after that parsing run, everything is fine until the user makes any change to the MSFS airport database. I also tried to figure out the changes in the BGL format. There are a number of new fields in the BGL that correspond to feature changes added for MSFS 2024. As to your question, I just start with a default MSFS 2020 airport, run it through one of the BGL to XML conversion utilities that can be found on fsdeveloper.com and then create a project in MSFS 2024 from that XML file.

Ha! I meant the option in the Developer Mode menu doesn't work. Your mod works perfectly.

Thanks. The Toolbar is really annoying in Developer Mode. The option to hide it in the sim doesn't work for me for some reason.

I actually do snorkel and scuba dive. My masks weigh very little in the water.

Or probably ever. That why it won't be mainstream.

I'm looking forward to the PS5 version, if nothing else but for the VR possibility. VR on the PS5 is actually usable, unlike my experience with the PC which has been an uneven mess with Meta and HP VR headsets. I even tried the PS5 VR2 headset on my PC and it wasn't much better. VR will never be mainstream until someone can sell a high performance, high resolution, light weight, wireless headset for under $200 US. Sadly, flat panel screens are here to stay for now.

If one surfs the Internet, one will find references to MSFS 2024 sound stuttering and even a few CTDs that follow the stuttering. It is usually fixed by disabling additional audio device drivers that are not used like Realtek, Sonos, Soundmax, etc.. In addition, MSFS 2024 seems to have issues with certain Bluetooth audio devices, which could be disabled as a troubleshooting step.

I guess that you didn't detect the note of sarcasm in my post. Asobo should make the walkaround an option that can be turned off in the menu.

What I do is create a flight plan that spawns at a runway.Then I use GSX to warp me to a gate. That's a lot of effort to make up for Asobo's walk-around.

That site has been a backwater for years. Let's hope that someone sensible buys the domain name.

You can try contacting them here: https://m.facebook.com/rcsimulations/ but I think that the registration is handled directly by Internal Workings, the company that developed VoxATC: https://voxatc.com/Home/Register If that's not working, then I guess that at present you can't buy it. Also, VoxATC for MSFS 2024 is in closed beta.

It seems to take Asobo a few tries before they get a workable SU beta

Alex, I sent you an email in case it ends up in your spam. Jay

All the work figuring out the 2024 BGL format may not have been in vain.🤞

The MSFS live weather uses METAR data at airports and Meteoblue model forecasts in between. Although these forecasts will show frontal boundaries, they are still simulations and the location of the boundary may not match real time data. There's really no way for the sim to exactly match near field weather as the worldwide monitoring network is too sparse.

It only took 8 pages for someone to mention XP, even though it has no bearing on the discussion. Here's the nub of Asobo's problem. MSFS 2020 is designed for a certain level of hardware and MSFS 2024 has higher hardware requirements. With those higher hardware requirements potentially comes more features. Those new features require more testing to get them to work correctly. MSFS 2024 was rushed out the door and has been a buggy mess since release. Collectively, all this has led to most of the users (at least according to the Navigraph flightsim survey) to stay with MSFS 2020. Eventually, as more users either abandon flight simming or buy new hardware, MSFS 2024 will become the dominant app in that market segment. Before anyone starts yelling at me, I use MSFS 2024 almost exclusively. I've sequentially uninstalled XP and P3d, but I've left a skeleton version of MSFS 2020 on my PC to test 3rd party apps. I've learned to put up with the issues in MSFS 2024.

While AS was on "hiatus" during the SU 2 beta, I reluctantly went back to using the MSFS 2024 Live Weather. First, the live weather was broken and showed only clear skies for about a week. Then it alternated between depicting clear skies and historical weather from the previous 24 hours. On the day that HiFi released the AS fix, the MSFS 2024 Live Weather was finally working. In concept, Asobo using a combination of METARs and Meteoblue modelled forecast data seemed like a viable option. Unfortunately, we all know how shaky the forecast model predictions are for NA, especially along the coasts. Asobo really needs to open up the weather API to 3rd party developers.

No Man's Sky and a few other PS5 VR2 games.

HiFi needs to release an update to AS.

Running 1.4.12 SU2 beta today and I also noticed that the Live Weather was broken. I flew a flight plan into KPHN and the sim depicted it as sunny, but the METAR and weather radar online said it was overcast and raining. Of course, Active Sky is also broken, so there no alternative for live weather in MSFS 2024.

https://devsupport.flightsimulator.com/t/effect-textures-without-mip-maps-cause-a-ctd-when-loading-a-flight-in-su2/13661 There's a bug that's been previously reported here that affects AIG and FSLTL aircraft in the SU 2 beta. This bug has been confirmed by Asobo and will be scheduled for fixing in an update to the SU 2 beta. For some reason, the bug does not always immediately cause a CTD and a flight may proceed normally for a period of time. The recommendation if to not use FSLTL and AIG models with BATC, FSHUD or VATSIM until Asobo releases a patched update to the SU 2 beta. Alternatively, opt out of the SU 2 beta and return to the SU 1 release.