Jump to content

rkraybill

Member
  • Posts

    54
  • Joined

  • Last visited

Everything posted by rkraybill

  1. The icon appearance sounds like the Magic Wand tool in PhotoShop - is that an accurate comparison? I haven't run across it in VW (version 8 through 2008).
  2. Another option: upgrading to Quicktime Pro ($30) give you the ability to open a JPG2000 file and export that to a standard .jpg.
  3. I am not familiar with VW for Windows capabilities, but can you export PDF, import PDF into MS Paint and then export that to .jpg? Or can you just export .pdf and use that file? - .pdf format supports raster graphics also. Hope one of those options work for you.
  4. What is the nature of the reference? Absolute or relative? Is is possible that a folder name in the hierarchy has changed since you set up this reference?
  5. When you get to Revit & 3ds, I would try running it in Parallels or VMware Fusion on your Mac and see if there is much of a performance hit. That would be a lot more convenient than running Boot Camp - you keep your Mac open and running as a Mac. You would still have Boot Camp as a backup plan if virtualization doesn't work very well. I use Parallels for a number of tasks, but nothing as processor intensive as 3D modeling/rendering/animation. Would definitely recommend going over your CAD drawing plan with some people in your department before getting too far down that road. Hope it works out that you can use VW.
  6. On certain projects we include our specifications on the drawings sheets for end-user simplicity. We still use MS Word to edit the master specs and then copy and paste into text fields in VW. In this case, making life easier for others causes us more work. I'm also very interested in hearing ideas on this one.
  7. I haven't, but it sounds like there has been some reorganization in the forum that is making your bookmarks obsolete. The addresses to these specific pages have changed. Given the ever-changing face of a forum, this may happen occasionally. I would recommend saving important discussions as a "Web Archive" to your hard drive. Then you can keep them where you want them - no one else besides you can change the address again.
  8. We usually restart our computers every day. Both VW users in the office are using Intel-based Macs.
  9. I have VW 2008 open most of the day, every day, along with a number of other applications. I see about 1 - 2 crashes per week. This often occurs while working with embedded .pdf files and other graphics. I don't typically use externally referenced files, but do often work with files that become somewhat large (20 -50 MB, due to amount of drawing objects more than embedded graphics). If the use of larger files causes some problems, I am willing to crash once a week for the convenience of keeping an architectural project in a single file. If I were crashing multiple times per day -as some in this discussion are- it would be a different story. Given the occasional LAN trouble that crops up in our general computing, my experiences might also be different if I were frequently accessing files over the network. We are working on an antiquated 100 mb LAN and will be interested to see how general performance will improve one we upgrade to a gigabit switch, etc.
  10. One issue that crops up is making background objects and images too complex. If you are adding image shaders/textures to objects, you don't need high resolution images if the final rendered image of that object is small. Adding lights is very helpful to the rendering quality, but can kill you on rendering time (you have to find a balance on that) - and some light sources may not need to have "cast shadows" turned on - another time savings. Objects with transparency and reflection take a lot of time to render - don't apply chrome shaders to background objects that are hardly noticeable in the final renderings. Spend your complexity wisely.
  11. I have been there a few times over the years. I have learned to shoot for efficiency in the model to help speed up rendering. Some methods of modeling take less time to render than others, even while yielding similar results. That processor speed does sound slow for today (I started my ray-trace rendering career with the Mac equivalent of a 66mhz 486). If you haven't experimented to see if you can slim down the complexity of the model, it would be worth the time to experiment regardless of whether you upgrade or buy new. If your model is as streamlined as possible now, a much faster processor(s) will be the key to speeding up the rendering.
  12. Yes - providing .pdf files has been our relief valve over the years. Up to this point, I have been providing .dwg files and .pdf files for each project. Our problems are going to start once our federal and/or state clients begin insisting upon .dwg format files that are printable, regardless of whether we also provide .pdf files - we have a project starting soon that appears to have that requirement. As to the .dwg file requirements in general: it helps the agency coordinate administrative or record drawings of their facility/installation/base. Despite my frequent frustrations with some of our clients and their file standards, I don't envy the people whose jobs involve coordinating and compiling all manner of plans for a base with hundreds of buildings, streets, site utilities, etc. That is why the ACAD layering is so critical - and why there are rigid standards. VW works well with that component. If I could work with an ACAD user to give me a standard pen settings file and then somehow hack the .dwg export from VW to recognize that file ... I would be way over my head.
  13. Trying to prime the discussion a little: Anyone using VW on US Federal Govnmt work? Our experience working with the US Air Force, the FAA & the Veterans Administration is that they say that the National CAD Standards is their rule, but don't actually enforce it to the full extent. Setting up the AIA layering adopted in the National CAD Standards (classes in VW) is not a problem - that has been our clients' primary concern up to this point. Setting up .dwg exports so that the end user can reliably print our files in AutoCAD would be a problem - a requirement coming soon for us. Any advice or experiences shared would be appreciated.
  14. I agree with Ray - it is obvious that NNA is working hard on the compatibility issues. Compared to a previous architecture-specific package that we used, I have found VectorWorks export capabilities to be very useful and reliable. Utilizing a little trial and error, I rarely have problems trading drawings with other people in the real world (where time is money). My issue is 1) certain clients examining our files with an eye for detail that make us wonder where they find the time and 2) the practical problems that come with an AutoCAD user trying to accurately print our files - if they insist on using a .dwg file instead of .pdf. If a client or other professionals are willing to grant us the slightest amount of flexibility, VectorWorks has excellent capabilities for .dwg export. If a client has very specific .dwg format requirements, I'm not sure that VW or any other non-AutoDesk software will be a reliable solution. I'm hoping that some others have some stories working with the National CAD Standards in VW that they would be willing to share?
  15. I have found running AutoDesk's TrueView (free viewer) a must for conversion sanity. We bought Windows XP for our Mac specifically for that purpose. It gives you the ability to view a .dwg file in exactly the same way that an AutoCAD user will see it. Having files kicked back to you as "unacceptable" a few times costs more than adding a Windows license to a Mac. I appreciate the feedback thus far. Any .dwg export improvements between '08 and '09 that I could look forward to utilizing?
  16. Just to clarify: I have been using VectorWorks since it graduated from MiniCAD and like it. I have enjoyed using the new features as it has grown from version 8. AutoCAD strikes me as a blunt instrument approach to solving fine problems. Unfortunately, it is AutoCAD users who sometimes determine whether my project is a success or not, partly by the nuts and bolts of my .dwg file configuration. I am trying to avoid the situation where I have an AutoCAD user "clean up" my files before submission or (worse) I become a part-time AutoCAD user and clean up my own files. I am very interested in what other experienced users have to say on this topic - Thanks.
  17. One example of our struggles: Setting up the AutoCAD export so that the client can plot from that AutoCAD file with pen settings, fonts provided as if I were an AutoCAD user sending my files to him or her. I have been providing .pdf files along with our AutoCAD files for years to smooth over this process. Wording in a recent RFP from a client tells me that this compromise may not cut it in the future. Also, the National CAD Standards calls out screen pen weights associated with AutoCAD layers that aren't necessarily intended to translate directly to plotting pen weights. Since I am printing WYSIWYG from VW, I have been fudging the pen weights for a better print. I don't expect for that to continue as a satisfactory solution. I am spending almost as much time trying to satisfy strict AutoCAD-using-clients with my files as I am doing real work. Any solutions, shared experiences or sympathetic gripes would be appreciated.
  18. We are an architecture firm that works with several US Federal Government agencies. We have found meeting their CAD file requirements to be a challenge using VW 2008 (and before), but have survived so far. Does anyone have any input as to AutoCAD compatibility improvements in VW '09 that would make our life any easier in this department?
  19. A follow-up to this: I recently had a project that required .dwg file submission. My only solution to this arrow head issue was to manual draw them at the end of my leader-lines and arcs. It was a small project and not very time intensive. For a typical project, that would not be an acceptable solution.
  20. Wes - thanks for the feedback. Its good to know that an upgrade may solve the problem - if all else fails. Anyone else run into this problem with '08?
  21. I have been having problems with arrows at the end of lines and arcs translating to AutoCAD since upgrading to VW 2008. I am assuming the new arrow menu (Attributes palette) is offering extra choices at the expense of compatibility. Does anyone know a work-around for this? This is VW 2008 running under OS 10.5.6. I am observing the lack of arrows using the latest version of DWG TrueView from AutoDesk. This would not normally be a major problem for me, but I have a government client that may make a big deal about it. Thank You.
  22. Another follow-up to this: The problem is related to the .dwg export process. VW doesn't recognize the arrow heads if you export a .dwg file and then import it back into VW.
  23. A follow-up question: Does anyone know of a way to "explode" or decompose a line or arc with an arrow so that the arrow becomes two lines (or three, depending upon your arrow style) that connect to the end of that line or arc? In other words, the appearance hasn't changed, but the arrow has become a set of lines instead of an attribute.
  24. I have been having problems with arrows at the end of lines and arcs translating to AutoCAD since upgrading to VW 2008. I am assuming the new arrow menu (Attributes palette) is offering extra choices at the expense of compatibility. Does anyone know a work-around for this? This is VW 2008 running under OS 10.5.6. I am observing the lack of arrows using the latest version of DWG TrueView from AutoDesk. This would not normally be a major problem for me, but I have a government client that may make a big deal about it. Thank You.
  25. Vectorbits was the solution - worked great for eliminating a problem that would have taken me several hours to handle otherwise. Thanks for the advice.
×
×
  • Create New...