Quasar Package Update

@jean sorry for the misunderstanding.

What I’m saying is that the room elevations are coming out shorter from your dynamo node (see the first image I posted above - the elevation has the correct width but a shorter height, hence the top of the room is cut out by the crop box). What I want is actually the view to have the same shape of the room with just an homogeneous offset around it. But, reading the code, it seems it doesn’t depend on that.

That’s why I was wondering if it was happening to you too that the ViewUtility.ElevationInRoom node generates views that have the correct width but the wrong height (again, like in my image above).

@ATassera, Elevations views’ crops are shaped based on the room boundingbox’s max and min values.
On top of that, desire offset will be applied. Which means if you use offset value " 0 ", view crops will be the same shape (height and width) with the room. One of my concern is the unit conversion because, in my node, I have already divided by 304.8 assuming that the project unit is millimeter.

Anyway, I will check again, is this node really have an issue or not?
Thanks mate, have a great day.

Thanks mate!
Let me know what you find out and have a great day you too :wink:

Hi Jean,

Just noticed something with the view ViewPortAlignment. If there isn’t matching views and legends it can use the location of a legend for a view. Highlighted area below is where it put the view. Awesome node otherwise.

image
image

@vanman thanks for your info. Of course, that will be improved in the upcoming version, too.

Quasar View Extension on Dynamo Version 2

Quasar Package version 2.x.xxx offers a view extension to organize the scripts. Upcoming features are under development. For now, please do enjoy as so. :hugs: :sunglasses:

3 Likes

The CopyLevelAndGridFromLinkedDocument node works,but if the code is run more than once, it copies the levels and grids again.

Can it be updated so that it doesn’t copy anymore once there are already grids and levels?

hi @Revit_Noob, thanks for trying out. My answer is if you’ve already successfully copied why do still need to use this node again.

in reality i will not of course, but it may happen :slight_smile:

just testing out the code

1 Like

I’ll toss a good reason out there:

Let’s say the source file was updated as the design team made a change in floor to floor height to add another level.

If Dynamo maintains ownership of the Revit elements you can update the levels and elements / data built up on them by opening the graph which created them, and hitting run a second time.

See here for an example: Element Binding in Revit

2 Likes

@JacobSmall :hugs: nice one, thanks for the info … Let try it out later.

2 Likes

Hi, Jean
I use Quasar create an element filter, but the DropdownSelection just output one list that is the last one selected. The DropdownSelection can output a list like a filter input list.:grinning:




c7b955800c1f5e175890f2512bac922

hi @zhao.zp, I do appreciate your feedback. May be, return a dictionary … like this:
{ "title" : [ "selected", "items" ] , ... }

Yeah~ but with another issue, When I frome the selection of the second of the last return to the third picture option that will show the option is empty.

Hello, i am using ThreeDViewByRoom node and it generates the views, however it creates lots of unwanted views. Plus, it is not making the correct bounding box.

hi @Thomaz_Yuji_Baba , please take a look at this sample :point_down: for the correct usage.

HI @jean,

When using the elevation by room & ceiling plan by room nodes I am getting errors. On the elevation node, the elevations are being created correctly but there are unwanted nulls & elevations in the Revit family. Can you help? Also with the ceiling plan node I am getting an operation failed error. If you can help that would be great. I have attached an example of the WIP script. Thanks very much in advance!

Hi @chris.millar CC: @SeanP , regarding these issues, i attached the on going discussion here …

1 Like

Hi @jean, something I’ve noticed with the viewport align. If a crop box has been pulled over a grid and it is now 2D. The viewport align will calculate the center of the grid outside crop box. This means if your grids are at different lengths it wont align properly. Would be handy to know its always been calculated by the center of the crop box. Not anything outside of it. What do you think? Hope this makes sense. Picture below to try show.

@vanman yes, you are right, it is calculated from the location point which is the center of the viewport (see the below screenshot).

If you really want to understand more : https://twentytwo.space/2019/09/17/create-sheet-with-custom-viewport-location/

1 Like