CrossWiseRanger

Flappie -- besides the one above, here are two more. I'm flying as Yank, wingman Bloke, in P-51's against Jacob and Hanz (Rookies) in Bf 109's. Both missions have zombie Jacob shootdown Bloke. Mission 1: "Hanz Yes Jacob What" Jacob is missing left aileron and right elevator. Bloke kill occurs at the 4:57 mark from 1547 ft at 5.8* angle off. Flaming my wingman File Link: Mission 1 Hanz Yes Jacob What Kill.trk An additional and frequent problem, as shown in debriefing below. Though I killed both Bf 109's, only got credit for one. Plus whatever that crazy info at end. Mission 2: "Hanz and Jacob Kill" Jacob is missing both ailerons. Bloke kill occurs at the 6:46 mark from 1076 ft at 2.6* angle off. Rolling onto Bloke File Link: Mission 2 Hanz and Jacob Kill.trk

That was an interesting experience in working with trks!!! The original file exceeded download limit. So I watched and found out could shorten by stopping the replay. Unfortunately, what you see in replay is not what appears upon running replay track. Kept ME 109 in center of picture but replay has to one side. Probably has something to do with flying in VR. Anyway. This shows Me 109 Hanz being shot up - loosing right aileron and part of right elevator. Then making perfect swooping rolls and shooting down my wingman with a short burst [300 yds 1* angle off]. That is some piloting skill. Must have been Erich Hartman. Describe what you would like to see. Maybe I can get it since I seem to see this frequently. Me 109 Hanz Right Aileron Bloke Kill.trk

What specifically does the track need to show? Asking because I thought that a track did not correctly model what occurs with other aircraft. I took the above screenshot photo when flew along side during mission.

My Error!!! I had misinterpreted the VA plugin documentation as TextVariableChanged() --> VA when it is the opposite. Since Vaicom already exposes the variable {TXT:vaicompro.playerdata.currentmodule.name}; just need the event trigger after the variable was updated. As you point out, this would be using a CommandPhrase specified such as: if (vaProxy.Command.Exists(“vaicompro.DCSMissionStart”)) { vaProxy.Command.Execute(“vaicompro.DCSMissionStart”); } Can he add this?

As per my message several back. In VA: TextVariableChanged(String Name, String FromValue, String ToValue, Guid? InternalID) – this event is raised when a watched text variable’s value is changed. If that VA capability was implemented in the Vaicom plugin by adding a TextVariableChanged event providing aircraft type when the mission starts -- I would be happy.

Why automate? My engineering training I guess. Spend time to fix recurring issues so go away. Is VC the reason playback tracks aren't working? Synching Controls As you know, DCS works with a signal present; but not with a signal not present. Not talking about toggles. You can map a switch to turn something on and a switch to turn something off. You cannot have a switch turning off do anything. I'll use the P-51 Mixture Control for my example. Use Warthog Throttle flap switch which has 3 positions. Full Up and Full Down provide a signal. Center / MWR does not. Here is my DCS Control setup: ACTION KEYBOARD THROTTLE Mixture Emergency Full Rich LALT+M Joy_Btn22 Mixture Run LCTRL+M Mixture Idle Cut Off Lshift+M Joy_Btn23 And here is my Mixture VA in synch controls: Mixture Run Begin Condition : (Joystick 2 Button 22 Is Not Pressed AND Joystick 2 Button 23 Is Not Pressed) Press Left Ctrl+M keys and hold for 0.05 seconds and release End Condition Additionally, there is a VA for Joystick 2 Button 22 Is Not Pressed and another for Joystick 2 Button 23 Is Not Pressed to send LCTRL+M when a switch is turned off. This gives me full control of the mixture switch and it gets synched to switch position at startup.

Below shows a Fw 190 missing right aileron, damaged left aileron, rudder significantly damaged, bullet holes thru the cockpit and canopy side-to-side of pilot, and engine smoking. It's also flying perfectly straight and level. It would not be a rare event to find such an aircraft suddenly on your tail and shoot you down. Even had them with the one gear hanging down do this. In such condition you would expect them to be out of the fight because of control issues if nothing else. These will also continue flying straight until engine quits and crash lands - but never showing as a kill. I don't know how many bullets of what type did this amount of damage - as Hits are not detailed in the debrief as with Modern. How many people would want to keep flying the Modern AC if your missile could take off a wing but it could still fly and take you out? When do the Warbirds get some love - and realism? DCS is an outstanding flight sim. However, it is also a battle sim. Loosing interest fighting zombies. What's the point!

Over a year ago, Debriefing hit details would show ammo type and quantity. This had stopped and I was hoping that with 2.7.2 and Damage Model improvements this detail would return. No joy. As can be seen in the graphics below. Warbirds as Targets show no hit details. Warbirds shooting Modern do show hit details. Can the Warbirds get some love? We spend a lot of time flying in realistic aircraft dogfighting with little visual results. We need feedback to keep the sim interesting. Modern easily see results of a missile strike. The bottom graphic would currently show only 4 hits on a warbird when the actual hit count is Ball (12), AP (19), API (9), APIT (9) = 49 Cal 50 hits. Additionally, would be nice to have battle damage info on target aircraft of at least major group such as right engine, pilot killed, etc. No Hit Details: P-51 shooting Ju 88 Hit Details: Spitfire shooting KC-130 Hit Details: P-51 shooting KC-130 Testing showed that No Hit data when target is Warbird, even when shot by a modern. Modern always show hits. Nation did not effect. Test Data: Shooter Receiver Nation Hit Details P-51D Spitfire UK No P-51D P-47 UK No P-51D Ju 88 Germany No P-51D Bf 109 Germany No P-51D P-51D USA No Fw 190 P-51D USA No Fw 190 A-20G USA No Fw 190 Spitfire UK No A-10C A-20G USA No A-10C B-17 USA No A-10C Bf 109 Germany No P-51D AN-30M Russia Yes P-51D C-130 USA Yes Fw 190 C-130 USA Yes Fw 190 AN-26 Russia Yes A-10C AN-30M Russia Yes

Per my earlier comments: I'm looking for a trigger from Vaicom for when a mission starts, along with the aircraft type, to auto change the profile to current aircraft. I do it manually now via voice. Would also use the start trigger to sync controls. Again, can do it manually. I'm not looking for guidance on how to use Vaicom or VA. Already have both under control and working well switching profiles etc. Wanting to step up the game with automating this task. The capability exists -- if Vaicom adds it to the plugin.

sthompson -- thanks for actually answering my question. You prompted me to check on the capabilities on the VA side. VA plugins do support a 'Variable Change Event' as: TextVariableChanged(String Name, String FromValue, String ToValue, Guid? InternalID) – this event is raised when a watched text variable’s value is changed. So, can Vaicom add a TextVariableChanged event when the mission starts which provides aircraft type?

Vaicom exposes some variables to VA, example: TXT:vaicompro.playerdata.currentmodule.name Upon mission start, Vaicom logs this info: Nearest ATC: Kutaisi. Player Rebel entered module Spitfire LFMkIX, unit callsign Enfield11 DCS mission | Spitfire Dogfight Fw 190 A-8 No. 2 Does Vaicom have the capability to send a trigger at the same time? Would use that trigger to perform profile switch in VA. Already doing the profile switch now by voice. Looking for a way to automate. I'm not asking about how to do button presses, etc. Nor about how to do profile switching. Already have my profile stack and switch the bottom one per aircraft.

I'm looking for a trigger from Vaicom for when a mission starts, along with the aircraft type, to auto change the profile to current aircraft. I do it manually now via voice. Would also use the start trigger to sync controls. Again, can do it manually. Running with a base profile in VA that switches aircraft profiles. Started as you suggested but it has limitations. For example, changing a HOTAS switch to send different commands for different AC. My issue was getting all of the actions logged even if switch thru VA did not pertain to current aircraft as was mapped in DCS controls.

Vaicom Trigger -- switch profile I know that can get the aircraft from: TXT:vaicompro.playerdata.currentmodule.name And this is logged at the beginning of a mission: Nearest ATC: Kutaisi. Player Rebel entered module Spitfire LFMkIX, unit callsign Enfield11 DCS mission | Spitfire Dogfight Fw 190 A-8 No. 2 ------------------------------------------ My question: What or how can I use Vaicom to trigger a profile change to the correct aircraft?

To begin, recent dog fight in Spitfire with FW's resulted in me getting shot. Was amazing to hear my heart pounding and groaning into O2 mask. Looked around cockpit but didn't see any blood. Forgot to "show pilot", maybe was there. Anyway - major kudos to DCS for this level of sound simulation. Now my problem is can barely hear the G breathing. Know the sound level is okay per the above comment. Running 2.7. Mainly warbirds. What changed and how do I fix it?

VoiceAttack is now 64 bit with release of 1.8.8 version. The new version should be installed in C:\Program Files\VoiceAttack and \Apps for Vaicom. Guidance on moving Vaicom to new location?

SOLUTION - UH-1h Partial Spit and P-51D Was able to get single player working for single PTT to initiate the radio transmission. Now, need help to find out why ATC does not respond for WW II AC; even with menus and VA not running!!! The key was understanding just what the RLY led was indicating. So I read the manual. Was a Multiplayer indicator even though running a single player game. Counter intuitively (at least to me) is that [Use with Multiplayer] must be checked. Nothing else on this page. VOIP Control at default of [Broadcast Parallel]. Once made this change UH-1h worked perfectly to send and receive ATC both radios. For the Spitfire and P-51D, the message sends but ATC never responds. This setting would also explain why those who fly multiplayer did not have an issue with single player comms.

hornblower793 Appreciate the help. Plain mission 2 ea A-10's hot end of runway. What is the magic setting I am missing? Ground Kutaisi AC End Runway.miz

Hornblower793 - per your request, files attached. Hopefully you can sort this out. TabSheetBar.luaspeech.luacommon.luagameMessages.luaVAICOMPRO.export.luaExport.lua RadioCommandDialogsPanel.lua

I'm gathering your files list.

Still no joy for single player with single PTT. Multi-PTT, A-10c works. DCS 2.7.1, Vaicom 2.5.25.2, VA 1.8.7 1. DCS Menus work for all aircraft to comm ATC and Ground. Never get Wingman to respond. 2. As above with Easy Comms on in DCS identifies the correct radio. 3. Learned that at least for these 3 preferences [Disable Player Voice, Disable Menus, & Hide On Screen Text] that Vaicom is changing setting in DCS. In other words, these settings are controlled by VAI whether VAI running or not. Would appear that DCS side is working. I'm Winchester until Vaicom gets this fixed.

Moving my information over to this thread from another one. Vaicom works with Multi PTT on A-10C. Running 2.7 stable. It is not working on single PTT aircraft. Specifically in my case: UH-1h, Spitfire, and P-51. The LCD displays all info correctly. Easy comm on / off no difference. MAP single / norm no difference. Observed, that when PTT initiated, "Listening Resumed" logs followed immediately by "Listening Suspended" in VA. The Vaicom PTT page shows the "TX1" illuminate, immediately goes off, and "RLY" illuminates until release the PTT. Have only flown single player. Never used the chat. UPDATE: Happened to notice the Debug button today, so ran with it on. Shows that in certain cases radios / operators not found. See attached. Vaicom Messages Debug Mode.txt

Update by OP. Tried MP settings suggested by Hollyood_315. No Joy. Using Caucasus map only. A-10 no issues whether ground or air. TX1 & TX2 work with ATC. Logs correctly. PTT indicator correct. UH-1, P-51, & Spit on ground; original problem. Can communicate with F Menu. In air, F Menu not functional. My ground missions show the airport in briefing window. My air start missions do not have any AB listed in briefing window. Also tried communicating with wingmen in Spitfire in flight. No joy. Did note that while I say and have Kutaisi logged as recognized; the message out to ATC logs [Air Traffic Controller]. For those who have radio comms working - what do you see that is different from how you are running?

Vaicom works with Multi PTT on A-10C. Running 2.7 stable. It is not working on single PTT aircraft. Specifically in my case: UH-1h, Spitfire, and P-51. The LCD displays all info correctly. Easy comm on / off no difference. MAP single / norm no difference. Observed, that when PTT initiated, "Listening Resumed" logs followed immediately by "Listening Suspended" in VA. The Vaicom PTT page shows the "TX1" illuminate, immediately goes off, and "RLY" illuminates until release the PTT. Have only flown single player. Never used the chat. Any solutions?

Before the stable update, a Hit would show Detail of what type of round and the number. Example: API-T(4) With the update, the Details box is blank for Hits. This is occurring on both the P-51D and Spitfire. Didn't check others. Miss the information showing effectiveness of aerial gunnery. Will this be fixed or has this gone away with the new damage models? Would also be nice to have battle damage info on target aircraft of at least major group such as right engine, pilot killed, etc. ***** UPDATE ***** Based on Flappie's comment below that it worked for him, I ran the DCS repair. No change. Did an analysis that shows when Hit target is a Warbird, no Detail shown. Otherwise, Detail shows ammo hit type data. Need to fix Hit Details for the Warbirds. Test Data: Shooter Receiver Nation Details P-51D Spitfire UK No P-51D P-47 UK No P-51D Ju 88 Germany No P-51D Bf 109 Germany No P-51D P-51D USA No Fw 190 P-51D USA No Fw 190 A-20G USA No Fw 190 Spitfire UK No A-10C A-20G USA No A-10C B-17 USA No A-10C Bf 109 Germany No P-51D AN-30M Russia Yes P-51D C-130 USA Yes Fw 190 C-130 USA Yes Fw 190 AN-26 Russia Yes A-10C AN-30M Russia Yes

BLUF: Wind locks up anti-torque pedals. Airspeed indicator shows ground and not air speed. 1: If the UH-1H is started in air with wind, the AT pedals lock up in response to the wind. [Picture 1] has wind 90* from the left at 29 kts. Helo is at 1600 ft and 87 kts. Notice that the right pedal is full forward and the ball is offset left. The pedals could not be cleared with either trim reset or pausing and continuing. Shifting the wind to the opposite side [Picture 2] reverses the pedal lock up to the left one full forward. First time tried with a start and follow on point. Next tried with only start point with 0 kts. No difference. Also, while hovering at 1600 ft, noticed the airspeed was at 0 kts. Should have been 29 kts. [Picture 3] was from a hover. Wind speed of 14 kts while airspeed indicates 0 kts.