Jump to content

ARCTIK

Members
  • Posts

    3
  • Joined

  • Last visited

Everything posted by ARCTIK

  1. Whenever F-16 is cycled between A/G and A/A Master modes - A/A reverts to RWS, and A/G reverts to Azimuth A3 (despite preferences, previous selections and/or DTC programming).
  2. Actually CMDS seems OK now (after a DCS restart) - Maverick BORESIGHT issue persists - even a "hot" start without Bore-sighting seems close - but trying to fine tune a boresight with hot-start shows same behaviors. Several different MP servers were tried.
  3. Describe your problem in detail For F-16C Viper - - - in latest version DCS 2.9.5.55300 - I was hoping that the MAVERICK Bore-sighting would be returned to normal, as stated in Changelog - but it still seems to chase a forward facing bias. Procedure used is an inflight precision boresight as per published procedures - bore sighting each pylon is successfully carried out normally but stepping to consecutive Mavericks demonstrate they are not looking in the same place (offset vertically and/or horizontally just enough that AUTO hand-over cannot take place without manual re-slewing (even after another re-bore-sighting after lock-on). Also, once locked and fired...stepping to next missile with WPN SOI makes TGP slew back to NOSE forward position until TGP is SOI (slewing it all the way back to TGP pointer - but not on bore-sighted center - requiring more manual slewing) Another bug has appeared in Countermeasures. After a CMS program activation - chaffs and flares are suspended - another program will not activate unless mode is switched OFF and Semi/Auto On again - but this will only allow another SINGLE salvo operation. In other words...once CMS UP/DN/L/R/Slap Switch is selected - you are powerless to activate any further expendables - unless you turn CMDS system OFF then ON again Additional comment I am a veteran F-16C only DCS member - very familiar with successful Boresight of AGM-65 on the ground and in the air (favor the inflight method to reduce parallax errors)
  4. Greetings Rudel_chw!

    This is my first MESSAGE on DCS (just joined) - I am having a brand new HOTAS COUGAR issue.  You seem to be an authority/expert on this . . . I have been using these joysticks for almost 20 years (refuse to fly without them since Falcon 4.0).  Since DCS is huge performance hog - Just bought brand new gaming computer for the sole purpose of DCS, however new PC with Win10 not recognizing HOTAS Cougar.  These joysticks work on my other Win10 machine (so I am familiar with process to "modify" patches to correct issue) . . . but CANNOT get them working on NEW machine with CPU/Graphix/RAM more suitable!

    researched the following (6 links):

    https://forums.eagle.ru/topic/218512-another-pilot-who-fails-to-get-his-tm-cougar-hotas-working-on-windows-10/

    https://forums.eagle.ru/topic/142555-tm-cougar-stopped-working-win10/

    http://www.stephenwick.com/thrustmaster-hotas-cougar-on-windows-10

    https://riseofflight.com/forum/topic/51154-hotas-cougar-not-recognised-after-re-install/

     

    I have trouble-shooted all of theese processes - NO LUCK - still not recognized...

    Other than buying a 3rd machine and running Win 8.1 - can you offer any other ideas/solutions (I understand a "fall-update" for Win 10 could be the reason) ???  This brand new SUPER-Gaming PC is a scrap if I cannot use it for DCS F-16C!

    MANY THANKS in ADVANCE!!!

    1. Rudel_chw

      Rudel_chw

      Hello,

      Did you followed this procedure for installing the Cougar dtivers? If so, at what point the procedure failed? Try to describe how you do the drivers install, so that I may have a better view of what might be happening to you.

      bedt regards,

       

      Eduardo

      pd, please send this on a private message, rather than here.

    2. ARCTIK
×
×
  • Create New...