Hello Bentley crew,
We have a weird situation where a lot of projects are undertaken using Rhino in the early stages; which then have to be converted to Revit or Aecosim (depending on the client's requirements). NetworkRail and London Underground here in the UK and I believe the MTA (NY, USA) require Bentley deliverables.
There is already a Mstn for ACAD users series on Bentley Learn. It would be good to add a similar series for Rhino users.
This should highlight the benefits of Mstn as a platform for large projects:-
Hello,
i would recommend posting your ideas on our Ideas page:
https://communities.bentley.com/products/microstation/i/
Regards
Derval Canny.
Attached is a quick table comparing Rhino and Mstn tools. The yellow cells are where Mstn is missing an equivalent tool. The table is based on Rhino's available tools. There are of course a lot of tools that Mstn has that Rhino doesn't.
When you are exploring/roughing out a design, it pays to have the freedom that comes with something non-parametric and less BIM/plan-based.. ie more CAD-like. Rhino has a reputation as being a robust 'swiss army' knife modeling tool that is well suited to 'sketching' concepts... that can be reinforced by Grasshopper and a large ecosystem of addons, if desired. Nevertheless, Its main strength is its NURBS-based modeling tools and handling.
OTOH, Mstn is also a long standing NURBS modeler that has much better solids and mesh modeling tools, due to all those civils roadway splines and terrain modeling verticals.
I started the table above as means to spare Rhino users getting frustrated when using Mstn/Aecosim. These users will spend a lot of time looking for tools they are accustomed to.... and occasionally disappointed in not finding any equivalent.
I found that there are:
As mentioned above, there seems to be a trend of using a separate tool for scheme design with either Rev*t or Aecosim for the later stages... for various reasons. It would be helpful to be able to transition Rhino users onto Aecosim as early and easily as possible to avoid the costs of paying for two licenses and the translation overheads.
Dominic. Good discussion topic and thanks for posting the table. Very interesting. I certainly do get your point and the below has certainly has not gone unnoticed.
"there seems to be a trend of using a separate tool for scheme design"
Hi Dominic,
Thank you, that is a useful list, we'll circulate it to our colleagues.
Marc
Thanks Dominic a really interesting read.
Brenden Roche
Applications Engineer
Bentley Systems, Manchester UK