Dunravin

Hi Holding the trimmer button does not unlock the cyclic as per Ka-50, Mi8 and Huey. In special options the trimmer is set to force feedback without springs as per other heli modules. I am using a logitech G940

Ka-50 you hold the trimmer in whenever making cyclic inputs, on release the stick should lock exactly where you left it. Trimmer button should be bound to right hand thumb to reflect Ka-50 cyclic trimmer button position. If its moving after you release the trimmer then you have curves set. Remove them. No curves with FFB fyling helo's. Also check the settings page for the Ka-50. You want the FFB with no springs option selected. FFB strength settings for your stick should be at 100%. There should be zero resitance with trimmer held in and 100% resitance when released. As for gertting tired holding the trimmer its something you have to adapt to as thats the intended way to fly it. Unlike the Huey there is no way to disable the trimmer in the Ka-50 or Mi-8. Best of luck!

Hey Pilots, I am about to order parts to make replacement throttle cable looms for the Logitech G940. Maybe your throttle HOTAS buttons, hats or rotary analogue are intermittent, glitchy or completely FUBAR This is a very common and annoying fault on the G940 throttle, if yours has not broken yet.... it will at some point! Let me know if this is something you would like so I can get an idea of qty I need to order. Thanks guys, happy flying. Please note this will not fix any issues with the 8 programmable buttons on the base. They dont utilise the same cable.

Much welcomed news considering multiplayer is a joke to join in VR and all the servers are "dynamic" template driven F10 text spammers lagged by silly scripts these days. But... how exactly does an AI with lost consiousness level out to 1G?

Hi the issue I'm having with my G940 is pressing DEB EFF on the cyclic does not relieve stick pressure and so pilot does not get full authority of the aircraft. Its like I'm flying with a permanent spring stick although holding the trimmer does seem to effect the AP channel indicators. Is this correct mode of operation? You need 100% FFB setting in logitech software and no curves set anywhere for the stick to hold correctly in the the three other heli modules (due to the stick having a sloppy centre and its own weight tends to pull it forward off centre if its at all slack.) As bove pressing DEB EFF does not releive the 100% pressure. Not what I expect and not met anyone yet who knows how the real Gazelle works in this respect. Can anyone enlighten me? Also the FFB curve settings in the special menu only seems to add massive amounts of dead zone to my control input? Very weird guys. And... My stick jumps about unpredicably when releasing the trimmer. (similar to if you set curves in the Ka-50... no no no) Sorry still not feeling it yet. the manual says "The magnetic brake maintains the cyclic in a defined position. Pressing the magnetic brake button at the pilot stick will define a new position to hold." Not whats happening and contrary to borchi is saying above. How are the rotor head, cyclic and collective mechanically connected and where and how do the gyro and AP come into play and get authority over pilot input? How does pilot override gyro and AP input? What is defining the position to hold? Seems counter intuitive under pressure situations to have to think about what the helicopter internals "think" is the airacrafts current attitude. I much prefer the rotor head following my cyclic and not a whacked out gyro. It seem an inherently dangerous design compared to the other heli modules we have. If as a g940 owner with some spare time I can be of assitance please call on me. Flight model seems improved, heli slips down the rotor plane now in a roll instead of rocketing up perpendicular to it. Still feels wrong in a vertical dive, even with the DEB EFF depressed the AP want authority over the nose pitch and prevents the full dive. It works better with the AP totally off. How does the pilot get FULL authority without resorting to turning master switches off? cheers Dun

1st time I watched the track landed fine, stopped centre of runway, on repeat views things start to go wrong as I come to a stop. Always end up tipped and off runway around the time aerodynamics gives way to ground-dynamics. (<Spit pilots will know what I mean) I noticed also that trimmer changes in game are reflected on my stick at replay. (FFB stick) I unplugged the stick but makes no noticble difference in game. Track corruption in the Spitfire is definately related to ground physics.

Suspect its something to do with "fudged physics" for tail draggers on the ground. The fudge isn't recorded or is out of sync with control inputs mebbe. I dunno, that's my theory. Airstarts fine. Just pitched around and dropped an extended two wheeler, the track is great until I take off for a second run... attached. NVLanding.trk

Good stuff The only thing I find detracts from the mission is JTAC tends to select support vehicles despite active armour and anti air in same location within LOS. Also way too much smoke. I'm out of touch with mission editing but thought it was possible for JTAC to smoke the AO once then talk on from there, kind of like a local bullseye. This would imporve the Ka50 game making it less of a duck shoot. I don't think it would have negative effect for the fixed wing guys with laser guided munitions as long as JTAC was lasing as normal just not laying smoke for every target. Many thanks, had fun flying the Caucasus mission.

Exciting stuff, can't wait for this module and thanks for the behind the scenes peek. Very interesting.

Hello, since todays patch to 2.5 Beta I am no longer able to load up Ka-50 Missions. "The module containing Ka-50 is required" Tried reenabling the module from the installed modules page without success. EDIT - The situiation is much worse. ALL modules are effected although they show as installed. I have only Su25T and TF51 available. Thanks for any assistance Dun

You read and understand my post? "Would it possible to include a setting to control which eye is used as output for the desktop render?" This request is made in the hope pilots can configure their game to suit their eyesight, left or right eye predominance. In a MiG-15 or ME109 with left eye dominance you're going to have to lean your head futher to the right.... Hope this clarifies.

Yes I know and have tried it with the right eye view but it's really not very good for quality or performance plus theres other issues. So we're back to requiring a VR menu option to select which eye is rendered to desktop or wondering if there's a file one can edit to achieve the same result as a workaround.

Would it possible to include a setting to control which eye is used as output for the desktop render? Stream viewers dont get the "down sights" view with the MiG-15 due to the gunsight being offeset to the right and its seems natural as pilot to position your head to use predominently the right eye for aiming. Suspect the same issue occurs with the 109-K4 In the mean time does anyone know if this is editable in any DCS config files or is it handled oculus side? Many thanks Dun

Open Alpha 2.20.12448 Horizon in mirror rolls with aircraft. Not opposite like the OP. Not tested other branches. :D

Okay Harrier released... time to bump up this thread. Is the Tucano still on the cards? Any sit rep on the airwaves? Cheers

Greetings I'm having lots of stalling issues and loss of control hence why I'm here. Found the performance stats pdf here - https://belsimtek.com/upload/docs/DCS_MiG-15bis_AERODYN_OPER_LIMITATIONS.pdf I quote from page 4 - Minimum airspeed limitations "Minimum control speed at which the control surfaces retain sufficient effectiveness is 300 km/h at altitudes above 12000m" I'm losing control at @400kph at even low to medium alts in dogfights and the AC is too slow to recover in a dive. Hella draggy. I'd like that extra 100 kph margin if possible :D Now I remember in beta phase this was a joy to fly, bags of power, now it feels like its too draggy and underpowered. I understand the beta FM was not accurate but IMO the current iteration does not tally with the documented statistics either and needs bumping up. I also notice slightly worse performance in 2.1 but I put that down to the QFE of Nevafa being around 900-1000 meters higher above sea level than Caucasus. I'm learning to let the MiG fly me and I just help it along but still I feel something is a miss here. I can live stream it if dev's are interested in seeing where it all falls apart in combat. Many thanks

Hi When trimmed to level flight and the refuelling boom is extended the AC starts to climb, this can be counteracted by trimming to aft. This happens because the pitch trim appears to be reversed when boom extended. Hence normal flight the stick will be trimmed forward to maintain level. When boom engaged my force feedback stick pulls back which suggests the trimmer has been reversed. Temporary aid is to reset trim on approach before extending the boom, settle and extend then trim (and remember to reverse your normal pitch trim operation) My force feedback stick still moves correctly in both modes, simply the input buttons get reversed. Great update, liking the flight model and new features, thanks

Hello, I have a force feedback stick, can you confirm if the FFB support has been fixed? As of last night I still could not get a sensible FFB effect in this AC. The 'standard Kamov-50 method' (for FFB?) you refer to I presume is the same as in the Huey where the pilot holds the trim button down while moving the cyclic, this removes all stick forces and allows for incredibly smooth control, when you release the trimmer button the stick is locked in place where you left it. Brilliant just what a pilot wants. For this to work correctly you need to apply 100% FFB in windows game controllers settings so this stick locks securely and you can hands off and it will hold a hover. But... in the Gizelle, my stick is always 100% forces whether the button is pressed or not, a flick of the Mag switch to down does nothing. So the result is that you have to apply much force to control attitude and subsequent presses of the trim button jerk the stick unpredictably resulting in crashing the heli. How are you supposed to fly with full FFB pressure acting on the stick all the time? Alternatively at very low FFB setting the stick is quite usable but then the Mag lock has no force available to lock! The situation is retarded. Its a no win situation whatever you set things too. So my question is what is the point of this trimmer? It does nothing comprehensible. There's no option to make it function like the Kamov and Huey. The other option is the fine trimmer which works exactly like heli trimmer in ArmA 3 - utter pants on its own but imagine very useful with a working FFB trimmer solution. I notice there is now two FFB sliders in the special menu, after sliding these to both extremes and subsequent testing I could not discern what the intention was with these sliders. Are they in addition to the FFB tune options available in the Axis Binding options? What is their meaning, do we really need more options? Do they override the Axis Tune options or do we have to set both or what? They did not appear to have actual FFB effect but rather seemed to lag responses, most noticeable when rolling, pitch not as much. All in all I cannot fathom the intention, and my concerns lead me to believe that Polychop does not have much of a clue what to do about it. Is it too late to request a refund? Totally unsatisfied with this product. I can fly it without FFB enabled but even then there a flight model issues I feel should not be happening even in a super light agile heli. For instance in level flight a slight roll left will induce some lift perpendicular to the rotor plane when in actual fact all helicopters in a bank will tend to slip down in the plane of the rotor requiring a bit more collective to balance that out. This anti gravity anomaly seems to have been reduced since the last time I flew but its still noticeable. Basically I have no faith in your product in its current iteration. I have no desire to fly it and am disappointed with the flight model.

Have been doing some research and it seems unlikely the Mk9 LF ever saw much action against 109K-4's. Its more likely to have been Mk14's G-1 & G-2 Yes K-4 No

How much do you want to wager? I dipped into the config and tightened up the convergence a little. It makes for a devastating difference... https://www.digitalcombatsimulator.com/en/files/2319994/

Not really, the Spit is an energy fighter, it depends on trading potential for kinetic, how do you do that at 500-1000ft as per the current offerings of the online airquake servers? At sea level 109's will piss all over you with unrealistic amounts of MW50 on tap which would probably of been used up in their scramble to combat altitude irl. The fuel concern was always a big issue for 109 pilots IRL, not an issue online which again make the game ridiculously unbalanced. You stand a much better chance with 190's if they decide not to run away. Anything over 260mph in the Spit and you will black out trying to keep up the pressure on a 109 who suffers something like a third less G. And you cannot afford to idle throttle and time a turn and burn (avoids G issues) as that technique depends on trading several thousand feet of altitude.

It should be top of their list, as they are losing me and others, I won't be dazzled by hype over new modules any more, I just want the core game play at least half as good as other titles.

+1 No more new modules thanks... lets get the fundamental core gameplay right first, otherwise what is the point in new modules anyway? Current situation is laughable.

3000RPM in combat - boost IDLE to 18 as required. At 2650 you get no benefit of high prop drag at low boost pressure and the awesome cooling effect that provides in even a short shallow dive. A tip for the Spitfire is to not expend fuel energy when you are trading potential for kinetic, then when you do apply the throttle there's a transition from the oncoming air turning the prop to the engine powering it, get through this zone smoothly to avoid over revving then you can safely open her up to even 20 Boost for a few seconds only then 18 - applying throttle this way when you are already gaining kinetic is key to catching 190's and 109's near the crest of their zoom. TBH I only ever use 2650 when I'm saving fuel with a boost around 7, it simply doesn't work for combat.

Afternoon Gentlemen Is it just me or does the Spitfire look very blue when you're spotting? I feel like the specular effect is too much, basically the plane looks to be the colour of the sky and has little to no camouflage against the terrain when viewed at distance. A bit if a disadvantage compared with the Dora's which can blend in very nicely and evade your senses. Your thoughts?