reported earlier F14A Incorrect Catapult Director Gestures

[HeavyGun1450]

Attached is two trackfiles showing a issue involving the Catapult Directors on the SC giving the F14A only, the wrong Gestures to hook up to the cat. The F14B does not have this issue and shows the correct Gestures to get hooked up to the cat. In the F14A, Cat Director will first not tell you to unfold/unsweep your wings, while in the F14B the director does direct you to unfold/unsweep your wings. Second, Just before salute/launch, in the F14A the director will tell you to extend your nose struct, which you obviously do not do in the F14, only the hornet. Obviously the gestures of the Director for the F14A should exactly match those of the F14B. Thanks you hope to see this reported and fixed in the future.

F14B Correct Gestures.trk F14A Incorrect Gestures.trk

[AKULA_OPTIMUS]

Yep, that happens with the A version.

[joey45]

In the GroundCrew.lua file there is a different arg number for the A and B.. 

 

    ['F-14B']   = 
    {
        wing_unfold_condition = {arg = 404,   value = 0.1, condition = '<'},
        raise_launch_bar_needed = false,
    },
    ['F-14A']   = 
    {
        wing_unfold_condition = {arg = 7,     value = 0.1, condition = '<'},
        raise_launch_bar_needed = false,

 

Edited July 17, 2022 by joey45

[near_blind]

bare in mind that lua is completely missing the configuration for the player F-14A. F-14A is unit name for old AI unit. F-14A-135-GR is the HB unit. A bit of a lingering whoopsie on ED's part. 

[HeavyGun1450]

1 hour ago, near_blind said:

bare in mind that lua is completely missing the configuration for the player F-14A. F-14A is unit name for old AI unit. F-14A-135-GR is the HB unit. A bit of a lingering whoopsie on ED's part. 

Has this bug been reported then?

[Flappie]

I checked: these issues were reported earlier, yes.

[Nealius]

On 7/18/2022 at 1:55 AM, joey45 said:

In the GroundCrew.lua file there is a different arg number for the A and B.. 

 

    ['F-14B']   = 
    {
        wing_unfold_condition = {arg = 404,   value = 0.1, condition = '<'},
        raise_launch_bar_needed = false,
    },
    ['F-14A']   = 
    {
        wing_unfold_condition = {arg = 7,     value = 0.1, condition = '<'},
        raise_launch_bar_needed = false,

 

 

Lua fix does not function on my end. Probably due to the missing -135-GR entry that near_blind mentioned.

Edited July 21, 2022 by Nealius

[SignorMagnifico]

Bump. Still having this issue in the current DCS 2.7.17.29140 Open Beta. I'm completely unable to launch from the supercarrier in the F-14A at night. During the day, I can launch. In both cases, the flight director gives the wrong instructions, and it's almost like I'm recognized as an F-18 instead of an F-14. I also noticed that the F-14A spawns on the carrier with the nosewheel in the kneeled position. Not sure if that is also causing the issue. Track files attached.

 

https://www.dropbox.com/s/748bvwrdkos4yif/F14SCBug.rar?dl=0

[Lt_Jaeger]

At night you have to turn on exterior lights to signal the "salute", which makes sense and adheres to real life procedures. 

[SignorMagnifico]

3 minutes ago, Lt_Jaeger said:

At night you have to turn on exterior lights to signal the "salute", which makes sense and adheres to real life procedures. 

Thanks! This worked. I can launch at night by cycling the light switch. The flight director directions are still wrong, though.

[Lt_Jaeger]

44 minutes ago, SignorMagnifico said:

The flight director directions are still wrong, though.

Yeap, known bug like forever 

[HeavyGun1450]

Any timelines from the ED team when this will be addressed? It's been a bug for so long now