Revit Migration

BillyCoopDraws
BillyCoopDraws
in 3D Modeling

Hi All,

Like the title says.

As I am journey level architectural designer (+20 years in revit), and I want out of that ecosystem, and….

As I design my structures with as much "first pass" workflow as possible (e.g., set up stories (levels) constraining my wall heights/slabs/plate -lines, all of that to predefined stories), I'd like to know if BC can utilize a similar "draw it once-draw it correct" work flow.

I understand BC is pushing fast, creative, super duper, but I don't want to draw solids, then assign walls, after the fact. I am good enough to design on the fly, and edit once everything is in place.

Is this possible in Bricscad, or does everything flow from solids, then get assigned params?

Thanks in advance, and especially, if any of you are recovering R users, I'd love to hear your takes.

All my best,

B.

Comments

  • zoomer
    zoomer

    (e.g., set up stories (levels) constraining my wall heights/slabs/plate -lines, all of that to predefined stories)

    I have and use Story/Level binding in another App, but Bricscad has no Story binding.

    In Bricscad you do primarily Solid Modeling. When you move a Slab the Walls should stay connected to the Slab. Or you could select all Solids Faces above and move them. The worst case would be if all Story heights need to be extended by 5 cm. Then you would need to do that n*number of Stories ….

    Also there are no Story bound Stairs (OK, very rudimentary anyway) and what will happen to Doors/Windows/HVAC, …..

    But honestly, how often would you need to do such Story height changes ?

  • BillyCoopDraws
    BillyCoopDraws

    Thanks Zoomer.

    Well, on large projects, I see your point, but since a substantial share of my market is custom rez, I can think of 3 homes I designed just this past year where my clients, once I had a home to DD complete, fully modelled in R, change there minds on plate heights (e.g., 10' ceilings on FF1, to 9', etc.) Also, there are all kinds of scenarios (contractor tells me they want 24" floor trusses, then decides they want TGI), etc., etc., where level bindings play a huge roll in that workflow).

    Without parametricity on relationships, this could be and is quite tedious. In that ecosystem I am trying to break away from, it's simply a click on a level indicator, highlight the number, edit, and the entire model responds and updates. I am not saying that makes it better, or worse, I am just pointing out the feature, and was hoping, since this is a bim package, it maintained parametric relationships (revit was founded on the word "revise it", which was nice, before the 800 lbs gorilla sunk it's teeth into it). I think, if I am interpreting correctly, you indicated if I move a slab (or a floor plate?), everything moves with it?

    So I have second question: what is the "story bar" even for, if walls, floors, slabs aren't really tied to them, parametrically (I ask because I honestly don't understand their full function, as I've just barely scratched the surface of this package). I also wonder if there is a way to hack to emulate the level feature in R?

    Sorry I push, but I think you can understand how changing my firms entire workflow could be very disruptive, so I need to take it upon myself to flesh out glaring discrepancies between workflow methods for the sake of my employees, and my workflow, so a transition is eased.

    Thank you for you response,

    B.

  • zoomer
    zoomer

    what is the "story bar" even for

    I guess it is mainly a nice 2.5D drawing mode. As in the past it was a bit hard to keep your Z height while drawing without reliable Axis Locks. Which got much better with Manipulator and Polar Mode also. And of course it is more legible for crowded designs and a fast way to switch between Stories.

    My problem with Story Bar is, although it shows elements from Story below and you can even extend the visual depth top/bottom - but you can't select/edit anything below your Story height. I always set Story height to Finish Floor height, while Floor Slab and Structural Slab below belong to my Story (so I can look into my Stories from above in 3D). That means that can draw and edit my Walls/Doors/Windows but I can't access my Slabs in this mode.

    My other BIM is totally opposite to Bricscad. Highly parametric and totally fast, as long as your Project and Workflow fits the tools. When you exceed that, it gets uncomfortable.

    Bricscad is a typical "destructive" Modeler, without modeling history, nearly non parametric (besides Compositions, Doors/Windows, ….). But with that Solid Direct Modeling, down to Component level you can model everything and exactly like you need.

    So both have their pros and cons.

    Initially in Bricscad you would/should typically start designing with basic Solid Modeling, then use Bricscad's Machine Learning to BIMIFY your building and let it sort your Solids to Walls/Slabs/Columns ….

    Meanwhile with tools like QUICKDRAW, you work already with Walls and Slabs, or apply Windows and Doors. With PROPAGATE you can create some (semi?) parametric Column/Beam Arrays or model Details and machine learning will find similar situations in your Model and apply the same detail automatically.