Setting visible condition based on difference of two value

[ksp1000]

Hi. Apologies if this is not the correct place to post.
Using the Composite Action function, I have a need to set the visibility of some text based on the difference between two Lvars. It appears that I can only compare an Lvar to a specific value. Is the only way to achieve this using a Lua script?
Thanks, Kevin

[Fragtality]

It surely isn't wrong ;)

You mean something like "if varA - varB < 4"? Yes, that is what Lua Scripts are for.

The Condition System of the Composite Action was never meant to replace that Use-Case (running more complex logic/conditions in lua) completely. The Idea is not needing to write simple (and most frequent) Conditions in lua for "variable at a certain value"

[ksp1000]

Hi. Thanks for the rapid response. I'm familiar, if rusty, with Lua scripts from some stuff I did a few years ago using FSUIPC and Mobiflight, so that's fine. I also wanted to say the plugin is so flexible and easy to use it!

My plan is to create an X: var which compares the two L: vars and then use the condition function to choose whether to display text on a display or not. Before that I created a simple Global Script that runs every x ms and increments a counter and then using a 'Display Value' function , I can show the incrementing counter on a button. The function works fine but the problem I am having is the time interval doesn't seem to make any difference. If I put 500 or 5000 in, it still updates about every half second. I don't really need it that fast; hence the desire for a slower evaluation time. Am I doing something wrong with the RunInterval function?

SimVar("X:KSP_VAR_01")
RunInterval(5000, "IncrementCount")
RunSim("MSFS")

SimWrite("X:KSP_VAR_01",0)

function IncrementCount()
local kspvar = SimRead("X:KSP_VAR_01")

kspvar = kspvar + 1
if kspvar == 100 then
	kspvar = 0
end
SimWrite ("X:KSP_VAR_01", kspvar)

end

[Fragtality]

Thanks!

I start with: the Plan certainly is not wrong on a general Level. It is a totally valid and intended Pattern, depending on the Use-Case.
E.g. if you would need to track/calculate something the whole Time in a Sim Session - regardless of which Actions are visible on the StreamDeck(s).

But your actual Use-Case maybe could also be solved through a Standard Script. They are loaded on Demand when a visible Action uses a Function from that Script. These Lua Functions can be used as Variable or Command in the Plugin - so for example also as a Variable for a Condition in the Composite Action.
So you might not need a Detour via an internal Variable and global Script in this Case - just a Function like

-- file: test.lua
SimVar("varA")
SimVar("varB")

function myCondition()
  if SimRead("varA") - SimRead("varB") < 4 then
    return 1
  else
    return 0
  end
end

and then use lua:test:myCondition as Variable.

On the Issue with the Interval don't making a Difference: that appears to be bug, I have to look into that. When the whole Plugin is restarted after the Change it does make a Difference. Seems the Interval isn't refreshed when the Script is reloaded through a file-changed (i.e. was edited).

[ksp1000]

Thanks again!

That is a lot neater and removes any need to limit the function to a specific aircraft type as execution will now be limited to the panel being used.

I guess the only risk is it is now executing that lua function every time it refreshes the streamdeck display (not sure how often that is) but as I am not processor cycle limited it is probably not a problem.

On the interval, you are correct. It works when you restart the plugin/sim, just not when you update a script.

[Fragtality]

I guess the only risk is it is now executing that lua function every time it refreshes the streamdeck display (not sure how often that is) but as I am not processor cycle limited it is probably not a problem.

All Lua Functions used by an Action will be calculated on the SimProcess Intervall - which defaults to 50ms and is also used for other Connectors respectively SimResources that have to be polled (refreshed on a Cylce). The Actions then are only reevaluated and refreshed (redrawn) if the Value has changed.

[Fragtality]

Please try the Dev Version just committed: The Issue with the global Scripts (changing RunInterval Timer) should be fixed now 🤞
https://github.com/Fragtality/PilotsDeck/raw/refs/heads/master/PilotsDeck-Installer-latest.exe

[ksp1000]

Sorry for the delay. Other priorities kept me away from the sim! I just tested your new version and it now restarts the script when you save the lua file.