Crypstik Posted October 2, 2013 Posted October 2, 2013 I decided to have another go of trying to fly the Ka-50. From the start it was crash after crash after crash. I had no idea what i was doing wrong and was about to give up again. Then all of a sudden i had a lightbulb moment............. Stop fighting the controls and as soon as i stopped trying to yank and bank it changed from a hungry tiger into a kitten. This thing loves to fly itself and within a few minutes i was beginning to get the hang of it. I know this isnt a great post with lots of yet unknown ideas, but for me it was a huge moment. I can fly the Ka-50.... Im not brilliant with it and there is a huge road ahead of me to get anywhere near the level of alot of you guys. Still this small pat on the back to myself has made me want to learn more and achieve more with this helo. I can now go and complete all the training flights and easier missions. Thanks for reading Crypstik out A-10A, A-10C, A-10C II, AV-8BNA, C-101CC/EB, F-14 A/B, F-15C, F-15E, F-16CM, F/A-18C & Super carrier, F-86F-35, L-39 C/ZA, Mirage 2000C, MIG-15BIS, MIG-21BIS, MIG-29, SU-25A, SU-25T, SU-27, SU-3. BF-109K4, FW-190D9, P-51D, Spitfire LF Mk IX, TF-51D. AH-64D, KA-50 2, KA-50 3, MI-24P, MI-8MTV2, UH-1H. Caucasus, Nevada/NTTR, Normandy 2, Persian Gulf, The Channel, Syria, Mariana Islands, Sinai
Maulkin Posted October 2, 2013 Posted October 2, 2013 Congrats! I feel for ya! The biggest lightbulb for me was when I learned to use the autopilot channels instead of constantly fighting them. :) For the longest time I would get frustrated and just flick the FD on but I have finally gotten to a point now where I am always trimming and I just let the Shark fly itself. --Maulkin Windows 10 64-bit - AMD Ryzen 9 5900X @ 3.7 GHz - 32 GB DDR4 3600MHz RAM - EVGA FTW3 RTX 3080 - Asus Crosshair VIII Hero motherboard - Samsung EVO Pro 1 TB SSD - TrackIR 4 Pro - Thrustmaster Warthog - Saitek rudder pedals - Lilliput UM-80/C with TM Cougars
Offlinepilot Posted October 2, 2013 Posted October 2, 2013 Flying the MI-8 made me give the KA-50 another try.. and it feels like the KA-50 is an easy to fly (and shoot with) miracle of (russian) engineering! The landings are almost automatic!
Crypstik Posted October 2, 2013 Author Posted October 2, 2013 Congrats! I feel for ya! The biggest lightbulb for me was when I learned to use the autopilot channels instead of constantly fighting them. :) For the longest time I would get frustrated and just flick the FD on but I have finally gotten to a point now where I am always trimming and I just let the Shark fly itself. Thats the same lightbulb. A-10A, A-10C, A-10C II, AV-8BNA, C-101CC/EB, F-14 A/B, F-15C, F-15E, F-16CM, F/A-18C & Super carrier, F-86F-35, L-39 C/ZA, Mirage 2000C, MIG-15BIS, MIG-21BIS, MIG-29, SU-25A, SU-25T, SU-27, SU-3. BF-109K4, FW-190D9, P-51D, Spitfire LF Mk IX, TF-51D. AH-64D, KA-50 2, KA-50 3, MI-24P, MI-8MTV2, UH-1H. Caucasus, Nevada/NTTR, Normandy 2, Persian Gulf, The Channel, Syria, Mariana Islands, Sinai
AhSoul Posted October 2, 2013 Posted October 2, 2013 Yeah I didn't know about the different autopilot channels at first so was flying manually. Kept shredding blades :) Much easier with the A/P on and using the trimmer button... [sIGPIC][/sIGPIC] Soul's pit thread
Erforce Posted October 2, 2013 Posted October 2, 2013 Heading AP is the first one i disable when flying. this channel is the main cause of rotor intersection, when flying at crazy speed. i don't turn off other 2, unless for a barrel roll or looping. Ka-50 is a dream to fly, it just needs a better graphic engine, especially at low altitude. TASK / ROLES acronyms guide Black Shark A.I. datalink guide illustrated (v1.2.4 Available on Wiki) DCS World Codex 1.1 : full units list (Speed/Weapons/Armor thickness/Threat zone/Weapon damage...) (Oct 2013) BlackShark 2 1.2.x Bug and glitches thread (v1.2.7)
slug88 Posted October 2, 2013 Posted October 2, 2013 (edited) Heading AP is the first one i disable when flying. this channel is the main cause of rotor intersection, when flying at crazy speed. Actually, low rotor rpm is the main cause of rotor intersection when flying at high speed. The faster the blades spin, the more centrifugal force there is to keep them from flapping up and down. So, keep your collective low to maintain a high RPM, and collisions should not occur, even when maneuvering at beyond Vne. Heading AP isn't really the culprit. Edited October 2, 2013 by slug88 [sIGPIC][/sIGPIC]
Fri13 Posted October 3, 2013 Posted October 3, 2013 Actually, low rotor rpm is the main cause of rotor intersection when flying at high speed. The faster the blades spin, the more centrifugal force there is to keep them from flapping up and down. So, keep your collective low to maintain a high RPM, and collisions should not occur, even when maneuvering at beyond Vne. Heading AP isn't really the culprit. RPM is not the problem, as RPM is kept constant all the times. Problem is collective what many virtual pilots pulls too much on high speed what cause flaps to collide when doing some kind faster change. So every time when doing on high speeds any maneuver, lower collective and maintain it enough so you get blades to have enough drag to allow you finish the maneuver. i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S. i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.
Recommended Posts