Fologram works by connecting devices directly to each other, using the same technology behind most video calls. Internet is required to initialize the call, after which data is transferred directly from one device to another.
⚠️
Fologram works best when all devices share the same WiFi connection.
Connecting to a session
Fologram enables sharing models between multiple users and devices in what are called “sessions”. A session is a peer-to-peer connection that handles synchronization of geometry and event data between Rhino, Grasshopper, mobile devices and the HoloLens.
To start a new session, run the Fologramcommand in Rhino to display the plugin window, then click Connect or run the XRStart command.
Once the session has been started, Fologram will display a popup window with a QR code containing an app link to connect your device to the session. Scan the QR code on your device and acknowledge any prompts to start Fologram and join the session.
📢
To connect a second device, click Connect again and scan the app link QR code.
Resuming a session
Fologram will automatically reconnect to a previous session after the app has been minimized. You can also re-join a session by re-scanning the app link QR code.
Stopping a session
To stop an existing session, run the XRStop command in Rhino.
My device appears as ‘New’ in the connected device list but I can’t see my model: Try running the XRStop command to stop any sessions that are currently running, then connecting again.
My device appears as Connected in the connected device list but I can’t see my model: If your device appears in the connected devices list in the Fologram plugin window but you don’t see your model in AR, try modelling a 50x50x50cm cube at the Rhino origin and confirming that this displays. If it does, check that your model is at a visible scale and located at the Rhino origin. If you can’t see the cube then you might be experiencing issues with your network. To solve common network issues, try connecting your laptop and device to a mobile phone hotspot, restarting Rhino and trying again.