Jump to content

Wing Fold Handle Jumps To Spread On Carrier Cold Start

Recommended Posts

This a variation on the above report, not the same issue described. 

When doing a cold start on a carrier in the Hornet, the wing fold handle is set to fold at load in and then jumps immediately to spread.  It doesn't seem to matter if it is the default carrier or the super carrier.  I have also seen this in both the Persian Gulf Map and Syria map.  Track file is attached.


The consequence is that when multiple jets starting up on the carrier, aircraft get damaged when the wings are unwittingly spread while in parking positions.  


The work around is to verify your wing fold handle is the correct position before startup.


Link to post
Share on other sites



I have not been able to reproduce this. 


Is your fold wing mapped to a button or switch, and are you using synchronise controls in the settings?


Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 10 Pro x64, NVIDIA MSI RTX 2080Ti VENTUS GP, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 32GB DDR @3000, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to post
Share on other sites

I have wing fold CW and CCW mapped on an otherwise unused rocker switch on a Thrustmaster MFD.  No switches that hold position.  And it's an instant jump from fold to spread.  Nothing is mapped to those actions.


I have Synchronize controls set.


I did notice that the only time this seems to happen is the first load into the cockpit.



Link to post
Share on other sites

Ok. But did you try? Did you try unassigning the buttons to see if that made any difference?


Win10 64, Asus Maximus VIII Formula, i5 6600K, Geforce 980 GTX Ti, 32 GB Ram, Samsung EVO SSD.

Link to post
Share on other sites
9 hours ago, WOPR said:

That part is ED's job.  They have the track file and can step through the code.

If you're really interested in finding the source of your problem as soon as possible just try to help the developers by deactivating the sync option or temporarely unassign the both buttons and report your conclusion.

Edited by AstonMartinDBS

[Modules] A-10C, A-10C II, F-14A/B, F-16C, F/A-18C, FC3, Ka-50, UH-1H, CA, SC

[Maps] PG, NTTR, Normandy, Syria

[PC] Z270F, i7-7700K, 64 GB DDR4-2666, RTX 2080 SUPER 8 GB GDDR6, SSD 970 EVO Plus 1 TB (M.2), 2 x SSD 850 EVO 500 GB (SATA3), 2 TB HDD, TM HOTAS Warthog (Grip@WarBRD Base), MS SW FFB2, Thrustmaster TFRP, TrackIR 5 & TrackClip Pro

[Checklists] A-10C, F-16C, F/A-18C, Ka-50, UH-1H

Link to post
Share on other sites

I can't reproduce this either, even using the exact same mission from the track. Your 'essential information' shows it happening, but if nobody on the team can replicate it on their own machines, then the problem is isolated to the machine the issue is present on.


What kind of peripherals do you use?
Have you tried running a repair?

Edited by Tholozor

REAPER 51 | Tholozor

VFA-136 (c.2007): https://www.digitalcombatsimulator.com/en/files/3305981/

Arleigh Burke Destroyer Pack (2020): https://www.digitalcombatsimulator.com/en/files/3313752/

Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Create New...