I’m troubleshooting trying to get multiple sequences to play via blueprints/remote control while using an nDisplay setup. I know blueprints can be tricky with nDisplay because many blueprint functions only work in play mode. However, nDisplay does function similarly to play mode.
for example, if I place a skeletal mesh that has an animation into my level, the animation will play on the nDisplay node. If I place a level sequence actor into the level with autoplay enabled, it will play on the nDisplay. These are both things that expressly do not work in the editor viewport unless I’m in play mode.
However, blueprint functions like loading levels in/out, instantiating sequencer objects, etc do not work in nDisplay, but do work in play mode.
I’m wondering if anybody knows what the key distinctions are, what works what doesn’t, etc.