Hello Jeff & Spark Team,
Right now, I feel overwhelmed with what appears to be intensive drawing name/ sheet number/designed by/revision cloud over-management by Spark/Revit. This is definitely going to get in my way of being able to use this software in a reasonable manner, probably ever.
So, until I can get my head around all that "management stuff" that actually will consume very little of my time, designing homes, rather than $500M convention centers, I think I would rather coordinate my drawing title, drawing lists, drawing sheet names and numbers myself, manually inserting those things, rather than becoming frustrated trying to understand how the database functions and how it wants to do it for me, and taking much longer in the process, because I forgot to scratch my head and pat my tummy at the same time (meaning: all the software complex steps to get all those things to operate).
Therefore, my question is: can I just use the 3D modeling aspects of the program, and insert views of that model onto my printout sheet masters in Spark? Any reason why not? I'd really like to concentrate on mastering the 3D modeling aspects right now, rather than trying to get my brain into the database management aspects for "labels", which, quite frankly, blows my mind right now. I don't honestly know if I'll ever understand how to makeall those things work. Not a big deal to me, as long as I can simply renumber sheets/names, etc. manually, and just focus on creating a great 3D design, then get the views of it loaded onto the sheets, then plot them out. IS THIS POSSIBLE? thank you.
If you do not use any labels in your titleblock that is fine. The one example one of yours that I have did not have any labels in it. Just load this titleblock into your project and create sheets from it. Once the family is loaded into your project, create a sheet from the view tab of the ribbon. Select your custom titleblock and a sheet will be created in your project browser tree.
By default it is going to get a number and a name. there is no way to stop this from happening. You can change the name and number by right clicking the sheet in the project browser. IN this dialog you can provide a name and a number. You CAN"T leave these fields blank. They have to have something. The sheet has to have values for these 2 parameters. This is not critical for you because you do not have a label in your titleblock family that reads these values, so it does not matter what they are, but the name and number will display in the project browser, there is no way around this.
Once you have you sheet created you can use text tool to create name and number if you wish, but keep in mind there is no connection between what you place as text and the values and what shows in the project browser.
To place views onto the sheets, drag and drop views from the project browser onto the sheet. The view is going to get a view title and number automatically. Not sure if you want that gone too. It can be done but there will be one extra step.
Continue to drag and drop views and add sheets as necessary to compose your document set. As you place views onto sheets the view references will begin to resolve (i.e. section marks and elevation marks will resolve with view and sheet number. The numbers that these references resolve to are going to be resolved with the parameter numbers (sheet number from project browser) and view number (from when it was placed on the sheet), so if you are labeling sheets and views manually, it is possible for these view references to get out of sync.
I would suggest at the very least having a label for the sheet number in your titleblock, and use the view numbers/titles that are added as views are added to the sheets, otherwise you will be spending a lot of time manually coordinating all of the reference numbers. There is a task I do not miss from my years as an Architect. Manually coordinating view references and door/window schedules. Those 2 tasks alone are well worth the time spent figuring out how they work in Spark.
thanks again, Jeff.
I am sure all of these database features have been programmed and put there to try to help us architects, but the interface is so foreign and complex that it could actually turn off some (or many) of your users who just want to draw in 3D and reap the benefits from that and not have to learn a complicated database program just to name and number their final drawing sheets.
There ought to be an option in Spark/Revit that lets non-DataBase folks like me turn off such features rather than have to fight with them to simplify our lives. ("Und you vill like it!").
Then, someday when we have a smart IT person that is at least half as clever as you visiting our offices, someone who can patiently sit next to us and guide us, mouse click by mouseclick and give us a step 1---> step 56 written method to accomplish some of these Dbase tasks, maybe then we will start to learn them. Until then, I fear I am going to wear out kind teachers such as yourself.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Start with some of our most frequented solutions to get help installing your software.