Jump to content

Diemos

Members
  • Posts

    176
  • Joined

  • Last visited

Posts posted by Diemos

  1. Maybe an issue with the way your monitor scales?

     

    In the Nvidia settings, there's a section "Adjust desktop size and position", and in there you can click on the "Size" tab to enable desktop resizing in the case of overscanned images (part of the image is offscreen)...

     

    Your mileage may vary, and other settings may apply.

  2. Others will supply the path, but you have to download the SPECIFIC beta version. It installs parallel to your current installation (puling over some files directly, rather than downloading the entire game (which is clever)), and you can run either the beta, or the release.

     

    The release will update after the beta period...

  3. As above, but with one additional step:

     

    For EACH controller, go to the options page, click in the column for the controller you are setting up, click Load Profile button at the top of the page, then find the matching profile for THAT controller to load. This must be done for every controller, and for EACH aircraft!

     

    If there were one GIANT wish I could ask for, it would be a "Load All USER Profiles" button...

  4. My guess would be it's at the end of the default Take Off and Basic Flight Maneuvers training mission, where you set up the jet at 040, FL 70, and 280 kts, then do a 360 level turn.

     

    Not sure why the completion isn't triggering, but try rolling back out at 040 once you've completed the first (only) 360 turn? I believe he awards you the mission once you've started to roll back level at 040...

     

    But no promises! ;)

  5. What would happen if you were to adjust the pitch knob to match the ACTUAL pitch up of the plane while sitting on the ground? Could it be that the errors are accumulating so radically from the original 5 - 10 degree pitch error of a taildragger to ground "level"?

     

    Haven't tried it myself... Just spitballing...

  6. If this is the case, a quick disconnect and reconnect before starting DCS should fix the problem as well. Though that could become rather tedious if you have to do it after every time you put your machine to sleep depending on how frequently your machine takes a nap.

     

    :) All I'm suggesting is that you wiggle the stick a bit before you start the sim...

     

    There is a setting deep within Windows that allows it to "turn off the USB" to save power. A little wiggle wakes it up, such as moving from off to idle and back to off...

     

    Probably not this issue, but it never hurts to have information...

  7. Possible issue: Even with the controller calibrated and active in Windows, if you don't "wake it up" (after a restart, or coming out of sleep mode), it is sometimes not recognized in games until you move it around some... A Windows issue, not DCS...

     

    Don't know if you already do, but maybe get in the habit of moving all your controllers through their maximum before you start the sim and see if that helps?

  8. I've never had Bitdefender list anything as blocked, nor anything detected as a threat, so I can't even say it's being blocked. In fact, DCS has never been mentioned in the Events list in any capacity.

     

    The ONLY reason Bitdefender comes into the conversation is I have yet to see anyone with the updating issue NOT have Bitdefender...

  9. I'm assuming that it's an issue with Bitdefender only because everyone who has commented they have the issue agrees they have Bitdefender as well...

     

    At the very least, the coincidence is enough to, perhaps, warrant an investigation by ED?

     

    The issue itself can be avoided by simply clicking "No" on the warning dialog, but I find it hard to NOT update software when I'm dealing with a reputable company.

  10. Obviously not a huge issue, as (apparently) not many people use Bitdefender, but I recently switched to Bitdefender after it scored well in a recent PC Gamer round up, so it might become a greater issue if others do the same.

     

    My question is; why doesn't it happen every time? I do a reinstall, and things work fine, usually just long enough for me to get all my controllers set up again, then BAM! "Updating myself..."

  11. Since you have discovered the 15 is the "bad" module, is it possible that a file was corrupted in the MiG-15 installer? Have you tried redownloading the 15, either standalone file from the site, or through the Module Manager?

     

    Not sure it would help, but if all else works without the 15, you might try...

  12. There are no keyboard commands when you select "Axis Commands" from the Category dropdown list. You will see all the keyboard commands when you select ANY of the other options from that drop down...

     

    The Axis Commands is a special section dedicated ONLY to analog controllers.

     

    Not absolutely certain, but I believe most (if not all) of the functions listed in Axis Commands are repeated in the other drop down selections ("All", "Flight Controls", etc.), and the default keyboard commands are listed there.

     

    If this is not the case, then of course you should reinstall...

  13. The indicated course shown in the course window in the upper right is manually set to the desired course/approach (set it to runway heading, etc.).

     

    The course shown by the needles in the instrument itself show the current course you are flying.

     

    if you want to approach from a specific heading, fly in such a way as to align the actual course (needles) to the desired course (window).

×
×
  • Create New...