JRBarrett

I used to maintain a Gulfstream G200 which uses the same PW-306 engines. Boris perfectly captured the groaning “howl” they make when accelerating after start!

The problem is that data for ASDA, TODA and TORA for a given runway is not contained in any navigation or facility database that MSFS uses - either default or Navigraph. For US airports, that information is contained in the FAA AFD supplement for a specific airport. Obviously, airlines that have their own custom performance apps would have that information in their database, but that info is not contained in any standard MSFS database.

Soy hablante nativo de inglés y me cuesta comprenderlo.

The YouTube clip says absolutely nothing about him being struck by a flying LP record?

I have a Fulcrum yoke and it is still recognized as such. I know some people have had issues with controller assignments and bindings changing, but that has never happened on my installation. All the controller assignments I made when 2024 first came out have never changed in all the subsequent SUs.

I browse Avsim almost exclusively with my iPhone using Safari. I use an ad blocker called “1Blocker” which is 100% effective. I have never seen an ad here even once.

I have done one flight so far from KMCO to KORD. The performance is fine, but this version definitely uses more VRAM than any other aircraft in MSFS 2024 on my system. I monitor VRAM using the Windows Gamebar performance widget. The 737 was using about 85% VRAM on the ground at MCO. It dropped to about 79% in flight and went up to a peak of 96% after landing at ORD. I did not run out of VRAM, but it came close. I have a RTX3080Ti GPU with 12 GB

The snow data provided by MeteoBlue does not have enough horizontal resolution in MSFS, so snow on the mountain peaks “spills over” into valleys. They do have higher resolution snow coverage data for New Zealand, which you can see if you go to the MB snow coverage map on their web site and zoom in. They either don’t provide the high resolution data to MSFS - (perhaps for reasons of cost?), OR MSFS cannot use the high resolution data because of the way the snow is overlaid on the underlying terrain tiles. The same problem exists in the European Alps.

Just because MSFS 2024 is a "new" sim, that does not mean that developers can (or should) re-write every bit of code "from the ground up". The data structures and classes that define the internal operations of something like the FMS take a long development time to test and optimize, and will almost certainly be re-used, because a new base sim platform does not automagically mean that there will somehow be a better way to implement those functions. For instance, the mathematical halversine formula, which is used to calculate the great circle distance between two sets of LAT/LON coordinates is over 225 years old, and is still used in every real world and flight sim FMS and GPS navigator today. The "ground up" rewrites will be for functionality that is new and specific to the MSFS 2024 SDK.

The approach should be valid. The current Navigraph Charts shows the RNP 24 approach at LSZG. The glide path angle is depicted as 3.34 degrees rather than 4.0 degrees. The chart is dated 06 March 26 and is effective 19 March 26. Could be a coding issue in the RXP nav data. I do not own the RXP product, so cannot verify.

If an aircraft is equipped with strobes, regulations require them to be operating at all times when airborne, no matter what the altitude. However, many airlines do switch off landing lights when climbing above 10,000 feet, and switch them back on when descending below 10,000.

In regular Live Weather, surface winds come from the latest METAR report (in knots) and winds aloft come from the MeteoBlue model. I believe the transition from METAR wind to MB model wind happens about 1500 feet AGL. Wind speed in a gridded weather model is always expressed in meters per second. The direction is expressed in rectangular coordinates U and V in which the U is the east/west component and V is the north/south component. Actual direction is calculated by doing a rectangular to polar coordinate transform. It appears that when winds are set manually, the entered direction is being used (as entered), but the conversion routines used for the MeteoBlue model wind speed are still active even though the model is not actually in play. That would explain why speed manually entered in knots is being interpreted as meters per second above a certain AGL altitude. It seems as if this would be an easy thing for the developers to fix. The MB model wind parser should be completely disabled when manually entering wind. The directional parser is indeed disabled, but the speed parser is still active when it should not be.

The initial beta just came out today. I am sure there will be many updates to come in the weeks ahead. Whatever changes/improvements to weather might be planned will probably come later in the Beta 5 process. They don’t necessarily include “everything” in an initial release.

I was 13, and the picture tube on our TV had died a couple of days before but the sound still worked, so I heard the landing but did not get to “see” it!

Domestic CPDLC is now being used increasingly in the US for communication with ATC centers. The difference is that the data is typically transmitted over a VHF data radio instead of via SATCOM.