goldleader

Don't forget there are two bindings for the Autopilot Engage disengage 1. AAP Engage/Disengage which is default bound to the A key and the Black button on the warthog throttle next to the Autopilot mode three position switch (ALT:ALT/HDG:PATH) 2. Left Throttle button which is default bound to the Q key and the Red Pinky button on the front of the left throttle handle AAP Disengage/Engage (A) is not functioning as designed, Left Throttle Button (Q) is functioning as designed quick fix is to bind both buttons on your hardware to the Left Throttle Bind in the game.

Hi, I don't know if this will help but this is my Export.lua using TacView, DCSBios (Facepanels Version) SRS and VAICOM, I found that the order in which everything goes in the export.lua makes adifference, I am not sure why mine works in this order, but everything is working like this. local dcsbioslfs = require('lfs'); dofile(dcsbioslfs.writedir()..[[scripts\DCS-BIOS\BIOS.lua]]) --BIOS = {}; BIOS.LuaScriptDir = [[C:\Program Files\DCS-BIOS\dcs-lua\]]; BIOS.PluginDir = [[D:\Users\Matt\AppData\Roaming/DCS-BIOS/Plugins\]]; if lfs.attributes(BIOS.LuaScriptDir..[[bIOS.lua]]) ~= nil then dofile(BIOS.LuaScriptDir..[[bIOS.lua]]) end --[[DCS-BIOS Automatic Setup]] local tacviewlfs=require('lfs');dofile(tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[scripts\VAICOMPRO\VAICOMPRO.export.lua]]) -- load the DCS ExportScript for DAC and Ikarus local dcsexportlfs = require('lfs'); dofile(dcsexportlfs.writedir()..[[scripts\DCS-ExportScript\ExportScript.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Tech\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil); Also I did notice you have local twice before the tacview line in your post of your export.lua Hope this is of some help

Hopefully this has not been asked before too recently, but 429 pages of messages to go through is a lot, so apologies if it has. Havinig a minor issue in the Huey while using SRS, if I set the SRS setting "Use DCS Cockpit PTT" to On everytime I press any of my Viacom keybinds my SRS Radio latches on, I have tried a few things but the only thing that seems to resolve it is turning that setting off, it only seems to affect the Huey Module, but I would like to be able to keep that on, as Intercom has just been implemented and I would like to use the two seperate PTT buttons (RADIO and ICS) for their dedicated purpose and use Vaicom without broadcasting everything on SRS.

Thank you.

Togg What Font did you use for your Icons, I am makng a couple more to suppliment your already awesome Icon set and would like to make the font the same. Thanks

Another here with the VAICOM plugin not working with DCS since the last update. Things I have Tried: I have done a Repair on DCS A full reset of everything except my License in the VAICOM Configuration Window I have uninstalled SRS and manually deleted all traces of SRS from my Saved Games folder, I have deleted my Export.lua file I have removed all files relating to DCS BIOS I have read through the install procedure in the PDF Manual again and everything seems as it should be. I tried with the GPS Module disabled, and then uninstalled. I have tried in various missions/situations/modules, I have tried everything and still no luck, I have been trying to get this to work for a couple of hours, the only interaction I seem to get between DCS and VAICOM is "Listening Suspended" and the low pich beep when I quit and return to menu in DCS, so there is obviously something happeneing, but nothing more than that. This is very frustrating, if anyone has any ideas, I would appreciate them Voiceattack is running as Admin Have since Tested on an Old PC Running DCS World Open Beta 2.5.5.40647 with SRS 1.7.1.4 Installed, DCS BIOS running and VAICOM works, so seemingly either a DCS Issue or a local issue. *** Solved *** Did a Lot of fault finding and it turned out to be an autoexec.cfg line without a value at the end of it caused the issue stopping VAICOM from working

1. dynamic spawns that enable/disable based on the coalition ownership of the airfield/farp? 2. Undo/redo 3. Ability to add custom kneeboard via the mission editor. Maybe not possible this time around but will ask any way. 4. native lua API access to the in-game warehouse system

When you are trying to set up any GPS/INS guided weapon using the ddi in Pre Planned mode and press an already boxed PP mission button the weapon switches to TOO mode causing any alignment to be lost and the co-ordinate entry process to have to be started again. .trk file attached Is this correct behaviour or a bug? JDAM TOO Bug.trk

Thanks for your work on this Ranma13, I look forward to the Release.

Thanks for the update Cobra. :thumbup:

was that just by editing the .dds files Jack? it looks amazing. :thumbup:

have you tried using the Hotkey Switch shortcut and have the key combo set to the same with one icon for on and one for off or does it keep the key depressed when it is in the on state?

DCS has requested the runtime to terminate it in an unusal way Hi @BIGNEWY, Thanks for the reply, I check the installation of those runtimes and they are good, now getting this error

Hi, I am currently working away from home for a long while and I am trying to run DCS World Open Beta 2.5.2 on my Mac Powerbook Retina with Bootcamp, I am alway booted directly into windows. Specs are Processor: Intel® Core i7-4870HQ CPU @ 2.50GHz (8 CPUs), ~2.5GHz Memory: 16384MB RAM GPU: NVIDIA GeForce GT 750M I am aware the minimum spec is a NVIDIA GT760M but even so I can run the Stable relase fine, obviously with my specs it is not the best but playable. The Game is loading ok, but when I try to start any mission on any map when the terrain starts to load I get the crash that is mentioned in the Title which is shown in the png attached. All windows updates are sucessfully installed and NVIDIA Drivers are 389.11. GeForce Experiene is installed. I have reinstalled both the vcredist and DXSetup that are in the "Dist" folder in the OpenBeta install folder and restarted. I have run clean up, repair and update via commandline, and Skatezillas GUI app I have set Power managemnet to "Prefer Maximum power"in the NVIDIA CP I have run /sfc scannow My Crashlog and DXDiags are attached Can somebody have a look and potentially tell me what I have been afraid of that I can play Stable but not OpenBeta so will have to wait for the F/A-18 and Persian Gulf! Any assistance would be greatly appreciated. dcs.log-20180602-005324.zip

With the new update to 1.2.10 the aircrafts folder is now aircraft, this will be why your mods stopped working, you need to rename you folder in each mod.

2 x Asus GTX 680