Brun

For starters, open the control options and confirm that nothing else is bound to the pitch axis. Be aware that you may need to scroll horizontally to see all devices.

Never noticed it but mine's the same. Don't think it's anything to be concerned about.

Sounds very similar to this... https://forums.eagle.ru/showthread.php?t=281467

Hard to describe any particular trick, but I definitely needed a lot of patience. Pretty sure tweezers were involved as well.

As far as I'm aware those aren't physical switches. They just show as 'on' when the throttle axes are at their minimum. I'm wondering if the axes aren't calibrated properly for some reason. Try downloading DIView from here and checking what values you get from each axis.

Looks pretty standard to me. You can see they're still rendering at a lower resolution.

https://www.airforce-technology.com/projects/tu95bear/ Infrared sensors of the Mak-UT IR sensor missile approach warning system are installed under the nose sections and on the top surface of the fuselage above the wings.

It's not a DCS thing, it's a physics thing. If you're ahead of something that's travelling in excess of Mach 1, you won't be able to hear it.

How fast are you going when this bug occurs?

It's my understanding that the carrier's speed will account for the headwind to maintain a consitent wind over deck. Faster wind = slower boat.

Why not just upload them? Use the 'manage attachments' button below the reply box.

The label isn't wrong. All the 'CB' actions are for the circuit breakers.

It's not necessary to make TARGET recognise DCS. You should just be able to open TARGET, load and run the profile and then run DCS. Assuming this is the 'Fly now' stuff you're trying to get working, it's nothing more than a convenience. This sounds correct to me. When using TARGET, the stick and throttle are combined into the Thrustmaster Virtual Controller. I'd suggest ignoring DCS for the time being and using the windows game controllers panel to confirm things are working as intended. Any buttons assigned to the keyboard you should be able to check in notepad or similar.

The blinking B indicates that the displayed altitude is barometric even though the switch on the HUD panel is set to radar.

If it works in windows there's no reason it shouldn't be assignable in DCS. Just double-click the assignment (in the Cougar column obviously) and then press the trigger.

This shouldn't be necessary. I can load a cold-start mission with both throttles in the off position. Startup and subsequent operation is absolutely fine.

Simple copy and paste from wikipedia: Maximum speed: 1,034 kn (1,190 mph, 1,915 km/h) at 40,000 ft (12,000 m) I reckon you're underestimating the effects of altitude and air density. Edit: The number you're looking at in the HUD is indicated airspeed or IAS. That's not primarily an indicator of how fast the aircraft is going, but more relevant to how it will manoeuvre in the current air density. Set one of the DDIs to the HSI and you'll see two speeds indicated in the centre, on the left (true airspeed or TAS) *is* how fast you're going. Fly at different altitudes and note the difference between IAS and TAS. The higher you are the faster you're going, even though that's not what it appears to say on the HUD.

That makes sense, thanks. Agreed that a target of 450-500 would make it perfectly clear. One other minor thing I'd noticed. It's possible to cheat a little by timing the final turn based on the appearance of the abeam score. I recently realised I'd started doing this subconsciously. Maybe that could be prevented by delaying it a few seconds?

I'm not familiar with Catia - or any CAD software - but there's no other format that would make it more editable than OBJ.

I was just about to post this. I got 5/7 at 448'. Either the target's wrong or the text is, feels more like 480 but it's hard to be sure. Minor issues aside, it's very useful and much appreciated.

How are you activating the switch? I'm wondering if it stays open if bound to a button which is held on, like the warthog throttle's switches.

Isn't that what the horizontal position of the velocity vector represents?

See my sig. Gimbals are U2 NXT, but that makes no difference.

You need to apply forward stick *much* sooner. You appear to know the nose will rise, but don't do anything about it until the velocity vector has climbed to almost 5 deg on the pitch ladder. You'll definitely need some forward pressure to maintain level flight when setting flaps to full, but it's not all that much if done correctly. Edit: Here's a video. Gear down at 270kt, flaps full at 250... Sorry it's a bit wonky, that's cos I recorded the track in VR before capturing a replay.

As far as software's concerned there's no difference between this stick, the standard Warthog's or the Cougar's.