Jump to content

DCS-ExportScripts for Stream Deck Community Github Library


Recommended Posts

@Bailey

Did you see my post about not seeing anything above 828?

Toni Carrera (Ice Rhino)

 

ThrustMaster HOTAS Warthog Throttle & A10C Stick, ThrustMaster F/A-18C Stick, ThrustMaster TFRP Pedals, ThrustMaster Cougars x 2, fitted to CubeSim USB Screens, TrackIR 4 Active LED & Cap Reflector, Stream Deck XL

Intel® Core™ i7-5820K 12 Core Processor, 32GB RAM, 1 x 500GB SSD, 2 x 256GB SSD, 1 x 1TB SSD 4 x 4TB Western Digital Mechanical. 2 x ASUS GTX 1080's SLI, ASUS 29" Ultrawide flanked by 2 x 22" IPS Monitors

Link to comment
Share on other sites

Has anyone tried to integrate Helios with the Streamdeck DCS Interface so both can be run at the same time?

Trackir4 using the latest Trackir 5 software, Win10 Pro [Creator Update] updated from Win7Pro Pro 64Bit, Intel® Core™ i5-2500 3.30 GHz 6M Intel Smart Cache LGA115 , GigaByte GA-Z68XP-UD4 Intel Z68 Chipset DDR3 16GB Ram, GTX MSI Gaming 1060 [6 GB] Video Card, Main Monitor 1 on left 1920x1080 Touchscreen Monitor 2 on right 1920x1080 .

Link to comment
Share on other sites

On 4/2/2022 at 10:09 PM, sobe said:

Has anyone tried to integrate Helios with the Streamdeck DCS Interface so both can be run at the same time?

confused. What would improve? As it is, streamdeck with the DCS-exportscripts functionality allows the stream deck to send and receive the states of control buttons and dials from the aircraft in dcs to be reflected on the streamdeck hardware. Helios as I understand it, is just a way to duplicate the gauges and screens  in the aircraft on secondary lcd panels on your desk (or simpit)

4930K @ 4.5, 32g ram, TitanPascal

Link to comment
Share on other sites

skypickle

For the most part, I prefer the use of Helios as the profile sets forth most of your controls on your second screen without having to look down and press several buttons.  Unfortunately, a good Helios profile takes a lot of time to do so supplementing it with a Steamdeck profile solves the missing commands, etc. 

  • Like 1

Trackir4 using the latest Trackir 5 software, Win10 Pro [Creator Update] updated from Win7Pro Pro 64Bit, Intel® Core™ i5-2500 3.30 GHz 6M Intel Smart Cache LGA115 , GigaByte GA-Z68XP-UD4 Intel Z68 Chipset DDR3 16GB Ram, GTX MSI Gaming 1060 [6 GB] Video Card, Main Monitor 1 on left 1920x1080 Touchscreen Monitor 2 on right 1920x1080 .

Link to comment
Share on other sites

  • 1 month later...
On 1/17/2022 at 8:34 PM, Bailey said:

UH-60 Profile is coming along. Cant figure out why the Gen, Bat, etc don't turn on via the SD (even though the switch visibly moved) unless they are clicked or activated by keybind. 

2022-01-18 11_22_01-Stream Deck.jpg2022-01-18 11_21_40-Stream Deck.jpg2022-01-18 11_31_33-Stream Deck.jpg

 

Have you finished with building this profile and is it available?

Link to comment
Share on other sites

13 hours ago, bones1014 said:

Have you finished with building this profile and is it available?

I did not have the opportunity to complete the profile. The extent of my efforts is here https://github.com/asherao/DCS-ExportScripts/tree/master/docu/StreamDeck Examples 

There is a person who went the extra mile to make a more complete profile. Ask around on the UH-60L Mod discord to find it. They put a lot of good work into it. 

  • Like 1
Link to comment
Share on other sites

Almost 4,000 lines of code later, added some awesome and interesting capabilities to the following modules:

F-16, F-5, P-51D, Mosquito, AH-64D, F-86F Sabre, UH-1H Huey (all within 8000 arg/DCS ID range):
- Added LoAircraftInfo -- Provides a lot of aircraft properties
- Added AirportInfo -- Provides info on the two closest airports
- Added WindsAloft  -- Gets winds at the aircraft
- Added GroundRadar -- Reports 2 closest friendlies and 2 enemies (Use in Single Player)
- Added AirRadar  -- Reports 2 closest friendlies and 2 enemies (Use in Single Player)
- Added IglaHunter -- Locates closest Igla (Use in Single Player)
F5Media02.jpg

F-5:
- Added Radio Preset Readouts

UH-1H:
- Added Radio Stack Readouts
- Added Radio Preset Readouts
- Added Crew Status Readout
UH1HPic01.jpg

All wikis have been updated: https://github.com/asherao/DCS-ExportScripts/wiki

Remember to use the features only when appropriate, eg, single player, friendly multiplayer.


Edited by Bailey
  • Like 5
Link to comment
Share on other sites

6 hours ago, bones1014 said:

What is Igla? Inbound ground launched something?

It's a manpad. Shoulder launched ir missile. A big pain in the rear. Literally. 😛

Link to comment
Share on other sites

I like the thought and effort that has been put into the update.

 

Here's some info I found with the updated UH-1H.lua.
 

local crewStatusInfo = parse_indication(6) -- contains table of the status of the crew

parse_indication is from DCS-BIOS, so that and everything after that's called in the UH-1H ProcessIkarusDCSConfigLowImportance does not run.
e.g. these

  ExportScript.CrewStatusRepeater(mainPanelDevice) -- Crew Status Window
  ExportScript.RadioFreqs(mainPanelDevice)
  
  if LoIsObjectExportAllowed() then -- returns true if world objects data is available
    if LoIsOwnshipExportAllowed() then -- returns true if ownship data is available
  ExportScript.LoAircraftInfo(mainPanelDevice) -- Provides a lot of aircraft properties
  ExportScript.AirportInfo(mainPanelDevice) -- Provides info on the two closest airports
  ExportScript.WindsAloft(mainPanelDevice) -- Gets winds at the aircraft
  ExportScript.GroundRadar(mainPanelDevice) -- Reports 2 closest friendlies and 2 enemies (Use in Single Player)
  ExportScript.AirRadar(mainPanelDevice) -- Reports 2 closest friendlies and 2 enemies (Use in Single Player)
  ExportScript.IglaHunter(mainPanelDevice) -- Locates closest Igla (Use in Single Player)
    end
  end 

I dumped the function from DCS-Bios into my copy of UH-1H.lua to work around it. 

 

function ExportScript.parse_indication(indicator_id)
	local ret = {}
	local li = list_indication(indicator_id)
	if li == "" then return nil end
	local m = li:gmatch("-----------------------------------------\n([^\n]+)\n([^\n]*)\n")
	while true do
        local name, value = m()
        if not name then break end
		ret[name] = value
	end
	return ret
end

I don't know if you can go about doing the same, something something licensing Simple Public License 2.0 vs LGPL-3.0 license.

I just got the XL as a gift so I was checking what it can do and so showing some ready made text is very useful. At some point I'll see if I can do something to highlight the EGT  and potentially measure/countdown duration in yellow/red zone, I tend to run a bit close to the limit and find myself falling out of the sky when I get distracted.

Link to comment
Share on other sites

21 minutes ago, Grev said:

I like the thought and effort that has been put into the update.

 

Here's some info I found with the updated UH-1H.lua.
 

local crewStatusInfo = parse_indication(6) -- contains table of the status of the crew

parse_indication is from DCS-BIOS, so that and everything after that's called in the UH-1H ProcessIkarusDCSConfigLowImportance does not run.
e.g. these

  ExportScript.CrewStatusRepeater(mainPanelDevice) -- Crew Status Window
  ExportScript.RadioFreqs(mainPanelDevice)
  
  if LoIsObjectExportAllowed() then -- returns true if world objects data is available
    if LoIsOwnshipExportAllowed() then -- returns true if ownship data is available
  ExportScript.LoAircraftInfo(mainPanelDevice) -- Provides a lot of aircraft properties
  ExportScript.AirportInfo(mainPanelDevice) -- Provides info on the two closest airports
  ExportScript.WindsAloft(mainPanelDevice) -- Gets winds at the aircraft
  ExportScript.GroundRadar(mainPanelDevice) -- Reports 2 closest friendlies and 2 enemies (Use in Single Player)
  ExportScript.AirRadar(mainPanelDevice) -- Reports 2 closest friendlies and 2 enemies (Use in Single Player)
  ExportScript.IglaHunter(mainPanelDevice) -- Locates closest Igla (Use in Single Player)
    end
  end 

I dumped the function from DCS-Bios into my copy of UH-1H.lua to work around it. 

 

function ExportScript.parse_indication(indicator_id)
	local ret = {}
	local li = list_indication(indicator_id)
	if li == "" then return nil end
	local m = li:gmatch("-----------------------------------------\n([^\n]+)\n([^\n]*)\n")
	while true do
        local name, value = m()
        if not name then break end
		ret[name] = value
	end
	return ret
end

I don't know if you can go about doing the same, something something licensing Simple Public License 2.0 vs LGPL-3.0 license.

I just got the XL as a gift so I was checking what it can do and so showing some ready made text is very useful. At some point I'll see if I can do something to highlight the EGT  and potentially measure/countdown duration in yellow/red zone, I tend to run a bit close to the limit and find myself falling out of the sky when I get distracted.

Thanks for the heads up. I did not know that it was a part of DCS-BIOS as I saw it in _G. Easy fix. Use 

`local crewStatusInfo = ExportScript.Tools.getListIndicatorValue(6)`

instead. It is native to Export Scripts and I happened to use it in the other aircraft, so this issue with the huey was isolated. Thank you for identifying it so fast. Huey updated: https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/UH-1H.lua

Looking forward to see how you do the indicator.

  • Like 1
Link to comment
Share on other sites

On 1/23/2022 at 2:44 AM, Scofflaw said:
  1. I downloaded ExportScripts from github yesterday.
  2. The only script I have installed in DCS is this DCS-ExportScript.
  3. I tried a full windows reset, nvidia drivers remove and reinstall, reinstall exportscripts, the problem is still there
  4. I have streamdeck running, but it's a default install without any profiles.  I tried removing it and I still have the problem.  Nothing else running

I did perform some more testing, with an FPS counter + graph this time.  In the attached image, I ran the exact same scenario twice (quick start -> F16 -> Caucasus -> ready on ramp).  On the top half, at exactly the same moment, you can see the FPS is very jittery, and I highlighted the stutters in blue.  On the bottom graph, I have the script disabled (removed from folder), and it's perfectly smooth.

I did narrow it even further down to \DCS-ExportScript\lib\Tools.lua.  When this lua is commented out from ExportScript.lua, it runs smoothly.  I guess this makes sense since this lua is the meat and potatoes of this script.

--dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\lib\Tools.lua]]) -- remove for testing purposes

I tried to have a look at Tools.lua to see if I could perhaps remove some sections to see if performance improves, but this starts to be a bit above my skill level.

I did notice another DCS plug-in (DCS UFC Android App) has some users complaining about the same issue with the ExportInterval value causing stutters, but I don't think they were able to resolve that issue either.

fps_dcs.png

I didnt notice this until know, but where did you get `dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\lib\Tools.lua]])` from, exactly?

I have `dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]])`.

Link to comment
Share on other sites

  • 3 weeks later...
On 5/22/2022 at 10:04 PM, Bailey said:

I didnt notice this until know, but where did you get `dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\lib\Tools.lua]])` from, exactly?

I have `dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]])`.

I found that line in ExportScript.lua.  I was disabling individual parts of the export script to see if I could isolate what causes the stuttering.

run come save me

Link to comment
Share on other sites

Hi all. New here and have been searching for information about all this. I know there are 3 or 4 primary GIT locations that seem to all be supporting the Stream Deck plugin by Charles Tytler. The stream deck plugin works fine and am using the default DCS interface v1.0.4 (july 7 2021). I have seen references to DCS-Bios as well as some other script exporters and am I'm trying to determine if what I'm looking for/to-do can be done with this plugin and the default asherao DCS-ExportScript from that same site. It looks like the plugin is no longer updated so that's question one, the second question is about the other script exporters and whether they would be a better selection.

Since the plugin only has a small selection of options, I wonder if anyone who has used this and the exporters for awhile would be kind enough to answer a few questions?

1) there are no tri-state buttons in the plug-in. While a rotary can inc/dec a given ID value it can only display at most 2 visual conditions, and that conditional change can only be based off one ID value. Simplest example; Any 3-state switch in any cockpit. I was wondering if there was another plugin that has more input button options for the stream deck or if there was a way to use the Charles Tytler plugin to perform 3-way button graphic changes. I have seen some example screen shots in this thread that look like a full-string is being concatenated and is populating the text field of a stream deck button. What I haven't seen or know if it is possible with the current plugin, tri-state graphic changes can be done, or is there even a plugin that can.

2) since multi-state conditions like a 3-way switch and rotaries are, from everything I've been able to find so far, represented and controlled by 2 or more stream deck buttons; one button for increment and another button to decrement a value, is there another option to using Stream Deck as an input device to DCS using any of the available exporters?

I have 2 stream deck xl's, so 64 buttons. I've had success using multiple buttons to overcome the 2-graphic limit (the switch plugin item and the temporary push-button with light button), but I would like to better emulate the conditions of the cockpit. One of the first that came up; AH-64D, APU. Open cover not activated (no text), Close cover not activated, then both of those have when the button is lit ("ON").  There's no way with the current SD buttons I've found to reflect that. I have a switch that graphically shows (and activates) the flip-up cover and another push-button that uses the unlit and lit states as well as the button push event. That's 4 states. The Fire Det panel is even worse since the underlying button has 4 conditions; Unlit, Fire, RDY, Fire over RDY and the 2 states of the cover.

Is there a way to do this with the Stream Deck that anyone is familiar with or could they suggest an alternative physical interface? I've seen Touch Panel mentioned in other threads, and while I have a Win10 netbook (touch screen) that would work nicely, Touch Panel seems to be a phone (iphone/android) to DCS solution. It would be nice to find something I could run on the netbook (win 10) that could communicate with DCS and allow more flexibility in representing cockpit switch/rotaries/etc more accurately.

I'm asking for suggestions from those who've been at this and have the knowledge. I've reached an impasse.

Also, I do not have a 'pit' setup. I have Thrustmaster Warthogs, TWCS, TPR, 2 stream decks, 2 netbooks and a keyboard and mouse on desk. I don't have any space left for pre-built USB gear that I've seen on the net (and have no idea if the stuff is any good). At this point I'm hoping for a software solution using the Stream Decks and/or netbooks if possible.

 

Thanks to any and all willing to educate me on what might available.

Quantum


Edited by quantum69
Link to comment
Share on other sites

6 hours ago, Scofflaw said:

I found that line in ExportScript.lua.  I was disabling individual parts of the export script to see if I could isolate what causes the stuttering.

Try the line I have. 

Link to comment
Share on other sites

19 minutes ago, quantum69 said:

Hi all. New here and have been searching for information about all this. I know there are 3 or 4 primary GIT locations that seem to all be supporting the Stream Deck plugin by Charles Tytler. The stream deck plugin works fine and am using the default DCS interface v1.0.4 (july 7 2021). I have seen references to DCS-Bios as well as some other script exporters and am I'm trying to determine if what I'm looking for/to-do can be done with this plugin and the default asherao DCS-ExportScript from that same site. It looks like the plugin is no longer updated so that's question one, the second question is about the other script exporters and whether they would be a better selection.

Since the plugin only has a small selection of options, I wonder if anyone who has used this and the exporters for awhile would be kind enough to answer a few questions?

1) there are no tri-state buttons in the plug-in. While a rotary can inc/dec a given ID value it can only display at most 2 visual conditions, and that conditional change can only be based off one ID value. Simplest example; Any 3-state switch in any cockpit. I was wondering if there was another plugin that has more input button options for the stream deck or if there was a way to use the Charles Tytler plugin to perform 3-way button graphic changes. I have seen some example screen shots in this thread that look like a full-string is being concatenated and is populating the text field of a stream deck button. What I haven't seen or know if it is possible with the current plugin, tri-state graphic changes can be done, or is there even a plugin that can.

2) since multi-state conditions like a 3-way switch and rotaries are, from everything I've been able to find so far, represented and controlled by 2 or more stream deck buttons; one button for increment and another button to decrement a value, is there another option to using Stream Deck as an input device to DCS using any of the available exporters?

I have 2 stream deck xl's, so 64 buttons. I've had success using multiple buttons to overcome the 2-graphic limit (the switch plugin item and the temporary push-button with light button), but I would like to better emulate the conditions of the cockpit. One of the first that came up; AH-64D, APU. Open cover not activated (no text), Close cover not activated, then both of those have when the button is lit ("ON").  There's no way with the current SD buttons I've found to reflect that. I have a switch that graphically shows (and activates) the flip-up cover and another push-button that uses the unlit and lit states as well as the button push event. That's 4 states. The Fire Det panel is even worse since the underlying button has 4 conditions; Unlit, Fire, RDY, Fire over RDY and the 2 states of the cover.

Is there a way to do this with the Stream Deck that anyone is familiar with or could they suggest an alternative physical interface? I've seen Touch Panel mentioned in other threads, and while I have a Win10 netbook (touch screen) that would work nicely, Touch Panel seems to be a phone (iphone/android) to DCS solution. It would be nice to find something I could run on the netbook (win 10) that could communicate with DCS and allow more flexibility in representing cockpit switch/rotaries/etc more accurately.

I'm asking for suggestions from those who've been at this and have the knowledge. I've reached an impasse.

Also, I do not have a 'pit' setup. I have Thrustmaster Warthogs, TWCS, TPR, 2 stream decks, 2 netbooks and a keyboard and mouse on desk. I don't have any space left for pre-built USB gear that I've seen on the net (and have no idea if the stuff is any good). At this point I'm hoping for a software solution using the Stream Decks and/or netbooks if possible.

 

Thanks to any and all willing to educate me on what might available.

Quantum

 

Hi there. Good questions. If my response does not get everything you can also try asking in the main DCS interface thread. 

0) The app isn’t being update for two reasons. The first is that it works. Awesome. He second is that CTyler is working on an update which natively incorporates DCS-BIOS. 

0.5) While I try to maintain the most up-to-date exportScripts, there may be others out there with features that you prefer. It’s ok to mix and match. 

1) Tri-pic in relation to state is a limitation of the stream deck itself, unfortunately. 

2) I have a similar solution for the Apache APU. While I have not modeled/coded the fire panel, I imagine the best approach may be to use text to show you the state of the switch.

You can get creative with what you have available. Take a look at the f16 wiki to see how I was able to display the many states of the ECM panel and it’s individual lights https://github.com/asherao/DCS-ExportScripts/wiki/F-16C-Viper

 

Link to comment
Share on other sites

22 minutes ago, Bailey said:

2) I have a similar solution for the Apache APU. While I have not modeled/coded the fire panel, I imagine the best approach may be to use text to show you the state of the switch.

This is the approach I've taken with tri-state switches such as the H2O switch in the AV-8B.

3.png

Link to comment
Share on other sites

@Bailey I see you took the route of concat your own strings with the var values in the mix. Nice. Does the export->SD (stream deck) allow embedded color codes in the strings? I noticed one of the pics you had an ECM button, the one with the A S... (auto=A I think for the bird your flying) letters in each corner and each letter was a different color. Did you gimp/mspaint the button and are just changing the number text in the middle? Just curious on that one.


@CornAddictyeah, I use gimp and have made several buttons to deal with the current limitations. I had wished the SD SDK might have allowed multiple graphics per button and it was the plugin logic that was missing. Such that tri-state and more could be represented in a single button (I guess some people call them 'tiles' as well. a new lexicon...)

Under the hood is just a touch screen so the SDK would have to be lacking in that regard <<-- huge assumption on my part.

I'll have to go to the main DCS interface thread and read around. I just got here and DCS has been around a while, without having to build a 'pit', which is not an option for me, perhaps in addition to the SD's I can find a way to use the netbooks as well.

thanks for the insights

Quantum

Link to comment
Share on other sites

5 minutes ago, quantum69 said:

@Bailey I see you took the route of concat your own strings with the var values in the mix. Nice. Does the export->SD (stream deck) allow embedded color codes in the strings? I noticed one of the pics you had an ECM button, the one with the A S... (auto=A I think for the bird your flying) letters in each corner and each letter was a different color. Did you gimp/mspaint the button and are just changing the number text in the middle? Just curious on that one.


@CornAddictyeah, I use gimp and have made several buttons to deal with the current limitations. I had wished the SD SDK might have allowed multiple graphics per button and it was the plugin logic that was missing. Such that tri-state and more could be represented in a single button (I guess some people call them 'tiles' as well. a new lexicon...)

Under the hood is just a touch screen so the SDK would have to be lacking in that regard <<-- huge assumption on my part.

I'll have to go to the main DCS interface thread and read around. I just got here and DCS has been around a while, without having to build a 'pit', which is not an option for me, perhaps in addition to the SD's I can find a way to use the netbooks as well.

thanks for the insights

Quantum

I have not tried color codes in strings. I have wondered the same, but dismissed the idea when I re-realized that the SD has a master color for text for the individual tile (also, if other ppl say “tile”, awesome!). I/we might have to revisit that sometime. 

For the F16 ECM what I did was msPaint the background with a very specific color as the backdrop. Then in the exportScript I used a combination of full blocks to hide/show which modes are active via some logic. Take a look at the code, it was quite interesting and a surprising success. The wiki link also has the example SD profile at the bottom  you can use to check it out. https://github.com/asherao/DCS-ExportScripts/wiki/F-16C-Viper 

I had been able to do something similar with the UH60. It’s navigation buttons have three states. Off, Mode1, and Mode2, for example. The three states are all independent, they cannot be combined or happen at the same time. Three states is an obvious problem for the SD right? Wellllll, what I did was msPaint the two On states, Mode1 and Mode2. I made those the two images on the “switch” tile. Then for the Off state I made a wall of black full blocks to cover the images entirely. Bam, with the addition of some logic I now had “3” states!

Ahh, that also reminds me. One of the things I have done for a tri-state is to have a rotary tile. (Yes, a rotary tile for an ingame tri-switch) The background will be simply images of switch up and switch down. Down text will always be “Off”. Up text will change depending what mode the switch is currently in.

Something I just thought of while typing that… Using a rotary, depending on what mode the switch is currently in, you can display that mode and also display the next mode on the tile too. So, when you look at the tile you know what mode you are currently in and the next mode. When you press the tile the “next mode” is the new current mode and a new next mode will automatically appear. I think this would work best for switches with 4 states (ww2, f5), but for tri-states it may require a little more maths….hmmm

Link to comment
Share on other sites

5 minutes ago, Bailey said:

I have not tried color codes in strings. I have wondered the same, but dismissed the idea when I re-realized that the SD has a master color for text for the individual tile (also, if other ppl say “tile”, awesome!). I/we might have to revisit that sometime. 

For the F16 ECM what I did was msPaint the background with a very specific color as the backdrop. Then in the exportScript I used a combination of full blocks to hide/show which modes are active via some logic. Take a look at the code, it was quite interesting and a surprising success. The wiki link also has the example SD profile at the bottom  you can use to check it out. https://github.com/asherao/DCS-ExportScripts/wiki/F-16C-Viper 

I had been able to do something similar with the UH60. It’s navigation buttons have three states. Off, Mode1, and Mode2, for example. The three states are all independent, they cannot be combined or happen at the same time. Three states is an obvious problem for the SD right? Wellllll, what I did was msPaint the two On states, Mode1 and Mode2. I made those the two images on the “switch” tile. Then for the Off state I made a wall of black full blocks to cover the images entirely. Bam, with the addition of some logic I now had “3” states!

Ahh, that also reminds me. One of the things I have done for a tri-state is to have a rotary tile. (Yes, a rotary tile for an ingame tri-switch) The background will be simply images of switch up and switch down. Down text will always be “Off”. Up text will change depending what mode the switch is currently in.

Something I just thought of while typing that… Using a rotary, depending on what mode the switch is currently in, you can display that mode and also display the next mode on the tile too. So, when you look at the tile you know what mode you are currently in and the next mode. When you press the tile the “next mode” is the new current mode and a new next mode will automatically appear. I think this would work best for switches with 4 states (ww2, f5), but for tri-states it may require a little more maths….hmmm

Yeah, I took a similar approach and used the 3rd option of the rotary tile (ok, we'll use tile(s) to avoid confusion), the section that allows associating text with returned values. I used some of the standard ASCII values; 211,212, etc (the block characters) to do 4-state indicators. I don't know if the SD would recognize ASCII above 255 but at least good ol' block chars are there. I remember the days of the old ASCII drawings (I'm incredibly old).

so text for the 1st state basically covers the underlying graphic, the 2nd state is effectively an empty string (though it has to be something) and allows 1st state graphic to be shown, 3rd state is like the 2nd; no text overlaying the graphic. Set the tile option for value=text accordingly. So a covered over tile is your off. value 0.0=<text that cover graphics>,0.5=<blank text,1.0=<blank text>

I'll give that go. Good thinking there.

 

Link to comment
Share on other sites

2 hours ago, Scofflaw said:

That will disable the script:

 

Untitled.png

It seems you have a much older version, not the version in the Library. 

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...