Hi @Tobias_Hathorn (assuming you are going to be the one to respond),
I am continuing to test the Data Exchange despite the "Generating Graphics" cycle times discussed in the separate post here:
I am running into a few other issues as well.
1.) When using the Data Exchange to transfer from Revit to Rhino, there are some families which have missing elements. I think this is related to a similar issue that I believe was addressed here: https://discourse.mcneel.com/t/invisible-block-issue/153329/22
I believe this was fixed in the latest Service Release Candidate for Rhino (7.30.23125.15001). Previously when exporting the Revit model to 3D DWG this same issue would occur (basically any nested families are not correctly translated to nested blocks in rhino, resulting in missing block/family elements.) When you opened this file in AutoCAD all the block geometry would appear, but you would need to explode the blocks in AutoCAD at least a few layers and resave so that there were no nested blocks. This was a major pain, but I believe was resolved in the Service Release Candidate. This Data Exchanger hopes to eliminate/replace this Revit -> export to 3D DWG -> import into Rhino workflow. However it appears this same nested block issue is occurring still with the Data Exchange "file". I am not sure if this is something that you are aware of, or something that will be fixed in the next release of the Data Exchanger, but it would need to be resolved before we can adopt this as the new workflow. Common Revit Elements that have issues are Revit railings and Revit equipment families which have imported CAD geometry (usually an imported block).
2.) Specifically I am testing this with some Projector Revit Families Isolated. In order to try to find a work around to this in order to continue testing the Data Exchanger, I am trying to go into the Revit family itself and explode the imported geometry as many times as possible without losing the geometry. (this was imported into the Revit family from Rhino as a block) separate from the pivoting mounting base which is in the same family. When I have exploded and resaved the family and synchronized the revit file, and updated the Data Exchange so that it says "V2" in Revit, I see the corresponding "V2" in the Rhino data exchange window, however the date is not updated, and I am unable to view the exchange via the web viewer either (it says its processing). This is not a very large Data exchange, about 11 instances of 2 families, so I can't imagine its taking this long to process on the cloud but I guess we will see later today. I am not sure if anyone else is running into this? This still applies if I remove the data exchange and reload it, or if I close rhino entirely and reload the data exchange, the date is still the original even though it says "V2".
This is the view in Revit and the Data Exchange Window showing the correct updated date for the "V2".
This is what I see when I try to view the "V2" on the web viewer:
This is what it looks like when I view the V1 version on the Web Version (i.e.. what should be showing up even if the data exchange wasn't updated):
This is what it looks like when I load the latest data exchange update in Rhino.
This is when you export from Revit -> 3D DWG -> Import into Rhino. No need to open AutoCAD. This is with the new Service Release Candidate installed.
I realize these might all be separate issues, requiring different solutions from different parties, but these are what I am running into this morning. If any one has any ideas I would greatly appreciate it. If it does manage to get the updated date and data for the V2 into Rhino I will update this post.
Best regards,
Drew
