Sephyrius

I think at one point I managed to break the harrier just by pulling up while at the same time jettisoning my ordnance (AWACS just told me I merged with an enemy and I didnt want to jettison into a dive for fear of hitting my own bombs) with the subsequent G loads breaking my airframe, sadly I cant confirm since external views were disabled and didnt have time to look outside before slamming into the ground.

Think of the water as a temporary "boost" to your engine. If you're at or close to (or over ;)) the weight restrictions of what you're doing, you'll want to use it to get that extra oomph. If you don't need it, well, then you don't need it. Personally if I don't need it I enable it and then keep the throttle below the point where it kicks in (a "W" lights up on the HUD and front-right panel when it's active) because it's good to have it ready if anything goes wrong. As for flaps, VTOL is for those kind of landings, but not all takeoffs/landings. If I want to do a runway takeoff at a higher speed I'll keep it at auto for 25' flaps but still use 40-60' nozzles to lift off without the (at that speed) unnecessary drag of VTOL flaps. Same for landing, sometimes if you're doing a landing at a higher speed you'll get surprised by the VTOL flaps that kick in when you drop to a certain airspeed (and look quite silly as your aircraft starts gaining altitude rapidly), so you don't always want them. But yes, for VTOL or most STOL you want them. Auto modulates the flap positioning depending on airspeed - and I suspect stick input and attitude as well - so it's good at giving you a helping hand at lower airspeeds or sharp maneuvers. Cruise is pretty much for that, level flight at higher speeds , and will give you fewer surprises since it wont affect your flying or trimming by introducing flaps at any point. As for the 62' angle, when VTOL mode is enabled and VTOL flaps are on, you will see a flap angle indicator on the bottom-right of the HUD indicating the flap position which varies depending on your nozzle angle. Things get really awkward if you forgot to check that it correctly goes into VTOL flaps and instead try to take off from a carrier with only 25' flaps for a quick swim.

If you press the 'missile launch button' while sitting in the pilot seat the sound and animation plays but nothing happens. Switch to the co-pilot seat and do the same, and the missile launches just fine.

I'll try to elaborate. Running a Sidewinder FFB2 with a ~10cm extension, and have already made use of deadzones and 70% saturation in the past (sadly any such changes break the FFB for the trim which helps a fair bit though it's not the end of the world since it does aircraft attitude trimming instead of stick trim). Cheers for the suggestions, but I'm not having an issue with the precision itself. The "feathering" issue I'm having is that if, say, I tilt the joystick 5' and hold it there to maintain stable flight at that attitude, the airframe either piles on and keeps pitching down, or wobbles back and forth, or even pitches up to fly level again. Even to figure out if I was in any way moving the stick myself, I bound the cyclic pitch to a throttle slider and left it in place - same thing. All I'm hoping to achieve is stable turns to be able to guide the Viviane reliably, which is an ordeal when I have to constantly feather the cyclic back and forth just to achieve a semblance of stable forward flight. Same with roll, constant feathering required to achieve a nice stable turn. Just not a fan of the crutches it induces. Level flight? Okay, works fine if you let go of the stick and let it do its thing. Stable flight at other angles? Rely on the force trim. Stable camera while approaching? Either force trim for easy stable flight or rely entirely on moving the camera and using its "auto-locking" because doing it manually is virtually impossible. Wasn't a fan of the KA50 because of its heavy reliance on the autopilot systems, and even caught myself causing a whole lot of PIO when flying the Huey because I was used to having to constantly compensate with the cyclic back and forth just for stable forward flight and turning. If the Gazelle is just a different beast and this is how it works, then okay, that's fine.

Indeed it feels quite weird. If you set the trim you can achieve very stable flight with ease (so that the very jittery TV is able to maintain a target instead of shaking all over the place and preventing slewing) but if you try to achieve the same on your own you spend all that time feathering the joystick back and forth with little joy. Maybe I oughta try disabling the AP to prevent it from trying to level out or something.

Haven't actually been able to get lasing + guided bombs to work in 2.5 yet, I'm guessing it's working fine for you others?

The AI needs an incredible amount of work for such a module to be worth playing. I'm already sick and tired of it as a chopper pilot when the tanks are magically able to see the tip of your rotors on the upper half of a thick treeline over a kilometer away and 180' behind them. Just feels dumb when trees are your worst enemy rather than your friend, pop-up attacks are virtually impossible to pull off unless you play the silly 'who has the longest max range' game which simply makes for bad gameplay.

Oh no.

Being back in Caucasus with 2.5 really makes me miss this server, haven't found its equal yet :(

Hasn't there been talk about how FLIR (and aircraft monitor outputs in general) are affected by the gamma settings? Might be why.

Has been the case for several months now, nothing particular for 2.5. Engaging SPAK attitude hold tends to cause the joystick to drift far off-center, forcing you to use alot of force to hold the joystick in place now that it centers far from the actual center point. Same goes for trimming, the only way to fly with a FFB stick is pretty much to avoid using SPAK modes and never trimming at all, which is quite painful. _____________________________ Nevermind, I'm a knobhead, forgot that you have to swap the FFB axis and whatnot to make it work properly. I'll see myself out. :doh:

Does anyone know whether 2.5 performance is on par with what's expected or affected by this bug? Haven't flown it for a few months since I've been busy with the Harrier, but 2.5 is great for the Viggen. Yet it feels quite sluggish compared to what I remember, had trouble taking off with a heavy load and without burners I struggled to avoid stalling at a constant 300-350kph speed. With a light load it takes quite a long time to get up to cruise speed.

Common map settings can lead to some very odd-looking weather effects, this one looks like the glowing sea from Fallout 4... To reproduce - "Winter - Heavy snow & clouds" weather preset, December, 10am (default). So none of these settings are a weird combo of any kind.

Well, at least not *entirely* transparent, still having a hard time against the super-AI being able to spot just the tip of your rotor blades through upper 50% of the tree foliage 180' behind them with their magical powers. :ranting: Engaging from behind trees seems about as useless as usual. Was really hoping that collidable trees and beautiful low-level scenery would make for a good rotorhead comeback, but maybe not... Wish ED would have more leniency with the detection system.

Personally I only use it for Russian aircraft (e.g. KA-50) because of the cyrillic text. Being unable to vocalize, the difficulty in memorizing words using a different alphabet and not having the faintest clue to even guess their meaning makes things a whole lot harder.

Appreciate the correction.

Just as a note though as someone who shies away from mods as well, custom cockpit labels are really quite easy to add, non-intrusive and well integrated into the options menu. That and skins are the only things I've ever dabbled with.

MRKR = Marker = Ranging laser to get distance information. TRNL = Training Laser = Training only use (haven't actually checked if this emits anything at all or is just a function to get familiar with the procedures during training)

Personally I've only gotten it to work thus far with the LST having direct view of the laser to hold a lock - so dive bombing - while it loses lock when going beyond its field of view - level bombing. Then again, I've only tried doing it thus far with the TPOD and no use of the DMT, will do more testing once 2.5 hits.

I wonder if there's any attack heli that would feature FLIR, RWR, LWR and maybe even a MWS that wouldn't be too contemporary to be classified.

Myself I'm gonna try to to use the mklink functions to make the PC think that 1.5 and 2.2 are installed in the SSD folders while they're actually on the HDD, and hopefully then it will still be smart enough to copy the files over for the 2.5 SSD installation. Since it overwrites 1.5 it might end up installing in the linked HDD location, but that's easy enough to move to the SSD once it's complete.

Just to add, if all other 2.5 maps perform much better than Normandy because of this then they should really up the system req's for the map instead of copy-pasting it from DCS. It would dissuade sales further but at least avoid angry customers since there's no refund policy.

Wondering that as well, I really hope the TPOD fixes finally made it in, would be nice to spend some time practicing while waiting for 2.5.

UH-60 Blackhawk and its S-70 family variants as far as declassification allows.

As for the effort of replacing the trees in Normandy, its current placement feels almost entirely algorithmic, with hedge-rows squares almost everywhere, every single road being lined with trees all the way, and few terrain changes to deal with (which is where stuff tends to mess up the most). But of course only the devs know the effort involved for certain.