Jump to content

Highwayman-Ed

ED Closed Beta Testers Team
  • Posts

    1740
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by Highwayman-Ed

  1. Thanks for the report, we’ve seen the AI behave strangely when they get low and sometimes the AI just goes dumb.

     

    if you can repeat the problem, let us know. The voice line loops were most likely a result of the AI hitting the water and it getting stuck in a loop waiting for it to get into the area where the fight will resume. 

  2. On 1/11/2024 at 4:02 AM, Rosly said:

    Understand, though suggesting to use different design decision for new Campaigns.

    Line of sight and range limitations are essential for UHF/VHF. DCS and SRS are designed to reflect reality in this regard.
    Using different units than the narration based ones, to emit on those radios will influence on ADF as well.

    To back up what BD has said here, we've tried and failed to utilize this method many times in the past with the pending radio changes coming.

    This issue comes down once again to the AI and the way it interprets multiple nested Advanced actions used as AI push tasks. To put it as simply as I can, the more actions you have in the list, the more likely it is for the Ai to just give up and go home, and god forbid you to try to edit that list and remove an action or add one into the flow because something needs to be updated or tweaked, you effectively have to rebuild that entire AI unit and all of its actions again from scratch and then all of the associated triggers. This is why we chose to keep the comms separate from the actual AI tasks, such as follow, engage, weapons safe, etc.

  3. On 11/30/2023 at 7:48 PM, algherghezghez said:

    No no mods. 

    I will do what you suggest and skip mission 2. Just an advice though: I have both raven one and raven one dominant fury. Read the first book and almost finished raven one once a few years ago. Would you suggest waiting for your update to raven one dominant fury and play that before replaying raven one or the opposite?

    Thanks!

    Something else to check here, we (DCS Players) often don't class VAICOM as a mod, but it does impact how DCS functions to some extent. During some recent testing, we found that players who used the OLD official version of VAICOM in the past, even though they are not using the program any longer were able to resolve their issues by removing this old version of VAICOM, backing up, and then removing their scripts folder in their DCS Saved Games folder, then performing a DCS repair. The new community version of VAICOM does not seem to be causing issues at this point, but I know the migration from the OLD version to the COMMUNITY version has caused issues for some players in the past.

     

    Not sure if this applies for you, but it's worth checking!

  4. On 12/10/2023 at 5:37 AM, PD919 said:

    Thanks.  There is also an issue with the flight radio cutting out mid flight.  It sounds like I am flying out of radio range even though he is right next to me.

    Another issue we're facing with the recent changes to how the radios work in DCS as well I'm afraid.

     

    Due to the complexity in the way that AI Tasks work and how a simple change to the order of those tasks can cause the entire thing to need to be re-built from scratch, we use hidden objects around the map to do the transmissions instead, and up until these radio changes, that worked fine. Now we have to account for the distance from that unit to you, so if you're too far away, or have an obstacle in the way the radio messages can get impaired...

    We're working on these as we identify them, but as you can imagine, there are a LOT of radio transmissions going on!

     

    The preset issue has been fixed and submitted to ED with the next patch release schedule, but for now, you can just set the manual frequency of the middle UHF radio to 251 and it will resolve the problem of not hearing the initial comms.

    • Like 1
  5. Confirmed that this is related to us assigning presets to the radios. The default aircraft frequency for the aircraft radio and Comm 1 (ARC-210 in the A-10C II) are bound.

     

    We’re currently investigating if this is meant to be bound, but for now you can manually tune the ARC-210 to 251MHz and you will hear the missing radio transmissions.

  6. Thanks for this report, we've identified a naming error on the Miz file that should be loaded when you chose to load ALT A or ALT B. This has been corrected internally. You can try to make a copy of and rename the mission in your DCS World OpenBeta\Mods\campaigns\FA-18C Raven One folder from "R1 M03 ALT A.miz"  to "R1 M03 v2 ALT A.miz"

     

  7. Confirmed that this is related to us assigning presets to the radios. The default aircraft frequency for the aircraft radio and Comm 1 (ARC-210 in the A-10C II) are bound.

     

    We’re currently investigating if this is meant to be bound, but for now you can manually tune the ARC-210 to 251MHz and you will hear the missing radio transmissions.

    • Like 1
  8. On 10/1/2022 at 6:46 AM, id275etac said:

    Mission 3.
    I sat in the chocks fiddling around with stuff.

    -2 (BIFF) started taxiing on his own, took off, crashed off departure end of runway.

     

    Otherwise, enjoying so far. Thanks!!

    OK, this is a little bit of an oversight with the wording of the startup process. It took us much longer to diagnose than it should have because when you know how things are supposed to work, you make assumptions... Sorry!

    The way the mission should flow is that once the IFCC part is complete, you should complete your aircraft startup prior to contacting ground. THEN you should contact ground for clearance and start to taxi, and Biff will follow shortly afterward.

     

    The current wording of the messages is ambiguous and does indicate that you should press Space to let Biff know that you've started up and are about to contact ground, but isn't clear that this should be done only when you are ready to taxi.

     

    Updated the on-screen prompt.

     

    Thanks for the report 👍 

  9. The keyboard diff was for the Gazelle only way back when I made the profiles back just after it was released. I have no real idea if it’s needed any longer.

     

    The zeros not iterating properly is something to do with the code of VA scripting. It’s something that plagued me for years with a zero value not working on and off in the back end of VA, and I grew tired of constantly coming up with new ways to fix it. This is the primary reason I’ve given them away for free now as I simply don’t have the patience to troubleshoot anymore.

     

    Sorry I can’t give you an answer with how to fix it, but it’s to do with the scripting that tracks the radio frequencies. I hope that leads you to the right location.

     

  10. 11 hours ago, Sprool said:

    I think 'Set' replaces 'tune' as its less erroneous for VA to understand.

    ^^^ This ^^^

     

    For some, Voice attack struggles to hear the word 'tune', it did for me, so I made another set of commands that is identical, just saying 'set' instead. I know I could have created an 'or' within the Voice recognition to recognize this, and I did try it initially, but it lagged quite badly.

    The Lua was for the Gazelle to change a couple of the default key mappings that caused issues for the profile, and at the time of creating them, some keyboinds were not mapped, which may have changed by now. See the last item in the list below.

    Please find the "read me" as such that I sent to everyone that paid for them;

     

    1. You currently need to be Voice Attack Preview build 1.5.12.17 or higher to use these profiles

     

    2. The default mapping in the Huey for the UHF 1MHz Decrease (LCtrl + LShift + R) doesn't work in game for some reason. Please add a binding of LCtrl + LShift + N for this commands as that is what I setup in the VA Profile.

     

    3. This profile is large and complicated. As such VoiceAttack will lag when it starts up with this profile, up to 15 seconds to load it.

     

    4. Due to point 3, please ensure that you backup (Export) any existing profiles that you use before importing these commands to them

     

    5. The first key command that VoiceAttack issues, if DCS is not your focused window, will be missed, if this happens, manually tune the radio to the correct frequency.

     

    6. Please ensure that the default frequencies for the aircraft are set at mission start, as the scripts in the profiles rely on this. These are as follows;

     

    UH-1H
    - FM 30.00
    - NAV 107.00
    - UHF 251.00
    - VHF 116.00

     

    Mi-8
    - ARC 1.50
    - ARC UD Channel 1
    - Jadro 02.0000
    - R-828 Channel 1
    - R863 127.500

     

    Gazelle
    - ADF 430.0 & 214.0
    - FM (doesn't matter)
    - VHF 124.000
    - UHF (doesn't matter)

     

    7. I have also posted up my keyboard mapping for the Gazelle, these add all of the necessary commands for the radios, but also change the default view center key to RCtrl + F12 as Numpad 5 is used for the radios

     

    • Thanks 1
  11. Hey Guys and Gals,

     

    I’ve decided to open these up for everybody to have at them. I used to sell them for a few US$ each, and they’ve paid for a pack of beer so far, so I’m happy!  That said, I don’t maintain them any longer as I haven’t flown the Huey, Gazelle or Mi-8 in quite a while, and some changes to VA have made some cases of recognising a Zero integer tricky, and to be honest, I can’t be bothered to troubleshoot them any more.

    So, without further ado, please find the link to all the profiles that I made for the DCS helicopters here:

    https://1drv.ms/f/s!AjB8XCqYiep2gaYA0JI2uLmF_rmeCg

    • Like 1
    • Thanks 1
  12. 7 hours ago, Yurgon said:

    For me it's sort of the other way around. I never use Easy Comms and would like to keep that off in my game settings, so in order to be able to use the radio with the Blackhawk, I force it to on in those missions that include the Blackhawk-mod. :drinks_cheers:

    LOL, I'm actually the same way, but I've found that most people struggle (present company excepted) to find the options in the mission editor 🙂

    • Like 1
  13. 26 minutes ago, HC_Official said:

    Yeah I was wondering about the radio menu not working when airborne as well

      

    7 hours ago, Yurgon said:

    Just went to check it out, this mod is fantastic! Massive thanks to the team, great job guys! 👍

    Quick question regarding AAR: In order to operate the radio while airborne, Easy Comms need to be on, right? With realistic comms, the comm menu wouldn't come up for me once I get off the ground.

    You must have easy comms on for the radio to work when Airborne. If you do, check that the mission you're flying doesn't have it forced off in the mission options. Option on the right is to allow (ticked), the option on the left is to enforce the option on the right (ticked)

    unknown.png

  14. On 12/30/2021 at 7:34 AM, Sr. said:

    Question: I'm trying to use Vaicom/VoiceAttack with this Campaign, however for some reason my TX buttons (Vaicom PTT tab) are being greyed out and all I can use is the TX5 INT button.

     

    Is this a bug or intentional? Would be so much easier to voice command all 3 radios, particularly in VR.

    Are you using Easy Comms? That's the only thing I can think of if the missions prohibit it, but I don't think they do. From the way you've described the PTT tab, I don't think you are...

     

  15. I used VAICOM during all of the beta testing and never saw this issue presented and was able to use all Voice commands needed as required, primarily a command to press space rather than fumble for my keyboard in VR!

    I do not, and have not used SRS with it, or tried to integrate ED's own Voice Comms with it.

×
×
  • Create New...