Jump to content


  • Content Count

  • Joined

  • Last visited

About flyco

  • Rank
  • Birthday 06/16/1943

Personal Information

  • Flight Simulators
  • Location
  • Interests
    Aviation, science, electronics
  • Occupation

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Le Cuvier, thanks a million - that was it! I had transferred changes I had made to the 'default.lua' in my A-10C to the A-10C". Usually I annotate all such changes that I have made so that I can find them later - for some reason I had not done so with this one and so did not think to check it. Thanks again.
  2. I have a switch which I use for the AAP Steer Up and Down. It works fine in A-10C. However, in A-10C -II, although I can program it, the switch in the cockpit does not move and the Steer Point is not altered. The Steer Point responds correctly to input from the HOTAS and the UFC on the screen and via Helios. I have got around the problem by assigning the UFC Up and Down switch to my hard-wired AAP switch. However, the switch displayed in the cockpit does not move. I suspect this is a bug.
  3. Sorry, I misread your post. Mine are mounted either side of my touch screen. I did originally try mounting them on the edge of the touch monitor, using just 3 bolts. However, they did interfere with the screen, unless they were spaced well in front, which led to parallax. In the end I left them without any visual inside their frames. I find them very useable that way, although I prefer to use the touch buttons on the main touch display.
  4. Is there any simple way of automatically starting TrackIR with different profiles for specific aircraft. So far as I can see, if you want different parameters for different aircraft (in my case to cater for HMD on the A-10C_2), you have to start TrackIR, enter it, set up the profile you want and then enter DCS. It would be simpler if the parameter could be auto-selected, according to the aircraft chosen. Or at least allow for multiple short-cuts on the Desk-top.
  5. Thanks, Yurgon, that is interesting that you don’t have a problem. Basically, I have set up Track-IR so that if I rotate my head by 20 degrees, the view moves by about 30 degrees. Thus if I need to look in my 5 o’ clock, I only have to turn my head by around 90 degrees. The problem seems to be that the HMD sight moves the same amount as my head. Thus the external view that I am seeing is at 5 o’clock, while my reticule is looking in my 3 o’clock, thus it is well to the left of my sight-line. I will take another look at my set-up.
  6. I recall seeing something about alignment between the Track-IR (with gearing), and the HMD look-direction previously in this forum. This is a problem I have been unable to solve. Basically by the time I turn my head so that I am looking at 90 degrees from heading, the HMD is only around 45 -60 degrees making it unusable. With my aging neck, I do need gearing on the Track-IR to be able to see over my shoulder. Does anyone know of a solution?
  7. I have run Helios for some years, and recently changed to 1.6. It runs fine with all of the standard Capt Zeen profiles that I use (A-10, F-16, F-18, etc). However, when I try to set up Capt Zeen's A-10C_II, it stops at DCS Monitor Setup with the first 5 viewports reported as provided 'DCS Additional Viewports', and then a warning and line which reads "The viewport data for this profile is out of date". When I click on the 'cog' symbol it throws up a tall thin page of data and then exits. It does exactly the same when I try to update the F-16 Ver 1.0 for Ver 1.1. Can anyone suggest a reason?
  8. I have mounted mine on MDF with no hardship. I use M4 screw in fasteners. I also drill a small hole immediately below the centre of the lower edge, to take the connection cable.
  9. Some trim in some aircraft is not available for potentiometer use. Others use the joystick trim button. The only ones I use a pot for are those in pre-1960s aircraft, such as the Spitfire.
  10. You’re absolutely correct grafspee - mea culpa!
  11. 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).
  12. 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!!
  13. 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
  14. 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).
  15. Pots with two and a half rotations from one end to the other are available. I have use one with a Spitfire.
  • Create New...