Slartibartfast

I seem to be getting thwarted right from the offset by not being able to tune my ADF for some reason. While I'm not able to find a signal at 430MHz I am able to pick one up a little higher in the spectrum and although this signal is broadcasting the Morse code for "LU" (._.. .._) the ADF arrow on the compass is not pointing anywhere near 120°. Am I doing something wrong?

Well, finally made it through. I had to trim the heli and use the Helios dashboard to input the frequency but it works well enough. The good thing about the Helios dash is that you can see much more precisely what frequency you are tuning. It probably isn't as accurate in terms of simulating a true Huey aircraft but given it enables you to actually enter the correct frequency while you keep one eye on the horizon it did allow me to get through. By the way, I have no idea if the co-pilot is actually taking the controls or not.

I have to say I'm finding this mission most frustrating myself! When your co-pilot says "Let me take the controls" is there something you have to do to actually give him control? First time I just thought he was going to keep the heli flying straight and level so just stopped flying and looked down and started fiddling with the radio buttons only to discover a few moments later we were horrendously out of control. I madly grabbed the stick in an attempt to arrest control only to snap the rotor off and plum it to my doom. Not being exactly sure why the copilot lost control, the next time I was sure to trim the aircraft before adjusting the radio using Helios dashboard on a second monitor so I didn't have to "look down" as such and did manage get the right frequency tuned in however I smash my tail rotor on landing by accidentally pressing the "force trim" button at an inopportune time —my mistake I know. The next two times I tried flying using the Oculus Rift and crashed the first time as once I tuned in the frequency he said I was given back control however I spent too long trying to turn the radio from "OFF' to "ADF" and crashed while trying to turn it on (acturly turning on the ADF is not so easy to do while using the Oculus Rift). The next time I was sure to turn ADF on while on the ground then tuned the frequency once the co-pilot had control bit didn't realise it had in fact picked up the "far north" beacon and flew way off coarse without realising (note; it's actually quite hard to read the compass in the Oculus Rift). And finally this last time, fed up with not being able to read the instruments with the Oculus flew without it but had the heli crash again while it was allegedly under the co-pilots control again! I know under the "cheats" menu there is the "Active Pause" option which allows you to do things like tune the radio whilst paused, but is there a way to do this without resorting to such "cheats"? I mean your copilot actually says he's going to take control but simply doesn't do it, or am I missing something?

Oh, wow. That has worked perfectly! I so wasn't expecting it to work but yup, works like a charm (: It turns out I did actually have a "Saved Games" folder in my "...\Users\Slartibartfast" folder, I just didn't recognize it before as it has a different looking icon to regular folders but yeah, sure was there and it had a "DCS" folder inside it. I had to make the "Scripts" folder inside the the "DCS" folder but once I made it and copied across the "MIG-21" Export.lua file it all works perfectly. Thanks for your help. I'm most impressed. (:

Sure, I can try creating the 'Saved Games' folder and putting the MIG-21 Export.lua file in there but I don't relay expect for it to work, but I'll give it a go when I get home :)

The instructions say to copy it into "C:\Users\yourusername\Saved Games\DCS\Scripts" however I don't have such a folder so searched for my existing 'export.lua' file and found it in: C:\Program Files\Eagle Dynamics\DCS World\Scripts So I renamed the "Export.lua" file that was in that folder and copied in the file located in this package (which I got from the top of the downloads page). Cheers, Slarti.

Hey there Capt Zeen. I have just started flying the Huey and am trying to implement your UH-1H profile accordingly. While I am able to have most of the buttons and switches on the panel update the cockpit in DCS I am unable to have anything in DCS reflect in the Helios panel. I have tried using both the "export.lua" file from with in HU-1H package as well as the one in the MIG-21 package (listed a the top in the green notes). I am also using the "UH-1H default keys for lastest DCS versions - 29/Sep/2016 ( use it for DCS v1.5.4 +)" key bindings. Any idea why I am not getting anything from DCS reflected in the Helios panel? Attached are my Helios profile files. (the "..._port..." is because I have my second monitor in a portrait orientation) HUEY_V1.0b_eng_port.zip All the best, Slarti.

Arr, wonderful! That appears to have fixed it. Thank you. :) :)

I'm new to DCS and a rank beginner in the Huey, but I just noticed today that there is a substantial delay between my moving the joystick and the cyclic moving in the sim. It seems there is a maximum rate of travel and it takes about 3 seconds for the cyclic to travel from full left to full right no matter how fast you move the joystick. The collective suffers the same delay however the throttle and rudder peddles react instantly. I check both the TF-51D and the Su-35T and all axis react instantly in those, so it is only the Huey that appears sluggish. Is this normal? EDIT: Curious. I am having this problem in the "Elbrus Rescue" mission. I was surprised I hadn't noticed this issue when I was doing the training exercises so just went back to check and surprisingly the cyclic and collective controls react instantaneously in the training exercises (but not in the "Cold Start" exercise). However when I attempt to try the mission again they're sluggish again. Is anyone else experiencing this? It seems very strange :joystick:

When doing the "Cold Start" training exercise I can hear the instructors voice perfectly well until he says "Turn on the AN/ARN-83 ADF reciever by setting the Mode switch to ADF" and I activate the radio. From then on I really struggle to make out what he is saying. I have tried adjusting the sliders in the "Audio Options" menu but it seems both the radio crackle and the instructors voice are bound to the "HELMET" slider. When continuing on to the next instructed exercise the radio crackle seems to be fine though. P. S. Any reason "HELMET" is in all caps? It's not an acronym or anything I'm not familiar with is it?

I've kind of hit the wall when I got to designing the spring return mechanism I'm afraid. You can see my progress in the SimHQ forum if you're interested though.

Wow, I just stumbled across this discussion and devoured every post in eager anticipation of the result but just a few posts from the end was surprised at how the wind just seemed to fall from the sails. What's happened? For my part I have been working on building my own joystick but ran into trouble when it came to designing the centring mechanism so have been scouring the internet for Open Source/DIY threads about joysticks when I happened across this one. I absolutely love the concept of this project and would like to encourage its continuation in any way I can. I myself am a software engineer/developer with many years of experience and would love to contribute to this project however I am a rank amateur when it comes to electronics, but do let me know if there is anything I can do to contribute. The reason I am designing my own joystick is that I am wanting to build a sim-pit that represents the ergonomics of a glider and have been completely unable to find a suitable joystick for such a build. The best I can find are helicopter cyclic controls however they are extremely expensive and are still a relatively poor approximation of a gliders control stick, so I've been building my own. I have run into problems though when it comes to implementing the return to centre spring (especially if you consider trying a add a trim control to the mechanism) so this FFB approach seems perfect for my needs! For my part the joystick I'm building is to be about 250mm in length but will only require a relatively light touch in terms of feedback.