Gizzy

Was nearly written off in the back of one coming across unseen low power lines at 80 knots hugging the drumlins in the same area... The video depicts one of the rare days the sun was shining on Palace Barracks.. Hovering over Belfast was a constant for many years... and still not gone away yet... Good to see you back Flick..

It may be the length of time that the 'key is actually pressed or pulsed' and interpreted by DCS. For example with my DFD Flight box, the rotary sends a DX pulse for each click, this is seen by my DCS KA-50 Abris rotary as 3 lines.... per click of the DSD rotary - the length of the pulse cannot be changed unless you use an external programme such as autokey.. With a G13 keyboard you can program the key push length, With .005 sec my DCS KA-50 Abris rotary gives 1 line, any more and the number of lines increase.

Keeping on topic, Yipster, have a look at these YouTube videos, really easy style, tutorials broken down into small easily assimilated videos... Then you have ED's own videos, a bit old but still good... There are lots of others about but for me, these worked .. Hope this helps...

AND SO YOU SHOULD, I checked and there was a MOD specific to 229th for objects etc.. that incorporated your early work. :smilewink:

@Starway Donated and got the DL. Great from high up BUT as I fly rotary wings 100% when you are low and dirty, to me, the ground appears totally overcooked and, well, pretty awful a lot of the time.... Just my view now, and of course YOU CANNOT PLEASE ALL OF THE PEOPLE ALL OF THE TIME.... Good Luck... and thanks... Example... NORMAL DCS STARWAY DL NORMAL DCS STARWAY DLC

When you unzip the top level folder name is different. Drill down and Config & Mods are there... This maybe what is causing confusion.... i.e. here are the 2 folder structures above Config & Mods... update: Starways Black Sea map_Update.1.1\__MACOSX\Starways Black Sea map original: Caucasus Map DLC by Starway Hope this helps....

Done... :)

Yes, PC Device sensitivity with the Gazelle in its current form can be an issue and of course greatly influenced by your own set up and equipment. 50% Y saturation as mentioned is fine to start with but I find 70% about right for me at the moment using a TMWH + 12cm ext. In turns, ASA issues aside, with this lady correct pitch will help greatly in co-ordination, not enough pitch and she will always try to level, but it is a balancing act. The sensitivity of the pitch axis can make this problematic. Pedals generally should not be necessary in a co-ordinated turn once estalished, of course you use them to maintain longitudinal trim if torque changes

Hi Vulpes, PC has a lot to do with it.... I used to run it on a i7 Laptop 2.5Mhz and it was not too bad with just a slight lag but on a my current high spec PC all is very, very smooth with no lag nor ASI difference...

Here you go, a mod from DEVRIM http://www.digitalcombatsimulator.com/en/files/668712/

Start at low altitude, 5 - 10m, visual clues easy to read to enable you achieve the right parameters to engage hover. Disengage the collective hoveer to climb to desired un-masked height and re-engage it...

Tnx for coming back 'txmtb'..... I'll leave it a long while....

The new version of TM Target seems a bit of a mess with me, W10 & TMWH, quite a few Throttle & Joystck switches dead when used with within the programme - H4L - PSF / PSM / PSB found in just 2 minutes, gave up after that so there could well be more... Any similar problems or is the issue localised?

Rudder was changed in 1.5 BETA last week.... then introduced into DCS 1.5 stable this week...

As it is working fine with Ka & Mi8 it sounds like the reset monitor action is the culprit. Been there, done that.... Delete the the Uh-iH *hpf and the associated *.bak & *.layout files, replace with a unedited Uh-1H. *.hpf from the download, reset monitors in Gadrocs profile editor and all should be good.

Absolutely Fantastic Capt.... works a treat, perfect.... Thank you..... Mi8, Ka-50 and now the Uh-1H...... you are certainly looking after us rotor heads.... :thumbup: :thumbup: :thumbup: :thumbup:

Correct. Same setting for both, on 1.5 rudder is so much better, no blackouts either on the slightest bump and the skid interaction with the terrain appears more realistic... just in a quick test...

For me, I've found that tuning your stick and collective to suit your equipment, and learning a more sensitive style of flying to say, the Huey, will give good results. Here's a quick vid, note the subtle positioning of the cyclic on lifting to a hover. My kit is TMWH stick (12cm ext) and throttle with a horizontal 15" collective zipped to one of the throttles & Crosswind pedals. Pitch / Roll, no curves, Y Axis @ 80% Collective no curve, Y Axis @ 70% Rudder 15% curve, Y Axis 100%

Autopilot. Couldn't get my head round the Speed & Altitude AP. In game they are a spring loaded switch and engagement with the mouse seems random.. Mapped to a button switch was no better neither... BUT mapped to a ON / OFF 2 way switch, all is good - working fine... Maybe the spring loaded toogle switch on screen needs some TLC or perhaps make it a 3 way ON(alt) - OFF - ON(vi) switch rather than a toggle. Just a thought... incidentally liking all aspects of the airframe realising of course this is just the beginning... Congrats on that lads..

Originally I put in 25% curves, then after a chat with an experienced guy involved in testing the model during development, at his suggestion, I dropped the Y axis on pitch and roll to 70%, in fact even go as far as 50% and work up, it is easy in DCS2 in flight so to speak. This (70%) works for me with no curves on TMWH setup + 12cm ext. Remember not to fly the craft like the Huey, absolutely minimal stick movements.... if it is getting out of hand, centre stick and pedals and wait a little, let the systems stabilise it, then gentle movements and away you go. If you bank, just centre the stick to return to level... not a large opposite stick movement.. Hope this helps a little..

Thanks for this FR, your time is appreciated :)

Pilot initiated and random within a tine period.... I'll be interested in that, could you let me know how, please?

Recently I was undergoing formal GS IP training and it was a bit fast and furious like, well away from the normal ‘gentle’ slick stuff, and then the IP introduced auto rotations at low level in various situations and speeds. Basically, I suck a bit and need to practice. Reaching over and hitting the ‘F’ key is always premeditated and always I would wait till I was level and there was a bit of clear ground ahead! To make things a little bit more realistic I wrote a simple autohotkey script that cuts of the fuel at a random period within a specific time period. #NoEnv SendMode Input SetWorkingDir %A_ScriptDir% ^j:: Random, Time_To_Wait, 60, 300 ;Get a random number between 1 min and 5 min Sleep, Time_To_Wait * 1000 ;Sleep deals in miliseconds, multiply seconds by 1000 to get ms Send, {f down} Sleep 15 Send, {f up} returnHere, once initiated, the fuel will cut off at a random time between 1 and 5 minutes.... And well you have to land whatever you are up toooooo Autohotkey is free, small and uses little resources. The script when compiled and running uses around 1.2mb of memory with me... Negligible... Have autohotkey installed and run the script or just run the f.exe (just the script compiled) and then fly. To initiate you just hit ‘CTRL J’ and the timing process will start BUT ONE issue though, is that if you hit ‘CTRL J’ whilst DCS has the focus it traps the keystrokes and does not pass them through to autohotkey. So a work around is to have notepad running open on say, a blank txt file.... THEN.... (1) Start DCS as normal and fly. (2) When you want to initiate the timer, ALT TAB to notepad, hit ‘CTRL J’ and ALT TAB back to DCS and continue to fly.... (3) and of course the fuel will cut off at some point and for sure you will crash some.... This is repeatable as many times as you wish.... SP or on the server, do it together with mates on the server... whatever.... It certainly makes autorotation training more realistic and dare I say it, more fun.... The f.ahk and f.exe zipped (500Kb) can be downloaded from my Google drive here https://drive.google.com/open?id=0B7FaeRwacSmPZlVLZnZCU25KVDA Autohotkey can be got here https://autohotkey.com/ If you use it and have any problems just shout.... # Remember this now....

The Ka-50 manual is excellent in many manoeuvre descriptions... It would be good to completely master these before moving on to other things... Turns and Spirals .................................10–35 Climbing U-turn (“Combat” Turn) .............10–36 Break Turn .................................... .....10–38 Climb................................................. 10–39 Climbing Turn ...................................... 10–40 Dive .................................................. 10–41 Flat Yaw Turn...................................... 10–42 Acceleration and Deceleration at Maximum Rates. 10–43 Manoeuvring at Low Altitude ................... 10–44 Flying with experienced players in different scenarios is very beneficial..

Now that I have a better rig and moving onto other rotary airframes ..... This one I got back with the enemy destroyed and the engines cut out 2m above the runway and I landed just fine :) Anyway I digress..... I had another look at Capt Zeen’s Helios as against the Hogtouch variant Ikarus for my usage. I found that Capt Zeen’s profiles for the Mi8 and more importantly the Ka-50 with the display screens really do make a difference to my flight enjoyment with my layout which is 3 screens - 2 vertically stacked for DCS and repeater instruments, and 1 off to the side for TS, Notes, Web, Manual etc... Exporting of viewports is really required for the Ka50 screens and requires me setting DCS to a resolution of 1920 x 2160 with the GUI set at 1920 x 1080 - this does cause a few problems with the sizing of the control indicators as these are based in the lua files as a function of the DCS resolution rather than the GUI... Using some pointers from Hawkeye, for my 2 monitor vertically stacked configs with DCS set at 1920 x 2160, I modified the lua files for the Huey, Ka50 & Mi8 to place the control indicator at the bottom left of the top monitor, sized appropriately and the indicators transparent background removed... Just my taste that's all.. I have them in JSGME compatible folder structures here if anyone wants to use them... https://drive.google.com/file/d/0B7FaeRwacSmPYmdDYnRvYlJRZDQ/view?usp=sharing Capt Zeen is working on a Huey profile and hopefully this will be out soon... There is a lot of work in these... he has a 'donate' button on his website http://www.captzeen.com/helios/index.asp - if you like and use them, maybe consider some beer money... :) Below are some pics that may make some sense of this and 2 videos, 1 KA50 & 1Mi8 demonstrating Capt Zeens profiles in use with 2 screens - both monitors are 1920x1080 but remember in RL, the top one is 32” and the lower one 24” R06-hwk0V-M GwdT7uC1MAM