Jump to content

Floyd1212

Members
  • Posts

    1019
  • Joined

  • Last visited

Community Answers

  1. Floyd1212's post in Uncommanded AGM-114K Firing was marked as the answer   
    I replayed your track and saw what you were describing.
    I then replayed it again, and took control before you lifted off, and was unable to reproduce the issue with my setup.
    I would double-check your binds and make sure you don't have something silly bound to your Weapons Trigger Switch - Second Detent, like maybe your left mouse button? 😉
  2. Floyd1212's post in FCR fix and slew - bug or feature? was marked as the answer   
    I think you will get a little push back on this statement...
    Raptor9 had a great post a few days ago:
     
  3. Floyd1212's post in Hot start mission issue was marked as the answer   
    I’m not seeing any new behavior with the collective not syncing on startup.
    My guess is you have another axis bound to the collective and there is “competition” for what position it should start in, then nudging your physical collective sets it back to zero.
    Having controllers get auto-assigned an axis is something we have seen after patching. 
  4. Floyd1212's post in Power lever problem was marked as the answer   
    With no binds for the throttle axis at all, and using the mouse to raise the throttles in the cockpit, the problem still occurs?
    Check that axis across all your controls. DCS likes to auto assign axis to controllers that you never intend to use for those functions. 
  5. Floyd1212's post in VPC collective control was marked as the answer   
    I think what you are seeing is normal.
    I hopped into a cold aircraft and yanked on the collective from 0-100% and the in-game animation of the controls is delayed some.
    I guess I never noticed it because it is a non-issue when actually flying the aircraft around.  Your goal is to be smooth with the collective, so you don't over/under-speed the rotor system, so keep your adjustments small and slow.
  6. Floyd1212's post in No Acquire with L Hellfires was marked as the answer   
    You are talking about getting target data for a Lima prior to launch?
    Do you see the TARGET DATA? prompt at the bottom left?  If not, de-WAS missiles and WAS again to start over.  You may have data stored from a previous spot you were lasing.
    Your ACQ source doesn't matter in this situation.  And whether they hit or not is a totally different question.
  7. Floyd1212's post in Where is the Rocket Steering Cursor? was marked as the answer   
    You don't have rockets WASed.
    This indicates your CPG has rockets WASed:

    This also indicates you don't have rockets WASed:

    When properly WASed, as shown in the snip from the manual below, notice the differences in the areas I boxed in blue above:

    You must use the binds on the cyclic or HOCAS to WAS weapons, not by pressing buttons on the MPDs.
  8. Floyd1212's post in IHAADS boresight fail was marked as the answer   
    Agreed.  An option to automate the process would be helpful.
    In the meantime, the saved Snap View is the best answer.
    Bring up WPN page Press Boresight Press IHADSS Hold down Snap View button Press BS NOW Release Snap View button Yes, it takes a few minutes to set it up the first time, but then you avoid the hassle for each cold start going forward.
  9. Floyd1212's post in Gunner seat manual tracking control issue? was marked as the answer   
    Maybe post a screenshot of all your analog axis bindings for the CPG seat?  It is probably double assigned with your pedals or some other controller.
  10. Floyd1212's post in Show/Hide George wont assign to HOTAS properly? was marked as the answer   
    This seems to be working for the rest of us.
    Don't forget, you need to assign the show/hide button for both the PLT and CPG seat.  Then the U/D/L/R functions of the hat are assigned in the George AI Helper list.



  11. Floyd1212's post in Fuel Transfer Failure...low pneumatic pressure was marked as the answer   
    This appears to be a known bug, mentioned in the Bugs and Problems forum:
    https://forum.dcs.world/topic/332503-external-fuel-tanks-and-hot-vs-cold-starts/#comment-5280033
     
  12. Floyd1212's post in How to use stored target points was marked as the answer   
    Page 240 of the new manual describes the procedure.
    Before you can type in a point using the KU you need to press L1 for "POINT>?".
  13. Floyd1212's post in Hidass brightness in cpg was marked as the answer   
    Page 74 of the (new) manual does a good job of explaining this.

     
    8. SYM Rocker Switch. Controls the brightness level of displayed symbology on the TDU or within the CPG’s HDU. When the CPG’s selected sight is HMD, the symbology within the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the symbology brightness on the TDU will be adjusted. The symbology brightness may be incrementally adjusted using short presses, or continually adjusted using continuous presses.

    9. BRT Rocker Switch. Controls the overall brightness level of the TDU or CPG’s HDU. When the CPG’s selected sight is HMD, the overall brightness level of the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the overall brightness level of the TDU will be adjusted. The brightness level may be incrementally adjusted using short presses, or continually adjusted using continuous presses.

    10. CON Rocker Switch. Controls the contrast level of the TDU or CPG’s HDU. When the CPG’s selected sight is HMD, the contrast level of the CPG’s HDU will be adjusted. When the CPG’s selected sight is TADS or FCR, the contrast level of the TDU will be adjusted. The contrast level may be incrementally adjusted using short presses, or continually adjusted using continuous presses.

    11. Asterisk Button. Resets the overall brightness and contrast levels to their default settings. When the CPG’s selected sight is HMD, the overall brightness and contrast of the CPG’s HDUwill be reset. When the CPG’s selected sight is TADS or FCR, the overall brightness and contrast of the TDU will be reset.
  14. Floyd1212's post in Anti-Torque pedal rigging since DCS 2.7.18.30348 Open Beta was marked as the answer   
    Here is a thread with a SME discussing the tail rotor thrust after the changes made in OB ver 2.7.18.30348.
     
  15. Floyd1212's post in Calibrate boresight via button? was marked as the answer   
    This is where the “cursor select” function on your analog stick comes into play.
    When you have the circles lined up and centered, just press select on your analog stick and you are done. You don’t have to take your eyes off the boresight reticle. 
  16. Floyd1212's post in Creating Map Objects in Mission Editor was marked as the answer   
    When you drop a unit in the ME you can check/uncheck the option to "Hide on MFD" for the group.
    If it is unchecked, the group will show up in the pre-planned "threats" category in the TSD.  It's been a while since I have played with it, so I can't recall if only some unit types show up, but I know it works for SAM units.
    You can search for "threats" and find the pertinent threads.
    In the future, when/if ED implements the Data Cartridge feature you might be able to plan out a mission and then preload points into the TSD at mission start. 🙏
    Edit: Found these threads:
    https://forum.dcs.world/topic/319135-placing-targets-in-the-editor/
    https://forum.dcs.world/topic/301194-option-for-automatically-importing-mission-editor-targetthreat-control-measure-points/
    That second thread is older, and I think some of the issues have been improved upon, but still not perfect
  17. Floyd1212's post in Is having Kilo and Lima hellfires on the same rack possible was marked as the answer   
    ED has indicated they are looking into it.
  18. Floyd1212's post in Random Trim issue was marked as the answer   
    We have seen a few cases of trim just straight-up not working. In the two cases I can recall, the solution was to reinstall DCS.
    For example:
     
  19. Floyd1212's post in Apache take-off with no Rudder input was marked as the answer   
    There was a patch a while back that changed the "neutral" position of the tail rotor blade pitch.  (I'm sure you can find some discussions about it if you search a bit.)  This change means there is now less pedal input needed for a given amount of thrust at the tail than there was. 
    In addition, the SAS is providing some assistance if you pull gently into a hover.  Even if you have your feet off the pedals, you can see the green mark giving it a little left pedal for you when needed.
  20. Floyd1212's post in Hellfire Missiles lock on and moving targets was marked as the answer   
    You can also apply curves to the LMC axis to get whatever sensitivity you are looking for.  I will say that having a quality thumbstick, like on a game controller, makes it much easier.
    Also, you are using IAT to "lock on" to targets now, right?  It wasn't available when this thread was started last year.
  21. Floyd1212's post in George / Memory Problem was marked as the answer   
    Like NeedzWD40 said, are you using [George Hat] Short Left to cycle him through his weapons, or are you WASing the weapon for yourself in the back seat?
    Telling George what weapon system to use is different than the system you are using from the back.
  22. Floyd1212's post in Back scatter warning was marked as the answer   
    I looked it up in the Quick Start Manual. On page 304:
    I only recall seeing the warning a couple times, but now I know what to do if I see it again.
  23. Floyd1212's post in First stage trigger behaviour was marked as the answer   
    I'm not seeing this behavior.  Maybe a control bind conflict?  Maybe a hardware issue?
  24. Floyd1212's post in Placing targets in the editor was marked as the answer   
    You need to make sure the "Hidden on MFD" is unchecked for the group in the ME, then they will show up in the threat database at the mission start.
    Some units, like SAMS and AA will show up as TGTs, where other units, like armor will show up as Control Measures.
    To see the CMs on the TSD, make sure you go to TSD > SHOW > COORD SHOW  and enable ENEMY UNITS.

  25. Floyd1212's post in Lasing crosshair disappears was marked as the answer   
    nullA screenshot of what you are seeing on the IHADSS and your TSD page when this happens would be helpful. 
    Like mentioned above, you want to make sure the Acquisition Source is set to TADS in order to see where the CPG is currently pointing the laser.

    If the TADS is looking 90 degrees off to the right, you won't see the dashed reticle unless you look off to the right for it.  The little dots around the LOS reticle will tell you where to look for it in relation to your current head position.

×
×
  • Create New...