Would you now like to see our hard work in action? What we did here was very simple in effect, but not easy to see by ourselves. There are a few methods I have been able to test something like this with:

• Two instances of Unity on the same computer: This is likely one of the quickest ways. Take your development directory and move it somewhere else on the computer. With your main project opened, run a second instance of Unity and open the project from this second directory. As you run through the various clicks in the program and move the machine around, you will see it move in the second instance.
• Two computers running Unity: Very much like the previous point, except you do not have to press the Alt + Tab keys to see it in action.
• HoloLens and computer: This is another option; it probably takes about the same amount of time in terms of iteration as the second option. When you move the machine through the HoloLens, you can see it moving around on the computer. Funnily enough, if you move it on the computer, it does not do anything on the HoloLens. This appears to be a problem with the world anchors in the editor.
• HoloLens and HoloLens: Well, it is not easy to test it like this, by myself, though I have tried. The constant swapping of HoloLens is mighty bothersome. Also, one issue, apparently, the system being not in place does not automatically sync up the spatial mapping of the other, or some other issues are happening. When you get both HoloLens up and past the spatial map, the two Skeeball machines are in different places. When either is moved, you can see them both move but they just happen to start in different places.