jiblet

Volanta. That's the cause of my problem! After reisntalling everything (like 200GB of everything) and then slowly reinstalling plugins, it seems that if you ahve this exporet file: -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) dofile(lfs.writedir() .. "Scripts/DCS_Volanta.lua") local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') YOu get the problem I had. If you ahve this: dofile(lfs.writedir() .. "Scripts/DCS_Volanta.lua") local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) THen it works... but with over a second of lag between pushing a button on the SD and seeing a result in-game~~~~. And if you have this:v -- dofile(lfs.writedir() .. "Scripts/DCS_Volanta.lua") local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) With Volanta commented out, or indeed missing entirely then everything works fine. FML.

Hah, no problem @frostycab - we all make daft mistakes and I'm happy to be called out on them because I'm fairly convinced that I am indeed doing something daft here. However, it's not either of these ID Lookup path is set and returns values from the game. And yes I'm in a mission when I try th eDCS Comms button. The Export.log shows things like "11:31:58:593 : File 'C:\Users\jiblet\Saved Games\DCS.openbeta\Scripts\DCS-ExportScript\ExportsModules\JF-17.lua' loaded" So it seems the DCS side of things is loading the right export script when I start the mission.

It's not so much the individual aircraft scripts. My problem is that the plugin can't seem to communicate with the game itself. Taht side of things seems to be handled by files within DCS-ExportScript\lib, like Tools.lua

The export scripts is what I meant. The stream deck plugin has various release so that’s fine. I’m just wondering if something in the more recent export scripts is breaking it. It’s probably something else though. I’m grasping at straws.

My suspicion (and it really is only that) is that it's an issue with DCS-ExportScripts. Only because there are no versioned releases for it on Github, you just have to get the current code, so no real version control. The setup video from CT shows there used to be versioned releases, so I'm not sure what happened there. But it feels to me like there might be an issue with the current state of that script. Though I'm really not sure. Anyone have an older, versioned copy of it?

I wonder if anyone can help with initial setup? Having followed the docs I have the export script installed and running (Export.log shows for example "11:31:58:593 : File 'C:\Users\jiblet\Saved Games\DCS.openbeta\Scripts\DCS-ExportScript\ExportsModules\JF-17.lua' loaded" when starting a mission in the JF-17 But when I try the "DCS Comms" button on a DCS-Interface button, it shows: "DCS module not detected." The ports appear to be configured correctly in the Stream Deck plugin: IP: 127.0.0.1 Listener: 1725 Send: 26027 And in the Config.lua for the DCS-ExportScript: -- Ikarus a Glass Cockpit Software ExportScript.Config.IkarusExport = true -- false for not use ExportScript.Config.IkarusHost = "127.0.0.1" -- IP for Ikarus ExportScript.Config.IkarusPort = 1725 -- Port Ikarus (1625) ExportScript.Config.IkarusSeparator = ":" -- D.A.C. (DCS Arcaze Connector) ExportScript.Config.DACExport = false -- true for use ExportScript.Config.DAC = {} -- first hardware ExportScript.Config.DAC[1] = {} ExportScript.Config.DAC[1].Host = "127.0.0.1" -- IP for hardware 1 ExportScript.Config.DAC[1].SendPort = 26026 -- Port for hardware 1 ExportScript.Config.DAC[1].Separator = ":" -- secound to n hardware --ExportScript.Config.DAC[2] = {} --ExportScript.Config.DAC[2].Host = "127.0.0.1" -- IP for hardware 2 --ExportScript.Config.DAC[2].SendPort = 9092 -- Port for hardware 2 --ExportScript.Config.DAC[2].Separator = ":" -- Ikarus and D.A.C. can data send ExportScript.Config.Listener = true -- false for not use ExportScript.Config.ListenerPort = 26027 -- Listener Port for D.A.C. Wireshark seems to show the expected values being sent and received on the right ports. 68808 1042.283182 127.0.0.1 127.0.0.1 UDP 42 1725 → 26027 Len=10 68815 1042.343534 127.0.0.1 127.0.0.1 UDP 42 1725 → 26027 Len=10 (And Wireshark shows it failing legitimately when DCS is not running): 111622 1892.546177 127.0.0.1 127.0.0.1 UDP 42 1725 → 26027 Len=10 111623 1892.546189 127.0.0.1 127.0.0.1 ICMP 70 Destination unreachable (Port unreachable) Any thoughts on what idiotic thing I've done wrong?

So er hey, how's it going?

Successful replacement of the tail on my broken Warthog: http://imgur.com/a/RYg3q, thanks debolestis! Although the piece works perfectly, there are a couple of things that other users might want to bear in mind: 1. I used a 2mm drill bit to widen the 2 screw holes on the bottom where DIN connector attaches. They're supposed to be 2mm according to the description, but were pretty much pin holes on my print, so without widening them the screws couldn't get in to begin biting into the nylon. Not a big deal to do. 2. Because of the narrow hole through the neck of the piece, I had to tweak/arrange and carefully bend the cabling , including the grounding ring on the black wire (into a U shape), then push it all through very gently with a chopstick (high tech!). Finally, I bent the grounding ring back into it's flat shape and all was good with the world. Better to have the extra thickness on the neck though, just don't panic when you see it :)

Thanks, now let me hop in my time machine and go back to nov 2011 so that I can tell myself that. Way to be a dick about it. I'm about to go through a reinstall to put everything up to 1.2 DCS-World and I happen to own BS2 upgrade. Right now I have BS2 installed (having had to install 1 and then upgrade it again after a rebuild of my machine). That's fine. And now to get to DCS World so that I don't have 4 carbon copies of Georgia, I to... what? Who knows? I'm assuming I need to install DCS World AND BS1, Then install the DCS World BS2 upgrade . DO you not see how tedious and unnecessary this is? Just because you bought it 3 times doesn't mean anyone else should have to. The BS2 upgrade installer should simply ask for your BS1 key and then let you move on with your life. The current situation is just silly and not befitting a software company of EDs standing; simple as that.

Sadly that appears to have made no difference. I need to figure out how to move the menu too since at the moment its showing over onmy right hand monitor on top of the MFCD outputs on softTH. I'll have another look through the lua later.

Anyone have any idea how to make a similar change for DCS:World? I can't find an equivalent menu.res file, though there are a few files containing "acceptmouse" none of them appear to be appropriate.

Is there an update for DCS World 1.1.2.0 to 1.1.2.1 anywhere or is it a case of downloading all 5GB again? :(

Better yet you wont even need one since DCS A10C will detect your fancy pants joystick and set (most) of the controls up for you. You just need to bind the trim hat to trim instead of view panning (assuming you have a TrackIR or substitute). You may want to make some other changes as you go so that you're reaching for the keyboard less and less. That's exactly how I had my old CH pedals connected with my warthog for the last 2 years. Just last week I bought some saitek combat pedals (though I cant recommend them myself... I miss my CH ones!) and gave my CH ones away to a guy who is successfully using them through a £10 gameport -> usb converter. Wrecking Crew is spot on. For the A10 you wont miss them one bit since you simply dont need their functionality. If you go back to Falcon (assuming you were playing that!) then you might want to have your old cougar throttle to hand (I still have mine on a shelf!) or you make do... The warthog does have one spare axis on the throttle that you could use as a range or ant elev... I use it as a view zoom in DCS though.

If it helps I came from a background of 2 cougars (first throttle died and the stick got very wobbly) and went to a HOTAS Warthog and it's like night and day!

If you have a Cougar then CMS, DMS and TMS should be simple to setup as your stick is almost exactly the same as the actual A10 stick. The only thing your missing is the clickable CMS (CMS Z-axis). Working from left to right across your stick hats they are CMS (H4 - farthest left hanging off the side of the stick). TMS - on the left side of the face of the stick - H2. Then DMS on the right side of the face of the stick - H3. Your throttle has a thumb microstick right? That should be your slew. The mic switch on the front of the cougar throttle I'd explore creating a modifier so that you can use that as both Coolie hat and Mic switch (when modifier is applied) As for boat switch you could put that on your Dogfight switch as it has the same movement. And china hat... I'm not sure where would be best to put that on a cougar throttle. I'd imagine someone around here must have made a usable profile for the Cougar, so you may be best starting with that and tweaking it as you find you need to. Edit take a look at this example: http://www.cavallersdelcel.cat/magatzem/comunitat/perfils/DCSWarthog_Viper.jpg