Jump to content

Recommended Posts

Posted (edited)

 Hi, guys.

I tried that setting up the route with Waypoint 4, through cockpit trigger action.. but i couldn't.

 

Like the picture, Only '4' is showing me on KU. What did I make a mistake?

 

image.png

image.png

Edited by sledge1-1
Posted
3 hours ago, sledge1-1 said:

tried that setting up the route with Waypoint 4, through cockpit trigger action.. but i couldn't.

 

Like the picture, Only '4' is showing me on KU. What did I make a mistake?


I’d like to help, but I’m not familiar enough with the Apache to know what you are trying to accomplish … can you describe in more detail the operation you need the trigger to do?

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)

Thanks for your reply.

I want to make Apache select the waypoint route via a cockpit trigger. 

So the gunship should types W04 (waypoint 4) on the KU (keyboard unit) then the pilot will get a route to WP4.

Surely I entered the ID and command in the correct triggers. But like KU in the photo, they did not completely follow my triggers.

Sorry if my English is bad, :'-)

 

 

https://chucksguides.com/aircraft/dcs/ah-64d/#[688,"XYZ",-8e-06,540,1]

 

You can find a 700 page in chuck's guide.

 

Edited by sledge1-1
Posted
1 hour ago, sledge1-1 said:

So the gunship should types W04 (waypoint 4) on the KU (keyboard unit) then the pilot will get a route to WP4.

Surely I entered the ID and command in the correct triggers. But like KU in the photo, they did not completely follow my triggers.

 

OK, I took a try and found that the KU keys need a bit of time to complete their animation and sounds, so if the trigger attempts to type too quickly then some keys will not register. Also, each key requires not only a "press" but also need a "release" or they remain in a "pressed" state.

Here is a sample, where I first press the CLR key of the KU, to "wake-up" the KU, then one second later I release that key and type the W04 sequence. Finally a second later I release the W 0 and 4 keys. The triggers look like this:

 

6t9Nxjb.jpg

 

here is the sample mission so you can try it yourself.

Best regards

 

 

AH64 - Test KU (by Rudel_chw).miz

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted (edited)

Your sample was not taken as I planned. But i got that your points!

According to your reply, KU needed a term! I can found my problem. Thanks! But i want to ask you one last question!

You say they remain in a "pressed" state.

 

What value number should i enter to press 'once'???

 

nullnull

Edited by sledge1-1
Posted
56 minutes ago, sledge1-1 said:

You say they remain in a "pressed" state.

 

What value number should i enter to press 'once'???


The value 1 presses the KU key, and the value 0 releases it. There is no single trigger for "pressing once", you need to do this using two trigger actions: one to press, and then another to release.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...