sobe

I just noticed that the quadrant diagram and arrows that indicate the direction of threat missiles detected is not being exported to my second screen. The quantity of flares and chaff show up clearly, but not the quadrant. What lua files are used to export the quadrant?

Bunny where did you place the CMWS panel so that the viewport shows through?

Bunny I didn't realize you had updated the profile, now all is well on the CPG comms panel.

Bunny In the output bindings for the CPG, I could not find the actions for HF Squelch switch, the IDENT button and the ICS Mode Switch. I think I see them in the lua interface file, but they do not seem to appear in the Actions column. I could be wrong, but perhaps you miscoded something in the lua interface file. They do appear in the Pilot action column. I play only single player so I do not have an answer for you on the KU.

Jusif See the profile made by Oze. There are seperate Lua lines for each KU in his interface I believe.

Bunny I tried your suggestion of: "The indicator should be assigned to the "Set Indicator" field and not "Toggle Indicator." Looks like I screwed that up on both the Pilot and CPG Tailwheel buttons. " but it did not seem to make a difference. On the CPG comm panel, is there a reason that the two Ident buttons (lines 2 and 3) and the voc button on the 3rd line have no actions or binding while the Pilot comm panel do? BTW, in my Helios setup, I have two difference Key panels AH64_CPG_KU = { x = 2640, y = 647, width = 480, height = 60 } AH64_PLT_KU = { x = 2640, y = 647, width = 480, height = 60 }

Bunny I am still having issues with the tail wheel light on appearance. I have the Input action CPG WHEEL UNLOCK LIGHT CHANGED bound to TOGGLE INDICATOR and in the OUTPUT, I have the pushed and released bindings bound to push and release CPG TAIL WHEEL pushed and released actions. Yet the button does not change color.

How do you set this up for single player?

Bunny Are your unlock button correct? The up and down buttons seem to be the same.

Kharrn Why can't the manual be written as clearly as your explanation. I never realized the difference and always wondered why the gun did not work sometimes. I also set up a voice attack command that sets the master arm to arm and at the same time, opens the trigger guard so I don't forget to do that.

Recluse Apparently you are supposed to read what is written in the manual, NOT what you think is written. Your track was perfect and I finally figured out what I was doing wrong. I owe you one. Thanks.

Recluse I watched both videos so perhaps I do not understand something. I get the MGRS numbers from the F10 map and go through the procedure to name the location as T01. If it is to far away from my seeing it or far away from a wp, how do I still designate that T01 location as an acquisition source? Is there any method to get the T01 on the coor page list?

I am having a hard time making my target T01 as an acquisition source for my TADS. I can make a point as T01 and can make it show up in the TSD in red. I can also do a direct to for the T01, but only by accident can I seem to make T01 as an acquisition source for the TADS. I cannot seem to make the show and coor buttons and the phase button all talk to each other. I can get the waypoints to show on the coor page, but not the target location. I am trying to avoid making T01 as a waypoint per the Redkite YT video.

frostycab. Thanks for the explanation. I was trying to figure out how to set up my controls and could not figure out why I needed both as I will be using George to fly the aircraft. Thanks again for the simple and concise explanation.

FOR THE CPG: I know that the RHG MAN TRK x/y axis' are the cursor controls for the TAD. However, what is the difference between the LHG cursor controls on the TEDAC and the HOCAS cursor controls on the collective? They seem to do the same thing.

I have issues with the navigation training mission being stuck when activating the guns.

I just double checked and this is my config: <add key="DCSpath" value="D:\Eagle Dynamics\DCS World OpenBeta\" /> <add key="SavedGamesPath" value="C:\Users\13057\Saved Games\DCS.openbeta" /> And it works so maybe the difference is not important?

I reinstalled everything and then did an update to Viacom and now it works. Nothing like a little excitement in the morning.

Here is the error. The problem seems to be in the line System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:\Users\13057\Saved Games\Mods\aircraft'. which is obviously the wrong location as it leaves out DCS world openbeta. Here is my kneeboard config file and it has the right location. <add key="SavedGamesPath" value="C:\Users\13057\Saved Games\DCS.openbeta" /> So for some reason the program is not picking up the correct line in the config file. Lost as to what to do. ====================================================================================== <?xml version="1.0" encoding="utf-8"?> <configuration> <appSettings> <add key="DpiSetting" value="150" /> <add key="DCSpath" value="D:\Eagle Dynamics\DCS World OpenBeta\" /> <add key="SavedGamesPath" value="C:\Users\13057\Saved Games\DCS.openbeta" />

When I launch Viacom Pro today, a large white box appears and nothing else happens. I reloaded Voice attack and Viacom pro, but no change. Is this just my issue?

I checked and no A appears in the HMD in a hot start

I checked and no A appears in the HMD.

I was on the fence as to what rudder pedals to buy for the Apache. I came close to ordering the new anti-torque pedals from Virpil, but those pedals were out of stock. So I decided to go with Crosswind as it was in stock. I ordered on a Sunday and they arrived on the West Coast of the USA on Friday. So if anyone is on the fence about which pedals to order and are concerned about delivery time, this is a great result.

I was on the fence as to what rudder pedals to buy. I came close to ordering from Virpil, but the pedals that I wanted were out of stock. So I decided to go with Crosswind as it was in stock. I ordered on a Sunday and they arrived on the West Coast of the USA on Friday. So if anyone is on the fence about which pedals to order and are concerned about delivery time, this is a great result.

will check later