Derk

I'm planning a pit too. got a nice office chair with netting for an armored seat project, an x-fighter joystick (replica b8 grip), and three 17" flat panels for the mip. All i need is tools and time. But as many a young father knows: time and budget are first to fall. Planning on pilot side and pedestal first, though with expandability in mind.

Okay, so i figured i'd dive into helios to get some export stuff going. But at this time i don't really know what i'm supposed to do. I got the export.lua file copied to the C:\user\[me]\dcs\scripts. Now how do i edit it so i can start adding the uh-1h codes/lines/thingies that are actually exported? And what does helios need to recognise it all? edit: My goal is to get gauges and lights export to work eventually.

Impressive Mnemonic! I am planning on building the UH-1H's main instrument panel. Any chance you could be persuaded to add those gauges to your program? Thanks!

Thank you Upuaut! rep inbound.

I like the pilot banners ED put out for their A-10 and Ka-50 pilots found here. Only i want a huey one! Anyone up for making some?

I believe a proper slick (clean) configuration is planned for the final release.

I have the same problem. I guess the message and completion is a triggered action? Perhaps the value of the trigger is a bit too high. I could also not get enough rpm on the ground, not even with use of the governer increase/decrease switch on the collective. Only during flight the message dissapeared and then after some time came another message saying that the tutorial ended and i was ready for take-off.

imho you don't want a deadzone on you cyclic because that will make it very hard to make those minor adjustments needed for a stable hover. Instead you can set up a curve on your cyclic axis for easier control around the center. I started with 50 and later dropped to 20. That's my happy point, for now. EDIT: I should add that i am flying with a Saitek X52 with 2 coils of the spring tie-wrapped and pro flight rudder pedals.

It switches back on automatically (well, actually it is electrically being hold in the off position) when you reach operational rpm. So no worries about that. That was also in the manual btw..

First flights in. The start-up training has a mean wind in it. Didn't crash though :) Set up a mission in the editor with clear weather and doing okay for a first attempt (imho). A bit of a curve on the pitch and roll axes helps a lot too! (Set mine to 20). Better watch where you put that tailrotor!

Fly time tonight! (just before a seven-day holiday trip). I knew those adult diapers would come in handy one day!

Great, nothing to lose then. Besides, I won't have time for that any time soon anyway! ;)

reading the manual and checklists (i used to be a quick learner grmbl...), buying Thrustmaster X fighter joysticks off the net and pondering on how to make a solid gimbal without powertools for a start. Because my better half said: "knock yourself out!" and i'm going to make sure she'll regret that ;) Only thing is i had to agree to a monthly budget of 30,- euro. So I guess i'll have to make do.

If she does come this week then probably not before thursday. However, i'm afraid 1.2.4. will let us wait longer than that.

There are a few options out there. However, since production is limited and demand low, the price for dedicated helicopter simulation hardware is relatively high. Imho you'd be better off getting an extension for your current hotas stick and build your own collective. Anyway, here are some off-the-shelf sollutions: http://www.komodosimulations.co.uk/index.php?option=com_content&view=article&id=6&Itemid=14 http://www.simkits.com/products.php?groupid=35 http://www.flightlink.com/ http://www.pro-flight-trainer.com/en/ http://www.computerrepairs.ca/Simulator.htm Scroll down for the "for sale" section. and i stumbled upon this page that is pretty much the answer to your post: http://www.helistart.com/helisimcontrols.aspx

Just want to point out to whoever edits that page that the "overhead console" and "flight control system" paragraphs are on both page 1 and 2. Looking good!

Chances are he's too busy to do either. Just around the corner now boys! Mind you though, the wait can be a long straight. Turn on some slow blues shuffle, sip your scotch and wait the wait. See you in the air.

Some people might not like that i suggest this, but i for one wouldn't mind would not mind to pay extra for DLC upgrade packges to a module. They cost time and money to develop, don't they? Rise of Flight comes to mind: You purchase a basic aircraft (much like this UH-1H now) and can buy (unlock) extra equipment from an online store to kit out your aircraft. I don't know if such a system is feasable within the DCS: world structure, but at the least you should be able to release different variants that require the base package to work. Short story: i would gladly pay another 15-20 dollars for a later developed and released huey update package that would bring it up to georgian army or US DoS standards. P.S. Please let's not enter into another pricetag debate here just because i called out some numbers. I'm just thinking out loud about how such upgrades could become a future reality. Thanks!

i'd vote a 'nam era chinook to compliment the cobra (it's coming, right?) and huey. But if you must go attack helicopter then go tigre! But then again, i have a feeling belsimtek will stick with bell for a while to come. so then, osprey anyone? edit: or Kiowa...

Ah, so we're moving forward with anticipation again? Great! I'll start her cold and dark. Then when she has warmed up to me i'll gently sweep her off her feet and we slowly drift away into the blazing... wreckage?!

Thanks EB, you have been clear about possible delays from the start. I don't believe anyone can justify feeling dissapointed too long about not getting their (your) huey over the weekend. Especially if you consider the reason for the delay is, in fact, progress. In the end, all the work that is being done now gets everyone a better simulation experience from the release. It might even save you an open beta build or two. I for one can wait a few more weeks or months if that is what it takes to bring forth a representable beta build.

Exactly Cowboy! We're rotorheads, we've got integrated cooling ;)

Lol, I mean it is my english that is lacking (As you just pointed out with this post), yours is the better formulated one. So, sorry for not being more clear twice!

That's exactly what i meant to propose, only in more clear english. +1 on this solution.

I understand the decision to use the idle-stop. It is easely clickable and the simpit builders will come up with their own mechanical idle stop and starter button and won't use the virtual cockpit anyway. So my problem is not so much with the button being unrealistically assigned. What i understand from the manual though is that as a result of this decision it left us without a proper engine shutdown procedure in that fully closing the throttle doesn't shut down the engine in the sim. I would rather see that the throttle range had a minimum of 6% and then a button assigned to idle-stop to enable the user to fully close the throttle if it's controlling axis or slider is at it's minimum range. This would then allow engine shutdown to be coded in at full-closed throttle, right? And as for the starter button: the clickable one in the cockpit could just as well be the tension adjustment ring on the collective, or even the side of the switchbox if you want to. That would make a lot of people happy without losing the ease of controlling engine start while using the mouse.