Jump to content

buur

Members
  • Posts

    580
  • Joined

  • Last visited

Posts posted by buur

  1. ok, I should look in the manual. For the ATC frequencies. There is no correlation
     

    Zitat

    NOTE 1: As there is no correlation between the frequency range on the C-26 remote, the manual frequencies are set automatically at mission launch. Each airfield on the map will have a specific frequency. The frequencies are distributed in equal increments over the frequency range of the C-26 remote. The lowest frequency is always allocated to the aircraft carrier, if available. This is a convention specific to the simulator.

     

  2. Follow your instructions and get the Essex class carrier. But no luck with airbases when I use the preset channels.

    Try to get the airbases manually with the C-26 remote controller. Found the airbases on following frequencies (if the ARC-5 shows frequencies) which not compare to the normal ATC frequencies found on the map.
    ANA 225; map. 250
    KRD 238; map 251
    Nov 249; map 252
    Kry 261; map 253
    MAY 275; map 254
    Think there is a problem in the programming of the navigation radio.
    @scoobie to help your brain try a morse tree for your kneeboard: https://www.digitalcombatsimulator.com/en/files/3345609/

  3. vor 1 Stunde schrieb Rockrend:

    Take a look at this video but note that due to changes in the last update, the previous issue with the CW/Voice switch on the C-38 control unit have now been fixed. It should now be set to CW, as opposed to Voice. Also note that the CW/Voice switch on the C-26 must be set to Voice. This ensures you are using the preset channel/frequency on the C-38, not the manual frequency on the C-26.

    This is not the solution for the above mentioned bug.

  4. vor 5 Minuten schrieb Codawa:

    Und wenn ich grad dabei bin: Wenn ich die Airbrakes auf eine Taste lege und die betätigte fährt das Fahrwerk aus. Hat die Kiste überhaupt Airbrakes? 

    Das ausgefahrene Fahrwerk dient als Airbrakes. Werden auch nur die vorderen Räder ausgefahren.

  5. Stream deck (or the script in the plugin) can read the clickable.lua where the button are described. The export script send the state of the buttons (on/off) to the stream deck.

    If you look in the export script you see [113] = "%1d", -- Master arm. The 113 is the DCS ID. You found these value also with the ID Lookup.

    Oh, and I see that I have forgotten to delete some lines from the Gazell export script, which I had used as basis for the Corsair.

    • Like 1
  6. All your inputs into the game is depending to your frame rate. Button down is detected in the first frame, button release in the second. If you have 10 frames per second on your pc than it is like you have pressed the button for 0.1 seconds. If your pc hat 100 frames per second it is like you have pressed the button for 0.01 seconds. With a higher frame rate your trim is much more sensitive. And therefore we have all individual computers the trim speed is different for each individual player. 

    There is a smallest input possible depending on the frame rate. And this is what you feel as trim sensitivity. 

  7. vor 12 Stunden schrieb Caput_58:

    After a little more study I found the files DCS uses.  They have files at 5 year increments from 2025 to 1985.  Presumably they are interpolating.  And presumably it all falls apart when extrapolated to 1972.  I'm trying to understand the files now to see if additional years could be added.

    You find these files also on the NOAA site and also some explanations how to compute them. 

×
×
  • Create New...