Our clients also have their own titleblocks we have to use, with the n+15mm width
Yeah - in which case the one size for the set gets used and added to the papers for printing, or a custom page size is used. Either works, but in all cases I recommend working with the customer or ensuring that you bill up for the customization work for prints. They’re costing themselves money this way no matter how you slice it.
That multiple clients are asking it does indicate that the n+15 is actually a standard, but not one that you’re set up for (i.e. ISO vs ANSI, where the A4 vs A is something like 15mm off…).
Kinda late to this party, but just wanted to say that we haven’t really seen any of the issues described here, but we typically only use 2-3 size sheets but that does include Arch D, E1, E which is the biggest (regular) size I’ve seen used. I will say that I have seen issues with Bluebeam and I always recommend folks use the Export vs Print.
One last thing, we built the Dynamo node functionality into our toolbar and it’s been pretty much flawless using the Export functionality with our custom naming / sorting features on top.
3 Likes
Do you never use viewports with a break in them?
As far as i can tell the distorted dimensions are always an issue when using the export function currently…
I do agree with this 100%, the graph i made with also works flawlessly for our naming convention and exporting speed (compared to printing only the same sheet sizes in one batch manually, renaming pdfs afterwards etc.)
I just yesterday moved the graph to a pyrevit button, which makes the experience even better compared to Dynamo player, but the benefit is absolutely significant compared to manually printing PDFs
I’m wondering if the limits relate more to Python than the API specifically in this case. We have had issues using it natively and in pyrevit vs the typical temporary sheet set + submit print approach that was used pre 2022.
Getting properly into C# these days so will know soon enough…
1 Like
As far as I know we have not had these problems as I stated, but I did also test and could not reproduce the issue either. Maybe in a combination of things that just align a certain way to make it happen.
1 Like
The main way i could fairly consistently simulate it where i work is sending through 1500 or so fairly small sheets. Tended to freeze up around thr 600 or so mark in Dynamo, pyRevit and also in revit itself.
It wasn’t a 100% chance, but enough for me to stick with the standard printing API, even though it is a bit slower and depends on a preconfigured printer with saving prompts supressed etc.
2 Likes