Bango

I took off in the Mi-8 as soon as humanly possible, having it all prepped for the "Go" call, where I'd just have to start my 2 engines and take to the air. I tracked too far north to begin with, trying to avoid that tank battle which was inconveniently placed between us and Senaki, while it seemed like Blue guys had a more or less straight shot. So they moved with the quickness and beat me to Senaki, which was the beginning of the end. I knew coming into it that it was well stacked for Blue side. Shorter distance to Senaki, no tank battle in the way, artillery twice as far away from us as ours to them, not to mention the aircrafts and weapons themselves. Even the hueys have flex guns, which in the proper hands are devastating, and were used to great effect. Mi-8 does not hold its own as an A2A attack helicopter, and using it as one would have surely cost us more points than we gained. So my team was there just to shuttle troops where they needed to go. When we found out there were no AA troops, that was another disadvantage to us, as we planned on placing lots of it around Senaki and our artillery sites. So that really just limited our utility to transporting troops to Senaki. But when Blue got there first, and were able to rearm there, like I said, the end was already being written, and there was nothing to do but grin and bear it, and keep trying to shuttle those troops to Senaki until endex was called. Watching the stream its even clearer that we Mi8's were just the cannon fodder for the hueys and gazelles, which doesn't feel great, but its what I signed up for, and I definitely had fun operating under that pressure and adversity. Next time we will know to sign up for hueys instead (We are 229th after all) :smartass: With all the hindsight from this one, I can't wait to see what's in store for the next one! A big thank you to Alpenwolf & the 104th for hosting & directing the tournament. I think alot of goals were achieved, including giving DCS Attack/Assault helicopters some much needed publicity. Hats off to you guys. o7

Looks like this took a lot of hard work and dedication. I honesly havent flown on it since DCS was more unstable and having performance issues, and all the objects made it lag really bad. I'll have to try it again soon!

Join us! Hi Entropy, yeah we fly joint operations fairly often with the likes of 229th, BSD, 906th guys. If you're serious about it, I can get you talking with the right people on the right discords. :) Thanks for reaching out. Add me on discord if you want, Wow! The man himself. Yes its true, so far you will be flying the Mi-8 with 3x 8 Mates in the upcoming tournament :pilotfly:. We're a great mix of casual and serious. We like big events, and tight formations. If you wanna hop in our discord as a Guest and get an idea of what we do and how, that's how we've been doing it, and its much easier to understand by experiencing it for yourself! We would love to have you. Add me on discord And yes, we will be ALL OVER the Hind when it finally releases. So you'll probably want to stick around just for that! Yeah we really like our pilotage, dead reckoning, and doppler aided navigation. I don't even have the GPS.

Hi Memphis welcome to the 229th. If you ask your questions on the 229th forum or discord we'll get you squared away. Maybe we can change your mind about the Mi-8 :)

Yes 'Toro 6', unless you want the full callsign, '(A/229) Toro 6 [H]' I'd also like a Mi-8 slot please. 'Huckleberry', or '(A/229) Huckleberry [H]'

Thanks for the info. What a great, active forum! EDIT: Confirmed working in JoyToKey beta with Saitek X52, very handy tool. Quick runthrough, get the zip from here. extract and run (you might need to run as admin) Create profile, bottom left. If you want to be sure it can read your joystick, Settings > Configure Joysticks > Configure Game Controller Property > (you should see your saitek selected now) Properties Press buttons and make sure they're reading. In joystick1 tab, find the button you want to map, select it, and click Edit Button Assignment. Click in the first input box (make sure youre on the keyboard tab) and press 5 on the numpad. It should now read Numpad 5. Click OK. Lastly, Settings > Associate profiles with applications Click Add, and open a separate explorer window Navigate to your DCS installation, /bin/DCS.exe Something like C:\Program Files\Steam\steamapps\common\DCSWorld\bin\DCS.exe Paste the directory path in the application path + exe filename input box, and give it a name in the box above. Also associate it with the profile you just created. Done. You should now be able to leave it open and run DCS, and use your joystick button mapping you just created to center your view in the Oculus Rift. I tested it out first by opening notepad, and clicking the joystick button and seeing that it was as if I had just typed "5". Not sure if JoyToKey stable is a trial that expires, but with the beta version, there's still an option to register, but I see nothing about having a time limit, which is nice, at least so far. Happy Flying

I've apparently got 3 profiles, default, UH-1H, and UH-1H_easy. default profile has ["name"] = "View Center", ["removed"] = { [1] = { ["key"] = "JOY_BTN5", }, }, UH-1H profile has ["name"] = "Center View", ["removed"] = { [1] = { ["key"] = "JOY_BTN4", }, }, UH-1H_easy profile has nothing relevant to center view. I went ahead and removed these 2 things from their respective lua files. It seems like nothing has changed in DCS. I don't even have saved profiles. I just go in and edit the controls, quit, and its the same when i return. Maybe going to All, UH-1H Sim, UH-1H and changing controls there makes different files for each one, like above. Anyway, I still can't get it working... EDIT: I've literally obliterated num5 from all mappings on "general", "uh-1h game" and "uh-1h sim". Replaced them with various buttons on my saitek (joy_btn3-5). Numpad 5 still works, and joybtn3-5 still dont. I've attached my user input profiles, if that's any help. DCS_Config_Input.zip

I have the latest version of DCS, an Oculus Rift DK1, and a Saitek X52 HOTAS setup. I just started playing on the DK1 today, but I'm having problems with head position drift, which would be fine if I could recenter with HOTAS, but alas, I cannot. I can go into controls and map the center view to joy btn 3, or any other joystick button, but it won't actually center the view when I click on the button I just mapped to it. Plot twist: Even when I unmap numpad 5 from being center view, pressing numpad 5 will still center the view. It's like numpad 5 is hard coded to be the only way to center my view, when playing DCS in VR mode. I fly the huey, so taking my hand off the cyclic to press num5 to recenter my dumb head that's looking out the window makes me lose control and fly like a fool. Plus I have to do this every minute or two, so I really can't keep a straight course to save my life now, unless I turn into an owl. I'll add a side note that this isn't a problem when not in VR mode, I can unmap num5, map joybtn3, etc just fine when playing on a regular monitor. I would really appreciate some help or insight into this matter. Thanks in advance, you smart, helpful people! Bango