Whisper

ED really need to start thinking about their ME et scripting engine as an integral part of their product and start consider talking about it clearly, put forward documentation, and show what is changed in each patch notes. They don't seem to consider that important, where it's what could kill or make live the sim. The scripting engine is not anymore that little tool they leaked as a toy for some of their customer, and that they can change at will without warning because it's just their internal tool, after all....

The 190 is still a mistery for me :'( Tried to see of Spit helped, I just can't get that cat in the air consistently :cry: 109 was already ok. That said, 190 has not received the time it deserves from me, so I can't complain , I should take the time for her.

To train on the dancing for both take off and landing, I did several pure ground run on a free runway : just align, accelerate, keep on the runway while dancing, then lower engine to decelerate and stop at the other end of the runway, still keeping on the runway with the rudder dance. Do a 180°. Rince and repeat in the other direction. Several of these got me to master the take off, somehow. Landing I'm now nearly never breaking the plane anymore, even though I still touch wing tips from time to time.

I just do exactly like in Sporg video, with a -1 aileron trim for takeoff. I just push super gently on the throttle, until I get around +7/+8 Boost. The tail goes up by itself, and the plane shows signs of wanting to take off by herself, at good speed, at which point I chose to do so or not, depending if I really feel it's ok :) All the while dancing on the rudder to keep everything straight. I've had zero low speed issues since, the worst that can happen is a bad dancing of rudder. Using stick for rolling is only necessary when sudden Boost changes are made during the run, when something bad is about to happen and I feel I need to speed things up (usually a bad idea, though, it often transform one problem into another one, often worse)

Not yet discovered the bird completely, but so far, for take off / landing loop training, my procedure is -1 trim for take off, then cruise settings and +1/+1.5 trim for cruising, that I keep during landing run. Not done it yet for combat settings.

For me it's the 190 which is untamable at take-off..... 109 or Spit seem rather fine. To each his own :) But you're right, learning the 109 makes it far easier for the Spitfire now. At least, it makes me accept my multiple crashes far more easily :) As for ground handling being a weak sim point... I'd refer to tail dragging post where it's stated that DCS (and BOS) seem to have nailed it.

Dammit, bad news.... In the same boat, I'll try reinstalling spring

From https://forums.eagle.ru/showthread.php?t=179253 (my new bible :) ) :

On X55, for all aircrafts that use a braking lever (L39, Mig21, Mig15, Mi8, and now Spitfire), I put the braking axis on one of the thumb rotaries, the down-most one, on the throttle. It get natural pretty fast, full rudder deflection right or left, and you control the amount of turn through more or less press of the brake lever.

Just chiming it to answer here, I never talked about communication. The point that made me react was this : As far as I've seen, the "last part" was : "I would suggest to first finish a module and all its systems, before starting some Viggens and Tomcats and whatnot, but that's just my two cents." That has nothing to do with communication, but with asking LN to only do bugfixing on current released modules and do zero work on upcoming modules, to which I cannot agree due to reasons I explained above. I was not commenting on their lack of communication :) You neither, btw, when writing "last part is spot on" ;) There's 2 parallel issues, comms and actual bug fixing. Again, asking to stop other module dev to only bug-fix the Fishbed is unreasonable imho. That means it takes more time to get things done? Too bad, I don't think it's an issue if it keeps LN afloat. Comms? Well, Cobra just seems to have answered your issues :) Using a separate bugtracker isn't that a bad idea, imho. It makes actual bugs and reproductability THAT much better for devs, and yes, it slows down a bit the dev process. From what I've seen it doing to BI and ArmA3, I can see the benefits. A3 may be now 3x slower in devs, buts it's heads and shoulder above the previous (poor) ArmA quality state.

I can confirm, wind affects max speed heavily, I tested in windless environment and 150+ kph is easily feasible without breaking the line

if a visible FARP nearby isn't too much of a problem, maybe by removing ammo / fuel from the base and having a trigger zone control the presence of the refuel / rearm vehicles at the FARP would do the trick? Players in zone => refuel/rearm vehicles present around FARP => refuel / rearm possible Players not in zone => refuel/rearm vehicles deleted => no refuel / rearm possible Immersive radio procedures may be tough to be done properly, but ....

I never said they should not fix issues nor talk about it, by "moving forward" I meant they have to now put a portion of their time into work that'll earn them something in the future, they cannot dedicate full time on a something that doesn't help them for a living. Again, nobody would do that, so don't expect them to do so. I was just reacting on the "fixing released products first instead of working on new modules" assertion. After some time, this is not possible anymore, we should all be aware of this.

Nope it's not, unless you want them to continue working for ages for zero revenue, something you would not do. They have to move forward at some point, even if that means slowing down released modules development. That is, if they want to continue as a studio

He actually wrote the comparison between expected result from chart and in-game in his second post. He'd have expected 38,8s for a full turn @700kph, 2km high , from the chart. He gets 26s in-game. more than 10s faster than expected.

Thks Looney. It seems my slingload breaks when going slightly above 100kph, with less than 1Ton charge, it's perhaps a little sensitive right now. Do you record the same in-game limits?

Am I the only one struggling with keeping the speed low enough not to break the sling? It's painful now doing long range transportation

Mi8 is just THAT badass

Got it, I didn't know

Eagerly awaited release on my side, the ability to have a flexible mission tasking & scheduler is a god sent. Imho, the possibilities of this for open-ended permanent missions are huge.

MIST-wise, I'd advise to put a Late Activation group and clone it each time you need it respawned.

It's a pretty defining feature that may warrant dev time. They have the incoming Mi24, working on multicrew is not time lost for them, quite the contrary

PU-26 is not UV-26 (yeah, it's confusing :) ) Stefaan is asking about the Gyrocompass settings EDIT : I've not yet read the new manual about this system, but I've developped the habit of re-aligning it to True North during startup procedure, not sure if it's something that must be done IRL.

This, +1000 I use zero curve, zero trim, and a cut down spring on my X55 to have a sensitive, low friction/counter force stick. You'll tame it pretty fast, tbh, it's not that difficult. The thing is, without the pitch/roll channel active, it's pretty damn difficult to stop it from going everywhere but where you want it to go.... And to add to it : at the beginning, you have a tendancy to be a little too rough on the controls, and when doing so with the collective on the Mi8, you often end up in a transitionnal "RPM low" state (it doesn't last long, but Bitching Betty warns you about it). In this case, your generator doesn't have enough power and some function are stopped, namely, the pitch/roll channel (in fact, the whole AP system) is disconnected!! So whenever you get an audio warning and the lady gets uncontrollable, check the green LED

See here : https://forums.eagle.ru/showpost.php?p=2963439&postcount=10 A) "AP Standby" button on the HOTAS section puts the AP on standby and resets the trim to neutral B) There's a trim reset button juste below the AA/Charge switch (left front panel)