Sephyrius

+1 disappointment.

If wishful thinking and speculation is fake news then you have another 100+ threads to move/close. Same goes for the mystery dev team, why would they be mad about something theyve chosen not to announce yet? If so, then thats another 50 threads of speculation to close down for aircraft that are already licensed by someone else. But fine, guess Ill edit it with simple and drab text that cant be misinterpreted if people get so antsy about it.

Jedi mind tricks. If we tell them it's true they'll make it so! ;)

I hope youre the Bo-105 devs Miltech-5 is working with.

Good to know, there's no point in people wasting time on providing feedback here if they're not gonna read it anyways. At least Razbam made a statement when they made such a decision.

Seems like PC have also resorted to 'radio silence' in terms of their community outreach. Not a good sign at all.

Very nice find, now I feel dumb for researching the Viviane instead of the HOT system :doh: And yeah, very limited expectations, but hopefully the devs will keep it in mind. It seems as if the vast majority of pilots have resigned to doing sneak attacks from a hover - and god knows how many have died to the training mission sniper tanks - so I was surprised at how it wasn't being mentioned as an issue . At least I'm not crazy. I'll try to do some more testing, most of the issues seem to arise from rudder input during sideways translation and evasive turns.

I'm guessing the Gazelle hitting the ground twice was a latency issue between what the pilot and the observer perceived. Wasn't there a Vikhr flying straight through a forest as well later on? i'm guessing (hoping) that was netcode too.

Cheers for the response, I bet alot of newer pilots would find this information handy. I'm already familiar with it all already. I was rather more trying to ascertain if and why the Viviane is so unstable/unreliable when used while on the move. I'll try to figure out a good way to record in VR and then try to show an example of its behaviour and comparison to the targeting system behaviour of other modules.

Could you elaborate on why having a limp stick is undesirable? I'm using an MSFFB2 myself, and I was under the impression that most helis - unlike fixed wing aircraft - don't tend to self-center (except via these force trim systems). Wouldn't this mean that a limp stick is perfectly normal for maneuvering? Quick taps makes it sound as though it's something to avoid.

So what advice would that be then? "Just fly and figure out what works for you"? If the stated trimmer use is common practice (and probably the procedure used in real life) then it's as good of a starting point as any. It's better to try and then deviate than fumble around in the darkness.

Are you sure? I fail to see how that would be the case. Asservi is barely ever used as it locks onto the direction of the camera, not anything else, right? I've only ever considered using it to visually ID with it if it matches up well with the L/Mistral version boresight. Or to remove the delay/FPS loss bump of turning it on from standby. All of the problems I describe apply to the PILOTE mode.

If the heli moves in any direction other than facing the camera (or hovering), then you have to compensate for the heli movement when slewing the camera. This makes it much harder to move the camera accurately. The problem is even greater when you are zoomed in because then the slewing speed is decreased. At maximum zoom, often-times you can't even move the camera fast enough to compensate, making you lose your target immediately and can't recover without zooming out or moving towards the target. And I'm not talking about crazy maneuvers - I'm talking about orbiting the AO while scouting, adding rudder input during your approach, angling off a bit and suchlike. The KA-50 has all of it built-in, yes, but it's because it's a highly automated single-seater. The Gazelle devs have mentioned that some features are shortcuts to compensate for the lack of a co-pilot (e.g. a pilot dedicated to hovering and popping up while the weapons officer is acquiring and firing). Having such a shortcut for Vivane "locking" if there's no actual locking feature in the real thing is problematic, so it's good to know what the conditions of it are. Does it lock terrain? Does it have a maximum distance? Sometimes it stops locking entirely And the lack of gyroscopic stability from the first issue means that you have to move the camera - hope it locks where you want it to be - move the camera - hope it locks again, which is really awkward. I'm just wanting to use the Gazelle to its full potential. Think I read on here about how pilots often conducted attacks in Libya while flying low and at 100km/h+, instead of being largely restricted to attacking from a hover (or have to fly straight into the target area and enemy tracers just for the camera to stay on target).

No one? Is it just me then?

Just picked up an MSFFB2 for about €14 (+€6 shipping) just as a backup if my first one dies. Pretty sure it's worth plenty more due to its rarity. Old/no longer produced stuff is pricey, just gotta get lucky or settle for used goods.

Options are always good. To each their own. If a full-real server with 30 minute rearms, no auto start-up/shutdown procedures, 1 life a week, no kneeboard marks, no-solo-flying-multicrew-planes server becomes popular, good on ya. Sorta kinda doubt it though. In the Gazelle for one, I'm gonna go with a kneeboard substitute for a co-pilot.

It's because it's not using SpeedTrees, right? Despite being pretty much the most densely forested map of them all... Atrocious performance, worst purchase I've ever done, DONT BUY IT. It's a goddamn disgrace. If it's a very old module (e.g. KA50), then I can understand it, but this is one is far too recent to in any way justify such a thing.

1. Is it normal to have to "fight" against the movement of the heli when slewing with a second joystick? It sorta works with buttons since they apply 100% movement speed, but they're still terribly inaccurate and subject to this issue, and I'd much rather use a stick since the real thing does. Makes acquiring targets while on the move *very* painful. The Viv also tends to rubberband after it has "locked" onto a spot while movement is pushing it elsewhere, causing the camera to jitter back and forth and usually spoiling any missile tracking (e.g. if you want to angle a few degrees away from the targets after launching to extend/avoid incoming fire without breaking the wire). It's practically a non-issue in any other targeting pods/systems of any other modules, which makes me suspect that it might be a design issue. I'd expect more from such a heavy gyro-stabilized sighting system. 2. Does the "locking" of the Viviane exist in any way in real life or is this just a helping hand to compensate for not having a dedicated weapons officer? (like the auto-collective and hover mode, no?).

Wonderful, thank you!

Hiya, how come all the helicopters were removed? I can understand some of them as they don't stand much of a chance in Air to Air (granted, doing hover-fighting amongst the trees as a Harrier vs Huey was glorious fun), but could we please get the SA342 Gazelle Mistral? Sorely missed. As I ended up having to fly the Viggen instead, any chance that it could be fitted with its flare and gun pod? It appears that RB74's occupy those spots at the moment (with no RB74's on the inner pylons iirc).

Does this not highlight why people are irritated by the DCS spotting system when that same improvement in readability and visual fidelity is at the cost of making it *even harder* to spot enemy aircraft? The two are at odds at the moment, and it hampers people's desires of upgrading if it just becomes a handicap.

Sadly, it often seems like a vicious cycle of some problem causing disinterest/frustration in a feature, leading to declining numbers of people still bothering, and then ED not prioritizing it because of the lack of beneficiaries still remaining. Just look at the online gameplay, going from being in its newsletter 6+ years ago, to nothing, to declining numbers standing the mess that online gameplay was, to "vast majority play SP anyways, so whatever". It took a pretty massive community backlash to finally get dedicated servers out the door. Huey piloting without working search lights for C/SAR, as in this case, causes disinterest in the module. The Huey could be a great co-op experience with multi-crew, but it barely seems as if that will ever happen. It's not a question of brand spanking new features that were never promised, it's a question of maintenance.

Just picked a second MSFFB2, so now I don't have to worry if one ever breaks. Question 1 : Sick of using a throttle for a chopper,so I'm thinking of running an MSFFB2 + SimFFB to simulate the collective, using its trim button function to lock it in place. Do real heli collective controls use a similar 'unlock' button or do they use friction to keep it in place? Accidentally nudging the collective seems both plausible and disastrous in flight. I know the KA50 uses its collective brake lever, but it might be an oddity. Question 2 : Does anyone know if running two MSFFB2's at once causes conflicts?

Hoping for a potential Kiowa as Im about to test fly the Jetranger later this year. And it being the only module mentioned it'd be the only one expected anytime soon at all.

I used mklink to move Nevada and Normandy to the HDD without any kerfuffle. It's not as if anyone flies on those maps anyways...