overalien

AOCS No Audio Output Hi Hollywood_315 I have the same issue with AOCS output not playing audible sound. I have checked and confirmed the MS TTS setup is working and correctly playing the samples through my audio device. The VAICOM AOCS function still plays no audio.

Share your fix please can you share how you fixed the permissions issue? I have the same problem you had. :smilewink:

This certainly gives a quality boost but for me with multiple screens it’s just that little too much drain on performance. I went back to 4x MSAA in game and MFAA enabled in Profile inspector. It’s an acceptable compromise for me. Sent from my iPhone using Tapatalk

I also sent an email. Understand you guys are busy catching up from the holiday but a quick reply to confirm receipt would help.. Thanks Sent from my iPhone using Tapatalk

++bump. I am also very keen on some new challenges. Sent from my iPhone using Tapatalk

yip Jester also ignores me when using this via AIRIO. EDIT: I get a "squelch radio" ICS sound in response but no "yessir" and no change in scan range

Viacom Pro with AIRIO is the way to go. Sent from my iPhone using Tapatalk

You must use MSAA 2x or 4x in DCS OPTIONS (in game) , not in NVIDIA. Sent from my iPhone using Tapatalk

You must activate 2x or 4x MSAA in DCS and set Nvidia to enhance app settings and turn on MFAA. On its own, MFAA does nothing if your in-game settings for AA are off. MFAA changes the calculation algorithm to a more efficient one. Sent from my iPhone using Tapatalk

Combine 2x or 4x MSAA in DCS with „enable MFAA“ and „Enhance Application Settings" in NVIDIA. That's a good balance of performance loss vs quality in my experience. Sent from my iPhone using Tapatalk

I noticed that my curve causes jumping at maxed out Altimter REading - I added two more points to the curve to counter this: { 0.000, 0.1166, 0.2279, 0.3356, 0.4506, 0.4878, 0.5212, 0.5546, 0.5880, 0.6251, 0.6585, 0.7142, 0.7699, 0.8255, 0.8812, 0.9629, [b]0.9629 [/b]},{ 0.000, 0.161, 0.278, 0.380, 0.466, 0.492, 0.517, 0.540, 0.565, 0.594, 0.623, 0.673, 0.724, 0.779, 0.846, 0.940, [b]1.000[/b] }

Hi CaptZeen: I made a fix for the wrong readings on the Radar Alt Needle here: Replace line 191 in Helios_F14.lua with this code: --[85] = MainPanel:get_argument_value(103), -- RALT needle Fix [85] = Helios_Util.ValueConvert((1-MainPanel:get_argument_value(103)),{ 0.000, 0.1166, 0.2279, 0.3356, 0.4506, 0.4878, 0.5212, 0.5546, 0.5880, 0.6251, 0.6585, 0.7142, 0.7699, 0.8255, 0.8812, 0.9629 },{ 0.000, 0.161, 0.278, 0.380, 0.466, 0.492, 0.517, 0.540, 0.565, 0.594, 0.623, 0.673, 0.724, 0.779, 0.846, 0.940 }) , -- RALT needle Fix I hope this saves you the effort of fixing it later :smilewink:

Some Release "Bugs" in Ver 1.0 @CaptZeen: I have missing needles for Radar Altimeter Pilot (inside and outside) as well as VVI and Rudder on the Control Surface Deflection Instrument. Looks like the instruments' profile config is referring to a MIG19 folder or other graphics files that are missing from the downloaded profile. The Fuel Flow and TT bars reference the wrong Network Value numbers. I managed to fix most of this by referring to other needle images which are in the images section as well as referencing the correct Network Values for the FF and TT bars. However, the Radar Altimeter over-reads by about 50 ft at 100 ft (Test Button depressed) and starts to under- read by as much as 1000 ft from about 3000 ft Radar Alt upwards. Lastly it looks like the flaps needle is not driven by a trigger value at the moment. The Flaps image is there but seems to have no input trigger. These values are direct comparisons between cockpit instruments in DCS and what is shown in the Helios Radar-Alt gauge. Am I missing some files or scripts that come from other profiles you made before or is the download file somehow corrupted? ON the positive side: the profile is a masterpiece of beauty, detail and realism - brilliant work as usual and much deserved thanks for your invaluable contribution to the community!

Latest Voice Attack Update OK? has anyone updated to the recent latest Voice Attack Version - any issues with VAICOM or AIRIO?

Is there any way to free up RAM on 2.5.5? I suspect that there is still a latent memory leak bug. My dcs crashed out of an MP session recently with memory at 99%..... and I have 32GB RAM with a 49GB page file. Sent from my iPhone using Tapatalk

has this been reported and acknowledged as a bug by @Heatblur? I read about the same issues in a few places and have both problems described in this thread.

Happens to me also occasionally. If you issue a specific formation command like 'go echelon right' it seems to force the command and you normally get a positive response. Sent from my iPhone using Tapatalk

sent you a PM.

VAICOM PRO plugin for VoiceAttack Thanks Hollywood. That's clear. This problem is a different one: although the radar is in fact not locked at all, AIRIO seems to think that it is. Repeatedly asking Jester to break lock does not help - he responds with "OK" but the radar still shows as TWS (no change, since there was no lock state to begin with). However, AIRIO thinks that it is still locked and lets no commands through. It seems there is a conflict between the actual radar state in DCS and what AIRIO thinks it is. I am not alone in having experienced this behaviour occasionally. A workaround in the past was just to restart the mission. Now it seems that this does not work. Sent from my iPhone using Tapatalk

This issue and the wingman getting stuck appears to be a DCS bug that came with 2.5.5. Sent from my iPhone using Tapatalk

I checked all but got no clues. Tried changing the order of the entries in the export.lua by moving the VAICOM entries to the last line. This might have helped since I experienced no delays since then, but in one mission the 'Radar is in Lock State' issue reappeared and remained stubbornly in the same mission despite restarts. Did you ever find out the cause of that one? Sent from my iPhone using Tapatalk

I have the same problem intermittently. did you manage to solve your issue?

thanks RedeyeStorm for clearing that up, I had a suspicion that this came after the latest 2.5.5 patch. The delays in response have been around a bit longer and are intermittent. A mission restart or DCS restart sometimes fixes it and sometimes it's not a problem at all. IN mission there seems to be no way to reset it. even restartinfg VoiceAttack does not help. I have Win 10 and am now experimenting with the UDP Packet fix to see if it might be related, even though that issue is not really Windows 10 related. Couild just be a DCS bug though... it's really frustrating when your mission pressure mounts and suddenly Wingman and Jester are smoked up on weed... :p

@ Hollywood: I have two problems at the moment: - Occasional long delays between VAICOM sending a command to DCS and DCS actually registering the command - sometimes up to 10 seconds. Direct comms using the menu manually go through straight away. This applies to AIRIO commands and AI radio comms. - Jester manual radio tuning is broken completely. Command is recognised correctly but results in random or no changes to the frequency Any ideas? Sent from my iPhone using Tapatalk

I got myself three Lilliput 8" touch screens and a powered usb 3.0 hub. Never looked back. I use the touch function for extra controls through Helios. Sent from my iPhone using Tapatalk