With the release of Rhino 8, many concerns have been raised in the forum. Many of these concerns seem to be right, as this version has been one of the most incomplete and buggy versions so far for me. Especially for a field with a large user base such as architecture, the lack of native IFC file support is a big deficiency. Moreover, since there is no roadmap, we can’t see if there is any progress.
For comparison, FreeCAD, whose main purpose is mechanical engineering and product design and which is completely free, can offer native BIM-IFC support. This creates a questionable picture in terms of Rhino’s competitiveness in the industry and its potential to appeal to different disciplines.
I hope that feedback and expectations expressed by users such as the following will not be ignored. The current direction leads me to worry that these features will not be added in Rhino 9.
I believe that McNeel should take more tangible steps to respond to these expectations and accelerate these processes by expanding his team if necessary. Rhino always has the potential to be one of the leading tools in the industry with its powerful and versatile structure; however, in order to sustain this potential, more attention should be paid to user needs.
My native language is not English so I asked him to make some edits.
I am not someone who uses Freecad. If it is considered as an ad, you can delete the post.
I only want requests like the one in the post I linked to to be taken into consideration.
All posts that get read are taken into consideration.
For the foreseeable future, if you heavily rely on IFC support, you’ll need to either find a plug-in that offers that or use a different application.
-wim
Hi @wim and @nathanletwory
The post in the link nicely brings together the crucial points. But it’s a pity that I can’t see any work on them in the current r9 WIP version (I haven’t used r9 WIP but I have been following the updates in the forum closely)
Since there is no roadmap, it is not clear whether these issues are being considered by you or not.
If we need to give an example from our workflow, we are dealing with ifc import-export and a lot of blocks in the facade sector. We use CadExchanger for file format changes and BlockEditNew plugin for block editing. But I think that such features should have been native to Rhino long ago and it’s really getting late to implement them.
Of course, not seeing anyone from McNeel under a post doesn’t mean that you are not interested or ignoring the topic. However, we are not sure if our voices are reaching you effectively enough.