Hi, looking at your videos, you are judging the InCamera VFX delay by looking at the nDisplay editor preview. That is not an accurate way to judge the results of your render nodes’ nDisplay output.
The nDisplay editor preview is to visualize what might be on the wall.
I was able to reproduce exactly what you described. When I do the same camera movement and look at the nDisplay output, the results are good. There is no delay.
You mention in this post that “the same is happening on the LED wall as well.”
Are you using Livelink over nDisplay for your tracked camera?
When an actor in the editor is moved, the rest of the Multi-user clients are not updated immediately.
The best way to move cameras and get real-time on all the multi-user clients is by using LiveLink over nDisplay:
So, if you are using LiveLink to send the camera transformation, there should not be a significant delay. But keep in mind that there are always some frames of latency from the camera moving to the camera’s motion on the wall, as you have a lot of technology in the middle that adds latency. For example, UE will have a few frames of latency, your motion control system will have a slight latency, and your LED processor will have a little latency. So, all of them will add roughly seven frames of latency.
And as Shaun mentioned, you can overscan to compensate for the latency on the camera move.
I hope this all helps.