Rob

Curious as well. After looking at various Corsair cockpit view videos on youtube today, I don't see any of the large amplitude, undamped yawing oscillations that accompany even tiny control inputs, even when trimmed. Here is a video where you can see the pilots legs through several maneuvers: https://www.youtube.com/shorts/-pBV5GD8flc In the DCS corsair the pilot would be doing so much rudder work they would look like they were running in place in the cockpit. I know such a video doesn't provide quantitative 'proof' by any means, so I'll just file it under 'interesting observations' and leave it at that.

Great guide! But unfortunately it does not align with my several years of real-world experience of virtual flying with DCS naval aviators. I will outline a few of the descrepancies as I have experienced them: Case 1 Marshall Pattern Adherence Adherence to the idealized Marshall pattern geometry of 250kn and 5nm radius shall be strictly enforced. Timing, spacing, safety of flight, and deconfliction are all secondary concerns compared to achieving the idealized pattern geometry. The same with desending from the Marshall to the initial point: strict adherence to idealized geometry over rides all other flight concerns. Time in groove Despite the ambiguities of determining the exact position of 'wings level', time in grove is to be precisely quantified. Anything other than exactly 15.000 seconds in the groove will be harshly considered way too short, or way too long. Paradoxically, the strict quantification of grove timing will be waved when viewing replays or videos of carrier operations. In these situations, all groves are to be judged 'way too long'. A single frame of the video at the initial is all that is needed for this determination. Timestamps of youtube video are not considered precise enough for grove timing purposes, and for this reason a single sight picture late in the base turn is all that is needed to determine that aircraft was way too long in the grove, despite a youtube playback being close to 15-18 seconds long. Spotting the deck/dropping All succesful recoveries are to be considered as 'deck spotting' in which the aviator will be judged to have used the stick to aim for the wires, regardless of the actual flight path. Target Wire Anything other than a 3-wire landing is to be harshly critizied, even if all other landing criteria are satisfied. Comms/Zip Lip Though often briefed as mandatory, zip lip conditions can and will be overridden by any flight member at any time. Valid reasons for breaking zip-lip procedures: Lead deviates more than 0.5 feet from the given Marshall altitude block Lead deviates more than 5 feet horizontally outside of the idealized 5NM Marshall holding pattern Lead's speed deviates more than +/- 0.5 knots from the 250 knot Marshall airspeed Lead applies more than +/- 0.1g during turns to descent from the Marshall pattern Strict adherence to what is not written in CV Natops Often it is what is *not* said in CV Natops that is important, and DCS naval aviators will find many hills to die on in this regard. Topics such as whether an aircraft passes directly over the carrier deck in the Marshall pattern position 1, or flies slightly to the side to be able to spot the deck are not explicitly explained in the CV Natops manuals. However, DCS aviators will chose the one true way, and all other choices are to be considered savagely incorrect. Choose wisely. Anyway, like I said, great guide, and this just scratches the surface of the discrepancies I see in real virtual fleet aviation. Kind regards.

Interested to see these videos if you have the links handy, I did a quick youtube search, and haven't found anything that unambiguously shows altitude, pitch, airspeed, etc.

That loft bombing in the video at 2min 20sec is great.

Please see the attached track. Order of events: 1.) Drop MK82 in CCIP, and show that it creates a target point. 2.) Undesignate to hide the created target point 3.) Fire rockets in CCIP, no target point created 4.) Fire gun in CCIP, no target point created Attached screen shots: shot01.jpg: Target point created after CCIP release of MK82 shot02.jpg: CCIP release of rockets, no target point created shot03.jpg: CCIP fire of guns, no target point created (not sure if working as intended or not, included for completeness) shot04.jpg: Screenshot at 1m48s of VMA-542 video prior to release, CCIP line up before firing rockets, no target point shot05.jpg: Screenshot at 1m50s of VMA-542 video after release of CCIP rockets, target point created Am not sure about the gun and CCIP target point creation, included in the track for completeness. AV8B_Rocket_CCIP_Target_Creation.trk

While I don't agree with with the delivery or tone of the message by the OP, I have a similar sentiment about the stability of the AV8B. In the 10 or more years I've been playing DCS, since purchasing the day-01 release of the Russian-only Ka-50, I've never experienced so many straight crashes in DCS, nor experienced such inconsistent and frustrating behaviour as the AV8B. At the risk of being crass and over-simplifying, I suspect that testers take hot-start jets, "test the $weapon once", and then call it done, and tick off their item in the bug-tracker/JIRA/whatever task managing software platform is used. Meanwhile us as users are flying more complex sorties and dropping a multitude of weapons and exercising the navigation system/EHSD/sensors more, and so experience more problems. Since I don't have a 15-second track or an exact bug report I accept that my comment will be dismissed. I don't care. I just want to express that the sentiment by the OP about the AV8B are felt by many virtual pilots in the community.

Thanks, I did a clean and repair and it no longer happen, I've never had cockpit or similar mods installed, but I should have done the clean/repair before posting. I have another bug posted about cycling waypoints with NSEQ boxed and a TERM waypoint set that continues to crash after cleaning the MOD folder and doing the full clean/repair. Would someone be able to see if they can recreate? Cheers, Rob

Hello, I can reproducibly get DCS to crash when cycling through waypoints in the EHSD, with NSEQ boxed, and a TERMINAL (TERM) waypoint selected. To reproduce: enter DATA mode, box NSEQ, using the Option Display Unit (ODU), press TERM, using the UFC keypad enter 4, Enter. Return to the EHSD by pressing Data, rebox NSEQ, and press the OSB buttons to cycle forwards and backwards through waypoints. Because it crashes, there is no track. Here is a video of a crash. Here is a video. It only takes a few seconds to test yourself and recreate. Attached is the .miz file that I was flying. It contains a single air start AV8B carrying JDAMS with 6 waypoints programmed in the mission editor, and some unarmed transport targets. dcs.log also attached. Once again, there is no track produced by DCS because it crashes, so I cannot add a track because there is no track to add.

Hello, I can reproducibly get DCS to crash while flying the AV8B and pressing the "DESG" button in the EHSD. It's happened on multiple maps, both cold start, hot start, air start. No mods. Because it crashes, there is no track. Here is a video of a crash: It's a hot start aircraft with 5 pre-programmed waypoints. As the EHSD is shown by default, just click the Left OSB 1. Attached is the .miz file from above. A single AV8B on NTTR carrying JDAMs, a bunch of Transports. Also attached is the dcs.log Once again. There is no track produced by DCS because it crashes, so I cannot add a track because there is no track to add. JDAM 02.miz dcs.log

Neither Fravor's aircraft, nor his wingmans were equipped with a pod for the incident. The video was recorded by a follow-up flight.

What sound settings do you have checked and what do you have your sound sliders set to? For example I have "hear like in helmet" checked, and the cockpit and helmet sliders down pretty low, and when I get in the aircraft I turn the AC/Defogger or whatever slider back to reduce the sound a little as well. Play around with these and you might get the sound more to your liking.

He tried, but the flight model was wrong

though USMC and not USN:

To me this seems like building in some deadzone automatically into the Auto Pilot mode in the hornet rather than into the control input curves is one of those seemingly minor changes that have a large quality-of-life improvement to the game. While it may not be the way that the real hornet behaves, the real hornet also isn't being flown with a huge variety of consumer grade joysticks in a variety of different physical setups. There are a lot of similar instances where we have to sacrifice 100% fidelity to allow DCS being a computer game running on a variety of hardware. Trimmer behaviour in helicopters, or the Hornets HMDs transmitting only into a single eye for VR users come to mind for instance as examples.

With a target in STT lock you are unable to silence the radar or enter the SIL sublevel by pressing the SIL OSB. Track file attached. Version: 2.5.6.49314 Cheers, Rob F18 Radar unable to enter SIL from STT May 26 2020.trk