Brun

Something else also mapped to the roll axis?

Think that's called Early Access.

Also note idle RPM is different between airborne and on the ground. The actual Hornet's throttles have a physical lock which prevents them being reduced to ground idle while in flight.

Your opinion is not going to change what is already realistic functionality. If you want the speedbrake to behave differently, you'll have to figure out how to do it with your joystick's software or a third-party alternative. What you need is when pressing the 'retract' button for longer than a quick tap (0.2 seconds?), releasing it sends a brief 'extend' command. That should stop the retraction and hold it in position. Am sure it could be scripted with Thrustmaster's TARGET for example.

It's definitely short-sightedness, my near vision is still good as close as 10cm. In the last couple of years I've noticed it's getting worse though, especially when corrected. Might soon be in the strange situation where I need reading glasses to hand when wearing contacts.

Might be the case for you, but I'm short-sighted enough to lose focus on anything beyond about 30cm. Can't use a phone or read text off a page without holding it far closer than normal, absolutely no way I can see a keyboard or monitor properly.

You'd simply be replacing your glasses with the VR lenses. If you're considerably short-sighted, every time you lifted the headset to see the outside world (e.g. your monitor), you'd need to put your glasses back on. You certainly wouldn't be able to use VR while wearing contacts, it'd be the same as wearing contacts and glasses simultaneously.

He often mentions the 'A model' (for example when turning on the DDIs) so he flew an older one.

Can't see how the tmc is to blame for that, the mapping for slew depress is 'SC' and it doesn't even appear to be there. Presumably it functions normally when not running a script? Slew depress and coolie hat L should be DX1 and DX6 respectively.

Should be noted that a typo in the lua has been fixed, and instances of CPT_LIGTHS have been corrected to CPT_LIGHTS Kinda critical for anyone trying to copy and paste.

Agree with the above. That could be doing more harm than good. A better solution would be buying a couple of case fans for the top and installing them so they push air out. As for the G2's power, I just pull the power lead from the break-out box when it's not in use. Not for the sake of screen-burn (it powers off automatically to prevent that) but I just get annoyed at a) MRP opening all the time, and b) the audio switching to the headset. The latter is really annoying because you can't prevent it without disabling the headset audio completely.

In case you haven't found this already, you can disable the auto switching in the MRP settings...

I didn't know the T-50CM2 could fool Target into thinking it was a Warthog until after I bought it. Was a great relief to find out it did, been working flawlessly with the Hornet stick. Calibration will account for any centering issues. Mine leans back quite significantly by virtue of a curved extension and the base not even being horizontal, but is fine when calibrated.

7.4 to 8.8 degrees.

The importance of AOA with regards to *carrier-based aircraft* is to maximise the chances of the arresting gear working as intended. That's the special case. I'm no aviator, but does the following hold true? Naval: Glideslope > AOA > Airspeed AF/CA/GA: Glideslope > Airspeed > AOA Or in other words, a naval aircraft's approach speed will vary by virtue of AOA being the primary concern. In the other cases, AOA will vary depending on target airspeed.

Only had chance for a couple of quick flights last night. Low level is incredible now, flying round the corner of a valley and straight into a bank of cloud, sh!t!

Fly the Tomcat for a few hours and then tell us the Hornet's HUD isn't smooth

https://www.turbosquid.com/FullPreview/Index.cfm/ID/1659994 No idea whether it's accurate.

I guess the problem is seeing it bumped creates an expectation of progress pictures. Locked to everyone but Dash may have made more sense.

At least one noticeable difference from DCS: After the holdback bar is installed, the aircraft is taxied forward until the launch bar is *on top* of the shuttle. Then once it's been armed, taxied forward again so the launch bar can be engaged. Is the position in 3A to prevent FOD?

My bad. Turns out the target I was destroying wasn't the intended ZSU. This mission really doesn't like me though. On two consecutive attempts Dutch took me out with an AIM-9 up the tailpipe while engaging the helos. Seems a better tactic is to provide top cover and let him deal with them.

I've twice got stuck at the same place on mission nine. Took out the two ZSUs successfully (from the south as instructed) and got some dialogue along the lines of "Holy shit did you see that", and "Affirm, one hundred over one hundred". Then nothing. Loitered for ten minutes and even tried dropping a GBU on the seven storey building in case Venom had nodded off. Still nothing. Any ideas?

What's causing the deflection of the rudders in that photo? Seems very coordinated, but obviously not NWS.

In terms of focus there's no near or far in VR, the lenses typically focus the screens at about 1-1.2m (3-4ft ish) so whatever works for your vision at that distance will work fine. Prescription lenses aren't necessary if your frames are a reasonably normal size, I've previously used Vives (original and pro) and am now on a Reverb G2 which have all accommodated my glasses perfectly well. I personally wouldn't fancy dealing with the inconvenience of having to put my glasses on every time i needed to look outside the headset.

The master arm switch has a special for joystick binding. How is yours set up?