overalien

I smacked them with the MK-82 and got the pilot reporting Artillery Splashed. I assumed they are all dead. I definitely got the IGLA too in that run Later saw that there was a truck or two standing undamaged and went by to take those out too. This was only much later though, when I got bored of circling the airport. Do all the units at that one location need to be killed in a certain time? Are there other enemy locations that I have missed? Sent from my iPhone using Tapatalk

Voice attack Audio recording and playback, like an audio memo I tried it and it's brilliant. I needed to make a few adjustment to the profile so that I could integrate it into VAICOM Pro - now works like a charm as part of my VAICOM profile. Sent from my iPhone using Tapatalk

The mission seems to not progress after splashing the mortars and being told to anchor above Kobuleti. Been flying in circles there for over 30 min but nothings else seems to happen. Trigger bug? I am on the latest OB.

Yep I have the same issue now. Looks like a bug to me. Sent from my iPhone using Tapatalk

Seems to me that the Auto Gain Control is bugged in the current OB version. I have to manually tweak the tgp contrast, brightness, gain and level before I get a decent image. Sent from my iPhone using Tapatalk

Does anyone have an iBeam in use with SSA Sound Module?. I use a mix of audio and SSA plus the jetseat on top (!!) . In the iBeam the brrrrrt in the Hog is somewhat disappointing and I'm lucky that the jetseat compensates admirably in this case. With other effects the iBeam is just amazing for immersion. Has anyone made tweaks to their audio samples for Sound Module ti I adjust for the iBeam's characteristics? I have already done the low pass filter in Voicemeeter and this made a difference, but I'm wondering if a sound smoke tweak might help some more. Sent from my iPhone using Tapatalk

I have the same problem. Is this a general bug or specific to the F-14? Sent from my iPhone using Tapatalk

Thanks for the help man!! really appreciate. Works like a charm now :smilewink:

I am trying to add axis commands to control volume of radios etc. to the A-10C. The normal method and code for later aircraft does not work for the A-10. I have also tried various hacks with guessed iCommand equivalents by using the axis command in the default.lua as an example, but this also does not work. Anyone figured this out for the A-10C? in clickabledata.lua, I found axis entries like this, which suggest that i could map an axis elements["PTR-ANARC186-VHFFM-VOLUME"] = default_axis(_("Volume"), devices.VHF_FM_RADIO, device_commands.Button_5, 147) Code example I tried in default.lua using the above which does not work and breaks the Controls GUI App: {action = device_commands.PTR-ANARC164-VOLUME, cockpit_device_id=devices.UHF_RADIO, name = _('UHF Radio Volume'), category = { _('_Radio Volume Knobs-MODIFICATIONS')}}, {action = device_commands.PTR-ANARC186-VHFAM-VOLUME, cockpit_device_id=devices.VHF_AM_RADIO, name = _('VHF AM Radio Volume'), category = { _('_Radio Volume Knobs-MODIFICATIONS')}}, {action = device_commands.PTR-ANARC186-VHFFM-VOLUME, cockpit_device_id=devices.VHF_FM_RADIO, name = _('VHF FM Radio Volume'), category = { _('_Radio Volume Knobs-MODIFICATIONS')}}, {action = device_commands.PTR-TACAN-VOL, cockpit_device_id=devices.TACAN_CTRL_PANEL, name = _('TACAN Volume'), category = { _('_Radio Volume Knobs-MODIFICATIONS')}}, {action = device_commands.PNT-LEV-RWR-AUD, cockpit_device_id=devices.CMSC, name = _('RWR Volume'), category = { _('_Radio Volume Knobs-MODIFICATIONS')}}, {action = device_commands.PTR-LGHTCP-FLOOD, cockpit_device_id=devices.LIGHT_SYSTEM, name = _('FLOOD LIGHTS'), category = { _('_Lighting Knobs-MODIFICATIONS')}}, {action = device_commands.PTR-LGHTCP-FLIGHT-INST, cockpit_device_id=devices.LIGHT_SYSTEM, name = _('Instr. LIGHTS'), category = { _('_Lighting Knobs-MODIFICATIONS')}}, I also tried various combos of this: {action = iCommandPlane_UHF_Volume, name = _('UHF Radio Volume')}, {action = iCommandPlane_VHF_AM_Volume, name = _('VHF AM Radio Volume')}, {action = iCommandPlane_VHF_FM_Volume, name = _('VHF FM Radio Volume')}, None of these bring any result. Any help would be appreciated.

Second that. +1 Sent from my iPhone using Tapatalk

Second that. Home Fries is a legend!!! Sent from my iPhone using Tapatalk

Performance on Surround is worse than using the one large monitor option described above. Not with the effort in my experience. Sent from my iPhone using Tapatalk

Tip: the link REPLACES the folder and has to have to same name exactly like the original folder including capitalization. Before making the link you should move all contents to the target folder and delete the original empty folder. Then replace it with a link with the same name. Sent from my iPhone using Tapatalk

Yes I have such issues with SSA and VAICOM as well. It is intermittent and hard to pin down. I assume it is a net resource conflict that comes up under certain circumstances.... Sent from my iPhone using Tapatalk

Not only in the F18. The Tomcat radar is terible in MP. Sent from my iPhone using Tapatalk

Same here. Intermittent on same mission. Tried run.exe and DCS.exe in admin mode but did not help. Sent from my iPhone using Tapatalk

Yip Sent from my iPhone using Tapatalk

2.5.6 Compatibility Issues unfortunately the campaign seems to be broken after 2.5.6 release by ED. scripting compatibility? my AI behaves strangely, AGM-88s fired by the Hornet SEAD Units seem not to track SAM radar and just fly past the targets at ridiculous altitudes and i get windows dialog boxes with script errors saying "unit does not exist". on mission end DCS hangs and there is no debrief or next mission cmd box.

I also have it. Sent from my iPhone using Tapatalk

I solved this kind of problem for myself in the A-10c by changing the snap view for default pilot view to a seat position further back and then setting an FOV that fits afterwards. You need to play around a bit with the xtrans parameter to get a good fit. Custom snap view must be enabled for this to work of course. Sent from my iPhone using Tapatalk

that sounds right. that is the default path. might be some permission issue then, I am not sure. I struggled long with mine but that was the solution i found for my issue.

the solution is simple: if your saved games is located anywhere else other than in your standard $USERPROFILE$ location on the C: drive, then you have to create a Junction Link in the $USERPROFILE$ folder called "Saved Games" which points to the actual location. This step is needed in addition to the modifications in the scripts as described by MBot.

I fixed the no-redirect drivers issue in DCS options - so that is working fine now. this made no difference to AOCS being muted - despite all redirects being disabled everywhere. various resets and re-installs also failed to help. tested the "single TTS Instance" option in VA. This also makes no difference. maybe we should collect some info on the others who have the same issue to see if we find some commonality. My HW specs are below in my sig, in addition i use the SteelSeries Arctis Pro Headphones. My problem started two updates ago, same as the other reports.

can confirm, I have same behaviour. have to hold the PTT until the "beep"

Hi @Hollywood_315 I did some more testing. When reverting back to two versions prior to the current VAICOM version, AOCS audio works perfectly, as soon as I update to the VAICOM Version prior to today's release, AOCS Audio is muted and nothing I do (including DCS Volume, full reinstall Voice Attack, VAICOM, checkng MS TTS) makes any difference. THe behaviour stays the same after todays VAICOM update, even when radio is tuned to Crystal Palace. To verify MS TTS, (while using the latest Version of Voice Attack and VAICOM) I created a command to test TTS from VA. The TTS audio works perfectly using this test command, but AOCS stays mute. I am stumped.... If it's any help, my DCS audio redirect options do not recognize any audio devices on my machine and stay blank when i select any drop downs. Could there be some issue here maybe? before I updated VAICOM all was working 100% though - i never had any funny problems with redirected audio from DCS and I never changed anything there anyway. So I am still suspecting a bug in VAICOM.