I haven't posted in a while and I figured this would be the best place to ask the following: Has anyone had this problem? Out of the 90+ sheets in our set, about 8 of them have the same issue; title blocks, xrefs and text file objects appear in Paper space, but will not plot. I've checked the following: -Viewports are on Defpoints -Page is 2D -Xrefs are on a visible and printable layer typically '0' -Text objects / blocks are on a visible and printable layer -Drawing has been Audited and Purged -There are no 'circular' xrefs.I began the above procedure at the bottom of the xref stack to ensure no loops.I've attempted to open the pages in 2005 as well. Same problem. I've searched numerous times on various Autocad help forums and cannot find any answers.
Compatibility Issues in Mixed Environments. Mixed environment: A computer environment, usually a network, in which the operating systems of. Mixed Water Out Valve Plaster Guard CAUTION: RISK OF PERSONAL INJURY. When this valve is installed, it must be calibrated to minimize the risk of scalding after calibration. The maximum water temperature should never. And/or hazardous environment, or improper removal, repair or modification of the Product. 2010xref>: 28 (checklist). For complete references and synonymy see xref ref-type='bibr' rid='B11'>Hansen. Florida Department of Environmental Protection, Tallahassee, FL.
They all seem to just reference other forum's threads and state the obvious. The OP's never find an answer. Has anyone ever had this problem? It began to happen to us on the night that our Bid Set was due and I had to switch all model space objects to paper space, scale them and essentially duplicate all the information to paper space to plot.
It's a royal pain in the ass and this would never happen in Vectorworks. This may be an issue with the printer set-up, make sure that the page you're defining in the plot dialog is actually the page that is being sent to the plotter.
All of our pc3 files have gone batty in the past few weeks (producing similar results as you describe) and it seems that ACAD is no longer sending the correct page size to the printer nor the correct position on page-the workaround that we use is to set up separate pc3 files for each page size we need. This is the old (pre-R2000) way of doing things-I'm wondering if 2009 has somehow corrupted all of the pc3 files from the previous versions (and doesn't like working in a mixed 2009/2008 environment). The only other thing that may help is re-creating the drawing from 'scratch', i.e. Copy/paste/re-xref into a fresh.dwg.
What i would do is check the properties on a line that doesn't print and compare it to the properties of a line of the same color that prints. One thing to make sure that are similar are the colors. I noticed on your image that a yellow line produces two types of screening.
For example, 'finished floor' is yellow but appears gray when printed.above that is a yellow square that appears black when printed. Are those objects using the same yellow? It's difficult to tell the difference between yellow 51 and yellow 50 on the screen but those two might have different screening percentage on your plot style/ctb. Similar thing is happening with red.
I noticed that red is producing two types of screening: gray for the perimeter wall hatching and black for the regular lines. Confirm the color of those not printing and then go into plot style and check the settings. A screening of 0 and dither off will not print. As an experiment, try using the match properties on a green line that doesn't prints to a green line that prints and see if that works. What is mind boggling is that it prints when you window around a portion but not when you window around the full layout. When you do this, are you also doing plot to scale or scale to fit? The only thing i can think of is that you are maybe doing a window with scale to fit and the lines are showing up because the line is getting scaled bigger, therefore visible.but when you do the proper plot scale, the lines become too small or faint for the actual scale.
I don't know. I just went through and tried what you described. I'm not scaling the plot.
When I do the window. Also, windowing the layout gives me the same result, although windowing a section shows the title block and missing information. What's puzzeling to me is that we aren't having this problem with other floorplans. Just this one. Same with the sections. One out of twelve will behave this way as well.
I've even had different paper space layouts in the same file behave differently. Say for instance the file 'Elevations' will have A201 - A204. Well, layout A202 won't plot correctly, but the rest will. Even when I rebuild it from scratch, and isolate this exact drawing information, we have the same result.
I'm going on 4 hours of 'problem solving'. Was this problem ever resolved? What JP describes is the closest thing I can find to my problem. One day everything prints fine, then all of a sudden, certain objects won't plot. The layering does not seem to be a factor. One more note. I'm not sure if John ever tried printing to different printers, but I have and some of them are unaffected.
I can leave every option unchanged except for the printer selection. The printer here in my office will not print the object, and they don't show up when printed to PDF (which is what i really need). I have to print the documents to a printer across the hall, and then scan the paper to PDF. Maybe this adds some insight?
We have mostly Windows computers, with a few Macs. Yes, we can run AutoCAD through Parallels and will as needed, but of course the Mac version of AutoCAD can never find the xRefs.
I know I must be missing this, as it is so simple it must be there, but how to I tell AutoCAD for Mac that when it see H:, it should really look at /Volumes/H Drive and repleace all with / And also tell it to do the opposite when saving? Again, this is something so simple, it must be implemented in such aq powerful program, I just can't find where to do it at.
At my firm we started migrating by buying Macs and using bootcamp in 2008. Today we are all Mac's but the original 2008 Mac Pro, which is still a work horse is still running bootcamp and thus working in a Windows Environment. We too work in a Mixed OS environment but I we're not having the same issue as you. Although our CAD standard setups might be quite different. We work by placing all our.dwg's in one folder categorized by stage.
There is minimal confusion with large amounts of.dwg files in the directory due to using standard naming conventions such as: A-PLAN-FLOR A-BLDG-ELEV X-XREF-CIVIL. We devloped our CAD standard for storing files in this maner because of similar issues back in 2000 when we were working with zip drives, not having servers, and other old school inconsistancies. We find that this is a great way of working. And might help you in if you modify your workflow! Unfortunately, that method doesn't work, as we recieve the Architectural files from others 99.99% of the time and many times we are asked not to rename them.
In addition, we do Mechanical, Electrical, Plumbing, Civil, Telecom, Fire Sprinkler, Fire Alarm and Structural, so you can imagine that if we have even 3-4 of those disciplines on one project how hard it would be to filter through all of the files if all files were in one folder. There should be a simple substition routine in AutoCAD for Mac where we can tell it if you see H:, then read it as /Volumes/H Drive/ and replace any with / This is simple and would be very easy for AutoDesk to do. Well if the architects your working with don't follow the National Standards file naming conventiosn then, i can see that as a big issue! We too work with other cosultants such as Landscape, Civil, Structural, Interior, Mechanical, Electrical, & Plumbing. I don't really worry about it their naming conventions since once I XREF their files I never have to locate their file in the folder again.
And since my files are neatly catagorized in the folder, i can still easilly navegate and locate our files. Sorry, I've not done the default directory path for XREF's in a long time.
There is no actual national standard (someone has tried to claim that they made one, but charges a ridiculous amount for it, so it's use is very limited), but believe me, no architect we work with follow any sort of standard for naming (as nice as it would be if they did). I think you misunderstood slightly, I am saying that we work on all of those disciplines, which means that we always have to have and find all of thos files easily. So, our Basic Project Folder Structure looks like this: Arch Civil Mechanical Electrical Plumbing Structural And add or remove disciplines that we are not working on for that particular project, but if we don't do this, it can get quite cluttered on some of the larger projects where each discipline can have 50+ sheets. Yes, going forward we are using relative paths, but we have a lot of older projects that don't use relative paths, so there needs to be an easy way to accomodate this. Of course there is a national standard!
Yes i understood that you firm provide all those different discipline services, i was just saying that we have their files in our folder too. But instead of sorting thru folders we sort with the discipline prefix conventions such as: A- C- E- G- I- L- M- P- S- The relative path is a great way of doing it but if i recall correctly one of the issues we had was when we did go back to reference older projects then we spent alot of time trying to correct the path for one reason or another. So we just concluded to drop all the files in one folder, which works everytime!
Xrefs In A Mixed Environmental Protection
We actually used to do that; however, the problem comes when the architect doesn't do that (which is very often, unfortunately) and they have 200+ files (also happens a lot), then you have 50+ for each discipline, that can now end up over 400 files in one folder. In addition, there is a limit to how many files you can have in a folder on Windows Server before it starts causing performance issues and a hard limit that it won't allow any more than (I forget what that number is, but we have hit it on several occasions when we put all of the files in one folder) The relative paths shouldn't be an issue, as we never need to reference old projects, it's just getting our old projects in a format that will work with AutoCAD for Mac. cid:ec130b97bedb6c46b03b7e4895665bee Chris Wade CAD Manager 1983 West 190th Street, Suite 200 Torrance, CA 90504 Office: 310-464-8404 x 247 Fax: 310-464-8408.