2004-05-06 11:46 PM - last edited on 2023-05-26 12:09 AM by Gordana Radonic
2004-05-21 03:38 PM
2004-05-21 03:47 PM
2004-05-21 11:27 PM
2004-05-24 10:15 PM
2004-06-01 05:36 AM
Graeme wrote:I have found this to be true as well. One thing I have found is that if you don't select anything immediately after opening the lbk you can link to a different AC file and it will read the appropriate drawings and disregard the rest. In addition some other things that prevent Read all from showing a "live" selectable pla or pln to read from other than when there are both files and projects selected is if there are views in a lbk from another project included, in this situation you can actually select an AC file to read from but nothing will happen. It would be nice of you could list the drawings by the name of the AC file or folder they are linked to. An important thing to note here is that if you have a lot of view sets in AC make sure that you select the correct view set as PM does not in any situation default to the correct set (the set the original placed drawings were imported from). Again it will appear to be updating something but nothing will happen. The same is true if there are drawing names (views) in your lbk template that are not in the AC file you are trying to link to.
Oops,
Seems to be working now. I will have to practice this one a bit more. I found I had to select AchiCAD models in the Files of Type dialogue box.
2004-06-01 05:50 AM
Matthew wrote:Most definitely-!! The office ArchiCAD project template should already contain your standard details and they should already be placed in your PM lbk template to be deleted if not needed. Create an independent detail for each one, it may sound like a daunting task but it really isn't too bad and well worth the investment of your or an associates time. The time saved from having to deal with these on every project is IMO very significant.
I recommend merging the standard details into the ArchiCAD project file.
2005-08-24 08:12 PM
2005-08-26 06:38 AM
tsturm wrote:That is why you don't copy. You create templates that are ALWAYS the starting point.
thanks for the suggestion gents. But copying office standards around from Project to Project helps to loose them as standards.
2005-08-26 05:07 PM
you must do this with the place module command rather than merge (I haven't had any luck using merge - maybe I'm missing something though...) This must be done fresh every time you start a new job.I think you must be missing something here Wes, modules are perfect for this. I have even made library parts of details, so that my clients could use favorites to insert them directly into their empty, pre-linked detail windows. Quick and easy! But if you use the same details in all of your projects then I agree with Matthew, just place them in your original template pln. Place them in their own detail windows and depending if you want them to be autoreferenced, place them in live or independent detail windows.
An important thing to note here is that if you have a lot of view sets in AC make sure that you select the correct view set as PM does not in any situation default to the correct set (the set the original placed drawings were imported from).I don't agree with this mate - I've never had a view get confused as to what viewset it came from. However if you have the same sections placed within the same layout book, the markers will only reference the first one. GS knows about this one - trust me!
The only thing that I need to do for each new lbk is add my logo to the masters, add the book info, check the arrangement of the placed drawings and start deleting the layout pages and drawings that aren't needed.Why not have your logo on the Master at all times? If you needed to turn it off or switch it out with other logos, simply place it on a layer of it's own. Do that by double clicking on the imported image, select it all, copy, close the image, and paste it on your master. Just delete the original, place the pasted image on the layer you want and use the layout book layer combinations to determine it's visibility.