Live Link works in editor but not in nDisplay (using Vive Mars)

Development Cinematics & Media Virtual Production
, ,
1

Edit: Solved – see first comment below.

Hi,

I have live link data for my Vive Mars camera tracker coming in through to the ICVFX/Cinecamera and can see the camera repond in the editor view. But when I fire up switchboard and launch nDisplay, the live link data doesn’t seem to reach the camera which remains still. I have set the live link default preset, have set a static endpoint in project settings for UDP, have enabled Live Link over nDisplay plugin, have turned on rebroadcast in the livelink settings, all of which have been pointed out as potential issues, but nothing seems to affect things.

Any further thoughts or ideas on what I can troubleshoot? Is there a way to see if a camera is receiving live link data at all? Or a way to somehow track if/how far live link data is progressing through Unreal/Switchboard/nDisplay?

Thanks,
Nikhil

2

I again ran into switchboard not picking up the livelink data. This was a hard one to solve – but since the live link data was working on the camera in the editor, just not in switchboard, I knew it was a connectivity issue and stumbled on a post that pointed to the IP address as a likely culprit. In short, do NOT use the loopback IP (127.0.0.1) and instead using the actual IP of the machine. Sharing the link that had the solve and a


video showing the places where I changed the IP address.

Solution link: see last post Camera tracker works only in UE editor but not when run ndisplay switchboard - #3 by Ulreal_SDH

2 Likes
3

this is my summary with pictures

4

nice solve – figured it had to be a live link connectivity issue on your node.

Question for you, as im both half curious, and half trying to be helpful – when your camera ‘wasn’t moving’ did you notice how the frustum still ‘moved’ and warped slightly when panning up/down? almost like it was pushing in ever so slightly…

Got me wondering what might cause that inconsistency… so my question is – have you applied an offset to your nodal point from your tracker location to you camera’s sensor?

5

Thanks. Yeah, it must be a bug as someone mentioned in that thread. There’s no reason why 127.0.0.1 shouldn’t work. Hopefully, it’ll be fixed, but I’m thinking it’s best practice and a good habit to start using actual IPs in all scenarios.

6

Good point about the offset for the nodal point – I had not gotten to that point yet, as I was just trying to get the connectivity working. But yes, I had not done that and need to do that. Thanks for the note!

1 Like