oldcrusty

Let's run it down top to bottom: The severe crosswind on runways was a rule in our online bunch back in the day. On the boat, the mission makers should follow a formula to point the angled deck very closely aligned with natural headwind corrected for carrier made wind. AOA scan... as long as you pay attention to it in some way. Terminology - feel free to call things whatever you like. VV or FPM, how about this one... the ACLS bullseye is called needles and ICLS needles (that look like needles) are called bullseye. Cool. Also, operating Hornets from land bases could be exciting as well

The borked 'burble' is exactly the same as before and dependent on wake turbulence option turned on. Keep on off until the burble is fixed.

I think this adverse yaw oscillation (in the recent FM update) is caused by aggressive roll input, followed by an attempt to stop the roll with a quick stick movement in the opposite direction, especially with c/l tank or heavier weight. It's not exactly the same as we've seen in early OB builds. I've read or heard somewhere this was a thing in Hornets circa mid 80's. I have no idea what 'proms' or blocks of Hornets and if indeed ED was trying to model it or this is something that needs to be tweaked. Another thing is damping... in later Hornets. I think 'may be' could be a bit better. It would be refreshing to hear some input from someone who flew it at one time or another

This twitchy trim in A/P threw me up and down couple of times as I was transitioning from T/C part of ACLS to P/R. I managed to engage T/C guidance from 80nm out. (ACL1 active, TCN and WPT nav unboxed, ILS boxed by engaging ACL) The only way I could trigger the 'CPL HDG' to intercept the marshal radial was by getting the clearance and calling 'established' . I also threw in 'commencing' just to be funny. It worked. The data started loading and was showing me a commanded a/s 250, descent rate 4000f/m, down to platform since I was commenced already. Well, I managed my altitudes, a/s and descend and arrived at 6000ft leveled off and by the time I passed my marshal point I was told to switch to approach and when I descended through platform I got another data update, cool. Since I disregarded the push time, I didn't have to uncouple the T/C steering for orbiting in marshal pattern and it stayed engaged continuously and flew along the marshal radial which in DCS is always colocated with FB. Everything looked good until the dreaded transition to approach mode. The procedure was to press CPL twice. First press cancels T/C, second engages P/R once available. Auto throttle also had to drop off before switching to PA mode. So... after gear down and flaps at 180kts, as soon as I touched the trim... it went wild. I managed to regain control and coupled the P/R. After this ATC was actually holding AOA quite good even before tipover, which was a surprise. So... it looks like some elements, bits and pieces are there. Someone needs to glue them together tho'

It startled the heck out of me when I saw it the first time, in my peripheral vision. I there is no plan to fix it, can we at least have an option to disable this part of scenery?

'Growler Jams' posted one of the best refueling vids we can find on YT. Plugging into KC135mprs (if I remember correctly) in turbulent air. He also explains the entire process.

Here's my re-learning progress. Slowly getting there but it's not pretty yet For those who like to gas up from S3's, I'm sure you already figured out you need to stay positioned a little higher then before 2.9.3 (actually since a few patches ago). I could wobble all over the place and stay connected as long as I didn't drag the basket down too far. My PIO's were spectacular behind an S3 (at light weight at 1500 ft.)

Speaking of tracks. I'm slowly changing my opinion on accuracy of track replays. Since the recent updates I haven't noticed any discrepancies in my replays, including some crazy missions with lots of maneuvering... well, I'm talking single player here. I'm aware of some complaints in MP sessions. As long as I don't get too carried away with changing the replay speed.

@rfxcaseyI was referring to your post in a different thread. For some reason I thought you started a separate thread...

, I threw the NATOPS in the trashcan like we know who... First, the only time I use a paddle is to kill the A/P. Second, I actually failed to induce oscillations that both darkman222 and I remember from olden days... they were severe and would continue forever. This would only occur in a clean jet with low fuel. In my short and wild flight I was actually quite happy with the results. Oh, occasional over g can definitely happen... w/o a paddle.

Similar problem occurs when entering PA mode with A/P still on. The A/P will disengage but the trim will be messed up unless we cycle to UA then back to powered approach mode. I was already on speed before coupling to ACLS , level at 1200. The ACLS lowered my AOA to maintain 1200 ft. above the water at 151 kts. Great, then I accidentally bumped the trim and the ACLS immediately decoupled. The trim function was extremely sensitive afterwards so I reengaged ACLS and let the ATC maintain the AOA. Yesterday, someone started a thread on this subject but I don't see it today so...

Well, with 2000 lbs of fuel, yanking and banking... can't do it for too long but during this hop I've only seen one instance of yaw oscillations when rolling and pulling on the stick. I can't really say what I did differently before this particular roll. I tried to unload before every violent maneuver. Overall it wasn't bad at all. The roll-outs were quite crisp and stable. Short clip from this test:

OK, my final take on this... flying the ball with 43,000 lbs all the way to 3 wire, I would definitely expect some sort of 'stress' on certain parts of the airframe. I simply wanted to see for myself whether reports of 'within weight limits and 700/800 f/min descent produced bent landing gear, that's all.

No obvious and visible damage as seen in some pics and vids (bent gear) Sure, I can hear the beeping and I noticed missing left main 'green' so yeah, it's going below the deck for a while.

I just tried it at various weights and I can't see it anymore. Even when pulling some g's before violent rolls. It would simply cause 'loaded rolls'. There is a very small FPM wobble (one or two) before it dies out. Give me your exact weight/loadout, altitudes and whatever might make a difference. Edit: I'll give it couple more tries. 2k lbs fuel, clean (no pylons)

There was/is an issue with configuring to landing mode without disengaging the A/P beforehand. The trim would start acting wild. I'm not sure if this is what's causing your trim problems.

I think current modelling is in the ball park... more or less My final test: 43,500'ish lbs on the runway landing the AF way then on the boat... well, I got some fault codes on this one but no visible damage. https://youtu.be/11CdUppYeX0?si=6ue8dcSGI1RalU0n

Hmm, I'll do some tests later on with different weights and loads. The problem you're describing was 'sort of' fixed years ago. The exaggerated wobble was always there even after the fix but the oscillations would eventually die out This was especially evident at very low weights.

Not like it was way back. Currently I only notice a wobble if I start rolling without unloading. I think Hornet dampens the inertia a bit better then again I've never flown a real one.

Not even a twitch in my test

By simply switching back to IP or any wpt before IP. The preset IP-to-TGT is still there, just being ignored when TGT is selected. Why would I need that... heck if I know Say I'm following a wpt sequence then I find out I can't follow that route toward my IP anymore but I still need to be on the TGT on time specified in the brief running in direct TGT. Yeah, I can go to DATA page and wipe out the ground speed and it's all good. Not really an issue...

Yes, some dark corners in my cranium are getting refreshed once I started flying more complex missions again. However (here we go again ) if I designed ths system myself, selecting a target wpt at any time during the mission would disregard preset ground speed and show required ground speed to get there... just getting nitpicky.

Disregard. I must've goofed somewhere along the way. I gave it a few more tries and every time I hit the target on time (within 3 or 4 sec ). I guess the key is having any waypoints selected before IP or the IP itself. The MC will guide correctly. From the IP the preset ground speed will drive the caret on HUD. If you select the target as your waypoint at any time before hitting IP, the caret will chase your preset ground speed for the attack run-in. Weird but as long it works in one way or another.

The question is: Will it be implemented/fixed/improved or I skipped some set up in ME? In my recent ground attack mission I set the TOT but the only help from A/C's mission computer was keeping me on preset ground speed regardless of my position, before initial or past, before target or past... On following flight I kicked in the blowers right after T/O and got to initial 5 min early, slowed down to preset ground speed, speed caret moved to center and I arrived at the target 5 min. too early with the caret glued to center... even past the target.