Kingsly

I have one of those inline usb power monitors - AND a bricked throttle! just discovered this thread and am eager to see if it works. My symptoms were that one day a few months ago the throttle just wouldn’t show up. The back lights illuminate when plugged in, but windows shows “a problem with this USB device”

Literally came to this sub to start a thread on this. Really disheartening to see it’s been on the wishlist this long. Everyone here has already gone into all the detail I wanted re: real life responsibilities, kids, work vs. desire to engage in longer more realistic missions, so just let me just add a humble “+1” Please ED. Save progress is kind of more important than, dare I say it, clouds.

I’ve only been used to the old one for about a week and it’s still a PITA...

Yeah, I can’t stand the training mission for that reason - stationary carrier makes no sense. I was reasonably confident in my Case I and III recoveries, but a two month hiatus to move into a house & work through a 2020-induced existential crisis will leave those skills badly bruised haha. All I can say to anyone else reading this is practice practice practice. Way back when I first discovered DCS I made it a point to end every session - regardless of module - with a few F/A-18 circuits around the boat followed by a hook down recovery. As this thread has made perfectly clear there is a lot of geometry going on, and thoughtful repetition through every stage will be the glue that slowly binds it all together.

Came here to post this bug too. Can confirm it is not fixed in the latest OB.

It’s not just this mission - every one I’ve tried including the new campaign if one doesn’t order wheel chocks removed before engine startup the chief ain’t going anywhere near the aircraft. Possible because the nozzles are dangerously close to personnel? Or just a bug. Either way, I’ve had to restart so many missions because I forgot to issue the dang order and it can get really frustrating.

Setting the altitude warning to 360 is a great idea! Noticed its seems setup that way in the posted video. I agree with all these tips - just another tool in the toolbox. If at the end of the day the plane comes to a complete stop, its a good day.

Yeah, needles are helping a ton to practice being on glide slope at the 90 - or at least knowing what is amiss and having a precious few extra seconds to correct before leveling out on final. Lots of hook-up touch and go’s today. LSO bot hates me

Thanks for the input! Good call on using needles and course line to find the 90 without scanning for the boat. Probably going to do nothing but carrier quals over the next few DCS sessions. (Side note- really excited for the Goosehawk!) I still need to wrap my mind around this turn to final. I always seem to roll out pretty far to the left and Clara at >1mi from the stern. Frustrated, I shallow my turn and come out so far to the right that the brass boots me to the Air Force... Haha. Re: your comment - is one not necessarily supposed to roll out at 3/4 of a mile? Is being a little long in the groove acceptable? Finally, for anyone else reading this and trying to figure out carrier landings - don’t be afraid of huge throttle inputs. Going to that awesome phantom side note above that left hand should be constantly moving and dramatically at that. I was manipulating the throttle gingerly like AAR and remembering that tip alone solved half my issues.

Word to the wise: Carrier landings are NOT like riding a bike. Definitely a perishable skill. After about a dozen WO’s I realize there is something I am definitely not remembering right. The diagrams/manuals all seem kind of vague on this - more or less roll into the groove at ~350’, 3/4 mi and follow the ball down. Well and good, but what are y’all up to between the round down and rolling level? I seem to be chasing after that 350 and end up with too much altitude at the rollout. Also worth noting - I cannot see the LSO station in VR, mostly just start my turn abeam the fantail. Pro tips there? That final 180º turn confounds me every time - even back when I was reliably catching wires!

Ran into this tonight while trying to qual myself on mavs. Did eventually discover like others that flying *straight* at the target before uncaging the seeker works 80% of the time (the other 20% could easily have just been me becoming task saturated and doing something else wrong :/) HOWEVER: I also discovered that a lot of times the tpod would clearly have a solid, zoomed in ptrk on a target right there in the DDI and yet my TGT diamond would be drawn in the hud a few hundred yards away. Of course, the TGT point was where the mavs wanted to look, not where the actual camera was placed....

I literally went to bed last night thinking I should post this. +1 A 90 and 180 would be amazing too. Out of the entire pattern that turn onto final is the part I can’t seem to master. Honestly I’ve had better consistency finding the groove flying SH approaches! :megalol:

Nice work! Congrats. My first module was the Su-33 and the feeling of elation trapping the first try was hard to compare. Definitely a case of beginners luck! :P Moving to the F/A-18 I made it a point that every time I played DCS, no matter what module or mission I was on, I had to attempt at least one carrier landing practice mission before I could quit. Most days I'd do a handful of touch-and-go's with the hook up, just to build the muscle memory of rolling into the groove and flying the ball down - then end my session with a trap. The practice very quickly paid off. :) Keep it up!

No time in huey’s but lots in Robinson’s and other types. The FM feels like a rl teetering blade helicopter to me! I agree there’s a little fore/aft oscillation. It’s really obvious if you speed up time whilst holding the stick perfectly still.

At very least, widen the invisible “bounding box” that the cursor seems to reside in. I point my head at, say, the right MFD, then hold perfectly still while positioning the mouse over whatever I want to click. It’s infuriating and takes way too long in the heat of a fight. Any head movement at all overrides the cursor position. I am actually a proponent of the cursor tracking with head movement, in that wherever you look the mouse should be readily available in front of you and not wherever you last left it, but it should be free to to move within the headset FOV.