Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by jjohnson241

  1. I have the same problem. I repaired my Beta DCS installation but same problem trying to apply update. I then reinstalled the Beta and during the redownload of modules the message "I-16 not authorized" was received. I excluded the I-16 from the module installation and the installation completed. I now have an updated Beta but without the I-16 installed. Obviously, the Beta update created this issue. Please repair.
  2. Autostart does not start plane. Engine fires then quits immediately. Appears that Magneto switch is set to "Off" by Autostart script when engine fires.
  3. use Autostart/Stop regularly and have since day one. It's not a "Cheat", it's a preference. Don't understand how anyone would think it's a cheat to use either command.
  4. Can you post your "all is right" file here? Thanks
  5. Thanks for the addition of AUTOSTART/STOP in the Viggen. Please add the capability to map both commands to a HOTAS or Joystick, etc., button as is typically found in other DCS aircraft. Thanks
  6. Same problem....solved. I deleted each module where DCS was asking for the Authorization key by using the Module Manager. Note that the A10A, Mig 29, etc., remain available in FC3 after deleting the unique module in Module Manager. Only problem using the Module Manager is that a restart of DCS is required after each module is deleted. Clumsy but it works.
  7. Hi, I'm getting Authorization messages requesting Authorization codes for C/A and all the modules that are found under F/C since applying the update. The initial message says there are 2 days remaining under the authorization. I license all DCS modules except C/A and the stand alone modules duplicated under F/C. I have never seen these messages before today's update. I tried a repair after disabling my A/V. That had no affect on the problem. I've attached my log files for your reference. Help please! Thanks Logs.zip
  8. I was reacting to the Module Manager in the Release version asking me if I wanted to download and install the JF-17, then telling me that the module was "Invalid". If the JF-17 is not yet ready for the "Stable/Release" version, fine, then please tweak the Module Manager in the Release version accordingly.
  9. [REPORTED] Can't Install the JF-17 using Module Manager on Dec. 24th Rel. Branch As the title says, I'm getting an error from the autoupdater that says"ERROR: Unknown module DEKA_JF-17". This is in the release version of DCS after application of the 12=24 update. Anyone help? Autoupdater log attached. Thanks https://forums.eagle.ru/attachment.php?attachmentid=223673&d=1577201984
  10. Hi, I'm getting an error from the Auto-updater that is preventing the download of the JF-17 by the Module Manager in the release version of DCS. This is after the update of the Release version today (12-24). I've attached the updater log that reflects the error. The error is "ERROR: Unknown module DEKA_JF-17". Anyone help? Thanks. autoupdate_log.txt
  11. Hi, :ooking at the Change Log for the 10-16-19 update, the missing key mapping for the ALT GEAR Handle remains unaddressed. Please tell us when this will be corrected. Thanks
  12. I see in the known issues list that the ALT Gear Handle is "not clickable". I just want to add that the ALT GEAR Handle is also not mapped to any key command and consequently the gear cannot be raised or lowered using a joystick button or key command. If that's the same as "not clickable", my apologies.
  13. Hi, In today's Open Beta update, the change log includes the key bindings for the Nose Wheel Brake On/Off. I can't find the key binding in the control list. Did I miss something?
  14. In the Cold Start quick mission, with the cockpit instrument panel in shadows, I cannot see the nose wheel brake switch nor any detail around that area of the panel. New textures did not help.
  15. Yes, that's the one I'm referring to. It's not mapped under any section of the key binds nor in the Axes.
  16. No Key Binding for Nose Wheel Brake As per the title. The Nose wheel brake lever is impossible to see in a dark cockpit. I have a warthog hotas and I see many other bindings missing as reported here. Please review and repair asap.
  17. Don't understand how you can develop without one.
  18. Hi, The VKB software "T-Link" won't detect the VKB Rudder Pedals after updating to Win 10 V1809. That means "differential brakes" cannot be configured using the MKiV pedals. The V87.05 Device Config software appears to be working under Win 10 1809. If anyone here has a fix for T-Link please advise. I've opened a thread on the VKB Tech Support forum but no response yet.
  19. After a few adventures with the Configuration Software, I finally got my Warbrd configured and calibrated with the Warthog grip. Everything appears to be operational regarding buttons and axes. I downloaded the latest (Rev 9/28/18) from the .eu store download page including the User Manual for the configuration software (note: not the previous "lite" version). The manual is ok but could be clearer, particularly in describing the step by step instructions to bring a brand new controller (base in my case) to life. Virpil, as a suggestion, put the manual and a new controller in front of a non engineer and see if they can follow the manual to configure the controller. I used the stock springs and cams with the Warthog grip. Feels pretty good but time will tell how it "flies". I had used a 3" extension on my Warthog stick to overcome the "sticktion" that we all know with the Warthog. I may try the extension with thw Warbrd but as it stands now it does not appear to be necessary. Finally, the Warbrd feels great and I'm looking forward to using it in DCS and elsewhere.
  • Create New...