Jump to content

AN Design

Member
  • Posts

    74
  • Joined

  • Last visited

Everything posted by AN Design

  1. I noticed at least a 40% increase in render speed since the update see my under hood below
  2. Automatic Wall Joins are turned off. Getting additional odd behavior on walls from files that were orig. created in VW2009 and opened w/ version 2010
  3. After joining all exterior Walls they randomly un-join I go back and rejoin (all are L joints) and then another corner will un-join. This is now happening on all walls drawn. Random unjoin. Fix a joint and another wall will unjoin. Quit VW and restart and it begins the same unjoin again randomly Mac OSX 10.6.1 w/ VW 2010 Designer w/ renderworks
  4. I can assist you further, and possibly save you a bunch of time w/ a 15 to 30 min conversation. Just give me a call 910-215-9901 I'll be in the office till 8PM eastern I have gotten numerous people off to a quick start if you so require Glad to have you on board !
  5. Don't get to edgy about the Mac or Apple I began in 1987 w/ Blueprint 2.0 Later it became Minicad and thereafter Vectorworks It was around 1995 I believe that NNA introduced VW for Windows Just be thankful that NNA even supports the PC It's roots began on the Mac
  6. Forgot to mention that I also have VW 2008 on both systems as well. VW2008 does not have the issue w/ DWG files w/ snow leopard, but opening the file into 2009 will crash it most of the time. That is why I reboot.
  7. Have 4 1 TB drives on my mac pro 2x2.26 QuadCore Xeon w/ 16GB Ram Drives 1&2 are mirrored w/OSX 10.5.8 running VW2009 Designer w/Renderworks Drives 3&4 are Mirrored w/OSX 10.6 running VW2009 Designer w/ Renderworks I use AAsync to keep my projects up to date and in sync on the drives. I boot up in Leopard 10.5.8 in order to import a DWG file into VW and save that file. I then Reboot under Snow Leopard 10.6 ,VW is running 98% fine, but much faster, than on the leopard system, a few hiccups occasionally but snappy. I only reboot now when I need to bring in a DWG file The 10.6 is so much faster when I render and I rarely get the beach ball. VW also runs much faster on my MacBook Air which is now only OSX10.6 This is my road machine and I see no need to take it back to 10.5.8 If you have a second bay, extra internal drives are cheap. Get one. It also can be a life saver if your primary drive has issues. Just be sure to Sync your Files on both drives w/ most recent version. And have a external drive for total backups.
  8. Does anyone know as of yet if VW2009 will be compatible w/ new operating system soon to be released ?
  9. I am know having out of memory problems since installing SP3 on VW 2009 Mac OS 10.5.6 When rendering in Shaded Polygon, stops and indicates out of memory No other apps running ( I've got 16 GB of memory in this system) Mac 8 core Mac Pro Processor Name: Quad-Core Intel Xeon ?Nehalem? Processor Speed: 2-2.26 GHz Number Of Processors: 2 Total Number Of Cores: 8 L2 Cache (per core): 256 KB L3 Cache (per processor): 8 MB Memory: 16 GB ATI Radeon HD 4870 PCIe Lane Width: x16 VRAM (Total): 512 MB Using 30" Apple Cinema Display 2 - 1 TB Hardrives Don't understand the problem
  10. Attached Front Elevation after SP3 Update Attached Rear Elevation before SP3 update Settings the same in Open GL as well as Preferences (VW & Document) drawings to follow
  11. Lee job Rear Model View in Open GL no Lights GL engine working well Can't wait to add lighting to see the results Check it out David Nichols
  12. Thanks Pete Will play w/ and see the results I did the same with some Brick Pictures I took and adjusted in Photoshop before bringing into VW How do you create Brick Soldier's & Header Blocks primarily for Arch & Round Tops for Rendering ?
  13. I generate Elevations similar to Pete, (NC Guys are Detail oriented) 3 Viewports per elevation, bottom layer Model Quality Renderworks w/ Lights, Next Layer Hidden Line Sketch Careful, Top Layer Annotations You have too trial & error numerous times in order to get the correct output, but once you understand your color options & line weights, you begin to feel what the output will look like. David Nichols Anderson Nichols Design, Pinehurst, NC
  14. VW2009 w/SP1 When creating joists from Polygon (Simple 75'x 45') Creates rafters as opposed to Beam which I selected, after completed it disappears. after 5 more attempts it worked (spinning beach ball & crash each time) Just wanted to create simple I joists (no longer an option, I joist was available in 2008) Got a I joist profile from Framing members , selected I-Joist Profile from custom, crashed again. Worked fine before SP1 update, how do I get the older plug in back. Once this project is finished, will again go back too VW2008. The bugs and problems w/ 2009 are to numerous to get into w/ this post. Any solutions for the Framing Tool ?
  15. Don't understand why in the new 2009 when you want to re-position a window or a door in a wall, the old Objet Info said Position, and you set it relative to wall choices, now in 2009 object info now say's Set Position which brings up a new Tool for setting. How do I get the old Position relative to wall placement back ?
  16. System RAM vs MMIO: the "where is my 4GB?" problem If you're feeling cramped within 4GB, hold on tight because things are about to get worse. The first issue is a historical limitation in the Intel x86 architecture, related to "Memory Mapped I/O." Essentially, all of the device memory used by video cards or any other expansion cards is mapped on top of the 4GB addresses used by the system's RAM. This didn't used to be a problem before anyone wanted to actually use the entire 4GB address space for system RAM. Note that this doesn't mean that MMIO "eats up" your RAM, it's just that the hardware maps that device-related memory over the top of physical memory, leaving fewer addresses available to the operating system to use for its system RAM. This problem is tied to 32-bit chipsets, which are independent from the CPU. There are 64-bit PCs with 32-bit chipsets. For example, Apple's 64-bit Core 2 Duo laptops prior to the second half of 2007 all used 32-bit addressing. That means that while they can execute 64-bit code and handle 64-bit virtual memory, they still can't address more than 4GB of physical RAM, minus roughly 0.75 GB of MMIO, for a grant total of 3.2GB usable RAM. If you install a full 4GB, the portion in conflict with the MMIO will simply not be used. For PC users installing a high end video card with 1GB of VRAM, the additional MMIO becomes an even greater problem: their usable system RAM shrinks by down to around 2.3GB. The great PC RAM swindle With Intel's "Santa Rosa" platform, Apple's Core 2 Duo machines gained chipset support to internally handle 8GB of address space. This allows Santa Rosa Macs to shove MMIO up into the high end of the space and reclaim all of the addresses below the 4GB mark, making the full amount available to the system. No version of 32-bit Windows supports this, and conversely, there is no 32-bit version of Mac OS X Leopard, so the "where is my full 4GB?" issue is now a Windows-only problem going forward. Prior to using the Santa Rosa platform, Apple sold its laptops as only supporting a maximum of 3GB RAM because of this. However, many Original Equipment Manufacturer PC assemblers represent their machines as supporting 4GB of RAM even though the operating system can't actually make any use of a big chunk of it. With hardware that only supports 32-bit addressing, no operating system can make use of the full 4GB. However, even with Santa Rosa-style hardware that can make use of the full 4GB, the mainstream 32-bit Windows Vista still won't use more than 3.2GB or less because it can't remap MMIO. One developer we consulted about the issue noted, "consumers are being scammed by [PC] OEMs on a large scale. OEMs will encourage customers to upgrade a 2GB machine to 4GB, even though the usable RAM might be limited to 2.3GB. This is especially a problem on high-end gaming machines that have huge graphics cards as well as lots of RAM." "Microsoft even changed the way the OS reports the amount of RAM available; rumor is, due to pressure from OEMs," the developer told us. "In Vista and prior, it reported usable RAM, while in SP1 they changed it to report installed RAM ignoring the fact that much of the RAM was unusable due to overlap with video memory." And so many PC users are installing 4GB of RAM in their PCs and thinking that it is being used by the system, when in fact it is no more beneficial than if the RAM were simply poked halfway into the CD slot. For example, Dell's top of the line $5799 Alienware gamer PC comes standard with a 1GB video card, 2GB of RAM, and 32-bit Windows Home Premium. That means the system can only possibly use 2.3GB of RAM, but Dell "recommends" users spend $250 (or $8 per month with financing) to buy a 4GB upgrade (below) that will offer them little more than bragging rights, as the 1GB video card and the roughly 750MB of other MMIO will make the extra 2GB unusable. Dell says "Upgrading your memory allows you to take full advantage of system capabilities as well as increasing system efficiency," but that's simply not true on this page.
  17. Lets Just Hope, That they don't leave the Mac behind, for it was the only platform they supported in the beginning. Windows version didn't come about till mid 90's. User since BluePrint 2.0 around 1987 I think, need to look at the old floppies to verify.
  18. How do you import .Iwa files into VW 2008. The Renderworks engine is Lightworks based and they should be compatable.
  19. After installing SP02 and following your instructions for Quick View, it does not work on Leopard, or I can't get it to work. Any Suggestions ? MacPro Quad core 2.66, 8G Ram 2 TB HD on OSX 10.5.1 & VWDS 2008 What do you suggest !
  20. This tool is about worthless. Have been using this product since Blueprint 2.0. Tool constantly has error script, then VW12 Crashes. Need to Load the tool from VW11.5. Tool is costing me Time & Money. See if you can't fix the problem. Rather than trying to create more tools, Try fixing the ones you have. David Nichols
  21. VW 12 Issue Followed the quicktime tutorial in setting up a custom tiltle block. Everything works great except it will not accept (the scale). I can type anything in this block and nothing changes. Reverted back to standard drawing borders and everthing is accepted. What gives David [ 11-07-2005, 07:54 PM: Message edited by: andesign ]
  22. Modifying a Roof errors, If you go to edit roof, Paste your clipping object, hold shift down to select the Roof Surface, You have to drag a Marq over the roof area (you just clicked the roof in version 11.0.1) then choose Clip surface, you get an error message saying illegal object selected.Then exit Group, the area has been clipped. In 11.0.1 You just had to shift click the roof plane you were clipping, no error message in 11.0.1. Additionally, very very slow w/ text and Dimensions. Reverted back to 11.0.1 much faster and more stable.
  23. Since upgrading to 11.5 from 11.1.5 When 11.5 is up and running it not only is slow, but when, open my other applications slow down as well. Mac OS 10.3.8 G5 Dual 2.0 8G Ram w/ 30" Apple Display. Reverted back to 11.1.5 and everthing returned to the faster speed I had grown accustomed too. Still getting error message in 11.5 when editing a roof w/ clip command and selecting a roof plane can only be done by dragging the marqu , when using 11.1.5 tis does not occur. Will discontinue using 11.5 until this speed issue is hopefully resolved.
×
×
  • Create New...