Wolf359

What he said. It's the same in the Hornet. Here's a tutorial for it:

For some reason, VA is not getting input from my headphone mic. It recognizes it when I unplug the usb, and when I plug it back in. Other software, such as Windows speech recognition, works fine, so it's not the mic. Recognition setting: Default - Headset microphone (alienware usb dac) Audio settings: all set to use Windows Default Running as administrator

I fly both platforms, and when the stable get its release, I hop back to it. Is there a way to merge the data in both OB and SR logbooks? For example: I have about 40 hours in the hornet on SR, and over 120 in OB. Can the data be "added" to SR?

When did the SC go to the SR platform?

"Default - Headset Microphone (Alienware USB DAC)

It appears that VA has stopped hearing me through the mic. The mic works fine in other apps. When I depress the comm button bound on the stick, the app recognizes Transmit TX1 press and release, but nothing in between. Thoughts?

I love having a deck crew to navigate me to the catapult! Very well done, ED. It's one thing to watch a video, but something completely different when you hop into the cockpit.

Is there a way I can make LED1,2, etc blink?

Some of you guys misunderstood the post. I asked how did the software already know where I placed the MFD's. In other words, when I plugged them in, they were already assigned the correct positions.

:lol::lol::lol:

Are you flying stable release or open beta? If you want the more frequent updates, and don't mind being a beta user (meaning dealing with some bugs, reporting them to the appropriate folks, etc) then fly OB.

You can use the updater utility to uninstall them all without restarting between each.

Something in the script is interfering with VoiceAttack. I'll have to investigate.

I KNEW it would be the chain command after reading the manual but couldn't figure out what I was doing wrong with the syntax...ONE parentheses LOL. Thank you!

Can something like this be done? MapKey(&Throttle, SPDF, DX7, LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); What is the appropriate syntax to assign the button AND turn on/off the led?

Burt! Welcome to the dark side!! :megalol:

I wonder if you have a corrupted temp file. Have you tried shutting down your pc and booting back up? This is different than a simple restart. Restart will not clear out temp files. Though this issue should be resovled, are you using Voice Attack?

The DCS page states the date as the 19th, but the video and the schedule state the 17th.

It hasn't been released yet. That's why is says PRE-PURCHASE. To be released at the end of the month.

I just have to ask this... How in THE hell did the software/DCS know which MFD was left or right?! I just plugged them in and when I checked the bindings, they were already in position. Meaning, I didn't have to switch to correct positions. BTW, I love em!

That's exactly how I have mine set up as well.

I don't have that faceplate; I just downloaded the image, updated the labels and printed out for my reference. The only thing I didn't like from Gizzy's profile is that it included the stick as well, and there is really no need for it. DCS and the sticks map just fine. The throttle switches are more important to me. You're gonna love the hornet!

My current layout config.

Spool, went back to the first file you had me download - warthogThrottleAllSwitchPOS. The problem in that script - at least where the hornet is concerned - is that some of the switches scripted as PULSE are not pulse. The APU and Engine crank switches for example. Even though they could be misunderstood as pulse, they are not. They happen to be in PRESSED states and the sim resets them. But they're not pulse switches. So once I went through and deleted the "PULSE" from each line code that I found not to be pulse, everything is working great. Same went for left and right throttle idle/off bindings - they're not pulse. All is working fine in that script now.

I can't get the throttles designated for left and right thrust, Spool. Trying to st this up for the hornet.