Jump to content

Eraseri

Members
  • Posts

    21
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I sincerely hope that this issue gets addressed. It is very limiting at the moment. For instance, there is no possibility to display AH-64D EUFD without failing integrity checks. It should be possible without "cheating" with scripts. Same goes for many other modules like AJS-37 Viggen. Viggen doesn't have radar or mawerick display availability.
  2. I noticed during my testing that 1440p has larger dots than the 1080p. I encourage other people to test 1440p against 1080p to verify my findings
  3. Hi, I would like to inform you that there is huge discrepancy between 1440p and 4K spotting. I'm running on 4K monitor and I've been having much harder time spotting things than flying buddies. I ran a test with 1440p and 4K resolution. The difference is tremendous as you can see in the attached photos. There are two targets in front. One is 3 Nm and another one is 6 Nm. The dots are virtually double the size on 1440p resolution. This test made me feel so sad of having 4K screen... So it's good if it has been improved but I sincerely hope that the work continues to bring different resolutions to same level. 1440p is like cheating compared to 4K. During this test only setting that I changed was the resolution.
  4. Partially replying to my own question. There has been some changes to the Mirage F1 .lua-files. Bailey's instructions give as an example the "Fuselage bombs pushbutton". In the example the Button ID is 3594. However, inspecting the clickabledata_common_F1C.lua -file reveals that the Button ID is actually 3517. When changing the button ID from streamdeck profile the pushbutton works. If someone would have some tips how to get the buttons to populate it would great
  5. Can anyone help with Mirage F1 with streamdeck? Streamdeck doesn't populate any buttons. Additionally, none of the inputs I push work. However, I can see that exports from DCS to streamdeck, such as button status, DO work. I'm having this exact .lua in this folder. Most of the other planes populate buttons just fine, excluding Ka-50 and F-15E. I have tried two different streamdeck-profiles, one made by Bailey. Both of them have the same issue. I have manually checked that the DCS ID on streamdeck is matching the ID on .lua-file.
  6. SOLUTION: Volanta is the culprit that is interfering with DCS-ExportsScript. When I removed everything except exportscript from export.lua, Streamdeck worked. After I put back everything but Volanta, Streamdeck worked again. After returning Volanta it didn't work any longer.
  7. Unfortunately it didn't help. Down below is my current export.lua. Export to Volanta and TelemFFB work just fine -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]]) local telemffblfs=require('lfs');dofile(telemffblfs.writedir()..'Scripts/TelemFFB.lua') local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil) dofile(lfs.writedir() .. "Scripts/DCS_Volanta.lua") Below is the start of my DCS-exportscript\config.lua -file -- Ikarus and D.A.C. Export Script -- -- Config File -- -- Copyright by Michael aka McMicha 2014 -- Contact dcs2arcaze.micha@farbpigmente.org ExportScript.Config = {} ExportScript.Version.Config = "1.2.1" -- 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.
  8. Is there anyone else having troubles with getting Streamdeck to work? Mine worked for quite some time. However, now it has stopped working completely. Streamdeck is not detecting any module any longer. Streamdeck can populate bindings for the planes, [that work]. I haven't touched the settings. I checked the network settings as in the instructions and they are matching. Other exports in my exports, such as TelemFFB is working fine. There was some hiccups with Volanta. When the software was not on, it pretty much disabled others as well. Here is my export.lua -file local wwtlfs=require('lfs') dofile(wwtlfs.writedir()..'Scripts/wwt/wwtExport.lua') -- load the DCS ExportScript for DAC and Ikarus dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]]) local telemffblfs=require('lfs');dofile(telemffblfs.writedir()..'Scripts/TelemFFB.lua') local Tacviewlfs=require('lfs');dofile(Tacviewlfs.writedir()..'Scripts/TacviewGameExport.lua') pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil) dofile(lfs.writedir() .. "Scripts/DCS_Volanta.lua") nullnull
  9. I found yet another module which doesn't populate the buttons on streamdeck; Mirage F1. It's very sad situation I used Baileys example-streamdeck profile. I also have to .lua -file from asherao's branch of ExportScript. There are also some buttons in the profile that work and some buttons that dont'. For instance, M-1 Mode switch button doesn't work when pushed. However, the status is updated if I switch it from game. I wonder what is different in Mirage F1-lua and Mig 19P lua-file made by Invictus84? Thankfully Mig-19P populates fine on streamdeck!
  10. Here is a video what happens to Jug every time after repair:
  11. Hi, This streamdeck profile is working just fine on single player. However, it doesn't work on multiplayer. Any idea of the problem? I haven't faced similar problem with any other streamdeck-profile.
  12. I can confirm I experience the same problem. First the aircraft is lifted for repair. After the repair the aircraft is dropped down from air and that's when the landing gear breakes.
  13. Hi, I have been playing as KA-50 in multiplayer servers. Few times Gazelle has collided into my rotor on purpose. Gazelle can survive such collision without a problem and go back into base for repairs. Here is an example of situation where Gazelle-pilot walked away unharmed from his chopper while the repair crew put some ductape to the hull for a new round. Surely this is unsportmanship behavior - that I can accept. What is harder to accept is the poor damage model of Gazelle. I would post ACMI, however, unfortunately it is over 50 MB.
  14. Port in particular. Follow this video: Additionally, check that you are using Bailey's fork of the DCS Interface. Also, test with another module if one is not working. https://github.com/asherao/DCS-ExportScripts/tree/master
  15. Thank you for nudging me in the right direction. The code snippet didn't help me a bit. However, it got me to open VSCode and worked my way with ChatGPT to extract the data. Sounds great! I spent hours with ChatGPT to extract the data from clickabledata.lua and devices.lua. It's not a pretty extract but it can be used to find all the required data for buttons to use with Streamdeck. My only question remains regarding the format of the data. Here is an example output I have: [262] = "%0.1f", -- ENERG-AER-RIT-PTRdefault_2_position_tumb(DCgroundPowerHint, devices.ELEC_INTERFACE, device_commands.Button_1, 262) Button ID: 3001, DCS ID: 262, Device ID: 2 So what is the formula for the output. How can I know whether its floating or decimal or something else "%0.1f" ?
×
×
  • Create New...