I’ve created a script that allows to select the levels, view templates and scope boxes and automatically create floor plan views and rename them to “Prefix Level Name Suffix”.
The next feature I want to add is placing these views in sheets. And so far it creates the sheets with the right Number and Name but always fails to place views on sheets. The view once applied the scope box fits into the sheet (if that makes a difference).
The error is something like:
Warning: Sheet.ByNameNumberTitleBlockAndViews operation failed.
View 0 could not be packed on the Sheet. The sheet is 2.75590551181102 x 1.9488188976378 and the view to be added is 12.0110831192295 x 8.95991527766546
I got the same behaviour. It comes when you try to generate views in the same workflow of placing them in a sheet.
I think this is a faulty behaviour of Dynamo. The views keep the original size when they were created no matter you try to apply later a scope box. No matter if you try to apply a passtrough before Sheet.ByNameNumberTitleBlockAndViews is going to pick up the views from the “original existence” with the corresponding size. In fact, if you create views from different ways you realise it only catches the “first view” was created.
I tried to use SetCropRegion of Rhythm and it did not work. In fact it even gave problems to generate the views.
I managed to get they to be inserted in the sheet with the tool Create Viewport of Rhythm but with the problem of viewport title line fit with the original size of the view. Even it is clearly smaller because the scope box you applied.
Obviously if you insert that created view in Revit you are not going to have that wrong behaviour.
yep, you need to use the transaction.end node to make sure the revit document is regenerated before trying operate on those new or modified objects. This would be the same as if you were using the Revit API directly.
Dynamo tries to pack everything into one transaction to save time interacting with Revit - sometimes that’s not what you want and you need to take control using the transaction nodes.
Hello - I’m having similar issues to this thread and I tried adding transaction nodes as you stated. Unfortunately it didn’t solve my issue.
The odd thing about the error (with the plan being too large) is that half of my plans ARE being placed on the sheet and half are not. If there was an issue with the overall plan size you’d think no plans could be placed.
Has anyone else resolved issues with this node? I’ve used it in the past and had success but this particular model just refuses to work.
Hi. I know it is old but I assume someone will have the same problem, unless Dynamo team have resolved the issue in future versions. The unique way I have found to resolve the issue with the views are bigger than the titleblock is adding a huge Titleblock type. I use 15000x15000mm so you get rid of this issue. Later, I change this type by the right one. This happen because the node takes the views before they are reduced by a template. No matter if you use transaction.