TimRobertsen

If I haven't missunderstood you completly I usually go for a fuelflow of about 30-35 to push the Hornet into the "hook-up" with the shuttle; once it's looked, I go back to idle. This might be contrary to what is most oftenly referered to: engine-percentage. I've found that fuelflow gives a bit more nuanced power-level-reading, atleast for operation at sea-level/close to sea-level. (Im probably not alone in this )

Verifying game files worked! Problem sovled Thanks for all the help!

I'll try that Jupp, I followed the instructions. The program recognized the different modules and tech, but wouldn't allow repair and update. Does DCS and DCS beta have different folders?

Did not work Did not work After setting it up, for some reason, I can't click the "Repair"-button. Launch, VR On, VR Off, Ded Server Mode, Modelviewer and Clean are available, but not "Update" and "Repair"

Hmm, i probably did something wrong I got this: I haven't found a way to just open Command Window.

I tried this one: But, it didn't work. I got this message: Could it be that Im running it through Steam?

Hmm I can't seem to find the shortcut, anywhere

This could be a stupid question, but what is repair? And how do I do it?

There is a way (although, I think it might be a bug, it doesn’t seem to be a feature on real Hornets) I don’t know if people do it this way, but I’ve never seen it mentioned anywhere. I “found” it when I was trying to find a way to avoid the ballooning-effect caused by the flaps deploying. It bypasses the entire process of “working down” the airspeed to on-speed-AoA With flaps in Auto, gear extended, throttle in idle and airspeed decreasing: when the velocity vector passes through the ideal AoA on the E-bracket, set flaps to half and then quickly tap nose-up-trim. This will lock the trim to AoA the aircraft had at the moment you tapped the nose-up-trim. After the tap you simply let go of the stick and let the Hornet glide into on-speed-AoA; or, if you're in a hurry (SHB) you can keep pulling pitch until you get closer to the on-speed-AoA/stall-speed, at which point you have to add some throttle or transition to throttle-for-pitch This can be done during turns, level flight, ascending, descending; and with pitch-input from the stick: in cases where you missed the mark and have to “force” the aircraft to the ideal AoA for the tap. This will of course mean that the flaps are extended at a lower airspeed than your typical 250kts, unless you’re pulling G’s/are in a high AoA-state (SHB for example).

After the 2.7 update the overlay stopped showing up. I've tried unchecking and checking the box in options, but it's gone. In the posts I've read it seems that it shows up sporadicly, regardless of whether the options-box is checked, but for me it simply doesn't show up. Does anyone know if there is a workaround/what might be causing this?

Jupp, spool-time and turbulence is what can throw an approach off. Especially if the Hornet is light weight; strong wind and turbulence can quickly turn a good groove in to a wave-off

Unless one is constantly making pitch-trim changes (which is not necessary once AoA is "locked in"), thinking about/or considering AoA and airspeed during an approach is really not necessary. The only real issue is throttle-overcorrection: if you get into a feedback-loop where you have to correct your last correction. But with some practice this isn't much of an issue either As far as becoming unstable, I dont know man, the Hornet is pretty damn stable Once it is configured for landing (flaps and AoA "locked in") you have to work really really hard, with deliberate intent, to crash it

Im no expert, but that seems odd, considering that the LSO-screen has a bunch of information: Hook-to-eye, Hook-to-ramp, Hook Touchdown, Basic Angle, all of which are lateral information, for the setup of the PLAT-camera's angle/glideslope. Or am I completely off here? Additionally, the PLAT-camera seems to be gyro-stabilized (Im not sure if that is the case IRL), wouldn't that make it the most precise instrument for estimating if an aircraft is on-glideslope? The Ball is fixed, as far as I know, so waves would throw it off. If B/A isn't glideslope, then what is it? If B/A is the angle between waterline and crosshair-center, then it seems pretty glideslopy to me To me it seems that if the pilots head is in dead center of the PLAT-crosshair when the hook hits the deck, you catch a good 3rd wire everytime (from my obervation atleast).

After about a month off, Im back doing some carrierlandings According to the DCS Supercarrier Guide, the LSO Main Screen crosshair aims for a 3-degree glideslope, but on the LSO Main Screen it says that B/A is 3,5 degree. All the while the Ball is set for a 3,5-degree glideslope. There is clearly a mismatch here, if you fly the Ball spot-on you’ll be a slightly above the LSO Crosshair. Does anyone know the reason for the discrepancy/deviation?

To me, and Im no expert, the wake seems to radially propagate a bit too quickly from an aircraft, especially in close. After I started flying with wake, my formation-flying changed a lot. There isn't much of those 3-feet-of-seperation-flying and following on-tail. Low and off to the side is more the norm; a little bit boring, but it works

It depends whether or not you use ground power during startup. With ground power on, and GP switch 2 in B and GP switch 4 in A, the radio is powered. If you dont use GP, then the radio turns on when the right engine is running. (you probably get power to the radio with just the left engine on, I havent tried, as you usually start the right engine first) As to how it is powered, Im not sure. I think it runs straight of the generators (when it is not ground-powered). As far as I know, there is no on-button for the radio, could be wrong on that

I just had to test it out The "Heavy" at 40k ft is greyed out because the Hornet really didn't want to fly with that weight at that altitude So, those numbers aren't worth looking too much at

Not as far as I know. If my memory isn't too off (which it usually is:p) the was only on some of the earlier blocks. It seems smart to have it, but I guess they, for some reason, found it to not be usefull:p I have no idea where I read about this. I have a feeling it was in the Natops, but I haven't got a clue as to which section. I think I just stumbled upon it while I was reading about/looking for something else (which is typically how I find out about most stuff)

Well, actually, if I'm not too wrong, on some of the blocks, the hook was illuminated. So the boat would actually see if the hook was down or not I meant no offense/denigration with my comment, consider it a sunday-idle-response

Im still waiting for the soundtravel of the afterburner turning off (and the aerodynamic stress-sounds of the aircraft) to not travel instantaneously, but rather at the speed of sound I know it's minor stuff, but it sticks out a little when making videos of flybys, and similar stuff

Hmm, sounds like something is buggy with the controls, maybe an axis is interfering. Have you tried applying parkbrake? It should give you max brake-input regardless of control-setup. Have the input-indicator on ("Enter", I believe), apply full wheelbrake (with button/axis) and see if you brake-indication matches your parkbrake-indication. I've found that sometimes, after updates, there's something wierd about the wheelbrakes if I it mapped to a button: they are stuck mid-position. I have usually found this out when I've started a mission mid-air, and then done a carrierlanding: the plane does a wheelie after it comes to a stop and is pulled back by the arresting wire.

They do Regardless of Case I, II or III. As long as the switch is in Carrier. They are repeater-lights, so they simply repeat the cockpit-indicator.

Found the problem. The Firmware of the Virpil MT-50CM3-throttle was not updated. After the update, everything worked as it should.

Discussions are fun and, it's friday

The AI has rear-wheel-drive, and uses a beryllium core quantum flux drive to change the aircrafts speed and direction