-
Posts
48 -
Joined
-
Last visited
About Arakahn
- Birthday 04/04/1978
Personal Information
-
Flight Simulators
DCS
-
Location
Montreal, Canada
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Since the last update I get a tremendous lag with the data display on the F18 UFC (5-10 seconds easily), where before the update the data displayed would be synced in less than a second
-
Mission 3 Broken (Latest OB Update)
Arakahn replied to Arakahn's topic in F/A-18C The Serpent's Head 2 Campaign
Awesome, thank you Badger! Really love the campaign so far; as all your other material it is quite fun, well done, great voice-overs and well worth every penny. -
I failed miserably mission 3 last week, and when I tried it again (after update .25026) the mission is no longer feasible a s you start boxed in on the carrier
-
cannot repoduce and missing track file Turning off ADF
Arakahn replied to Arakahn's topic in DCS: F/A-18C
Even with the ADF turned off? What does the Off do then? -
cannot repoduce and missing track file Turning off ADF
Arakahn replied to Arakahn's topic in DCS: F/A-18C
That does indeed get rid of the beacon indicator on the HSI, however as soon as I go back to that frequency the beeping resumes, so it is indeed broken (when turned off it should actually turn off). -
[REPORTED] F10 Map broken with Custom Viewport / UIMainview Sizes
Arakahn replied to ams999's topic in View and Spotting Bugs
Having the same problem as well 2_monitors-FA18C.lua -
Help :( Finally decided to use the ADF (all AB I was using had Tacans before). When I turn on the ADF, everything works fine. When I put it back to off and reactivate the SQCH, the beacon still displays on the map and the ADF beeping continues. I tried everything; switching radios for the ADF, off, on, reactivate SQCH on both radios, etc. Still cannot get the ADF to turn off...:helpsmilie:
-
I used to have the Tacview item in the DCS options, but I noticed that I no longer have it. Currently running the latest version of DCS Beta. I tried uninstalling Tacview and reinstalling, both in version 1.7.1 and 1.7.2 (final release, not beta). It is exporting the files from DCS, but the menu just is not there. I did find those lines in the DCS log though: 2018-08-30 00:02:10.446 ERROR SECURITYCONTROL: Failed to parse manifest: mods/tech/tacview/dcs_manifest.x86_64 2018-08-30 00:02:15.942 INFO Scripting: plugin: SKIPPED 'Tacview by Raia Software': not authorized Help? :(
-
I also offer my voice if you like; feel free to pm me
-
Had the same issue as Sanatog, indeed deleting the lua file and rebuilding solved the issue. I also had the issue that the export script messed up my Helios export, so I modified the script as such: local lfs=require('lfs'); dofile(lfs.writedir()..'Scripts\\Helios\\HeliosExport.lua') --dofile(lfs.writedir()..[[scripts\SRS\DCS-SimpleRadioStandalone.lua]]) dofile(lfs.writedir()..'Scripts\\TacviewGameExport.lua') -- VAICOM PRO server-side script -- Export.lua (append) -- version 2.5.4 -- do not edit next line: -- 075CB672-F323-4995-B97D-AB363BAE61E4 dofile(lfs.writedir()..'Scripts\\VAICOMPRO\\VAICOMPRO.export.lua')
-
SUCCESS!!!! :D For those who it does not work in the F18 with the latest OB update, here is the solution that @Hollywood_315 and I found. In the DCS World\Mods\aircraft\FA-18C\Cockpit\Scripts\devices.lua you should have that line: -- HOTAS Interface devices["HOTAS"]= counter()--13 -- Stick and throttle grip In vaicompro.export.lua change the device ID in this block: if mod == "FA-18C_hornet" then GetDevice(38 ):performClickableAction(3027,0.2) GetDevice(38 ):performClickableAction(3027,0) LoSetCommand(179) would become if mod == "FA-18C_hornet" then GetDevice(13):performClickableAction(3027,0.2) GetDevice(13):performClickableAction(3027,0) LoSetCommand(179)
-
Here is what I have in the devices.lua: -- Radio & Comm devices["UHF1"] = counter()--38 -- VHF/UHF Receiver-Transmitter - ARC 210 devices["UHF2"] = counter()--39 and the vaicompro.export.lua: Flush = function(self) local mod = LoGetSelfData().Name if mod == "FA-18C_hornet" then GetDevice(38 ):performClickableAction(3027,0.2) GetDevice(38 ):performClickableAction(3027,0) LoSetCommand(179) return end I see in the PTT tab that COMM1 is at device 38 and COMM2 at device 39, recognizing FA-18C; works in easy comm but not in full comms :(
-
Tried playing around with the values (38, 39, 40, in every combination), no luck :(
-
Just tested with easy comms and it works, still no go with full comms though
-
Ok, been browsing all 76 pages in am unable to fix the problem. Since the OB's last update I too have the problem many have had; VA recognizes the command but is not being activated in DCS until I press my COMM1 hotkey (ralt+\). I tried everything; resetting everything in VAICOM, reinstalling to the latest version, removing and re-adding the chatter.dll, deleting all the .lua files as mentionned by another poster, repairing DCS, redoing my key binding and making sure I don't have any conflicts in DCS. No error in the log file. I'm at a loss... Attaching here my export.lua in case. Export.lua VAICOMPRO.export.lua