bradleyjs

I tested this extensively late last night and I can get it work but NOT like it's designed to - the UI Sounds, beeps, blip, click, thud and flat beep sounds are missing. Page 15 from the VIACOM manual: • Confirmation (beep) • Awaiting additional input (blip) • Recipient not available (click) • Error (thud) • Ambiguous (flat beep) And, of course, it shows as disabled. This is not normal behavior and I'm hoping that the developer can address this issue and then provid a Hotfix. I forgot to mention earlier that I have the latest version of VIACOM Pro - 2.5.12.1 and also I'm running the latest (as of late yesterday) the newest Beta of VoiceAttack. Also, just for pure troubleshooting purposes, I disabled (not loading) any of the AIRIO plug-in LUAs. The behavior is the same; no change. Plus, I have Debug on as well.

The TX2, UHF, is the only one not Disabled (not grayed-out). Not including TX5 and TX6. See attch pics - Before and After

I think Wags explains the UHF radio in Startup or the Orientation vids. Also, I might have heard it from the Grim Reapers vids when I get some time later today, I’ll see if I can find it in the EA Manual and the F-16C’s Dash-1 (I found a legit copy of the Dash-1 online a couple of days ago). But in the long run, the bottom line is, it’s modeled in the sim. So, in the mean time, let’s spread our wings and Fly! :pilotfly:

I have tried a 100 different combination of this - except completely blowing it away and re-installing fresh; which I rally, really don’t want to do.... It seems like either the new OB release yesterday and/or yesterday’s installation of AIRIO is when I started noticing this PTT TX2 (only) problem. Otherwise VIACOM PRO has been working as designed. Well, it still works perfectly with both A-10C and F/A-18C. BTW: I’m using the TM HOTAS (and its firmware and other drivers re up-to-date effect @2-3 weeks ago along with the new software for my Saitek Pro Flight Rudder Pedals [i think that Logitech owns them now] Not sure what else to try - guess I’ll wait and see what Hollywood thinks. :joystick:

A UHF, similar to the one in the A-10C, and is located in the middle of the Left Console. I use the same key bindings for all modules; which makes it easier to remember. I will have to investigate the profile that you just mentioned. I’m also probably going to have to review the LUA code to see if anything is glaringly wrong.

I just tried the other modules that are working properly then went back to the Viper, while leaving the PTT dialog up, and as soon as it’s time to fly, it disables all other TX’s. As soon as I exit the Viper module, then they are all re-enabled like magic!

F-16C and PTT Issue The F-16C has three (3) radios, but only two (2) are mostly used. In the latest version of VIACOM PRO the PTT only allows for one (1) TX versus the other two (2) that are missing thus only allowing communication over that single TX. Does anyone know if this is just an Early Access issue or is the VIACOM tool not properly coded to support this new module? Both the A-10C ad F/A-18C have several TX’s to use, so there’s no issue with those modules. What do you guys think? :huh:

The F-16C has three (3) radios, but only two (2) are mostly used. In the latest version of VIACOM PRO the PTT only allows for one (1) TX versus the other two (2) that are missing thus only allowing communication over that single TX. Does anyone know if this is just an Early Access issue or is the VIACOM tool not properly coded to support this new module? Both the A-10C ad F/A-18C have several TX’s to use, so there’s no issue with those modules. What do you guys think? :huh:

I have the A-10C HOTAS systems and it is very sluggish. I modified the Curve to 30 on both X/Y Axis’. It just mad it worse, so I put it back to the default settings. When I was doing my first real testing yesterday (it takes lots of time to reprogram the entire HOTAS system to something comparable to the Cougar HOTAS [which I gave to my oldest son years ago and wishing I had back....]) thats when I noted the sluggishness and was just assuming it’s attributed to being super-Alpha’ish Early Access issue. So, I will just make due with it and see if the flight modeling changes. My HOTAS works perfectly with A-10C and the F/A-18C.

I took the time to listen to this today - throughly enjoyed it!

I like that approach - maybe they will —- But, I’ve been around developers for many years and they don’t always have the end-user in mind. I’m primarily an enterpeprise system admin for over 30+ years (and also a developer - but for system admin user tools) and when developers get into “code-mode” they typically don’t see the real-world; but that what management has to reign in.

I strongly suspect that this issue will roll-over to the Release version next week. However, I always backup my settings (via a batch file I wrote and assigned to a macro key on my Alienware keyboard ), on a daily basis as small changes creep-in from me here and there. So, if bad, then I will overwrite the config lua files from my external backup.

Ok - good! Then its not just me. I agree it “should” be easy to fix.

You can download the “Release” version of DCS World and you won’t need to worry about the OpwnBeta bug issues. It’s a separate install that will also take up plenty of disk space. I personally have both versions and they work fine by themselves.

I originally posted this in another thread: The only binding issue I’m having is “Arresting Hook - Cycle” default is “H” and it doesn’t respond to the H key or HOTAS binding. The “Down” I set to “H” and the “Up” I set to “LShft+H”. All other “highlighted” bindings have been corrected. It only took me a few minutes to fix. So, I’m assuming this is a bug. Unless I’m the only one to have this issue.

The only binding issue I’m having is “Arresting Hook - Cycle” default is “H” and it doesn’t respond to the H key or HOTAS binding. The “Down” I set to “H” and the “Up” I set to “LShft+H”. All other “highlighted” bindings have been corrected. It only took me a few minutes to fix. So, I’m assuming this is a bug. Unless I’m the only one to have this issue.

I hear ya brother!

My bindings show up in the config GUI and I don’t have a new set of files like that last time you mention. Most HOTAS bindings are working - however I have done a full test yet. For the moment, the speed brake isn’t working for me at all either HOTAS or keys, When I get some more free-time I will do a full test.

I can't get the speedbrake to extend/retract either by my WH HOTAS or the keyboard --- anyone else having this problem too? I even put the config files from a backup I made before the update - no joy.

I can't get the speedbrake to extend/retract either by my WH HOTAS or the keyboard --- anyone else having this problem too? Edit: I even put the config files from a backup I made before the update - no joy.

I was 22 - now way too old!

It wouldn’t let me use my Bonus points - it suggests that it will accept a Coupon; I looked but couldn’t find one. So, I paid the full price. I spend more than that with a dinner-out with my wife. So, I skip a dinner or two - she’ll get over it ‘-))

I just took the plunge!

I’m confused - after tomorrow does the free module(s) stop working or gets deleted? I own FA-18C and PG but not the Su-33.

+1