funkster

Hi - Been away a while. Am I right in stating that the patch for the consolidation of versions hasn't been implemented yet? I.e we still have two versions? Just checking in case I need to change shortcuts etc.

Are there any plans in the roadmap to expand / improve George? I.e. Moveable UI (Compass / Target List etc) Control FOV, Zoom, FLIR/TV, Slave from Pilot seat? Improve / "fix" Flight and trim handoff when changing seats. Better Pilot (AI) threat evasion. General communications / awareness comments similar to F14 Jester. etc etc At the moment the UI feels very "barebones" to say the least , compared to something like the F14 Jester system! Surely real life communication between pilot and CPG would be more in depth and this should be represented in the available UI functions. P.S I am aware that there are of some mods for additional key binds but it would be far better to have official / supported changes.

The old MT workaround was to create a shortcut pointed to the DCS.exe in the Bin-MT folder. This still opens the launcher! Which I assume is correct and the launcher should appear regardless of which .exe you run It would be better if they built in a checkbox into the launcher for MT / NONE MT Versions

Has this now been addressed?

Has this been solved? Or is it still with Devs? I am assuming the later based on my own testing?

Sorted on Viacom Discord. In case it helps anyone else. I needed to perform a full reset of the app...(Reset page - check all boxes and click master Zero). I noted that before the applying the fix, that the Keywords under the editor page /select keyword drop down were very limited / short and didnt seem correct... I therefore assume the fix was the reset of "Keywords"....but just do "all" in case. Also note that as I mentioned in my original post - I had to move the viacom code in the export.lua to the top so that it runs before the Winwing code. Hope it helps someone in future. Thanks again to the Viacom Discord and BIOCRAVEN! Top man!

Just come back to DCS after short break and updated VA to 1.14 and Vaicom to 2.9.5.0. however viacom has now stopped functioning. Essentially , Viacom displays the correct DCS modules in the PTT tab of the Viacom app. Keywords are recognised in VA but nothing happens. ....even internal commands like " Chatter" or "Kneepad" ....are recognised but do nothing?? export lua seems fine - I only have Simmapp pro (Winwing) , Tacview and Vaicom in there. I did have to move the Vaicom code to the top but other than that it seems to be fine. Any ideas ??

Quick question I've got Simapp working just fine for multiple devices including keybinds etc however I would like to clarify how the Key binding in Simapp pro actually works. i.e. Do you need to select the module / click run every time? What actually happens when you click run on a keybind profile? i.e. does it update the relevant DCS planes keybinds LUA and therefore is then saved? (i.e the LUA in the input folders in saved games) Depending on above -Do you need to exit DCS to load a new Keybinding if you change planes?

Hi - I have also have the same intermitent issue as the OP i.e. the WPN button being pressed (Ghost) repeatedly in CPG. It prevents: Continuous Lasing. Slaving from Pilot seat. Jerky/ stutter movement with Man Trk on TAD Changing to any other page on the MFD. I checked control assignments and there are none set for the WPN button so it isn't a hardware conflict. Also it is strange that this is happening on multiple setups / PC. Although rare (ish) it has happened multiple times Track uploaded - issue starts to happen in the last 5mins (guess) when the CPG Man Trk appears jerky. I then realise and change page on the left MFD which then shows the WPN button continually being pressed (Ghost) AT 18.07 (track time). AH64 WPN Button Issue track.trk

+1

Thanks alI for suggestions. Much appreciated. I had tried the remove shader and repair etc before I posted (I should have said so apologies). As suspected it didn't work .....However I have just found the solution. I had to change the cockpit display resolution to 1024 every frame and they now work.

awesome ! Thank you so much!

Is this a known MT bug or just my installation? Although I am not sure how this could be if the normal version of DCS works fine.

Have always used this util - fantastic! And great news on the new version and features! Quick Question -Will this work with the MT executable? Will we simply be able to configure a build for MT?

My Mirrors in the A10CII are just blank/blueish when running the MT version of the .exe ? Any ideas?