bradleyjs

Is there been a timeframe announced as to when the anti-collision / formation lights will be implemented?

Anyway, nice find guys! I like the effect.

The Left drift is from the huge prop on the nose thus having to hold in Right rudder to compensate the torque! :megalol:

30% seems to be about right.

Actually, my biggest issue is with the very mushy, in-effective wheel brakes. Now, I’ve tried landing (still a little heavy) with and without the 370 gallon tanks and have overrun the EOR twice. This was before the recent patch too. I will have to test more tomorrow but I just wanted to vice my thoughts. It’s not exactly on key with this thread - but it could be somewhat related.

There’s a new Beta version of VoiceAttack available, as I just updated to it a few minutes go. I have never had any issues with updating to VoiceAttack’s Beta Software. I cannot say that for other vendors. And, I’ve been in the IT industry for almost 40 years. :music_whistling:

Thank you Hollywood for addressing this issue. My gut tells me that ED will fix it fairly soon. In the meantime, no harm, no foul! ;)

Wow! It seems like I opened a can of worms here! LOL Anyway, I’m guessing that the issues that we’re experiencing will be solved in the coming months from either DCS and/or VAICOM. So, hopefully the information provided here can assist it’s that. I’m available for testing if needed...

Yes there is. Just press the default button that controls the chatter. On my TM HOTAS, it is the mic button depress. It toggles On/Off.

So, just to be clear, the semi-functioning TX1 PTT is working as designed? If so, how come no other aircraft module (F/A-18C, A-10C, F-14B) that I have exhibits this behavior. I.e. if the radio is not broken or disabled it shows up in the PTT dialog as "good" and the UI Sounds (beeps, clicks, thud, etc) work appropriately. In my situation, only the TX1 [VHF] radio shows and sounds unusable; but somehow it T/R my requests "almost" all the time; it has been a bit quarky. It is my belief, at this point, that there's something wrong with either the F-16C module and/or VAICOM PRO latest version. And, I fully understand that this module is EA and I have no issues if it is a bit buggy. Hey, we pay to be public beta testers and we/I love it! This is why I'm adamant about this possible issue. Here's a thread [https://forums.eagle.ru/showthread.php?t=198297&page=315] that is a more in-depth discussion with others having the same issue. Again, I just want to be clear and this is considered "normal" behavior but only for the F-16C module. You are the SME's and I will take your word for it. Thanks

Is this the binding that you're referring to? I'm using the TM HOTAS Warthog System and Nvidia 1080Ti SLI - dual cards setup. "JOY_BTN1" ENABLE Switch - Depress Throttle Grip; HOTAS The reason I ask, as in my limited time configuring the F-16C's optimal Graphics Settings and the seemingly never ending JOYSTiCK and THROTTLE bindings, So, I couldn't get the mini-stick's JOY_BTN1 to lock on to any target. I haven't spent much time investigating as I've run into a problem with VAICOM PRO working with some PTT issues. But, I saw the question and thought I'd ask about it too.

You can - it’s not a big boost in sound but it is better than nothing. Under the Audio tab (in the config dialog) increase the volume slider of AOCS in the bottom left side of the first column. The system is usable “as is” and I believe the issue will be fixed in the near future. Thanks for your help today!

The functionality of TX1 is only partial and it doesn’t work the same as TX2. The UI Sounds when pressed indicate an error and it has a disabled look in the PTT. So, does you TX1 or 2 look like in the pic and does it seem to be disabled like mine? When I first discover this issue late last night, it didn’t seem to work at all. I think that’s where I might have confused you. As the day went by and after further testing I was able to determine it does actually work; just not with the same behavior as a “good” radio.

I use that same configuration and get it work but TX1 is not showing visually that it’s available for use. If you open and display the PTT tab while using the F-16C module, is TX2 NOT disabled and has white text, while TX1 looks disabled and when used does have the familiar beep UI Sounds denoting hardware availability. In the pic note that TX1 is disabled, but it does T/R voice and is missing the UI beeps..

Here’s the image I promised. I took this screenshot after I exited DCS - the PTT / Config gialog does shoe F-16C Viper when its in use BTW

I posted this in another thread - I will post here for clarity:

LOL :thumbup:

I found it - eureka! MS Speech Recognition Profile Manager Tool https://www.microsoft.com/en-us/download/details.aspx?id=22358 This seems to create a file with the extension of .spf. Not sure if its the best tool to use, but it beats having nothing and it’s compatible not to mention: FREE! Ps - I forgot it’s Football Sunday right now and the games started at 1300. My Viper is down for maintenance (it’s a Code 3 in USAF terms) and could be in Hangar Queen status for the remainder of the day!

When I first loaded VAICOM PRO (got the spelling correct this time) I spent hours training my voice. I also used a MS Dictionary Backup Tool (I think It was a MS tool - it was a long time ago) and saved the trading files. And I did notice a positive difference with recognition after the training.

I will do a Live debug session later in the day and post the results. My wife has me doing some Honey-Do’s at the moment. There’s just not enough “Playtime 60 minutes” built into the Frag Order of the day! :doh:

According to the Dash-1, its just a UHF Backup Control Panel. I guess I just misunderstood its purpose.

Nothing glaring....

Here's what the Debug info is showing me. Nothing is really jumping out at me. I'm guessing that this whole issue is with the F-16C Module itself. It's probably still half-baked in this area... :book: Ignore the error about TeamViewer as I use that tool, plus Microsoft's Remote Desktop, to connect to my PC via my iPad Pro 12.9" I see either the 4/5 DcS-side files were updated or 5/5 DcS-side files were updated - I guess it depends on what mood it is in at the moment. :music_whistling:

I will send you what I’m seeing in a few.

I checked the audio source and its work fine. As far as the beeps and such goes, I don’t get the proper feedback with the disabled TX. But, I do get the voice read back only when I saw any correct phrases; but the proper UI Sounds are mostly missing. On the non-disabled TX2, it works properly - read back and the applicable beeps/sounds.