This post contains a list of known bugs and unsupported features in Fologram for Rhino.
Changing the name of a synchronized parameter in grasshopper does not update automatically in the Fologram session
If a synchronized parameters name is changed in grasshopper, the previous name will remain in the Parameters slate on any connected device. To update the name on any device, either change the parameters value, or un-synchronize the parameter and re-synchronize in grasshopper
Synchronized objects are not compatible with grasshopper’s Area and Volume components
If a synchronized object has area or volume properties, connecting to an Area or Volume component will result in an error reading ‘Area properties could not be solved.’. To solve the area properties of a ‘Sync Object’, first connect it to an empty grasshopper geometry container of the geometry’s data type (ie. if your geometry is a mesh, connect your Sync Object to a ‘Mesh’ geometry container, then an Area component).
Scaling Text objects and Dots in Rhino can lead to unexpected behavior in a Fologram session
Text objects and Dots are supported in Fologram, however scaling them in Rhino can lead to different discrepancies between Rhino and your device, such as over-scaled or skewed text
Graft/Flatten/Simplify/Reverse icons are not visible on the Sync Object component
Grafting, Flattening, Simplifying and Reversing data in the inputs and outputs of a Sync Object component is supported in Fologram, however they are not currently visible on the component. If visual reference is required, connect the component to an empty grasshopper geometry container of the geometry’s data type.
Not all layers appear in the model a Fologram model on startup
Fologram does not synchronize layers that are hidden on startup. If you wish to synchronize any geometry on hidden layers from Rhino, turn the layers on. If you turn these layers off again, they will remain synchronized in your session.
Only geometry used in a Fologram session will be saved when saving a model
If you have geometry in your Rhino document on layers turned off, this geometry is by default not synchronized to your session. This means if you create a saved model from your session, only the geometry sent to Fologram will be saved, not any geometry on hidden layers.
Only one object at a time can be manipulated in the HoloLens 1
Whilst multi-object manipulation with both hands is possible in both HoloLens 2 and mobile devices, only one object can be manipulated at a time in the HoloLens 1
Connected devices in Rhino can double-up
It is possible for two identical names for one connected device and appear in your Fologram panel for Rhino. To fix this, restart your Rhino session and device session. This should not adversely affect your session.
Basic material types are not interpreted correctly, and changing layers to these material types is not always detected
Basic material types found in Rhino (ie Glass, Metal, Paint) are not displayed correctly in the Fologram session. Changing a layer material to these types is also not detected. It is recommended to create your own material, or import materials from the material library.
Default Rhino Texture mapping does not immediately assign on NURBS object
When applying a texture to an object in Rhino, a default mapping is applied. This mapping however is not applied in Fologram simultaneously, which can cause a mismatch between the mapping in a Rhino session and a device running Fologram. Applying a new mapping to the geometry will synchronize both sessions.
Texture mapping does not scale when changing model units in Rhino
When changing the modelling units in Rhino (ie from inches to meters) texture mapping applied to objects are not scaled in the Fologram session, which causes textures to display correctly in Rhino but not Fologram.
Assigned materials lose synchronization in Fologram when the grasshopper document is changed
When a material is assigned to a Sync Object with the Assign Material’ component, the material loses synchronization if the document is changed, and then changed back.
Aruco Marker tracking can cause application crashes on iOS
If Aruco marker tracking is turned on and markers are being successfully tracked, iOS devices connected to a session can experience infrequent application closures.
Fologram does not currently support point objects. To visualize point locations, it is recommended to create a plane, box or sphere at the point location instead.
Fologram does not currently support shadows from the Sun in the Rhino document, and instead uses a default sun location.
Fologram does not currently support Rhino blocks. To display any geometry contained in a block, explode the block in your Rhino document
Fologram can stream geometry from groups, however manipulations of any objects in a group will be on the individual object
Fologram does not currently support clipping planes
Fologram does not currently support occlusion materials
Fologram does not currently follow layer orders from Rhino
Sync Object and synchronized parameters in Grasshopper Clusters
Synchronized components and parameters are not supported when contained inside a grasshopper cluster.
Fologram does not currently support colours for Text objects or Text Dots
6 degrees of freedom hand manipulation on HL2
Fologram does not currently support interactions using the 6DOF object manipulation available on the HoloLens 2