Archicad Standard Details

[Anonymous]

We have started making files that are depositories of standard details that we use over and over again, or use frequently but with minor changes. For example we have a file where we put frequently used roof details called A400.pln. We then link the details file to the new project file through the organizer and drag and drop relevant details onto the roof details sheet (for example) in the project file.

This all seems fine for awhile and then the links seem to start to break, or even if A400 is already open new versions of A400 will open to update each and every detail incorporated.

Clearly I am linking the details incorrectly, or there's a setting I need to change. Any advice?

[Eduardo Rolon]

Please do not double post.
---
The way I work is that I have a set of published modules, pdf's and PMK's these I copy in the same folder as the project file in a "Project Details Folder" and these are the ones that I link. Conceptually it is the same as having a "Specific Project Library" in addition to an Office Library.

[Eduardo Rolon]

I also avoid dragging and dropping files and use the Place External Drawing command. It might not do anything but I have avoided the problem you have.

[Anonymous]

Eduardo,

I agree with you: Do not Drag and Drop. DandD is an OS controlled operation,
uses OS designated paths. GS hard codes internal path requests based
on Windows XP and earlier. Places like "My Documents", etc., either don't
exist or no longer have the same path and AC hasn't been updated.

W7 uses a fix called "junction points" to convert path requests from programs
like ArchiCad. "Junction Points" add another layer of abstraction and may be
the source of your intermittent problems. Especially if you are on a network.

To see what I mean: Look in the WE under Special Folders. They all are
hard coded with c:\documents and settings\... But W7 has no such path...

One possible solution would be to reset all Special Folders to locations that
you have "browsed to". Make sure your office standards reflect these
locations across all machines.

Snap

[Anonymous]

I understand the criticism of the drag and drop technique, however, the external reference of published detail has a couple short comings for me, mostly having to do with lossing the dynamism of archicad.
That is, when I drag a pdf of a detail onto a layout the scale will show up as 1::1 not, for instance 1'-0"::3" because that is the scale of the pdf, not the drawing on the pdf.

In terms of trying to correct the shortcomings of the drag and drop technique it seems like if the project file never moves and the detail files never move there should be a way to hardwire in (for lack of a better term) the file path relationship between the two since that is what the external reference method does.

[Anonymous]

Well yes,

Graphisoft should provide an updated solution for AC to locate system paths in the last two versions of Windoze.
Maybe updating AC every year would help.

As far as "wiring in" a path: Allowing users to refer to system variables for paths and such would be a step in the
right direction. Like %systemroot% etc. Microstation allows the user to specify their own %projectdir%, then it
registers that with the OS and voila, no more retyping project paths.

Snap

[Anonymous]

I want to make a couple more clarifications to see if we can figure out how to fix my problem.

1) I'm in OS 10.6

2) When I say drag and drop, I mean I am linking a file with details to the project file through the AC navigator/organizer/ project map pallet.

We were actually sold a template with several details and assemblies which we were taught to attach to our project files in this way. So what I'm looking for is some kind of setting or configuration that I need to correct, because I know what I'm trying to do will work.

[Anonymous]

and one last piece of reference material on the subject. Attached is a screen shot of an error message I just got when I tried to update a detail

[Erika Epstein]

Mickey,

If you've bought a template system and are having trouble using it you could contact the seller with your questions. By the way, you haven't mentioned which template it is

That aside, I would suggest placing details you typically use directly in your template. This will have them pre-linked and any project customization will not affect any other project and the detail will retain the changes.

A separate detail file(s) works only if you don't make changes to any of the details. You can use the pmk solution that Eduardo suggests or make a copy of the detail file(s) for each project so changes will not affect any other project.

In your work environment >User Preference Schemes>More Options : uncheck the the 'do not launch new instance of archicad when placing a view onto a layout'. Don't forget to redefine the User Preference Schemes so this change is incorporated in your work environment.

You can set details and views to manual update if you are going to make changes to a detail or view that you don't want to revert to the original, but this is not good work practice. Instead create a separate instance of the detail/view as described above.

HTH

[Anonymous]

Erika, I think we may be on the right track. However, here is my new error message.