G58 regression

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

No

Which aircraft are you using that experiences this issue?

Beech Baron

Brief description of the issue:

Load out has 4 passangers instead of 6. Airspeed indicator does not work.

Should be

max_number_of_stations = 8
station_load.0 = 170, 0.6, -1.1, 0.9, TT:MENU.PAYLOAD.PILOT, 1
station_load.1 = 170, 0.6, 1.1, 0.9, TT:MENU.PAYLOAD.COPILOT, 2
station_load.2 = 0, -2.6, -1, 0.9, TT:MENU.PAYLOAD.FRONT_PAX_LEFT, 4
station_load.3 = 0, -2.6, 1, 0.9, TT:MENU.PAYLOAD.FRONT_PAX_RIGHT, 4
station_load.4 = 0, -6.0, -0.6, 1, TT:MENU.PAYLOAD.REAR_PAX_LEFT, 5
station_load.5 = 0, -6.0, 0.6, 1, TT:MENU.PAYLOAD.REAR_PAX_RIGHT, 5
station_load.6 = 0, 5.5, 0, 1, TT:MENU.PAYLOAD.FORWARD_BAGGAGE, 6
station_load.7 = 0, -8.4, 0, 1, TT:MENU.PAYLOAD.REAR_BAGGAGE, 6

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

take the baron for a spin

PC specs and peripheral set up:

Processor Intel(R) Core™ i7-9700K CPU @ 3.60GHz 3.60 GHz
Installed RAM 32.0 GB
System type 64-bit operating system, x64-based processor
SanDisk SSD G5

Edition Windows 11 Pro
Version 22H2
Installed on ‎10/‎28/‎2022
OS build 22621.2066
Experience Windows Feature Experience Pack 1000.22634.1000.0

NVIDIA GeForce RTX 4070ti with 12g memory
Driver 545.37/536.40
DisplayPort
G Sync Monitor: Dell 27 Gaming Monitor - S2721DGF
HP Reverb G2

Honeycomb Alpha & Bravo
Thrustmaster TPR Pedals

Internet Speed
230.9 Mbps download
32.5 Mbps upload

Are you using DX11 or DX12?

DX11
Are you using DLSS?

No

:loudspeaker: For anyone who wants to contribute to this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

Are you using DX11 or DX12?

Are you using DLSS?

If relevant, provide additional screenshots/video:

Check your temperature, if you have encountered icing, the pitot tube will be blocked up. To solve the issue, turn on pitot heat located on the bottom side panel. You will notice the speed indicator returns to normal.

1 Like

On the other hand, the speedband shown in the PFD seems to be working…

1 Like

I imagine that could be a “GPS” based calculation so it doesn’t rule out a pitot tube freezing situation or prove that the guage isn’t working as designed
Pitot tube freezing needs to be ruled out.
Not that that’s hard to do.

I have tested and ruled out icing.

Do you have the same issue if you follow the OP’s steps to reproduce it?

Same standby airspeed indicator issue. If I start on the ground, it will start at zero and slowly move up to about 50 knots (but never matches actual speed once you start moving) and then just stays there. If I start in the air, it’s already at 50 knots and never moves above that regardless of weather conditions, even with pitot heat on.

Provide extra information to complete the original description of the issue:

Are you using DX11 or DX12?

DX11

Are you using DLSS?

No

If relevant, provide additional screenshots/video:

Starting on the runway, airspeed at zero:

Climbing out, airspeed doesn’t match:

Regards

Are you using the G58 Improvement Mod by chance?

No mods for me.
Regards

No mods for me

Do you have the same issue if you follow the OP’s steps to reproduce it?

yes.

Provide extra information to complete the original description of the issue:

G1000 and Standby airspeed doesnt match

Are you using DX11 or DX12?

DX11

Are you using DLSS?

no

If relevant, provide additional screenshots/video:


footage speedup to reduce the playback time

1 Like

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

NO

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

YES

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

BEECH-BARON-G58

Brief description of the issue:

Speed discrepancy between PDF and steam gauge

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

Fly the Beech-Baron-G58 and look at the subject devices PDF and Steam. Different speeds will be observed.

PC specs and/or peripheral set up if relevant:

HP OMEN - Ryzen 5 5600G, nVidia RTX 3060, 16 GB 3200 RAM

Build Version # when you first started experiencing this issue:

Latest build of MSFS 2020 updated today 9/29/23


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

Same issue since version 1.34.16.9

:wave: Thank you for using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

2 tags are required: One for platform, and one for aircraft.

Are you using Developer Mode or made changes in it?

No

Have you disabled/removed all your mods and addons? If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the Community Support section.

Yes

Which aircraft are you reporting an issue about? (Please also add the proper tag for it)

Beechcraft Baron

Brief description of the issue:

Standby Airspeed Indicator is inoperative.

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

n/a

PC specs and/or peripheral set up if relevant:

n/a

Build Version # when you first started experiencing this issue:

1.34.16.0


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

:wave: Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.

Are you using Developer Mode or made changes in it?

NO

Brief description of the issue:

The number of payload stations appears to be 5 when it should be at least 7.
Missing are REAR_PAX_LEFT and REAR_PAX_RIGHT.

Expected stations are below (the actual offsets are not available):
station_load.0 = ?, ?, ?, ?, TT:MENU.PAYLOAD.PILOT, 1
station_load.1 = ?, ?, ?, ?, TT:MENU.PAYLOAD.COPILOT, 2
station_load.2 = ?, ?, ?, ?, TT:MENU.PAYLOAD.FRONT_PAX_LEFT, 4
station_load.3 = ?, ?, ?, ?, TT:MENU.PAYLOAD.FRONT_PAX_RIGHT, 4
station_load.4 = ?, ?, ?, ?, TT:MENU.PAYLOAD.REAR_PAX_LEFT, 5
station_load.5 = ?, ?, ?, ?, TT:MENU.PAYLOAD.REAR_PAX_RIGHT, 5
station_load.6 = ?, ?, ?, ?, TT:MENU.PAYLOAD.REAR_BAGGAGE, 6

Provide Screenshot(s)/video(s) of the issue encountered:

Detailed steps to reproduce the issue encountered:

N/A

PC specs and/or peripheral set up if relevant:

Build Version # when you first started experiencing this issue:

1.24.5.0


:loudspeaker: For anyone who wants to contribute on this issue, Click on the button below to use this template:

Do you have the same issue if you follow the OP’s steps to reproduce it?

Provide extra information to complete the original description of the issue:

If relevant, provide additional screenshots/video:

I don’t think Jorg Neumann has any interest in letting Asobo fix issues with previously released products. As a marketing guy, I’m guessing he’s thinking “We’ve already got their money for those. How does fixing anything previously released make Microsoft any money?” Marketing Philosophy 101.

So sad.

1 Like

You nailed it.

1 Like

You may be right, but you’ve got to try!

1 Like

And that’s what I don’t get…Jorg Neumann isn’t even trying. For instance, he has excluded any previous bugs from being fixed in SU9. If existing bugs aren’t fixed in a Sim Update, and not being fixed in a World Update, then when are they going to be fixed?

I don’t think Jorg Neumann understands his core customer base, or doesn’t want to accept the priorities of his core customer base. I’m pretty sure most MSFS 2020 customers are less interested in the next new shiny thing and more interested in core features working correctly. Who cares about the next new plane when the current planes don’t work right?

And this is why I think we’ve seen massive sales running in the Market Place for the past 5 months. I’m guessing it’s because sales have slowed as enthusiasm has waned due to all the bugs in the core flight sim. And the Market Place is where Microsoft earns its incremental income after the initial sale of the product. To keep sales brisk in the Market Place, Jorg Newmann is going to have to focus on fixing the core sim functionality and not the next new shiny thing. And I wonder if he gets that.

Wow, that’s a lot to take in. but I see your point. The Sim Update 9 BETA testers are reminded that they should only report “regressions and not old bugs found in previous versions.”
However, the instruction doesn’t imply that “old bugs” won’t be fixed… we wait with bated breath to see the outcome!
Thanks for your invaluable contribution.

Here are the missing parameters…

max_number_of_stations = 8
station_load.0 = 170, 0.6, -1.1, 0.9, TT:MENU.PAYLOAD.PILOT, 1
station_load.1 = 0, 0.6, 1.1, 0.9, TT:MENU.PAYLOAD.COPILOT, 2
;
station_load.2 = 0, -2.6, -1, 0.9, TT:MENU.PAYLOAD.FRONT_PAX_LEFT, 4
station_load.3 = 0, -2.6, 1, 0.9, TT:MENU.PAYLOAD.FRONT_PAX_RIGHT, 4
station_load.4 = 0, -6.0, -0.6, 1, TT:MENU.PAYLOAD.REAR_PAX_LEFT, 5
station_load.5 = 0, -6.0, 0.6, 1, TT:MENU.PAYLOAD.REAR_PAX_RIGHT, 5
;
station_load.6 = 0, 5.5, 0, 1, TT:MENU.PAYLOAD.FORWARD_BAGGAGE, 6
station_load.7 = 0, -8.4, 0, 1, TT:MENU.PAYLOAD.REAR_BAGGAGE, 6