Jump to content

Sport

Members
  • Posts

    577
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Sport

  1. https://alert5podcast.podbean.com/e/episode-05-launching-into-2019/

     

    10 January 2019 - Episode 05: We're back! The guys are excited to be back and over the New Year's hangover, catching up on the exciting happenings of the holidays and what is to come for the New Year. In the news, Dutt finally got IL-2, some interesting updates coming to the DCS F/A-18, and an exciting module announcement from Eagle Dynamics. No interview today, but the guys chat about VR, their personal home control setups, as well as their choices for flying when they're on the road!

     

    We welcome your feedback!

     

    Join our Discord!

    https://discord.gg/3wDMSSb

     

    Contact Us!

    Email: alert5podcast@gmail.com

    Twitter:

    Facebook: https://www.facebook.com/alertfivepodcast/

     

    Come Watch Us on Twitch and YouTube:

    Tricker:

    Sport: https://www.youtube.com/c/DCSSport

    Dut:

     

    Time Stamps:

    0:40 - Introduction

    1:18 - Opening Discussion and Catching Up

    20:45 - Dutt gets IL2

    22:45 - DCS Changelogs

    26:00 - F/A-18C Changes

    28:15 - F/A-18C Mini Update from Wags

    32:40 - F-16 Talk

    35:10 - MIG-19P

    38:05 - MI-24 HIND

    39:28 - P-47 Thunderbolt for DCS (Warbirds)

    41:47 - A10/KA-50 Updated Cockpit Textures

    43:45 - Middle Eastern Map

    46:08 - IL-2 Changelogs

    50:40 - IL-2 Module Updates

    53:30 - Hardware Setups (VR)

    1:01:00 - Our personal Setups

    1:10:00 - Flying on the road

  2. Whether VPC devices can or cannot work with VKB grips, one should ask VPC.

    VPC base controller as we believe only recognizes axes signals sent by VPC grips.

    VKB F14 grip will be equipped with Gunfighter compatible electronics capable of working with both buttons and axes.

    Whether VKB F14 (Warthog version = buttons only, no axes) will work on VPC base, we have no idea, and explicitly refuse to promise.

     

    If it works as an axis, then sounds like that's great for us, but if not and it reverts back to a push button, not all is lost their either!

     

    Thanks for the response!

  3. I think it has changed. They removed the dot/lock indicator.

     

    Hold the target in the sight until you get the tone. The seeker see's it but it's not locked yet. Wait until the tone pitch changes, now it's locked and can fire.

     

    It appears aircraft aspect is now a factor when determining if the seeker sees the target.

     

    I made this last night, but used a combination of in-game and other sound. As you can see, though, there's no lock indication, but the missile guides just fine:

     

  4. IIRC there was a yellow dot at the bottom center of the sight which turned green with a valid lock (thermal signature). I haven't booted up CA in a while.

     

     

    For some reason, I can't get a yellow dot or lock at the bottom, do I need to turn the weapon system on, or is it buggy in the current build?

  5. Been trying out CA a little bit and wanted to play around with human controlled MANPADS. For some reason I'm not getting any lock tone or indication while using the Stinger or Igla. Should I be? If so, how do I activate the weapon system.

     

    I am able to shoot and the missile tracks, but no lock indication or tone

  6. @Sport

     

    I believe MOOSE has this kind of behaviour already built-in.

     

    https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Functional.Sead.html

     

     

    Features:

    -When SAM sites are being fired upon, the SAMs will take evasive action will reposition themselves when possible.

    -When SAM sites are being fired upon, the SAMs will take defensive action by shutting down their radars.

     

     

    I've never used it, though. Might look into your mission tomorrow, see if I can reproduce your trigger logic in a single MOOSE script.

     

    EDIT: Can you change the A-4E-C aircraft in your mission to something DCS generic like Su25T? Your mission can't be loaded unless the A-4E-C module is present.

     

    Sorry about that! I replaced the A-4s with F-4s... take a look at your leisure, thanks for the help!

    SEAD_Test.miz

  7. See how this works for you.

    https://forums.eagle.ru/showthread.php?t=118175

    Zelgadis has also designed a similar script if memory serves where they will shut off and relocate.

     

    I’ve used grimes’ script to great success, but they don’t shut their radars down when attacked. One of the core premises behind SEAD is the SUPPRESSION of the radar. Getting the bad guys to shut the radar down is just as much a mission success as killing it.

  8. I've figured out how to make a semi-realistic SEAD "script" using several triggers. Essentially, if an enemy SAM site detects a Shrike or other ARM within its zone, it kills the radar for a randomized amount of time. As of now, it takes approximately 7 triggers for each SAM site to work. How can I turn this trigger logic into an executable lua script that I can instead attach to each unit, saving time and simplifying the trigger list?

     

    I've attached the test mission below.

     

    Thanks in advance!

    SEAD_Test.miz

  9. All of the buttons or just some of them? If none of them are working, check the cable connection.

     

    I don't even use separate profile for Warthog grip, just loaded the T-50 profile into the base and swapping the grips works fine. The profile would be needed if you wanted some physical buttons mapped to different DX buttons, or different deadzone to account for heavier Thrustmaster grip.

     

    So just to clarify - Before, I was using the T50 base with the Warthog grip as just a plug-and-play unit. Windows recognized them both and the base + grip buttons worked as advertised. I noticed, however, that for some reason, windows would indicate full after stick deflection when in reality I had about 20% more aft travel yet to go. So I decided to load the Virpil software and followed the manual to try and get it to detect the full range of motion. The first issue I ran into was for some reason the virpil software had the X and Y axes inversed, but then I noticed the software wasn't detecting any of the buttons on the grip. I had not changed anything except software and unplugguing/replugging the USB cable during this whole process (i.e. no unplugging the grip from the base). Is there a different profile to load or setting I need to change to get the software to detect the grip?

×
×
  • Create New...