Anatoli-Kagari9

I can add to this yet another episode where the whole tail section of my Spitfire was ripped off by a chasing Fw190, and I kept pursuing the 109 ahead of me, feeling the aircraft a bit strange, but still flying... As I changed to external view and noticed the whole tail section wasn't there, just out of curiosity I started waving the rudder and the elevator, which got no effect ( at least that was coherent...), until after some aileron input the Spitfire entered a flat spin, all the way to the ground - I mean really flat!

This!

It appears to me that there is something really still too "Early Access" in the Spitfire module, although I have noticed the same happening to other modules as well... I usually take the Spitfire in the "Battle over the Lake" SP Mission that comes with it and sometimes while chasing one of the Axis aircraft I get shot by another one chasing my Spitfire, lose the port or the starboard wing ( more often the port ) to the root, but the effect is practically unperceptible until I see flames and look... I believe that the true thing would wildly start to roll ? Either it is still a very crude damage model that causes this behaviour or the flight dynamics need some tuning right ?

@docWilly: Thank you SO MUCH for the information you cared to collect from a real heli driver! That was remarkable, and indeed although I believe when he answers that he doesn't have to care about countering torque for collective inputs while cruising he's assuming SAS ON, the way the Gazelle + Fenestron are designed will probably allow for minimal need, or probably none at all IRL too.

Glad you sorted that out. I and at least another poster mentioned that as one of the possible reasons :-)

Has happened to me to at least once. During a dogfight, while chasing a foe who, on it's turn was chasing one of our Spitfires, I must have dropped some shots, unintentionally on that poor friend, and got downrated because of that :-(

In my tests I also made sure the Gyro was disengaged, but I still can apply collective, say at 110 knot, without having to use the anti-torque pedals.

@docWilly: First of all, as being one of the authors of posts in this thread, thank you for your excellent post and for providing further insight into some of the issues identified. In as far as I am concerned, the video of the approach in an upside down situation was probably recorded with a former version, and this is no longer possible in version 1.5.6 ( ? ) Regarding the "abrupt" collective inputs I mentioned in my post, well, I made sure all of the SAS, AP, Gyro and Trim systems were Off for my tests, and I really don't think there should be no need at all to input anti-torque compensation. As much as the fenestron system can be a very advantageous one, the main torque itself results from the main prop, and should have an impact unless the SAS is working ( ? ) Finally, regarding the flight model mode, I'll check how mine was set and report back. Just as I forgot to untick the FFB option from the General options, I might have skipped this one too ?

Thx and this other video even makes things worst... A total immersion killer for me :-/ I'll be back when basic aspects of rotary wing flight dynamics like this get fine tuned ...

I just posted about there being no need to compensate for collective adjustments provided we're moving, even if at low / médium speeds. Even abrupt collective inputs, that I would expect to require anti-torque pedal compensation, do not cal for it, thiswith SAS, AP, and MAG Trim off . Is this the way the real Gazelle handles ?

just like me, you do not have a FFB joystick... I was pointed to this mistake on my recente upgrade and mess around with settings at the Gazelle fórum. The trim was reversed and I posted at the "Bug" thread, but someone kindly suggested me to check if I had it enabled in teh Game settings, and indeed it was set under Settings / Misc / Force feedback. It also made a difference on how the Spitfire now feels ( for better ) :-) ?

Good observation!

Just tested it - was the FFB enabled in the Game Options, when I do not have one ! But that total lack of need to compensate for collective adjustments, even with SAS and trim OFF, as soon as we get away from near stationary still puzzles me :-/ Is the real Gazelle that "easy" to cope with when collective is lowered / pulled ( even abruptly ) without requiring any sort of anti-torque ( rudder ) input ? To make sure it wasn't the SAS, I turned of the AP and all of the three SAS channels as well as the mag trim, but still no need for rudder input with collective adjustments if I have a fwd movement with just a médium speed.

Thank you So Much Holton! That must be it !!! Still at the cafeteria, reading the manual and browsing the ED and AVSIM forums, but will try it ASAP at home !

I just got training in my new Gazelle module. I had seen before videos like this: showing some weird ( IMO ) behaviour, but yesterday after completing the startup training mission I decided to lift off by pulling the collective slowly until the Gazelle lifts from ground and enters IGE, and then, without ANY cyclic or anti-torque correction, I climbed all the way up this way, rolling around the vertical axis, with no drift or drag hint or displacement requiring cyclic corrections ... I repeated with the AP and it's three channels disengaged, and the same is possible :-/ Also, the trim options for "left wing down..." and pitch seem swapped ? I programmed a button for left wing down and the heli rolls right, another one for nose down, and the heli pitches up ?

Been able to play only in SP missions selected from those available for the Spitfire, and where there were no micro-freezes like in the old times where there were problems with some explosions, now under some circumstances I get sudden freezes although overall the FPS stay at 60 fps ( I've got VSync enabled ).

But in the Spitifire, on some of the SP missions, I have had my tail ripped off, and the worts that happens is entering a flat spin.... I would expect the loss of a tail on such na aircraft as having a much more pronnounced effect ... Welll.... Sims....

This is truly the sort of stuff that kills the immersion for me in a flight simulator. I understand it can be due to poor damage modelling, but heck - this doesn't make justice to good standards of flight dynamics modelling, so I have to assume the FDM isn't actually seeing this damage...

ROGER that guys! Thx for the hint. I remember I had started DCS in the morning just before leaving for the traffic battle, while waiting for wife to get dressed - it makes sense then :-)

When I started my DCS beta last night, still somewhere in 1.5.5, iti didn't identify the new version being available and started pushing it. Then I restarted it and the same. I eventually decided to manually run the updater from the ED programs folder, and it then pushed it into my PC :-) - Enjoying this update so far :-)

Update was fast on my i5 2500 gtx 960 rig. I am on the beta branch only, and have nothing more than the ww2 fighters and the Gazelle. Update didn't take that long, at 3,4 MBps. Starting Missions appears to take a little longer, but I couldn't tell for sure. On SP missions I experienced 2 CTDs and a deep stutter situation, one of those that reminds me of when some explosions caused stutters, but then I was unable to reproduce it. I didn't use any MP missions because all slots appeared to be dedicated to the new kid in town - the Viggen :-)

I've been there !!! Look for "jcomm" in the pilot's board.... Sometimes all Spitfire slots are filled, so I pick the 109, although my preferred is still the p51d, but it requires more skill and altitude to be used to it's advantages....

What I haven't yet been able to find were the gyro precession errors.... When i start a mission i align it using the M-8, and after no matter what time and type of flight / dogfight, they're still in sync...

Thx Schwarz! Will certainly search for it !

Great landing Schwarz! You mentioned - realtime weather ? Are you using any sort of weather injector in DCS ?