We have a virtual camera moving on a dolly path defined at runtime looking at a target. In editor it works exactly as expected. However, when we build out to windows standalone the dolly movement fails. It still looks at the target, but it sits at 0,0,0. We're running 2.1.10 in 2018.2.7f1, and saw the same behavior in 2018.2.6f1. We haven't been able to find any editor specific code that could cause this and using the visual studio debugger is showing the bad position coming from the virtual camera's state, but also that the dolly is created and hooked up. Our other cameras using transposer offset in world position execute identically in editor and build. We're at a bit of a loss at what to look at next.