-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conflict with VLED program #101
Comments
Unfortunately this project just uses the DCSExportScript tool and doesn't have any control over that lua export implementation. Since that project is no longer receiving updates I have been working towards DCS Bios support as an alternative which you can try (in the other thread you commented on): #41 (comment). That is an early beta build that still has some limitations and will probably be a couple months before I can continue updating it. However it may allow you to use both tools at the same time. |
If I use some of the existing profiles for stream deck that use the sd interface, will this new version work with them? I guess I'm not sure I understand what one button type means. I'm also looking at a version VPC LED system that also uses DCS-BIOS so maybe hope there. Thanks for your comment and all your hard work! |
No you would have to create a new profile using only the DCS Bios button. It only supports momentary button presses right now. |
I understand! Is it compatible with DCS flight panels fork of DCS bios? |
Yep, that's the fork I recommend. |
I have alerted the dev on the VLED program, but he has previously been unable to find the cause the two programs are conflicting. There is a work around scripts attached created by a community user but I wonder if there is anything that can be done on this end to prevent the conflict. Thanks!
VLED Program
https://forum.virpil.com/index.php?/topic/3903-vledcontrol-for-dcs-control-the-leds-of-your-virpil-devices/
VLED Lua Export.
https://github.com/Nereid42/VLEDCONTROL/blob/main/VLEDCONTROL/Scripts/vled/VledExport.lua
Fixed Workaround (Page 4 of thread)
Scripts (1).zip
The text was updated successfully, but these errors were encountered: