NOTE: Evaluating REDBACK BIM
NOTE: 0020 — Tuesday 24 October 2017
REDBACK BIM will eventually seek to enter into the world of Flux web applications. Below is a screenshot of its logo design and label when situated in Flux.io.
There are of course still matters of where it stands as a finalised product (mainly because it is an open-source product), the constraints and limitations are listed below:
Constraints + Limitations:
- Better performance with low poly count — approx 4500 faces. Is not lightweight for some reason. Smaller the better (0.1 scale factor), less polys the better (under 4500 potentially in total per key)
- Has yet to define an object’s name — must be entered in manually within the JSON string. Cannot select to preview attached section of JSON string
- Users must understand how JSON structure works + Flux JSON schema to add values. I.e. custom attributes and colours/transparency. If entered incorrectly, the object would not be understood as geometry and will be defined it as invalid
- Grouping objects into scenes is yet to be found
- Lag in interface for loading / interacting with objects in the Flux Viewport — unaware of the issue that is happening here
- Tends to crash inconsistently — it could be an internet thing (bad/low quality connection)
- In order to add more geometry to a key, it must be in an array of objects or defined within a scene. Not sure how we can restructure the JSON yet.
- Is ideal to have grouped geometries (1 mesh per object) but that means that customisation on colours and details is difficult to achieve
- Delayed orbiting and editing requires time for it to fully function at ideal speed. Unsure why this is occurring. Could it be because it’s not published to the web? As in it’s using localhost or is it the internet connection?
- Would be fantastic to include an input text area for users to add in additional JSON strings for more objects in space. But then how could you add it into an array? Or scene object?
- Limitations in terms of JSON schema only reading things like the origin — if you think about how to position a door, it would require the bottom face of a rectangular prism, otherwise the door’s centre would need to be calculated to find the ideal position.
- Classification of objects for BIM
- You can build your own JSON schema for Flux, however with lack of knowledge on how to implement that, it meant that you’re again restricted to follow their guidelines.
At the moment, when you select an object or geometry, it console.logs the JSON string of the selected. We could create a new key that can collect the JSON for whatever objects that are selected?
© Emily Y Leung and Project Redback, 2017. Unauthorized use and/or duplication of this material without express and written permission from this site’s author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Emily Y Leung and Project Redback with appropriate and specific direction to the original content.
Last modified on Tuesday 24 October 2017
