Penshoon

Yawing the helicopter sideways and using combination of bank + pitch feels quicker when slowing down. You can come back on power a bit earlier when you are about to exit ETL so you can do a more gradual increase of collective so you down let the rotor rpm decay when you go back to hover power. One wheel takeoff requires a light load and just as Cibit says you need to keep increasing collective as you gain speed. At the beginning of the run you have excess power to lift the rear wheels off the ground by forcing the front one into the runway but as speed increases the power isn't enough for a significant lift of the rear wheels. At that point you have to pull back on the stick a tiny bit to increase lift to lift the rear wheel again but pull too much and the front takes off as well. Really hard to do.... 9wnN_EJaw38

SimFFB, link https://forums.eagle.ru/showpost.php?p=1394206&postcount=18

9wnN_EJaw38

You can remove the exhaust IR suppressor in mission editor. ON Off

Thanks for posting that, I think the effect of needing less and less left pedal as aft cyclic is applied in he turn is due to more air being forced though the rotor as you pull in the turn that's assisting the engine to keep up rotor rpm, governor tells engine to decrease throttle and less torque is generated. I bet that with emergency gov on we would see a decrease in rotor rpm as aft cyclic is applied in turn but with no need for right pedal instead unless throttle is manually rolled up. Look closely on the torque meter and you can see the drop and increase as ball moves.

I would also love to hear someone explain this slip/skid indicator behaviour. When I make turns it initially moves the ball in the opposite direction of the turn? but after turn is established it will mostly center again though. Kinda like a pendulum effect? Pretty sure it's the same at least in the the ka-50. Recorded a quick video for reference when I didn't touch collective or pedals after I've put the ball centred in straight level attitude.

Yeah that would be nice, got plenty of unused toggle switches on warthog throttle I use for collective but simFFB only supports trim switch rebind on same device as it sends effects to and g940 stick has no toggle switches :(

I'm using simFFB for damping and friction ffb effects so not possible.

For this reason I bind my trim button to the trigger of a g940 and basically fly with it held down all the time to get non force trim feel on the controls. When I release stick and trigger the force trim activates & holds it in place so I can stay in same attitude. Like a dead man switch.

The Ka-50 has been the most rewarding module for me to learn in DCS and I'm still learning a lot every time I fly it. The auto pilot, coax rotor, powerful engines and systems makes it easy to pick up, fly and employ successfully from the moment you first get into the cockpit. So getting it from A to B and back to A in some fashion is easy to do and I think many people mistake its initial ease of use for a shallow flying experience. Hmm, I find that the Ka requires a lot more attention from the pilot order to control it cleanly during fast manoeuvring and also knowledge of its distinctive handling quirks and limitations during different modes of flight with various ap channels engaged/disengaged. Staying in control and using the ap to enhance the handling within it's larger flight envelope compared to mi-8/Huey is the reason I find it so much fun to just fly about even in non combat situations. I'd recommend the Kamov but I do love both helicopters, just maybe not equally as much much. :D

Simffb does allow hat trim behaviour, go to options and check "progressive trim" or "both" to enable it. To help with the trim deadzone issue with the g940 you can try to rebalance the stick a bit better than logitech managed. Add some kind of spacers on the bottom front of the stick base to make it less front heavy, I've center-mounted my stick on my chair and balanced it so it stays put whenever I let go even without force trim. Helps a lot for precision.

Managed to finished the course sub 7min but had to get out the old Kamov to do it ;)

Sharing the cleanest run I've managed to fly yet, Time ~7:16. Sub 7 minutes should be possible ;)

Try saving a wider default FOV in the module and then loading the track. Pretty sure that works.

Yeah recording the replay in normal 2d mode is much easier both performance wise for your pc and for the audience as accept ratio fits normal monitors. I wonder if it would be possible in some way to add smoothing to the recorded head movements of the track file afterwards? Silent recordings works ok but live commentary does indeed make the video too shakey imo. Increasing FOV + having a drink or two while recording and result is a bit more steady ;) :cold: :beer:

I'm necroing this thread as I have some questions on the rudder trim and heading autopilot channel. Just like AlexandrT I use a set of rudder pedals with no spring force (MFG Crosswind with removed spring + G940 FFB for cyclic + Warthog throttle for collective). As I understand, the heading autopilot channel will only be programmed & engaged when the pilot remove his feet from the pedals to disengage the small switches on the pedals. So say a real pilot take off with Mi-8 with heading autopilot system on but disconnected due to pedal pressure. After taking off the pilot pushes the stick trim button so forces on both cyclic & pedals gets removed. Now as the pilot removes feet from pedals the heading autopilot will engage and keep the helicopter flying locked in same heading. The pedals will stay in the same position and not return to center due to rudder force trim used. This doesn't happen ingame. After trimming the cyclic and pedals virtually I still have to move the pedals to centre for the heading autopilot to engage making the nose first swing left as I add left pedal, then right as autopilot engages to try to control heading. This simulated behavior only works with usual artificial rudder trim method when you have to center pedals for trim to take effect. Easiest way to fix this would be to add an option to make the force trimmer button also program the heading autopilot like how it works in Ka-50. I understand that this is not exactly how it works irl (pedal switches program heading autopilot, not force trim switch) but the effect and procedure would be same as irl (deflect stick and pedals to get wanted aircraft attitude, trim & remove feet from pedals). Hope that made any sense, Love the Mi-8!

Is it really due to main rotor over revving? Sounds like a case of mast bumping, is your cyclic centered?

So you don't want people to report bugs to help the developers improve the module? Somebody gotta do it if it's to improve :(

Please don't mistake reporting potential bugs and unusual behavior for "dev bashing". We all want their current and future modules to shine as we have invested time, money and effort to support it. :thumbup: The way I see it, the more info we can give Polychop now the easier time they have validating it through their sources when time comes for that. Supporting claims with videos and documents will only ease their labor.

Nose swings left, tail goes right, in order to push the nose right, tail has to be pushed left using right pedal. I'm guessing pedals is centred in this photo?

It's pretty easy to check whether you are cpu or gpu bottlenecked with a gpu monitoring tool like msi afterburner/evga precision. Run DCS and monitor gpu usage with said program. If usage is less than 100% then you are cpu bound and a faster graphics card wont help.

I haven't tried it but maybe either software "UJR - Universal Joystick Remapper" or "Universal Control Remapper (UCR)" can be used to trick DCS into believing your Cougar is force feedback enabled by creating a FFB virtual stick that has it's axes bound to your HOTAS cougar axes?

Razorback, have you tried dual binding both your G27 & your Cougar axes to roll & pitch in controls? Maybe DCS FFB device detection of the G27 will take priority and overwrite the spring centered style trimming behavior if FFB in enabled in DCS settings? Guess that could introduce spiking issues from G27 axes but that could maybe be fixed in Axis tune by reducing saturation to zero and adding 100% dead zone to only the G27 the axes?