Jump to content

Recommended Posts

Posted (edited)

I had the same but with Voice attack, I tried calling up the AI gunners menu multiple times. Then I tried (blind) changing ROE and burst lengths. I tried the AI gunners menu again and it finally popped up and yes the ROE and burst had changed from previous voice commands (VR used).

I think in my case it is voiceattack/Vaicom having problems communicating with the CH47 module.

Edited by Rogue Trooper

HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled.

DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!.

Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.

Posted
9 hours ago, tribundf said:

Are you using Helios or have a special monitor file? 

He's in VR. 😉

8 hours ago, Rogue Trooper said:

I tried the AI gunners menu again and it finally popped up and yes the ROE and burst had changed from previous voice commands (VR used).

Strange. I haven't changed from default, and mine are the same as in the Huey and the Hip. 

8 hours ago, Rogue Trooper said:

I think in my case it is voiceattack/Vaicom having problems communicating with the CH47 module.

No issues on my end, while I had to change the "target" in VoiceAttack a while back, (a year ago?), with the introduction of MT because name of the app/what VoiceAttack saw changed. 

Posted
6 hours ago, MAXsenna said:

He's in VR. 😉

Yeah, saw that. Can still use Helios tho. That’s what I do, and my AI panel is also wired and I’m missing a few other overlays like cargo box etc. 

Really need an option from ED to move those overlays and make it a bit easier to adjust them

 

  • Like 1
Posted
2 hours ago, tribundf said:

Can still use Helios tho.

That's true of course, while I've read that some users have had some issues. Can't really remember what.

2 hours ago, tribundf said:

my AI panel is also wired and I’m missing a few other overlays like cargo box etc. 

So, the AI panel works fine, what's your screen layout? I had to tinker a lot with the Gunner Status panel. 

2 hours ago, tribundf said:

Really need an option from ED to move those overlays and make it a bit easier to adjust them

Well spoken, and true words! 

I don't understand why we can't have some drag and drop system for the overlays. IFLOLS and Kneeboard works, except position isn't saved for some reason. This goes for other displays too, and they are too dim. 🤷🏼‍♂️ 

Cheers! 

  • Like 1
Posted

I use a 10” touch screen and a standard monitor. Have the touchscreen setup to the right of my screen. 
 

Half the Gunner panel is on the bottom left of my main screen and the other half nowhere to be found 😂

 

Kneeboard box shows up in VR but the actual knee board only on the VR mirror. 
 

controls indicator and cargo box is nowhere to be found. 
 

Im using open knee board anyway, so at this point I’ve stopped messing with it. My gunner ROE etc. is setup with keybinds anyway, so I just cycle through 

Posted

@tribundf Well, that makes sense then. If you post a screenshot of the Windows layout, I can guess where they are. 

Controls Indicator is rendered in the lower left corner of the total display area, the gunners panel lower right, and cargo top right. There seems to be issues with Kneeboard rendering. Sigh.... 🙄 

  • 2 weeks later...
Posted
On 10/25/2024 at 10:04 PM, MAXsenna said:

He's in VR. 😉

Strange. I haven't changed from default, and mine are the same as in the Huey and the Hip. 

No issues on my end, while I had to change the "target" in VoiceAttack a while back, (a year ago?), with the introduction of MT because name of the app/what VoiceAttack saw changed. 

I think in my case it was when I was using the VHF head controller instead of the CDU to tune the vhf radio, I was having all sorts of game crashing and strangeness.

  • Like 1

HP G2 Reverb (Needs upgrading), Windows 10 VR settings: IPD is 64.5mm, High image quality, G2 reset to 60Hz refresh rate. set to OpenXR, but Open XR tool kit disabled.

DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), DLSS setting is quality at 1.0. VR Driver system: I9-9900KS 5Ghz CPU. XI Hero motherboard and RTX 3090 graphics card, 64 gigs Ram, No OC... Everything needs upgrading in this system!.

Vaicom user and what a superb freebie it is! Virpil Mongoose T50M3 base & Mongoose CM2 Grip (not set for dead stick), Virpil TCS collective with counterbalance kit (woof woof). Virpil Apache Grip (OMG). MFG pedals with damper upgrade. Total controls Apache MPDs set to virtual Reality height. Simshaker Jet Pro vibration seat.. Uses data from DCS not sound... goodbye VRS.

  • Recently Browsing   0 members

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