SU 7.1 - 3rd party planes drag values now broken - fighter jet slow acceleration

1 tag is required - add them in the tag section next to the title above:

  • One for platform (ms-store, steam, xbox , or xcloud)

  • One for aircraft if related (start typing in your aircraft name in the tag section and pick correct option)

Feel free to delete this quote section after adding your appropriate tags.

ISSUE DESCRIPTION

Description of the issue:

The drag coefficient values are completely broken for third party aircraft now as of SU beta 7.1 - all of my fighter jets are accelerating very slowly now with full AB and no weapons payload. Even at height, I can barely shoot past mach 1.

FREQUENCY OF ISSUE

How often does this occur for you (Example: Just once, every time on sim load, intermittently)?

All the time, in flight.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Get into any third party fighter jet

  2. Accelerate at full AB

  3. Observe how the thrust now feels like an exec jet or airliner and not a fighter jet.

YOUR SETTINGS

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 User Support Hub.

What peripherals are you using:

[PC Only] Are you using Developer Mode or have you made any changes to it?

[PC Only] What GPU (Graphics Card) do you use?

[PC Only] What other relevant PC specs can you share?

MEDIA

Please add a screenshot or video of the issue occurring.

Took off in my F-14 with 30%fuel and no weapon payload. It took veryyy long to exceed mach 1 and seemed to have lost thrust as if there’s extra drag on the aircraft.

Opted out of 7.1 beta, all is normal, planes accelerating as expected at various altitudes.

Is this a wider problem?

Seems like the drag issue is fixed with 7.1 regarding statements of developers and msfsf

Try it out yourself. Get into a 3rd party fighter jet.

1.5 developers reporting “it seems fine now” for their specific a/c and a cheery “issue fixed” from Asobo (who never even knew they broke it in the first place) is not a verified fix for the whole ecosystem of available a/c.

What we need is

It’s not resolved as of now with third party planes, I can personally vouch for that. In the public build, my 3rdP fighter jets are flying absolutely fine, accelerating as expected and hitting top speeds correctly at various ceilings, but in 7.1 beta they accelerate as if carrying several tonnes of cement blocks no matter what the service ceiling.

I really hope they don’t release this as is, because then we’ll be stuck with these broken drag values, at least on third party jets.

Why not just release SB 8 with no broken values, fully functional external lights on ALL aircraft during the day, and proper runway light visibility in foggy, hazy, and rainy or low contrast, low viz weather conditions during the day??

Probably asking too much, am I?

Have you reported the issue to the developers of your 3rd party aircraft ?
Can you replicate with a 1st party aircraft like the F/A-18 ?

At this point topic is moved to Sim Update 7 Beta | MSFS 2024 > External 3rd Party Products since as per description issue happens with 3rd party aircraft. If you can replicate with a 1st party aircraft, feel free to create a new report in Sim Update 7 Beta | MSFS 2024 > Aircraft & Systems.

No, I haven’t because all is working as expected between SU7 beta and SU7 public. Only beta 7.1 breaks the values.

About the Hornet, let me do some testing and get back to you, mate.

Seriously? I think you should report it to the developers. It’s definitely worth reporting. I’m wondering how we’re supposed to reproduce the issue if, for example, I don’t own any 3rd-party fighter jets.

Who’s ‘we’?

Can you list the a/c which exhibit it, along with the test sequence you are flying to replicate (location, height, weather preset, fuel load etc) and a comparison table of the su 7 vs su 7.1 numbers that show the divergence from the expected.

That would help greatly for anyone to test, replicate, and validate.

I don’t know about that, what are third-party developers to do, or can do, if issues are detected on an ongoing MSFS Beta? :thinking:

If they start fiddling with their aircraft then the Beta may change in the meantime.

Imagine if some third-party developers tried to compensate for the drag bug during the SU7 Beta, some aircraft would be flying fine, others, including first-party, would be bugged. Then the 7.1 drag fix comes and they have to revert their changes.

Hornet feels slow in the public build, not accelerating as expected.

You may not know, but I do. After reporting an issue to the developer or developers of the affected aircraft, they can contact Asobo in several different ways to work towards a solution. For example, they can create a topic on the dedicated developer forum.

I’d like to point out that I never said in this thread that developers need to change any lines of code in their aircraft.

It doesn’t matter if the beta version changes in the meantime. What matters is reporting the issue to Asobo and, if necessary, sending them a PM with data that we don’t have access to, but that third-party developers and Asobo do.

Just a reminder that I never said in this thread that developers need to change any lines of code in their aircraft.

I’d kindly ask you to read my posts more carefully in the future :slight_smile:

I read it.

In it you never specified the objective was to report to Asobo so I assumed it was for a 3rd party fix.

If you report the issue to the third-party developers, they’ll know what to do and where to report it. I’m not going to tell them how to do their job, which is why I didn’t mention those details earlier.

I’ve now explained how this could potentially work, and I hope you have a clearer picture of the process.

I am not a fighter jet specialist but in SU7.1 Beta, F/A-18 acceleration seems ok (at least for take off):

How do you evaluate the acceleration ?

By accelerating at full mil power and then AB, all done at various altitudes to assess top speed and overall consistency. Also, steep climbs after approaching mach 1 and going into a steep dive from a high altitude with full AB. Its definitely slower.

Still a problem after 7.1 Release?

It seems OK now: I just tried the Mach Loop challenge league race:

up to a few hours ago, it was hard to do 2:32, now in a few attempts I just did 2:27…