RazorbackNL

But there actually was a “Top Gun” movie about helicopters back in the days! You never saw “Firebirds - Wings of the Apache”, starring Nicolas Cage, Tommy Lee Jones and Sean Young?

Would go with those also, as long as it has Wessex in the nametag :thumbup:

A DCS version?? Oh yes, PLEASE!!!

If you already have the Black Shark I would go for some rudder pedals. Makes flying the Shark way more easier.

Thanks for the feedback, guys. Unfortunately still nothing gets deleted :( Apparently the paths are not correct. I forgot to add the [joystick] folder after each module folder but that does not do the trick either. UPDATE: It is working!! Needed to use: Users\Razorback\Saved Games instead of: gebruikers\Razorback\Opgeslagen spellen Thank you for your time, guys!

Hi guys, Could someone please take a look at this batchfile I am trying to create? It isn't working for me. I want to delete every Cougar joystick file from every module I own before I start DCS. Thanks in advance DCS.zip

I did a totally clean fresh reinstall of DCS World OB today, including my SavedGame folder. OMG, the Gazelle flies like a dream, no more deadzones for me! My sincere apologies to you, Polychop! The problem lay with me all the time! Keep up the good work!

What I am trying to do is to give each aircraft an individual "takeoff from ground" parking spot on the map so clients can start their aircraft (heli in this case) from an unofficial parking spot. The problem is I can't move each aircraft seperately when they are part of a flight.

When I create a flight of multiple aircraft I can only move the first aircraft to a certain point on the map. The rest of the aircraft can't be moved individually. The all move with the first aircraft in a right echelon line. Any thoughts? Running the latest OpenBeta version.

If it has a rotor, I'll buy it!

The download link seems to be broken. It directs me to a screenshot.

If Polychop would just make a permanent fix for this issue instead of having us looking for a workaround. This issue has been here for too long.

Maybe there is another option that is gonna work for you. It did a lot of good to me. I assume you are using Foxy for programming the Cougar? In Foxy go the Download tab and enable the “Reset axes when downloading” option. This option gave me a completely different Cougar. I hope it works for you also.

It is awesome in VR!!

The main panel glareshield light doesn’t work also (one of the six rheostats on the overhead panel)

After the latest OpenBeta update, some mods are broken and need to be updated for the latest OB build. This means that updated mods don't work in Stable anymore because this version is now one build behind on OB.

Assuming you use custom snap views, go to your saved games/dcs (or dcs.openbeta)/config/view. In here you will find a file called Snapviews.lua. Make a backup and open this file with notepad++ and delete the complete a-10c section. Save the file. All should be good now when starting DCS.

Awesome! Thank you!

Can you explain to me how to do that? I know it might be a little bit awkward to start using the Cougar as DX controller, but I really want to give that a go, just to see if things will be different for me. Hope you can help me out. Thanks, Razor

Hi Rudel, How did you manage to assign 2 buttons (#3 + #7) to the same action? Does #3 behave like a modifier button this way? Been using the Cougar for years in User mode but I want to start using it in DX mode. Thanks

Never seen that before. Did you try a repair? Maybe that fixes things.

I have made a custom cyclic with hall effect precision sensors. The pitch and roll axis have absolutely no deadzone. Every other module have full control around the center without having to fight build-in deadzone. Needless to say I fly all modules without any saturation, curves or extra deadzone. The Gazelle is the only module which is effected with this behaviour which wasn’t there since some updates ago. This is a software issue, not a hardware issue.

This ridiculous deadzone has been around since some updates ago. Not sure why this hasn’t been adressed so far. The Gazelle is unflyable without adding saturation and/or curvature which should NOT be necessary in the first place.

Personaly I don't think setting up curves and saturations should be the way to go to make the Gazelle behave in flight. I fly all the other choppers with no curves or saturation at all and I am doing good this way. I am not going to debate the flight model. I am sure Polychop did their homework on that subject. The problem with the Gazelle lies in the way the flight controls are done. The cyclic has that weird build-in deadzone giving it an on-off behaviour around the center. The collective is going up and down in steps instead of a smooth motion. This can all be judged by looking at the controls indicator. Once these imperfections are being corrected we have one hell of a chopper without the need to mess with curves and stuff.

Thank you, Maverick.