M76T66A (TempoEx) - Mappings triggered by TempoEx cause interruptions in the execution tree

[Lolo401]

I'll try and explain this one:

Test conditions:

• M76T66A
• Blank profile with a single Vjoy set as Input.
• Default configuration.

A blank profile was created.

1. The following mappings were entered on buttons of a single hardware device:
   1.1.Btn 4: VjoyRemap inside basic container triggering Vjoy 1 Btn 1 (set as input):

1.2.Btn 7: VjoyRemap inside a TempoEx container (long action) triggering Vjoy 1 Btn 1:

2. A single Macro was setup in Vjoy 1 Btn 1 as follows:

It was expected that depressing either button 4 or 7 would result in the same indications on the input viewer. However the behavior observed on the input viewer was different:

When Vjoy 1 Btn 1 is activated via Btn 4 (Basic container + Vjoy remap):

20250927-1538-02.9326738.mp4

This is the behavior as expected.

When Vjoy Btn 1 is activated via Btn 7 (TempoEx container + Vjoy remap):"

20250927-1539-10.3408799.mp4

The Macro entered in Vjoy 1 Btn 1 is not being executed.

Log Entries:

1. Btn 4 (Basic Container):
   2025-09-27 11:41:16.658 INFO EXEC: Callback for container [3dbc7359dae645c3a57846177491d0e7] executing node: [3dbc7359dae645c3a57846177491d0e7]
   2025-09-27 11:41:16.659 INFO >!!! Executed action VJoyRemapFunctor VjoyRemap: VJOY device: 1 unhandled: [VJoyButton]: 1 action result: PASS
   2025-09-27 11:41:16.660 INFO >Overall Result: PASS
   2025-09-27 11:41:16.660 INFO >Overall Result: PASS
   2025-09-27 11:41:16.660 INFO >Overall Result: PASS
   2025-09-27 11:41:16.660 INFO >Overall Result: PASS
   2025-09-27 11:41:16.660 INFO >Overall Result: PASS
   2025-09-27 11:41:16.674 INFO EXEC: Callback for container [0daeeceb5a654725af5823fd16340d87] executing node: [0daeeceb5a654725af5823fd16340d87]
   2025-09-27 11:41:16.674 INFO >!!! Executed action MacroFunctor Macro sequence: steps: [3] exclusive: [False] EOR: [False] AutoRestart: [False] AutoStop: [False] action result: PASS
   2025-09-27 11:41:16.674 INFO >Overall Result: PASS
   2025-09-27 11:41:16.674 INFO >Overall Result: PASS
   2025-09-27 11:41:16.674 INFO >Overall Result: PASS
   2025-09-27 11:41:16.674 INFO >Overall Result: PASS
   2025-09-27 11:41:16.675 INFO >Overall Result: PASS
   2025-09-27 11:41:16.782 INFO EXEC: Callback for container [3dbc7359dae645c3a57846177491d0e7] executing node: [3dbc7359dae645c3a57846177491d0e7]
   2025-09-27 11:41:16.782 INFO >!!! Executed action VJoyRemapFunctor VjoyRemap: VJOY device: 1 unhandled: [VJoyButton]: 1 action result: PASS
   2025-09-27 11:41:16.783 INFO >Overall Result: PASS
   2025-09-27 11:41:16.783 INFO >Overall Result: PASS
   2025-09-27 11:41:16.783 INFO >Overall Result: PASS
   2025-09-27 11:41:16.783 INFO >Overall Result: PASS
   2025-09-27 11:41:16.783 INFO >Overall Result: PASS
   2025-09-27 11:41:16.798 INFO EXEC: Callback for container [0daeeceb5a654725af5823fd16340d87] executing node: [0daeeceb5a654725af5823fd16340d87]
   2025-09-27 11:41:16.799 INFO >!!! Executed action MacroFunctor Macro sequence: steps: [3] exclusive: [False] EOR: [False] AutoRestart: [False] AutoStop: [False] action result: PASS
   2025-09-27 11:41:16.799 INFO >Overall Result: PASS
   2025-09-27 11:41:16.799 INFO >Overall Result: PASS
   2025-09-27 11:41:16.799 INFO >Overall Result: PASS
   2025-09-27 11:41:16.799 INFO >Overall Result: PASS
   2025-09-27 11:41:16.799 INFO >Overall Result: PASS

2. Btn 7 (Tempo Ex):
   2025-09-27 11:41:57.114 INFO EXEC: Callback for container [9854a267e9c645c09f8b9a04b640235a] executing node: [9854a267e9c645c09f8b9a04b640235a]
   2025-09-27 11:41:57.115 INFO >Overall Result: FAIL
   2025-09-27 11:41:57.222 INFO EXEC: Callback for container [9854a267e9c645c09f8b9a04b640235a] executing node: [9854a267e9c645c09f8b9a04b640235a]
   2025-09-27 11:41:57.473 INFO >Overall Result: FAIL

test.xml

system.log

[Lolo401]

After replacing the macro In Vjoy 1 Btn 1 by a Vjoy Remap pulse button the profile refused to start and prompted the user to check the log.

The log reported a bluilding execution tree error:

system.log

[muchimi]

Aren't log files great?

[muchimi]

The execution tree build failed because the container returned it was invalid.
I am going to add an option to allow containers to fail at build time because some advanced containers may indeed fail until the container itself is loaded and the functor initialized.
I'm not sure what's going on here as to why it would fail, but at least it would not prevent the tree from building.

[Lolo401]

T67:
Same behavior as above.
Unable to retrieve logs due to the cog wheel being non-functional.

[muchimi]

It looks like you are using vjoy 1 as both input and output in the same profile. That isn't normally supported because vjoy cannot be used at the same time as input and ouput.
This said, I'm looking if it can work.
First pass I'd say it won't work because the output button 1 trigger on vjoy won't trigger the input so will never execute because the dinput event may not trigger so not be seen.
I'm verifying this as it would be great if it worked.

[muchimi]

Second pass is that it does work in some circumstances. Looks to be a timing thing as depending on how the button is set, it may or may not trigger a direct input event - most likely having to do with VJOY interface "lock" time.
Looking into this because the difference in behavior is intriguing.

[muchimi]

So were I am landing with this is that it can work in some situations, but not in others as the whole thing depends on the VJOY interface and behavior. Here's the diagnostic info:

First, GremlinEx is not meant to send output to a vjoy device it uses as input (and this is in fact why there's a warning message to this effect).

I have verified the behavior by tracing through the code and events generated.

In this case, when button output is set (vjoy 1 button 1) from tempoEx, the VJOY device is held, probably a few milliseconds, in "I own this device" state. The VJOY interface does not issue a dinput trigger (event).

This is completely time dependent looks like, as sometimes when a button is set in VJOY, it does trigger a DINPUT message which is why GremlinEx detects it and does something with it.

What may be an option here is to figure out how to coerce VJOY to fire a DINPUT message, but without changing the code, unsure.

For the moment I'm going to label this one as designed, as the issue is likely a race condition setup in the VJOY interface dll - something GremlinEx has no control over.