Monday, December 31, 2007
Tuesday, December 11, 2007
Main points considered will be:
* Management of Tool Palettes
* Types of tools for placement on Tool Palettes
* Working with tools on Tool Palettes
* Use of Tool Palettes in a network environment
|System Requirements |
Required: Windows® 2000, XP Home, XP Pro, 2003 Server, Vista
Required: Mac OS® X 10.3.9 (Panther®) or newer
Tuesday, December 18, 2007
10:00 AM - 11:00 AM PST
Friday, November 30, 2007
Thursday, November 29, 2007
After that I stopped by the flight deck. If you watched the general session video I posted it showed what looked like Google Earth and the guy flying into it and around a city. Well guess what. That was an Autodesk piece of software built using Autodesk apps. The controls were a joystick that works with any flight simulator and showed your speed from 0 to Mach 1. This model was much more detailed than Google earth which simply drapes satellite imagery over terrain. This was an actual model built of Washington D.C. and this thing ran smooth as butter. What a trip that was to use the same thing they were running in that demo! Stay tuned to Autodesk labs for more developing info on this promising tool!
Wednesday, November 28, 2007
Sorry if I missed your name but my memory hasn't been the same during AU - I've been drinking the forgetful juice... :-)
Tuesday, November 27, 2007
When it comes to dealing with grass, recommendations included using the hair and fur modifier in extremely close up shots involving grass. Then for medium range shots try using displacement maps to generate geometry at the time of render without adding additional polys to your scene.
For dealing with placing vegetation in the scene try using a P-Flow system for randomizing the placement of objects in the scene over a plane object – esp. if you can convert it to an editable poly and activate the face sub-object mode to use the paint deformation tool to shape your landscape and make it feel more lifelike.
Also check out these pictures taken during the session – one about Advanced Painter which can be found on a place called script spot and the other listing some references for great resources for landscaping with MAX.
However, the creme de la creme happened last. They highlighted how an Architect might utilize Autodesk applications in designing a new library for a civic center in a metropolitan setting. They started using Maya to design a funky looking sculpture which invoked a sense of fabric flowing in the breeze. They took that and other designs into Revit and built a model of the building. Then they shared the building model with the structural engineer that designed the structure of the building and analyzed the structural members of it using Robot Millennium to check for the capacity of the members being used to support based on the stresses generated. They also shared the model with the MEP consultants for them to design the support systems for the building. hey also coordinated with the Civil engineering team to see their design in the context in which it would be built. Then they proceeded to dump all this data into Navisworks to run collision detection to ensure that the Architecture, Structural and MEP data did not hit any road blocks and helped coordinate a list of everything that needed to be addressed. They also used Navisworks to help the construction team see the different phases of the project and how the building would come together.
To put the icing on the cake, they followed it with a design visualization of the building in context using a new program called Newport. This is the first I've heard of it and I will have to add that they closed the general session saying that some technology is not ready for public release - meaning Newport is either in Alpha or Beta testing right now - hmmm.... Anyways, they were able to coordinate the Revit model much better in a 3D Realistic rendering than can currently be done - and much smoother. Autodesk said they have really been stressing having all their products work seamlessly together.
For the cherry on top, they put all this data into something that looked like Google Earth and did a realtime fly by simulation from outer space down to the project site with the building and all its related data in place. They showed different pieces of the data live on the set - something which is much better demonstrated live as opposed to writing it out. I recorded the demo and will post live to youtube later tonight somehow and link to my blog. You're gonna love this!
*edit* Here is the link to the video I took and posted to you tube.
Thursday, October 25, 2007
Wednesday, October 17, 2007
* Common mistakes to avoid while drawing walls.
* Understanding walls – Building and modifying wall styles.
* Wall/opening endcaps and wall cleanup group definitions – what they are and why you need them.
Wednesday, October 24, 2007
2:00 PM - 3:00 PM PDT
Required: Windows® 2000, XP Home, XP Pro, 2003 Server, Vista
Required: Mac OS® X 10.3.9 (Panther®) or newer
Space is limited.
Reserve your Webinar seat now (link)
Wednesday, October 03, 2007
That link showed the web address for labs.autodesk.com - once there I immediately found a tool I am going to give a try: CommandComplete
There is some other pretty cool stuff I see at first glance but will have to get into it another night.
Tuesday, September 25, 2007
Sunday, August 26, 2007
- MAX 9 and VIZ 2008 - Get Mental
- AutoCAD Architecture 2008 - Feature Enhancements for AutoCAD Architecture 2008
- Revit Architecture 2008 - Revit Architecture – Interoperability from Revit to 3ds MAX
- CAD Management - How to Deal with 300 Users That All want it Their Way
Wednesday, July 25, 2007
Friday, June 29, 2007
Learn how to harness the power of Project Navigator in ACA 2008 in the most robust version yet released.
Space is limited.
Thursday, June 21, 2007
To allow all lines of the table style to print, you will need to modify the table style. Please reference the image below the steps.
Go to the menu Format and choose Table Styles…
- For step 1, select the Sheet Keynote Legend table style.
- For step 2, click the modify button.
- For step 3, select the appropriate component of the table in the drop down list.
- For step 4, click the borders tab and click the button to give all cell edges border lines.
The follow up question to the solution above was: "Is there a way to change the style permanently so I won’t have to go through this every time?"
Right click the Sheet Keynote Legend tool on your tool palette that you are using and choose properties. Refer to the highlighted path in the image below. Browse to your file and setup the table style in that file to use the settings you want. Please keep in mind that just like any other AutoCAD drawing, once a style is defined in a drawing, it will need to be re-defined to use the new settings. I would recommend using Design Center to update the table styles being used in existing drawings.
Wednesday, June 20, 2007
August 23 @ the Anaheim Convention Center
I will be presenting several classes this year. The SCCS website will list specific descriptions for each class. Here are the classes I will be running.
- MAX 9 and VIZ 2008 - Get Mental
- AutoCAD Architecture 2008 - Feature Enhancements for AutoCAD Architecture 2008
- Revit Architecture 2008 - Revit Architecture – Interoperability from Revit to 3ds MAX
- CAD Management - How to Deal with 300 Users That All want it Their Way
Thursday, June 07, 2007
- The detail engine in ACA and what they offer over traditional detailing methods
- What kind of details can be created
- How to create one architectural and one structural detail
- Annotate details via keynoting system based on CSI Master Format
- Other possible uses for keynotes
June 20, 2007
Registration is free! Each attendee will receive a $5 Starbucks gift card as our token
of our appreciation for your time. That's worth at least one drink!
Tuesday, May 29, 2007
It really depends on where you would rank the type of graphics card you purchased. Since I have not had to spec a graphics card for some time, all I can say is what is on a manufacturers website stating whether it falls under the ultra-high performance, medium or entry level category. It has been my experience with previous versions of MAX and VIZ that Direct X (or DX3 as some tag it) displays better and handles on screen graphics better than open GL on a poor or mediocre graphics card, sometimes you even needed to resort to software driven. However, with the newer cards that are out there today it has become much less of an issue. What does this have to do with AutoCAD based applications?
To give a little history, Open GL started back when the film industry and other high end graphic applications were on the rise and using Silicon Graphics workstations. They needed an open source to write code to display all the 3D objects that applications were running. DX3 came as a solution for game developers who needed a consistent platform on which to build their game engines. Microsoft has always been the developer for DX3 and has not turned it into an open source code - meaning they are the only developers for DX3. During that time, it was a big deal to choose the correct driver. Typically Oxygen cards (now bought out) were the best of the best and only ran Open GL and there were others that focused on DX3 only. I was never fortunate enough to run a system running an Oxygen card, but that is a moot point now as they are defunct and out of date. Now most cards support both drivers and run very well using either one. An application can only use one driver at a time and usually needs to be closed and re-opened before switching to the a different driver.
With that out of the way, I would have to say that it would be up to the individual to give preference to one driver over another at this point. Yes, AutoCAD based apps are different than MAX or VIZ, but the same principle of the state of your graphics card will apply. I would say that if you have bought a graphics card in the last year that was either medium to high end, it will be a wash and difficult for the average user to tell a difference in performance between the two. Since both drivers are for displaying 3D objects live on screen, AutoCAD will not use either until you break into a 3D view. MAX and VIZ on the other hand use it all the time so it becomes more apparent. I would give both a shot for one whole day each and if you feel a better performance between one or the other, go with the one that seems to run the fastest.
For an even greater in depth read on the differences between the two drivers, have a look on Wikipedia. http://en.wikipedia.org/wiki/DirectX_versus_OpenGL
I'm also planning on a CAD Management class and a MAX class for our upcoming SCCS in August. Check back here for some tidbits on what those will involve and why you will want to be there.
Tuesday, May 08, 2007
Here's the deal. Using a 3D laser scanning device such as Faro or Leica a user builds what's called a point cloud that has millions of data points that represent actual coordinates of all desired geometry. These points need to be tied in with some sort of geographic location such as NAD or somewhere in the GPS grid. When that is done and the geometry imported into CAD, the point cloud is typically millions of units away from 0,0 due to each region of the NAD having one common point. Millions of units generally translates into hundreds of miles which is a LONG ways away from 0,0. The point clouds can be used to build all sorts of data - terrain, buildings, tunnels, crash scenes from auto accidents (including the wrecked vehicals).
When geometry is located that far from 0,0 - things start to happen - strange things I might add. Commands stop working properly on obects, things display wrong in 3D - even vertical apps built on top of AutoCAD such as ADT start displaying things incorrectly. To start with, Shaan has made a few posts on his blog that discuss this. Post 1, post 2, post 3. Reading these posts are essential to understanding what the problem is when you have geometry far away from 0,0.
Shaan's article uses the drawing of the solar system that many of you may remember from the older days of AutoCAD. You can draw the solar system to scale, but you run into problems when you try to draw a lander on pluto to scale due to the limit of digits that the computer can use. Currently that is 16 digits total and that does not mean 16 on each side of a decimal point. 16 total means you can have 10000000.00000001 or 1.000000000000001 or 100000000000000.1 as a number. When dealing with coordinates in the millions, you run out of decimal places real quick and that is what cause things to stop working when far away from 0,0.
Also, there is a lovely article on Cadalyst that discusses this in depth too. This article describes some lovely workarounds for dealing with this situation. Typically, if the user doing the scans knows in advance that the points should be registered to a local 0,0 instead of a state plane - the point clouds come in close to 0,0 which is great. But what if that wasn't done before the point clouds were generated? What if the user cannot move the point clouds near 0,0? Well, those are questions I don't have an answer for right now - nor does anyone else seem to. If I find something more on this, I will post an update.
Friday, April 20, 2007
- Annotative scaling for AutoCAD, AutoCAD Architecture (ACA) and AutoCAD MEP (AMEP).
- IFC 2x3 compliancy for ACA and AMEP along with the Revit based products is now built into the software package.
- Display settings are now available on the Properties palette for editing (my personal favorite)
- VIZ 2008 inherited all the sweet mental ray goodies from MAX 9.
Tuesday, April 10, 2007
Wednesday, April 04, 2007
Friday, March 23, 2007
ADT is really still here - it's just sporting a new name and a new look. I know many have mixed feelings on the name change - as do I. I was introduced to ADT with the release of 2004. I immediately embraced the step up from vanilla AutoCAD and jumped right in with both feet learning the platform in and out. For those that remember the splash screen from ADT 2004 and 2005, it was a picture (tinted blue) of the Tokyo International Glass Forum Building (picuture included at end of post). In 2005, I had the opportunity to give the building a visit while on vacation in Japan. I have to say it's a wonderful building, but then again, I'm also a big fan of all things Japanese - so I'm a little biased. That being said, ADT has been all I've known the product as. Others who go back further recall it as softdesk (prior to Autodesk buyout). So I suppose one more name change isn't that big of a deal in the grand scheme of things, right?
Perhaps. Change is part of our life. Yet for some reason, when it comes to technology, many people don't like change (I'd say 50%-60% - this might change as the years go on, but currently that is my opinion). So for some, this name change is world shattering - life ending. For others, it's just another day at the office. At first, I was more than a little bothered by this name change, however I quickly snapped out of it and realized a couple of things. One is that change is, as I said, part of our world. The other was that I had no ability to change the mind of a multi-billion dollar company and their marketing departments' choice to change a few product names. So I quickly moved on and accepted the fact that ADT was gone and replaced by AutoCAD Architecture or ACA for short. This change affects more than just Autodesk - many other companies will have to adapt to this name change. Blog names will need updating. Websites need updating. Speaking of updating websites, the ADT/ABS Community on AUGI is being updated in anticipation of the new products shipping. I suppose I should get busy editing those web pages!
Tuesday, March 13, 2007
While I agree, this is not for everyone, it will work in many situations. Beth also mentioned she was curious about performance seen from keeping content locally vs in a network location. What the end user will see varies greatly on a number of things. Size of the company, locations of the office or offices, network policies, number of people trying to access the network and so on. I guess what I'm saying is that it would be very hard to put an average number to any perceived performance boost due to varying network conditions. I think it would be safe to say that a small office of 50 people or less would probably not notice a difference between content stored locally or on the network. Medium size offices (50-100) would see some difference and a large office environment (100 and above) would see something much more noticeable. I've have seen companies spread out over a WAN that had some really complex network systems in place to keep everyone connected. Hopefully you are not building the content so it has to pull across the WAN - that would make things painfully slow.
Either way, as Beth mentioned, consistency will help tremendously. I've seen that more now than ever before as I have seen things become much easier in deploying the next version of the software. Whether you go with content locally or on the network, it's your call. If given the choice for myself, content will always be local if feasible.
Sunday, March 11, 2007
The Profile.aws contains a number of things about how palettes - specifically tool palettes - are displayed. The aws file extension stands for AutoCAD Work Space and is a fitting name since it remembers changes you make to the environment of AutoCAD. If you were to open the aws file with Microsoft word or Internet Explorer you will find that it is based on XML code. While I do not write or fully understand XML code, the structure of it allows you to start to understand it if you look long enough (kinda Matrix esq, huh?). One thing you can try if you open it with MS Word is to use the find command on the Edit menu to search for a name of a tool palette you know is available in the program. Once it finds the palette name, look at the surrounding text to see what is around it and it should give you an idea of what data is stored in the file.
In vanilla AutoCAD, tool palettes allow you export the tool palette groups to an xtp file which can then be imported to another users computer. While this is dandy, for those using ADT (even if you run a profile to use ADT as AutoCAD), this option is disabled to prevent exporting tools on palettes that only run in ADT to users of AutoCAD. While I find this response from Autodesk somewhat lame, it is what it is. While I would know better than to load ADT palettes onto a system running only vanilla AutoCAD, appearently Autodesk thinks there are some that wouldn't know any better. I suppose they are right but this leaves us advanced users trying to figure out how to make ADT have standard tool palette groupings. One could use Catalogs and have them mimick tool palettes, but I find this to be somewhat of a long winded process that novice users have a difficult time with. This means the advanced user is stuck going around dropping palettes from catalogs onto everyones system and we all know the advanced users time is better spent elsewhere.
Enter the Profile.aws - this file contains all the info of the tool palettes on a system - order of palettes, which palettes belong in which group and the location/size of the palette on the computer screen. This file exists for both vanilla AutoCAD and ADT, so it does not matter which platform you run on. So if you as the advanced user builds and organizes 50 palettes into multiple groups and sub groups with specific ordering to them, this file is the key to duplicating that orginazation to everyone else on your team or in the company. Where can you find it? There will be a profile.aws in a folder that corresponds to the profile name in AutoCAD. This is the *.aws file you want - the FixedProfile.aws file will do you no good. If you installed AutoCAD (or ADT) via the application defaults for support files then you can find the profile.aws in a location similar to this: C:\Documents and Settings\USERNAME\Application Data\Autodesk\ADT 2006\enu\Support\Profiles. Once inside the last folder in that list, Profiles, you will see folders for each profile available in AutoCAD. Go into the one for the profile we are working with and you will find the file Profile.aws. Export your profile from options and import it to a test system. Close ADT and then copy the aws file and drop it onto the test system in the mirror location for it. Reopen ADT and you should have the palettes grouped in the same order as the source system!
Saturday, March 10, 2007
Here's some questions you can ask to help determine where the content needs to be store.
- Who will be maintaining the content if it needs revising or additional content added? Advanced, technically savvy users should have no problem placing the content anywhere they choose and maintaining it in addition to that.
- If no such user exists in the office, who will be doing the revisions? If it will be an outside consultant that has limited time in office, you may defer to their preference.
- What content needs to be accessed and used with AutoCAD/ADT? Depending on what the content is, you may choose to have a mixed environment where some content is stored locally and other content stored on the server.
- Who interfaces with the company and how flexible do you need the standards to be? If the company has strict policies on the use of their content outside the workplace and have tight controls on what data enters/leaves the workplace, then storage of all content on a server is unavoidable due to the need to restrict user access. This also means you most likely will never have to worry about project consultants trying to use the same tools as the rest of the internal company staff. However, more firms are beginning to realize the benefits of having their own employees be able to use the same tools at home as they do at work in the event they need to work overtime on the weekend and wish to do so from home. In addition, many firms have outside consultants helping to generate plans as well and they realize if the consultants have access to the same tools then they get more consistent plans that match what they would do in the office.
- Is the content something that will be re-usable for future releases of software or will it need to be rebuilt? Certain parts of the software are not backwards compatible. For example, tool palettes have been getting little tweaks as the releases of the software move forward. If you use those new features in a more current version, will you need to think about keeping a legacy set of palettes stored in that case? Hopefully not, but something to keep in the back of your mind...
For AutoCAD, I would consider things like templates (dwt, dst and dws), fonts, CUI (menu) files, plot styles, profiles, dynamic blocks, tool palettes, etc. that ship with the product to be ootb content. For ADT, I would consider things like AEC styles (architectural, documentation and miscellaneous), ADT tool palettes, Detail Component and Keynote libraries, PN template projects and Content Browser Catalogs that ship with the product to be ootb content. Usually most firms have their own version of these items. Due to that, I will typically let all ootb content be installed to the local machine. The main reason being is that if for some reason a problem happens on a system, I have a fall back to check and see if the same problem occurs under ootb settings. Some might say that now the users have access to non-standard content. Well, if the average is able to somehow find it, then they are no longer an average user since the content's default location is buried in Documents and Settings and most never venture that deep into the system. In addition, the office deployment will most likely replace the majority of the ootb tools with their own version of it. You can also stress to users that it is not their job to customize AutoCAD - that's my job. They should instead focus on getting those drawings out the door. If they want to play with the software, they are in the wrong position.
Company Specific Content
When I refer to company specific content, I'm referring to blocks, AEC styles, things the are actually drawn in the drawing. The amount of this content will depend on a number of things. How much legacy content have you been bringing forward, how much new content will be generated by future releases and how much content will be built as time goes forward and people find new parts of the software they want to take advantage of. For new users of ADT, the content typically will start small and expand overtime as they begin to use more and more of the software. Where will you place this content?
Well, the location of the content is something that you do not want to change, especially if the content is placed on tool palettes. The reason being is that the content on tool palettes are hard pathed to the source files the drive the content on the palettes. For this reason, I try real hard to pick a location that will never change, otherwise you have a lot of tools to fix. Many like to place tool palettes on a network drive. That's great until one of several things happen. What if IT decides the location of the content needs to move to another server drive and the drive letter previously mapped was S and now it is place on a drive mapped with letter T. All tool palettes that referenced the previous drive are broke and need to be fixed. What happens if the network goes down? No content. What happens if you want to use the tools and the palettes outside the office? You get to go thru an extensive process to package up the tool palettes into a catalog and hope the user can set them up on their own at home. These are the main reasons I prefer to place the content and the tool palettes for company specific content on a users local drive and in a location that can be consistent everywhere they go. Hence in my second post why I outline placing everything in a folder on the root of their local C drive. Every computer I've worked with has a C drive.
Other options I've seen used if you must keep content on the network is to burn it to a CD or DVD and remap the optical drive to match the server drive. You could also place the content on a flash drive and remap the flash drive to the server letter. You would want to do that after disconnecting from the network and prior to launching AutoCAD. The advantage to using a flash drive is if your content and project files are stored on the same drive letter you do not need to repath xref'd files when working at home. Simply drop the project files on the flash drive as well and you are set to go. As a side point, you can use a flash drive at home mapped to the server drive letter your project files are stored on to avoid repathing xref files when working from home. Another option is to use something like Robocopy to copy files from the server down to a local folder each time a user logs into the network to ensure they have the latest version of files on their local drive.
Ultimately, this is something you want to think about long and hard for each situation you come across. Believe me, I know from experience, it is not fun to get all your content built and placed on palettes only to find out they should have been mapped to a different location.
I consider things like fonts, plot styles, pc3 files, CUI files, lisp files (or any custom apps), templates - basically anything set for use in Options, appload or the CUI - to be support content. Tool Palettes are the one exception to this. Again, where you place these files will reflect the office environment you are in. Most of these items get placed in their own respective folders for the particular team or office. In the situation that I gave at the beginning of this series, there are variants of each of these items. For the standard office content it goes something like this.
- C:\Company CAD\Custom - This contains any general apps, files or other misc content that is the same for everyone (i.e. - acad.pgp, master lisp file, arx, vba, etc.). Let me stress that if you have a company that is bringing forward legacy custom commands from previous releases (like back to R14) take the time to sit down, document all commands, make sure they work as intended and look for any duplicates. It's not a fun task, but highly worth it in the end especially if they have a lot of them since you will then have a base on which to develop additional commands if needed and not wonder why it is calling up some other command you didn't know existed.
- C:\Company CAD\AutoCAD - This contains the CUI files used for this variant of the install.
- C:\Company CAD\ADT - Again, contains CUI files used for this variant of the install. If they using the Acad.cui loaded as a nested CUI inside the adt.cui, then there is a unique acad.cui I place in this folder. Do not reference the one inside the folder C:\Company CAD\AutoCAD - I have found issues trying to do that.
- C:\Company CAD\Team A - Once again, contains CUI files used for this specific team. Do not reference the CUI files in the other Company CAD folders - I have found issues trying to do that.
If you are wondering what issues I have found, when I first started playing with this situation, I had the bright idea to make my life simpler by having an enterprise CUI loaded with every team CUI loaded as a partial. The problem I quickly ran into was running the menus and toolbars and commands via workspaces and profiles did not work they way I expected them to. This is what led me to the above break down of CUI files. Just trust me on this one if you are using the same approach I am.
For the other support files, here is a little more break down on them.
- C:\Company CAD\fonts - Everyone in the company uses and has access to the same fonts so they go here.
- C:\Company CAD\Lisp - An extensive library of custom LISP routines has been collected over time and compiled in this folder. They are loaded with a master lisp routine located in the folder C:\Company CAD\Custom.
- C:\Company CAD\Plotters - This folder is empty, minus one shortcut folder inside it. The shortcut folder points to a location on the server that holds all office plotter files. This allows the user to add plotter config on the local machine outside the office if needed.
- S:\Company CAD\PMP Files - This is the one exception where I have a folder pointing to the network. Everyone gets the same PMP files for the office. If the network goes down, you can't print anyway.
- C:\Company CAD\Plot Styles - This folder follows the same principle as the Plotters folder. Individual users can drop project specific plot styles for projects from subs on the project into this folder to print their drawings if needed.
What about Autosave, temp and log folders? For ease of users looking for such files in a panic, I place them in a seperate folder under the root of C called C:\AutoCADresourceFiles. Remember to empty these on your local machine prior to compiling the exe for the team content or the compiler will add your autosaves, temp and log files in the exe, thereby adding unnessecary size to the exe file and increasing compilation/installation time.
- C:\AutoCADresourceFiles\Autosave - Pretty self explanatory.
- C:\AutoCADresourceFiles\Log Files - Any log files that are generated from things such as exports, etransmits or plotting/publishing.
- C:\AutoCADresourceFiles\Temp - Any temp files generated by AutoCAD during operations such as refediting xref's, opening host files that contain xrefs, etc.
For AEC content such as Tool Catalogs, Detail Component and Keynote Databases, I leave them pointing to their default locations. For Tool Catalogs, if these are used they typically per team or project and would be placed in the teams folders and then added to each individuals Content Browser. I find that they are rather unnecessary in this particular case since tool palette setup and management are controlled by the exe. In my opinion, Detail Component and Keynote Databases (if used) should be on a project by project basis, copied from a master set on the server and set current via PN. Same goes for project based tool palettes if used. At the end of the project, you should evaluate if any changes or additions made to the project specific content should be added to the teams standard or master set of tools.
I apologize for the length of these posts, but this turned out to be a bigger project than I had originally anticipated. On the flip side, I've finally written down what I've been lugging around in my brain for the last year and a half and it feels like a great weight has been lifted. This has been something I've been wanting to do for some time and I'm glad I finaly did. Hopefully this will help you determine what to do with the variety of content and situations you might run across. If you have something else that you feel I didn't cover in this subject, please drop me a line!
Friday, March 09, 2007
For phased work, I personally would start the project with a defined set of classifications to help in separating objects that do not need to be scheduled. Outline the main phases and base your classifications on the phases. As for PN, you could use divisions for each phase, but I find that gets a bit tedious. I would be perfectly comfortable keeping all phases under one division. The exception to this would be if different phases overlapped into parts of the building already built - I.e.: Phase 1 is the exterior shell and phases 2 is the interior finishing - or something like that. Then I might consider using divisions, but even then I would be hesitant. Another approach would simply be to use folders in each part of PN (elements, constructs, views and sheets) to identify the drawings of each phase. Either way you approach it, the drawing file names should all be unique to the phase they are associated with (I.e.: phs1, phs2, etc. should be included in the file names) for archival purposes down the road.
For modernization work, what you do may depend on what needs to be done with the legacy drawings. In the typical scenario where the old drawings must remain un-touched for archival purposes, simply make a copy of the original project. If it was previously done in ADT using PN, see if you can re-use the existing PN project as a base for your files or simply import the old drawings you need into element files. If working with the copy of the old files, you can either edit them directly to reflect the changes, or xref them into new drawings and use them as backgrounds (which you might want to do if you need to show part of the old building as screened that is being untouched by the modernization). Here you will begin to see the similarities between Phased and Modernization work. You can again use classifications to help in separating objects that do not need to be scheduled. Whether you are using old drawings as a background or editing them directly, you need to make a distinction between the old files and the new ones so they do not have the same names (leaving the old files named the same, but appending mod1, mod2, etc to the new file names). Again, use of divisions are optional in my opinion, I would prefer to use folders in each part of PN as it is a bit more visual for me.
Wednesday, March 07, 2007
- Type PELLIPSE and set the value to 1.
- Draw an ellipse with the values needed.
- Right click any wall tool on a tool palette and choose Apply tool properties too... -> Linework.
- Select the ellipse and you will have a wall that is segmented, but in the shape of an ellipse.
The majority of the stuff in this area is generated by the first screen in the script wizard. Make sure to save your script files in the event you need to update the office content or are facing a new version of AutoCAD that you are rolling out. Then all you have to do is change the version of the exe and they can run the updated version. If it detects a previous verion on the system it will overwrite it and bring the user up to speed. Keep in mind if you have removed files from the folder containing your content, those files will not be removed unless you use add/remove programs to remove the previous version before installing the new one.
This is the line that will place the desktop icon on the desktop to run the company profile for AutoCAD.
***Warning!!!*** Registry values are extremely picky. They make programs work the way they should and if the wrong one is deleted the program (or a bunch of programs - maybe even the OS) most likely will stop working. If you've never worked with the registry or don't even know what I'm talking about, proceed at your own risk. Everytime you make a profile in AutoCAD and modify it or move toolbars around in your workspace, that data is written to the windows registry. Each version of Autodesk products have their own location and values in the registry. As I've worked with AutoCAD and ADT over the years I have tried to take some of the mystery out of what exactly happens when you tell options to set Autosave to 10 minutes instead of 30 minutes or tell options to give you a white background in paper space instead of black. Previously if I had someone import a profile for use in AutoCAD, it was in there for good. The only way to force them to update to the changes I made in Options was to delete the profile in AutoCAD and reimport the new one. This gets very tedious if you have 300 users and you forgot to change something in options that everyone needs (i.e.: support paths or the like).
Well, when I discovered that the changes we make in options are stored in the registry (and the specific location), I was jumping up and down like a kid given a pot of coffee. Usually they can be found in HKEY_CURRENT_USER\Software\Autodesk\AutoCAD\R16.2\ACAD-4004:409\Profiles. Inside the Profiles folder there will be a folder for each profile in AutoCAD along with keys for each profile.
***Important!!!*** Ensure all Autodesk applications are closed! When you delete the folder with the profile name, it is removed from options the next time you go into it. Why is this a big deal? Because in area 3 of the script file I have a line that will delete the registry key associated with the profile being used by the cad standards when the exe is run by the user. This ensures that every time a new version of tools is issued to the user, they see the really important changes. No more manual deletion of the old profile.
To edit the registry, go to your Windows Start Menu -> Run, type REGEDIT and hit enter. Use the following screen shot as a guide to where you can find the settings. Keep in mind that even if you are running ADT, you will not find an entry for it in the registry - it is listed as AutoCAD.
This is where the compiler looks for all files needed for installation. Important things are the desktop shortcut icon (AutoCAD 2006.lnk in the first line of area #4), Company CAD folder and contents, Profile.aws and the AutocadResourceFiles folders. You'll notice that profile.aws is listed twice. Normally you should just be able to drop it into the current users directory for that machine, but sometimes it needs to be copied to the administrators folder as well.
This tells the exe what to do with the desktop shortcut you packaged up with the program. You'll notice the icon is only placed on the current users desktop. This is because this exe we built needs to be run for each user. If I log onto someone elses computer I need to run the exe to ensure I get the profile.aws dropped under my username so I see everything the way it needs to be in AutoCAD.
Hopefully I haven't lost you along the way here, but I've basically just documented a process I've been fine tunning for over a year now. Right now I have this working like a charm. I started using this when a company was on ADT 2005, used it for the rollout of ADT 2006 and it worked even smoother since we had ironed out alot of details. This week I built a network deployment, script file and generated the exe for the tools for ADT 2007 in one day. Very powerful stuff! Cheers!
Thursday, February 22, 2007
What exactly can Inno Setup do?
Some of the key features include:
- Supports creation of a single EXE to install your program for easy online distribution. Disk spanning is also supported.
- Complete uninstall capabilities.
- Creation of shortcuts anywhere, including in the Start Menu and on the desktop.
- Creation of registry and .INI entries and modifications.
- Silent install and uninstall.
Now how do you use it? I found the help system a little lacking (there is a M-FAQ on their website, but that will only get you so far) so if you are going to get into the more advanced portions of the program, you need to endure the help system and be brave to experiment in your script files. Remember, this is a free peice of software, so you can only expect so much. To create the initial script file that will generate the executable (exe) I start by using the wizard provided to get the script started. This will get things rolling and give you a base to add to if you desire more options to be used in the exe. Here are the basic steps used to create the initial script and an explanation of what some of the sections do.
When you first launch it there will be a welcome window asking you what to do. Start with the script wizard for the first file to get you going.
The next thing you will do is to set what the App name, version, publisher and website that you want to use. Versioning is important as it allows you to know if someone has the latest version and to issue updated versions as things get updated or progress.
On the next screen uncheck the box "Allow users to change the application folder" since that will really mess things up for your well conceived CAD Standards.
Now you are at a point that requires some thinking. First order of business is to check the box "This application doesn't have a main executable" since the executable is AutoCAD. That is a different exe than the one you are building. This screen is also where you add all folders and files that will be packaged with the exe.
Next up is a few other items to fine tune per your liking.
I typically like to show a brief little statement about what just happened on the users computer and what they should do next and this screen is where you do that. Make a txt file and stick it in with your CAD Standards folder and place whatever stuff you want in it. I haven't gotten to the point of needing a license file, hopefully you haven't either.
The next screen I leave as is.
After finishing the wizard, you will find yourself staring at the script file that was just generated. Look for the little icon in the top with the gear (compile) - click it and it will build the exe.
***Important!!!*** Keep a backup of your files somewhere else in the event running the exe you just made messes up your beautiful arraingement! When running the exe the first time, I prefer to test it on a different machine than the one I am using to make really sure it works and runs the way I expect it to.
Thursday, February 01, 2007
- Run the deployment.exe - this is a silent install which gets everything where it needs to be for ADT.
- Run the AutoCAD.exe, click through the buttons for the install wizard.
- Run the ADT.exe, click through the buttons for the install wizard.
- Launch AutoCAD for the first time - be sure to cancel if asked to migrate previous settings.
- Select the appropriate workspace in AutoCAD.
That's about all that a user would need to do to get the basic set of custom content and tools onto their system. The work required behind the scenes is a bit more detailed.
To start with, you need to collect all your content into one location. The computer I use onsite with my customer is what I use. I install the release of software I will be working with. Since no desktop icon is created I will use the shortcut placed in the Windows Start menu -> All Programs. Once the program has finished launching, I'll create a new profile in Options and name it something along the lines of ADT 2006 (as you get more customized and more teams onboard this will need a more detailed description but for now this will suffice). In centralizing the content on my local C drive, I will create a general folder and subfolders if needed.
- C:\Company CAD
- C:\Company CAD\fonts
- C:\Company CAD\Lisp
- C:\Company CAD\Custom
- C:\Company CAD\AutoCAD
- C:\Company CAD\ADT
- C:\Company CAD\Team A
- C:\Company CAD\Team B
The list would go on depending on how detailed you wanted to get or however many itterations of the customization you need to build. Each of the paths I listed above are pretty self-explanatory for what would go in them. Inside the folder AutoCAD, the items I would place in there are the menus (cui's), desktop shortcut needed, the exported profile from AutoCAD Options (AutoCAD.arg), the profile.aws file (more on that later) and the readme file for the executable that will install all this on the users system.
Once you have your content localized, you can start customizing your environment in AutoCAD. Start by pointing your paths in Options to point to the folders on your local drive. Then, start configuring your CUI to load any custom content needed such as LISP files, partial CUI's, etc. which should all be located in the folders on the local drive. I usually do not put anything in the startup suite of Appload since all LISP files are loaded with and main, enterprise or partial CUI files provided they are loaded in the CUI.
To help avoid users tampering with the setup of the custom content, I place the AutoCAD CUI as an Enterprise CUI and the office CUI files as partial CUI's inside the AutoCAD CUI. Since the enterprise CUI is read-only, when first configuring your CUI's, you will have to load the AutoCAD CUI in the Main CUI slot inside AutoCAD Options. Once you are done configuring the CUI's drop the AutoCAD CUI file into the Enterprise CUI slot and fill the Main CUI slot in with the custom.cui file that can be found under your username application data folder since all users will have this as a common file on their systems. Then if they want to build custom menus/toolbars or change the way their interface looks they can do so without altering the standard install.
Once everything is setup, go back into options one last time and export your profile to the folder for your customization on your C drive - in this case C:\Company CAD\AutoCAD and name the profile AutoCAD.arg. The other file you need is located in your username application data folder called Profile.aws. There will be a profile.aws in a folder that corresponds to the profile name in AutoCAD. This is the *.aws file you want - the FixedProfile.aws file will do you no good. If you installed AutoCAD (or ADT) via the application defaults for support files then you can find the profile.aws in a location similar to this: C:\Documents and Settings\USERNAME
Once you get AutoCAD configured and running the way you like, it's time to start configuring the executable. That comes in Part 3.
This makes for an interesting scenario. Most of us like to keep everything on the server since that is usually backed up on a nightly basis, can be locked down with permissions to prevent tampering with customized CAD content and is conveinent if a change is required in the content that was customized. However, how do you handle those that want to work from home or the consultants? Those working from home could use a VPN, but think of the logistics and paperwork nightmare this would create for the consulants to be allowed into another companies network. Even if VPN was an option, you would now be at the mercy of the speed of your connection to the outside world and in a production environment this is no good.
This meant that all custom CAD content needed to be located on the users local C: drive. What content? Fonts, menus files (cui), Lisp routines, tool palettes, CAD blocks, etc. Many will counter with the arguement that the user now has local access to this content and can modify it at whim. Well, since the process of placing the content is completely automated, and the users job is architecture - not CAD Management, we have found they leave the custom content alone. We encourage them to submit requests for changes in the content or custom menus instead of them doing it themselves which seems to be working for now.
Currently there are 2 default setups for the general populace. One for AutoCAD and one for ADT. The site employs Architectural Desktop (ADT) solely for ease of installation in a mixed environment such as this. One network delpoyment is created of ADT and installed from that to all users systems. In addition, one deployment per campus is created since each deployment must point to the correct network license server. This means that a total of 4 network deployments are created, one for the main campus and 3 additional ones for each of the sattelite offices. When I build the deployment, I set it so that no desktop icon is created on the users desktop when they install from the software image on the server. I also use the application default for locations of all support files. Also be sure to choose to install Express tools and/or 3D DWF Publishing as they are not turned on by default. The beauty of this is that now I can keep the customization of their CAD content completely seperate from their software installation. I'll discuss that in the next post.
Also, keep in mind that as I discuss this, I will interchange the terms AutoCAD and ADT. At the level we are dealing with here, they are one and the same. They both use similar installation methods and both use the same behind the scene methodologies for running the programs. I am also basing this write-up on 2006 and above platforms of AutoCAD/ADT and you will see plenty of references to CUI's and how to handle them. If you are still in a 2004 or 2005 release of the software, this is still fully relevant since the programs were setup the same for those releases as well. Instead of CUI's, you have the good ol' mns files and the joys of text coding your menus and getting appload to run what you want and such.