Deezle

FWIW, you do not have to use surround with DCS (not that it hurts). I would suggest using the single screen profile, not the 3 screen one. Also I think you aspect ratio needs to be 4.8 (1.6x3). And make sure your left most monitor is your main display in windows.

Or you could spend two minutes to edit the default.lua like I've had to do for all the other aircraft to work with my controls. Everyone's setup is different.

This is intended, this makes the switches work for single state switches, such as found on the TM WH, and many custom panels, however they should really include binding options for other inputs, although it's not hard to do yourself. I have custom default LUAs for all the modules to work with the TM WH and my panels, and simply keep them in a JSGME mod, with the Gazelle for once I didn't have to make many custom inputs.

Thanks for the info, I haven't been very happy with my recent driver update.

Before the EDGE engine was released, using HDR with SweetFX made the HUD washed out. However the default HDR setting we have now seems to make no difference, the HUD is simply unreadable against a bright background, for me, on or off.. Other aircraft HUDs are fine, it shouldn't take this long for ED to fix this.

Personally, I like that Starways textures don't have 2d buildings in them, I really don't like textures with that. I think his fields, trees, and mountains are fantastic too, but the generic grass texture around the map looks a little odd, especially if you're a chopper pilot.

Those are massive deadzones.... I was flying with someone online that had this problem a couple times but I can say it has never happened to me in all my many hours. I'm guessing your controls aren't in the correct spot before disengaging..

I wouldn't say that, the C program is like 90% effective against MANPADS and Strelas. I am interested to try those though. ETA: Quick test against an Igla, SA-9 and SA-13, for me the default C program was much more effective than C or D in the modded profiles. It uses a LOT of flares, but using a lot of flares is better than dying.

Here's a quick followup video clearly showing the pass-through problem.

That video is mine. I've since found the laser likes to pass through hill/mountain tops, if what's beyond the hill top is farther than the 15km max laser distance, you will not get any range and it will not slave. I can make another video tonight clearly demonstrating this.

That actually reminds me. I was playing with Sniperbob on 1.5 and I was in an A-10C and he was providing recon in the Gazelle, he attempted to give me target coordinates with his method and they were quite far off. So it looks like there may be something to that method being inaccurate in the Caucasus.

Donated.

Sniperbob spent hours trying to do just that with no luck. This explains the function, but I also struggle to understand of what use it is.

The range finder also currently has trouble with mountain tops, it looks right through them.

Is he looking at the wrong fuel gauge? The gauge at the top of the canopy will only show fuel when nearly full as it's for the auxiliary fuel tank.

I also have the TV exported to a lower monitor but I cannot fire missiles from the pilot seat :huh: The button makes the click sound but nothing happens unless I move to the commander seat.

Add the line I posted above and also confine the center to 1080 instead of screen.height;.

Roie, make sure your monitor config file has this line in it, this will confine the GUI to the main monitor. GUI = { x = 0; y = 0; width = 1920; height = 1080; }

If you're in 2.0 there hasn't been any update since the Gazelle was released.

Only applicable if you have it mapped to a separate joystick/axis, if you're only using a single joystick for both the cyclic and viviane, you won't want it inverted, for obvious reasons. IMO, it's intuitive the way it actually is. In aircraft, pulling back=up.

For most stationary targets I do prefer a JDAM, sometimes not quite accurate enough to kill a tank though, I try to carry one LGB for hitting a moving target which will then get the column to stop. I don't like how limited LGBs are below 6Kish feet, they tend not to find the laser on time and fall short. JDAMs can be fairly quick to employ too, place your HUD TDC on a target, make it your SPI and pickle. I think the G/K model Mavericks are underrated, they pack quite a punch.

Theoretically, once the laser is properly measuring the distance of objects, it should be possible to shoot a helicopter without a launch override, but certainly not ideal.

Yeah I had it freeze on me the other day.

Two separate failures, rotor RPM does not change when this occurs. I can't even seem to get the rotor to overspeed if I put myself in a hover 500m up and slowly lower the collective to zero and freefall, it speeds up a little but not outside of it's normal operating range. Most of the time in normal flight this isn't an issue, however I had spent a lot of time on the 104th earlier this morning, I was in the target area and dodging some enemy fire, I went to hide behind some buildings and accidentally lowered the collective a bit too fast in an attempt to stop and that was it, engine died and I fell to my doom. Frustrating.

Nothing special but I really like this shot.