EGIW with Supercarrier

[Paarthunax]

Something I don't understand with the hornets FM and SC LSO with the context of an EGIW grade. (Ease gun in wire) The hornet behaves VERY strangly once crossing the deck, it seems to porpise up and down, which is not what ground effect is supposed to do, and even if you have the throttle pinned, you will still an an ease gun in wire grade which is very frustrating. I've attached 4 track files, the first 3 are examples of my approaches where if you show the control indicator, you'll see I intentionally never touch the throttle past the deck but I still get an EGIW. The last track, while not a great approach, is the only way I can avoid an EGIW by advancing the throttles before the wheels touch down in the wires which is not something I should have to do to "trick" the LSO.

 

Specs
Windows 10 64bit
AMD Ryzen 7 3700X 8-core
NVIDIA GTX 1050ti
32GB DDR4 RAM

f18 example of strange deck behavior 1.trk f18 example of strange deck behavior 2.trk f18 example of strange deck behavior 3.trk f18 example of strange deck behavior 4 fix.trk

[Solo_Turk]

it might be related to this

[Mistermann]

Known issue for quite some time.  Multiple threads combined over the years...

 

[Fresh]

Try switching off wake turbulence, the "burble" isn't programmed realistically and causes a strange pitch-up...

[Paarthunax]

15 hours ago, Mistermann said:

Known issue for quite some time.  Multiple threads combined over the years...

 

You're absolutely right, but I'm making sure this thread stays alive so they can actually address it instead of ignoring it. Not to throw shade at all, I know there are other problems, I just want this to be acknowledged.

[Paarthunax]

12 hours ago, Fresh said:

Try switching off wake turbulence, the "burble" isn't programmed realistically and causes a strange pitch-up...

Turbulence was set to 0 on all tracks

[draconus]

56 minutes ago, Paarthunax said:

Turbulence was set to 0 on all tracks

He surely meant "wake turbulence" option on Gameplay tab.

[Fresh]

Thanks, yea, I meant wake turbulence, not the weather turbulence.

[Mistermann]

8 hours ago, Paarthunax said:

You're absolutely right, but I'm making sure this thread stays alive so they can actually address it instead of ignoring it. Not to throw shade at all, I know there are other problems, I just want this to be acknowledged.

Bravo!  ... thanks for keeping hope alive .

[Mistermann]

Wags just released a new video showcasing the new plane directors coming in the next patch.  He uses Auto-Throttle for the entire trap.  At 9:54 when he gets the LSO grade what do you think popped up ... yup, EGIW.

The man told us in the video his hand was OFF the throttle and on ATC, so how does the jet not have enough recovery power?  IDK, maybe this is real life behavior?  Maybe someone with real life experience can explain?  

@BIGNEWY or @NineLine is it possible for the team to acknowledge this is a known defect within the DCS ecosystem?  This EGIW concern has been around for years.  Maybe its just too low a priority or too difficult to correct to be worked on or possibly working as intended - and I appreciate those are possibilities, especially after all this time.  Any type of status update ED can provide would be appreciated. 

Thank you.

Edited November 17, 2024 by Mistermann

[Stearmandriver]

On 11/17/2024 at 6:24 AM, Mistermann said:

@BIGNEWY or @NineLine is it possible for the team to acknowledge this is a known defect within the DCS ecosystem?

Guess not.  Oh well.

[Mistermann]

8 hours ago, Stearmandriver said:

Guess not.  Oh well.

Its pretty difficult to remain positive sometimes, Stearmandriver.  A simple acknowledgement.  

I'm sure those guys get inundated with all sorts of @mentions each day, so I'll give them the benefit of the doubt that this particular one fell through the cracks.  Let's try again, shall we?

Adding @Grimes as he's responded to many bug inquiries over the years as well.  @BIGNEWY, @NineLine

[Mistermann]

My wife and I have a saying that feels pretty appropriate for this particular situation ... "No response IS a response".  Usually a two-word response.  Disappointing to say the least, @Stearmandriver, but can't say I'm surprised.  

[Nealius]

8 hours ago, Mistermann said:

My wife and I have a saying that feels pretty appropriate for this particular situation ... "No response IS a response".  Usually a two-word response.  Disappointing to say the least, @Stearmandriver, but can't say I'm surprised.  

A variant of that I like to use is "actions speak louder than words."

[Dangerzone]

Wasn't there supposed to be some sort of official scoreboard coming to DCS's supercarrier for the supercarrier that was going to have a greenie board or similar? 

While the lack of response and acknowledgement on this is blatant, I'm holding on hope that maybe this will get a look-in if/when that board gets closer to completion. 

[norman99]

On 12/16/2024 at 2:08 PM, Dangerzone said:

Wasn't there supposed to be some sort of official scoreboard coming to DCS's supercarrier for the supercarrier that was going to have a greenie board or similar?

Ha, I’d completely forgotten about that, so I just went digging a little…

Almost 3 years ago, in a Feb 22 newsletter:

(https://www.digitalcombatsimulator.com/en/news/newsletters/a0c80064aadb198118ac590f28a21ec7/)

“The work is essentially finished on the Greenie board that is connected to the actual LSO station data, which provides live updates during the mission.

We are currently working on the functionality of crew tablets where you will be able to see mission briefings as well as check and change loadouts. In addition, the briefing officer can control the projected picture that is visible on the main screen and choose what to show on the auxiliary TV screen located above his head.”

[Dangerzone]

6 hours ago, norman99 said:

(https://www.digitalcombatsimulator.com/en/news/newsletters/a0c80064aadb198118ac590f28a21ec7/)

“The work is essentially finished on the Greenie board that is connected to the actual LSO station data, which provides live updates during the mission."

Well - I stand corrected. it looks like this issue isn't going to get a look-in as the board gets closer to completion, as it was "essentially finished" 3 years ago - and this bug hasn't been acknowledged, let alone dealt with since.