Jump to content

brudgers

Member
  • Posts

    1,323
  • Joined

  • Last visited

Everything posted by brudgers

  1. We all know NNA's offical party line is "Buy a Mac" and their official policy is not to help people specify their PC's.
  2. Here's a nice solid dual Xeon Cad system for less ($2253) than a single core MacPro with only 3 gigs of RAM ($2499...actually $2748 with a three year depot warranty...you can't get an onsite warranty from Apple). ftp://brudgers.com/arefaq/arefaq-public-docs/configure.us.dell.pdf Why would anyone choose to spec their PC based on what Apple sells?
  3. Dell Precision T7500 with dual Xeons. 8 gigs of Ram Some QuadroFX card. That ought to about do it.
  4. Probably easier to parse the vectorworks output using the Auto part of AutoCad.
  5. What type of graphics processor does your Viao have?
  6. I guess you're missing the point. Long time Vectorworks users expect and accept such a high number of them that they don't bother reporting them. You put up with this bug for years across eight or nine releases (if you first encountered it with the initial release of 2008). The user is not supposed to be finding bugs...let alone isolating them. That's what test engineering is for. That's what alpha testing is for. That's what beta testing is for.
  7. And just last week you were defending the fact that the tool/command distinction was made manifest in the interface...
  8. At some level, I'd agree w. you - but you're missing something if you put this entirely on the engineers' shoulders. Though the analogy isn't 100 accurate, this isn't totally unlike having an issue w. your new car addressed by the dealer/manufacturer. Which of the following will get better/quicker results:? "My car makes a funny noise. I want you to find the noise and fix it." "My car makes a metallic grinding noise whenever I'm braking and making right-hand turns. It seems to be coming from the front, right-hand side of the car. I've talked to several other owners who are having the same issue." W/o real-world info from the owner/user the mechanic/engineer might NEVER find the issue. Guess where the analogy between simple mechanical systems and software breaks down. And your mechanic doesn't say, "Oh, we fixed that in the 2010 model. Sounds like it's time for you to upgrade."
  9. You could use a custom symbol and attach a door record to it if you really need the 3d enough to justify it. Otherwise, it could be handled with schedules and legends and a little drafting.
  10. It didn't become a bug just because a bug report was filed. I don't know which is worse, if NNA had reports of the behaviour bet set it on the back burner because Users weren't able to replicate it, or if nobody reported it because it was just seen as within Vectorworks background range of bugginess. In my opinion, figuring out how to replicate a bug is an Engineer's job not the user's.
  11. Here is a demo version of a menu command that does the job. It will allow you to select multiple objects and create a separate extrude from each one. The objects can be on different layers. You can set different heights for each object. Each extrude will be on whatever layer the source object was. The non-demo version can be ordered from kludgecode.com as a menu command or a vectorscript. It's $3.43 via paypal.
  12. You can spend as much time on the model as you want or need to. It's a question of what works best for you. I prefer breaking down the shell from the interior conceptually.
  13. Another case of, "that's just the way vectorworks is."
  14. I prefer to model the shell separately from internal floors.
  15. What time are you checking the file, before or after 2:00? Do you have autosave turned on? Is it set to "overwrite" the original file?
  16. Figuring out something is a bug is frustrating enough. Jumping through hoops to report them is just another level of distraction. At a certain point, people start treating bugs as "just the way Vectorworks is." After losing an hour or two, I know I often resent the feeling that I'm debugging an application I paid for.
  17. On the one hand money. On the other, problems such as this persist in the current version.
  18. Just to be clear, I was able to directly create the problem in VW2008.
  19. Just out of curiosity, do you have any other objects in those classes? If not, try adding some primatives non-symbol regular extrudes to those classes and see if the behaviour persists.
  20. I can't repeat it in 2008 with a plain extrude. However, the code could have been refactored for 2010...after all a plain extrude is just an EAP with the path generated automatically...it doesn't really make sense to require a second type of object, IMO.
  21. I can reproduce the behaviour. Make an EAP. Place the profile in one class, the path in another (not sure this makes a difference). Put it in a symbol. Place the symbol in a third class (not sure this makes any difference). Turn off the profile class (this is also the EAP class). Now turn the profile class back on. I can select the object using ctl-a (select all). But it's not drawn on screen. right clicking and editing the 3d component will make it redraw.
  22. Actually, it triggered something in my memory. I had a similar experience when I was experimenting with 3d objects and classes. If you assign the path and profile of an EAP to different classes then turn the various classes on and off...the EAP will fail to regenerate sometimes even though all it's classes should be visible. I just experimented with it and I can reproduce the disappearing behaviour. I even used a 3d only symbol to add a third layer of complexity. If one were using saved views, it would be easy to experience this frequently. It's as if the changes in class visibility aren't forcing a "regen" all the way down the tree of the EAP, but the render modes often will.
  23. What happens if you add a 2d component to them...aka make them hybrid?
  24. Try turning quartz off? Same for anti aliasing, 2d excelleration, and other visual settings that are available in your verion. Might also play with the 3d resolution as well. The intermitent nature sounds like a screen buffer type problem. You might also stop operations you are running in the background as these could effect the video buffer.
×
×
  • Create New...