Jump to content

Highwayman-Ed

ED Closed Beta Testers Team
  • Posts

    1724
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Highwayman-Ed

  1. You are welcome to use any and all assets for this, I like the campaign idea to the training too
  2. 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.
  3. Great script, really like how portable you’ve made is and it was easy to add the elements into our existing missions.
  4. Yahooo! I'm the sheet hotest fighter pilot baby
  5. ^^^ 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
  6. 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
  7. This stuff, is golden with helping to build a living world
  8. You sir, may like this mission I posted a few days ago Highway's Mach Loop - C-130 Edition (digitalcombatsimulator.com)
  9. 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
  10. 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)
  11. 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...
  12. 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.
  13. Same here, it's been like that for quite a while now.
  14. Pretty sure there is one for the 737 in the base installation.
  15. Does the Orion support the Warthog grip via the adapter same as the Super Libra? I asked WinWing a week ago, but they haven’t given me the courtesy of answering my emails…
  16. I've stopped chasing ghosts in the Oculus Tray Tool and the Oculus Debug tool, I spent more hours than I care to remember tweaking and fiddling with settings over the years, and as my wife pointed out to me a while ago, I spend more time messing around with things for DCS than actually flying it! With one final pieced of advice I'll pass on my settings. My settings may work for me, but there is a very good chance that they will not work well for you. Be it in terms of frame rate, stutters, whatever it may be the subtle variations in CPU, RAM, GPU, Link cable, other programs installed on your PC, and also the aircraft and situation that you fly in, as well as the lucky 8 ball shake that seems to occur every time you start DCS, results may vary, so don't get hung up on it! So, with Oculus Desktop software version 30, and Quest software version 29, my settings are: I do not use Oculus Tray Tool (any more) I do not use Oculus Debug Tool (any more) Oculus Desktop settings: I use this as my unofficial Link cable, and it gives me unlimited play charging the battery faster than it drains: Which yields the following test scores: However, be warned that it will draw 5 Amps from your USB port, and one of my friends had issues with his Quest dropping out because his motherboard couldn't reliably supply that amount of power over his USB C 3.1 ports. After he changed to a USB A 3.1 cable that only drew 3 Amps, his issues went away. DCS Settings (note that I've upped the Pixel Density to 1.2 since the photo through the lens, but it's not much clearer than at 1.0, I use it as it helps with aliasing of the terrain which only became much more of an issue for me since flying the Hind low level) The important settings in here to note are MSAA on x2 and Anisotropic Filtering on x16, the Pixel Density of 1.2 also helps but is not as critical as the first two. With these set, they are aliasing the edges and eliminating most of the absolute shit show of shimmering that I experience when close to the ground, which is a complete and utter deal breaker for me (See Wag's Video of ATGM's in the Hind, when he looks through the sight, that's what I'm talking about). All 3 of these settings however have only a little effect on the readability of the MFD's, I'm using them now because I'm flying the Hind close to the ground. As a result, my frame rates are nowhere near as good as they could be and I'm well aware of that, but this is the balance that I have come to achieve with my rig. As such, I maintain around 40fps with DCS right now in the Hind, but things like multiplayer, the Super Carrier and others will drag it down to almost half of that on occasion, so I generally avoid these for the time being. If I'm whirly birding, I'll use what you see above, If I'm flying high in a Tomcat or the Hornet, I'll drop the PD down to 1.0 to give me a few more frames when I'm on or near the carrier. The only other advice? Clear your shader caches often i9-9900KF @5.2GHz 32GB DDR4 MSI RTX 2080Ti Gaming X-Trio (Nvidia 466.77 driver) DCS on Samsung EVO 970 SSD Good Luck!
  17. +1 for an option for this, but I'm actually fine with it how it is... There's simulation, then there's just busy work, and I'd class this as the latter. What I would like to see as others have stated is the option of inserting your own images as per the kneeboard here so they're not so cluttered with short distances between waypoints, or flight legs that write the time and distance notes over one another. Most definitely need key bindings for the etch'a'sketch as well as it's painful to adjust this in VR
  18. No joystick mapping available for close canopy (LCTRL + C) either
  19. Agreed, I'd like to see this implemented too.
  20. Here's a through the lens photo of what I get in my Quest 2 via a link cable with DCS VR presets and standard PD setting of 1.0
  21. That setting is in settings in the headset when linked to desktop, but I believe that it's only for the Desktop GUI, not anything that renders directly like a game.
  22. Pushing either of the encoding values up when using v29 and 120Hz causes occasional audio stutters for me. if you want to push those higher, drop your refresh rate back down to 90Hz.
×
×
  • Create New...