You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@bhowes-tt, I got the Edmonton project and managed to export the structure. However, the skin and the bowl are linked files in Revit. I have discussed two options with @nmundell-tt:
-A) Merge (copy+paste) the three models into one in Revit. This is tedious and will probably create a really heavy json file
-B) Allow the viewer to take more than one json file. This seems to be a really good way to collaborate with others, since json files will most likely come from different models (architecture, structure, etc).
I feel that option B is a better approach that we could really benefit from in future projects. What's your take on this? Thanks!
The text was updated successfully, but these errors were encountered:
This has been brought up again by Hiram under a different problem. He is trying to view a Revit file of a section of a stadium that becomes a 60 MB json file that crashes Chrome.
Approaching this issue by telling the user, on the Revit side, that the file size is too big and asking them if they'd like to create separate json files per Revit category seems a good solution. Then, add the possibility to select several json files on the web interface and/or add new ones as needed, like they do in the three.js editor:
I'd like to take a stab at this in the next couple of weeks, since I did this for the custom website I'm currently working on. @bhowes-tt what do you think?
@bhowes-tt, I got the Edmonton project and managed to export the structure. However, the skin and the bowl are linked files in Revit. I have discussed two options with @nmundell-tt:
-A) Merge (copy+paste) the three models into one in Revit. This is tedious and will probably create a really heavy json file
-B) Allow the viewer to take more than one json file. This seems to be a really good way to collaborate with others, since json files will most likely come from different models (architecture, structure, etc).
I feel that option B is a better approach that we could really benefit from in future projects. What's your take on this? Thanks!
The text was updated successfully, but these errors were encountered: