flyco

Rick, your response mirrors my experience - it should be easy but it doesn't seem to be! I have a Streamdeck but have not used it in earnest yet - perhaps I should give it a go. It's just that I do have 24" touchscreen right in front of me that is totally blank when I fly a non-Helios ac. I could just click on it without having to use my Track-IR or mouse - I'm not even looking for any visual feedback (Button press, toggle switch etc).

I set 1 degree nose-down, for take off, start with full aft stick, and use around 8" of boost (rudder full right trim). Once the IAS exceeds around 80, i gently let the stick go forward to neutral and it flies itself of. Once I am above 120 kias, I ease back very slightly, confirm a positive ROC and then retract the undercarriage (not the gear - this is a 1940's RAF aircraft!). Its the bit from 0 to 80 kias and from 120 kias to 0 that I have problems with!!

I use Helios for most of my DCS aircraft. I was even able to modify some of the profiles in the past to suit my way of operating. However, as I approach my dotage, and with the new Helios in use, I feel that such mods are now beyond me. Is anyone able to explain how I can use my existing Touchscreen to accept an input and thereby send a keyboard (or similar) press to DCS? With such a system I could draw a simple push button on my screen (with a suitable LARGE typeface labels), and use these to input the appropriate commands. I plan to use this to input a dozen or so inputs to the less complex sims as the Spitfire and Yak. At present, I use a pair of MFDs with suitable background cards, to achieve this. However, using my large, unused touchscreen, sitting right in front of me, on which I could put electronic titles, would be much easier. In effect I am looking for a 'poor mans' Helios Thanks for any useful input.

Just copy the “default.lua” for the aircraft you are using, and rename it as “F16 MFCD 1.lua”, and again as “F16 MFCD 2.lua”. This should solve your problem and allow you to map any of the MFCD to your other controls (not axes).

Pots with two and a half rotations from one end to the other are available. I have use one with a Spitfire.

I find the rate at which you can change the pitch trim of the Spitfire totally inadequate. I have over a 1000 hrs flying single engine training aircraft (prop and jet), and am well used to the need to trim constantly. When you make a flap or power change, you get to know how much trim you need to put in before fine trimming it. However on a normal aircraft this takes 1-2 secs to move the trimming wheel, whereas on the DCS Spitfire it takes very much longer. I have timed how long it takes the DCS Spitfire trim to move through its full travel and it is over 40 secs, as compared to less that 4 seconds in, say, a Chipmunk. This surely cannot be accurate. Surprisingly, I have never seen this remarked on in these forums. Does anyone else find this a problem?

Thanks Tanuki - that works perfectly.

Is there any way to re-position the AI display? I run Helios, with the bottom right corner of the total display outside my monitor coverage. I suspect that bottom left is the default (only?) position in which this display appears.

Thanks AG. The updated version fixed my problem. I had already found an interim 'quick and dirty' fix by changing the final line of "A-10C/Cockpit/Script/device_init.lua" to point to "Data/Kneeboard Builder Config/ etc". But I feel happier knowing it was a 'bug' and not me, and it is now fixed. Again many thanks.

Thanks for the very quick response. I will install it tomorrow.

Is anyone else having problems with using Kneeboard Builder with both A-10C and A-10C_2 installed. In simple terms I am unable to move the Kneeboard Display to a different location. Having looked through the various .luas it would appear (to my untutored eyes) that Kneeboard Builder is sometimes unable to differentiate clearly between the two A-10C versions. Has anyone installed KB and used it to move the kneeboard, for both versions.?

I run the Huey in Helios, using a 3840 x 2160 Main Screen and a 1920 x 1090 Helios Display Screen - I also have an 800x600 Lilliput to display Kneeboard data. I cannot get the Gunners AI display to reveal itself. I suspect that it is lurking in the bottom RH corner of my total display, an area which is not visible. Unfortunately my cursor will also not leave the bounds of my display and so I have not been able to 'fish' for it and drag it back. Can any one suggest a solution, other than attaching another monitor to cover the 'forbidden zone'. I have had a poke around in the 'UhH-1H\Cockpit\Scripts\AI area, and think I have discovered the area where the problem lies - However, I do not feel bold enough to make any significant mods. Any advice would be welcome.

Stop pestering Capt Zeen. The new A-10C is out shortly - he will have his hands full of more worthwhile activities.

Kneeboard Builder not writing to Kneeboard Builder Config for some ac. I have a problem with some aircraft, notably the Spitfire and the BF-109. It would appear that they are not adding the relevant folders and 5 .lua files to 'Kneeboard Builder Config\Custom Kneeboard Settings'. Consequently the cockpit area is not being rendered. Can anyone suggest a reason, or, better still, a cure for this. I have not investigated whether these are the only 2 aircraft types showing this error. I should have added that I use Helios - although this does not stop other profiles from working normally..

I am seeing a consistent discrepancy between instrument readings on the main DCS screen and those shown on my Capt Zeen's Helios display. This is not a new problem, it was also present in earlier profiles. They are not large differences but do put some of the readings very close to limits. Read-outs on the ground, with throttle closed, are as follows: Main Screen Helios Engine RPM 660 rpm 695 rpm Torque 12 psi 14 psi Gas Producer 88 % 78 % Exhaust 550 C 565 C Is anyone else finding this same discrepancy, and does anyone have any idea how to correct them?

In reply to your question, a pop-up would be helpful. However, the update was very straightforward, thanks to your clear explanation. I will know in future to look on your Helios GitHub. Thanks again.

Thanks, Derammo. That worked perfectly. Excellent response in its clarity and timeliness. No I don't use Discord I am afraid. Since I topped 75, I decided that social media et al was not for me.

After updating to the latest Open Beta version of DCS, I am unable to load any of my Helios Profiles. I am getting a warning notice, saying: "Patching DCS 2.5.6.53756 would fail DCS 2.5.6.5376 failed to apply patch to Mods\aircraft\FA-18C\Cockpit\Scripts\Multipurpose_Display_G roup\AMPCD\Indicator\BAKE\AMPCD_bake_page.lua: CONTENT_NOT_FOUND please install a newer Helios distribution or patches with support for this DCS version" Is anyone else having this problem? If not, can anyone suggest a solution?

I have used Helios for a number of years. But I always wait for a few weeks after an update, just to check on others' feedback. I currently use 1.4.2020.0315. However, when I try to update to the latest version (1.4.2020.0530), it tells me that I have a later version installed and then exits. It also continues to prompt me to update to the latest version whenever i enter Helios. The version as installed works OK. Any suggestion as to what might be the cause?

Exactly the same here. Spring loaded toggle up/down switch moves up or down 2 waypoints ata a time. Along with other change to hard wired switches since last update.

Following on from my last post - and assuming that my assumption is true - it would be nice for someone at DCS to just put up a post saying. "Sorry, it is broken - a fix is in hand" before everyone starts wading through their control bindings. I cannot believe that the adage "Never apologise - never explain", is a good one for any business.

It would appear that the last update revised the .dll files within the A-10C Mods\aircraft\A-10C\bin directory, and a lot of the same files for other ac. I don't think that wading through the keybind files will do any good. We will have to wait for DCS to fix it. I use a bespoke cockpit with a large number of hardwired controls, as well as Helios. I have found a number of my controls have changed their behaviour as a result of this latest update. I am resigned to wait and see.

Falcon87. Spot on! I did use A/P over the sea, and I did operate the switch to disconnect it before coasting, and I confirmed visually that the switch was in the "A/P OFF" position. Unfortunately I checked the switch on my Helios panel, which did show OFF , but I did not check the switch on my main display, which showed ON. This does seem to be a recurrent bug, with both Helios and a hard-wire switch failing to be detected first time by DCS. Stupid mistake on my part, but thanks again. I just wish there was a way to delete this thread before anyone else spots it!

Speed has not changed significantly, other than that resulting from climbing and descending while crossing over hills and valleys. What were you thinking?

I have written a mission which involves an F-16 taking off from Sukhumi, flying north over the sea at low-level (250 ft 420kias, before coasting in north of Sochi to attack Maykop - the load is a C/L tank, and 8 Snake-Eyes. I have flown this mission about 4-5 times, and each time I have experienced the same phenomenon. As I cross the hills, the ac starts to suddenly and randomly pitch down. The pitch is fairly severe, but very short lived and now that I am used to it quite controllable, although I give hill tops a greater margin that normal. After 3-5 minutes it tapers off and eventually disappears. The effect is similar to a terrain-following radar, except that this pitch is down and not up. Because it happens around 20 minutes into the sortie, any Track that I try to check on, has long since flown the ac into the sea. I use the autopilot over the sea but disengage it before turning to coast-in. Can anyone suggest a possible cause for this, or has anyone experienced anything similar?