Saving Helmet Settings

[SmeagleGoneWild]

Is there a way to edit a config file so that whatever settings we set in the STAT menu, saves. I.e keeping the FOV and SPI visible all the time versus OCLD

[Rhinozherous]

DTC would be so nice... something like the special options in the JF-17.

[Ready]

There is an easy workaround. I use VoiceAttack for programming the HMCS everytime I start. I recorded a string of HMCS commands and just execute them with a voice command. 

See the first few seconds of this video where I say 'display'.  

 

Edited November 5, 2021 by Ready_ENP

[Rhinozherous]

10 hours ago, Ready_ENP said:

There is an easy workaround. I use Vaicom Pro for programming the HMCS everytime I start. I recorded a string of HMCS commands and just execute them with a voice command. 

See the first few seconds of this video where I say 'display'.  

 

Nice idea! 

[Ready]

Yes I think I am also going to add some more settings to also adjust the lights and turn down the brightness and contrast on the MFD's, RWR etc for night ops. 

[QuiGon]

On 10/30/2021 at 10:37 AM, Desert Fox said:

We still wait for some kind of DTC (data cartridge that would save all these info in RL) feature that was said to apparently be developed years ago (for the F-18 but maybe carried over) but never heard of since.

There was indeed a long silence on this, but it has recently been broken by @Chizh, who has confirmed that this is still in the works, but probably won't be ready this year:

On 10/7/2021 at 11:51 AM, Minsky said:

Hornet: Aircraft Settings & Mission Card are still planned, but most likely won't be coming this year.

 

 

Edited November 5, 2021 by QuiGon

[MAXsenna]

There is an easy workaround. I use Vaicom Pro for programming the HMCS everytime I start. I recorded a string of HMCS commands and just execute them with a voice command. 
See the first few seconds of this video where I say 'display'.  
 

Not trying to be pedantic, but in case someone misunderstands.
One doesn't need VAICOM as what you do is VoiceAttack commands only.
But I would highly recommend VAICOM as well for the comms of course.
Cheers!

Sent from my MAR-LX1A using Tapatalk

[Ready]

1 hour ago, MAXsenna said:

Not trying to be pedantic, but in case someone misunderstands.
One doesn't need VAICOM as what you do is VoiceAttack commands only.
But I would highly recommend VAICOM as well for the comms of course.
Cheers!

Sent from my MAR-LX1A using Tapatalk
 

Thanks, you are right. Will correct.

[SmeagleGoneWild]

These are great ideas!

[glcm1961]

On 11/4/2021 at 4:22 AM, Ready_ENP said:

There is an easy workaround. I use VoiceAttack for programming the HMCS everytime I start. I recorded a string of HMCS commands and just execute them with a voice command. 

See the first few seconds of this video where I say 'display'.  

 

 

How did you record the keystrokes to voice attack?   I have the Cougar MFDs but voice attack doesn't recognize the button presses from those.   Did you have to assign each OSB button to a keyboard key and then when setting up your voice attack profile using the word "display" use those keyboard keystrokes to get it to work?  Great idea BTW!

[MAXsenna]

How did you record the keystrokes to voice attack?   I have the Cougar MFDs but voice attack doesn't recognize the button presses from those.   Did you have to assign each OSB button to a keyboard key and then when setting up your voice attack profile using the word "display" use those keyboard keystrokes to get it to work?  Great idea BTW!

Well, you make a new command, add the keystrokes (many as you like) and you're done.
Apart from this. A task can be done in several ways in VoiceAttack, but if you want to use your Cougars for a "macro" in the command, you need to add the Cougars to VoiceAttack settings, only four concurrent joysticks are supported so far. But I asked Gary on his Discord if we could have more in the future. Hopefully unlimited.


Sent from my MAR-LX1A using Tapatalk

[jaylw314]

You can use Joystick Gremlin or the like to consolidate multiple USB controllers into one uber device (or at least fewer than four devices) for VA to read

[MAXsenna]

You can use Joystick Gremlin or the like to consolidate multiple USB controllers into one uber device (or at least fewer than four devices) for VA to read

Very true, I keep forgetting it. But I think it would defeat the purpose as if you were to consolidate three cougars into one device, you'd loose a lot of automapping in several modules.
I need more devices in VA mostly throttles and grips, because VA changes the physical PTTs (with VAICOM) depending on the module I'm in.
For a super device with buttons for VA, I'd probably go with vJoy.

Sent from my MAR-LX1A using Tapatalk