Hi Eric,

Do you get any errors when cooking in Unreal or when launching the cooked project in Aximmetry?
If yes, this might be related: https://my.aximmetry.com/post/1510-dmxeditor-error-when-cooking

If not, do you use the DMX tracks https://docs.unrealengine.com/4.26/en-US/WorkingWithMedia/DMX/Tracks/ and this doesn't work in cooked mode? And do you use Unreal's DMX plugin or a 3rd party DMX plugin?

Aximmetry can also receive DMX signals: https://aximmetry.com/learn/tutorials/control-methods/using-dmx-artnet-to-control-a-scene/
And send DMX signals: https://aximmetry.com/learn/tutorials/control-methods/control-lighting-equipment-via-dmx-artnet/ 

Warmest regards,

Hi Eifert, thanks for your help.

- I'm using Unreal's native DMX plugin.

- It works fine in the editor and it cooks with no error

- It works in Composer with a live signal (from another lighting software), so I know the program and level are listening and reacting to DMX.

- Artnetominator shows a DMX activity (on 127.0.0.1 : 6454) as soon as the map is loaded in Composer, so I know the DMX track is being played out (I think).

- But it's like Unreal is not listening to itself when cooked, if that make sense.

Thanks

Eric

Ok, so I made a discovery... 

For some reason I don't understand yet, I does work when the values are animated... But not when they are fixed in the DMX level sequence.

All this time, I was trying with a simple "full on" keyframe in the DMX track in Unreal, and it wouldn't work in Composer. When I actually added more keyframes to change the light up and down, it magically worked.

That's maybe why it worked also with a "live" signal, as I was obviously changing it.

I this a bug or a feature/normal/known behaviour from Aximmetry ?

Hi Eric,

It likely has nothing to do with Aximmetry. But some settings, features, or bugs of the DMX level sequence causes it.

Can you send a screenshot of your DMX track that didn't work in cooked mode? We might be able to figure out the issue from that.

Warmest regards,

I suspect there's an "optimization" trick somewhere that checks if DMX is being changed before updating the fixture, making it not react if it's always the same value in cooked mode (even if "full on"). 

The test setup is as barebone as you can imagine (one fixture, one key or two) and it's been reproducible every time so far on my end, now that I pinpointed the issue.

When the DMX track is "static", nothing is happening in Composer+cooked scene (although Artnetominator shows the Values at full power)

When you add only one keyframe to make it animate over time, it's picking it up again :

I hope that helps other people not lose their sanity if they just want to use the DMX fixtures for the nice static beams without having a whole lightshow programmed.

Best,

Eric