-
Posts
1802 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Bailey
-
This is doable with programs such as voice attack. A native solution would be nice to accommodate those short on hats.
-
It is possible to move the popups around. I totally understand what you mean with the cross-eyed thing. When it pops up it is "focused" at infinity, far away. Unfortunately this means that if happen to have that part of your display it is hard to focus on it when the cockpit is focused at a meter. I changed the positions to naturally be in the right eye for the status menu and in the lower left eye for the target menu and compass. When the target menu and compass pop up they are more likely to be outside the left window, therefore properly at infinity and not fighting with the inside of the cockpit.
-
Are you not able to add those two keybinds yourself?
-
A temporary solution is similar to the trigger guard solution: Here it is. Copy this code: --------------------------------------------- -- Custom ----------------------------------- --------------------------------------------- { down = tedac_commands.RHG_LRFD_TRIGGER, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, name = _('RHG LRFD Trigger - SECOND DETENT - PRESS'), category = {_('TEDAC'), _('Right Handgrip'), _('Custom')}}, { down = tedac_commands.RHG_LRFD_TRIGGER, cockpit_device_id = devices.TEDAC_INPUT, value_down = 0.0, name = _('RHG LRFD Trigger - SECOND DETENT - RELEASE'), category = {_('TEDAC'), _('Right Handgrip'), _('Custom')}}, { down = tedac_commands.RHG_LRFD_TRIGGER, up = tedac_commands.RHG_LRFD_TRIGGER, cockpit_device_id = devices.TEDAC_INPUT, value_down = 1.0, value_up = 0.0, name = _('RHG LRFD Trigger - SECOND DETENT - PRESS else RELEASE'), category = {_('TEDAC'), _('Right Handgrip'), _('Custom')}}, { down = tedac_commands.RHG_LRFD_TRIGGER, up = tedac_commands.RHG_LRFD_TRIGGER, cockpit_device_id = devices.TEDAC_INPUT, value_down = 0.0, value_up = 1.0, name = _('RHG LRFD Trigger - SECOND DETENT - RELEASE else PRESS'), category = {_('TEDAC'), _('Right Handgrip'), _('Custom')}}, and then paste it into this file: `C:\...\DCS World OpenBeta\Mods\aircraft\AH-64D\Input\AH-64D_CPG\joystick\default.lua` in this location near the top: There you go. Enjoy. The catch is that this file may be replaced during DCS Repair or a DCS version update. You will have to replace the code afterwards. Just keep this thread handy and you'll be fine. I have tested it ingame and it works great.
-
VA does not need to know what mode the AI is in unless you are doing error or situational mode context checking. It will do the wrong thing if you say the wrong command, just like pressing a keyboard. Not optimal in many cases, but can be overcome via the GUI provided. As for the "Turn left 30 degree" type commands I had successfully done the full 360 degree compass. I has also done a full range of altitudes with commands such as "Climb 40 feet". To my dismay, when I restarted DCS all of my work was wasted. Due to the input repeating lag, the poll rates, the frame rates, etc, The results were nowhere consistent between play sessions on the same machine, same mission, same command. It was quite unfortunate. For my Apache profile (which is now available), I have opted to use commands such as "turn right 4" which is the equivalent of holding the button down for 4 seconds. It is entirely relative, but much more predictable. For those wanting to make their own hold commands, beware the possibility of holding and something interrupting VA or DCS. If you use the simple press action in VA it will not release after a disruption. There was someone I was playing with that made such a command for the Enter key (you can see where this is going...) and forgot to make a release bind. They ended up having to restart their computer. You can see my solution for this unlikely, but possibly serious issue in the my Apache profile.
-
Long presses for actions are fine. I set them to be hold and press for 0.75 seconds. Short presses as 0.25. The crossover for the AI is 0.50 seconds. You don't have to track the state that ED AI is in. It is up to the user to know what state they are in. The benefit of discrete commands is that if you say "George slide right" but you are at 140 kts in flight mode, ideally, he would either say "No can do" or do some other action indicating that it wasn't a proper option in that situation. As it is now George will do the button combination equivalent to sliding right. In this case the result wouldn't be horrible, but I have seen things get out of hand quickly if the wrong commands are used.
-
Bailey's VoiceAttack Profiles (Added OH-58D Kiowa!)
Bailey replied to Bailey's topic in PC Hardware and Related Software
It's officially here! AH-64D Apache Voice Attack Profile: User Files Download: https://www.digitalcombatsimulator.com/en/files/3321355/ Enjoy! -
Bailey's VoiceAttack Profiles (Added OH-58D Kiowa!)
Bailey replied to Bailey's topic in PC Hardware and Related Software
If literally nothing is happening then the issue is at the Voice Attack level. Make a new custom profile. In that profile make a command called “test 1 2 3”. In that command have it press and release the letter g. Try that in notepad. If it does not work then reference the VA Help pdf for solutions. If it does work, then we have somewhere to continue troubleshooting. -
For these buttons it takes about a second for the sim to register if they are activated externally (much like the F18 ON/OFF button for those who were familiar with that one). Specifically for the tail wheel lock, in the sim the tail wheel must be aligned before the lock can physically drop into place. To make sure it is working I suggest a cold start. Here is what I have for the tail wheel. Most of the other buttons of this "type" follow the same "logic" of making sure you press and release.
-
Sweet. Enjoy!
-
Mi-24P Stream Deck with DCS-ExportScript
Bailey replied to Bailey's topic in PC Hardware and Related Software
You are welcome -
Mariana Island Weapons Range mission problems
Bailey replied to Bailey's topic in Missions and Campaigns
In the Cold and Dark Marianas mission the third MGRS says C2 instead of CS. The brief is missing a few spaces between a few words. -
The first MGRS easting has the first two digits swapped. For some reason I could not get the Insurgent location to show on the TSD. When I played the story element, I blazed the way, which from the way it unfolded, may have not been then intent. If so, maybe adding that this is an "escort" of the friendly forces would be a cue and incentive the player to stay near them. Results 100 would be nice with the completion message. and a "deedle deedle MISSION SUCCESS!" after landing back at base
-
Bailey's VoiceAttack Profiles (Added OH-58D Kiowa!)
Bailey replied to Bailey's topic in PC Hardware and Related Software
Thanks! The link to the profile is in the video description. I will "release" it here once approved by ED User Files. -
Stream Deck XL - AH-64D Profile not Working
Bailey replied to Toni Carrera's topic in PC Hardware and Related Software
No problem at all! -
I would personally backup the file and delete everything else other than the export script part.
-
In Remarks on the kneeboard the south range is noted as the north range. Two of the vehicles at the start are inside each other
-
Enjoyable mission. Just finished it with invincibility on (of course :P). In the brief "Then flight the flight plan to BP 53" should be "Then fly the flight plan to BP 53". I also have immense trouble hovering out of OGE. (Mostly skill issue imo, haha). I noticed the kneeboard errors. Looking forward to the fix. I spent much longer than I should have trying to find out what I was doing wrong. Confirmation on mission end would be great along with the mission points as mentioned.
-
Double check your export.lua file. Play with it a bit. You can post it here for assistance.
-
Stream Deck XL - AH-64D Profile not Working
Bailey replied to Toni Carrera's topic in PC Hardware and Related Software
Oh no, your "Button ID" and "Device ID" entries are swapped. I have accidently done this before too. This can be fixed in two different ways. Manually swap them (which I would recommend). Or use ID Lookup to put the correct ones in (which I would recommend for new buttons). Profile looking good btw!