Jump to content

IanH

Member
  • Posts

    795
  • Joined

  • Last visited

Everything posted by IanH

  1. Presumably if you render in one of the renderworks modes, it renders normally? If so, it definitely would point to graphics card issue. Don't think you ever said what graphics card it was.
  2. Most people ignore what their governments say so not sure why this is any different
  3. I've just tried this file in 2011 on a Vista PC and found nothing strange. It looks likely to be your configuration or hardware. If you Right Click on your desktop, select Personalise then Display Settings, your Video card details will be visible on the display settings box. There are other ways to get this info too. I still think first port of call should be checking that your graphics card is suitable to run Vectorworks then checking whether its drivers are up to date. Can a suggest asking a fellow student or member of the IT support team who is a bit more PC literate to help you out. Hopefully you will be sorted with someone spending 20 minutes hands on with your PC.
  4. Ok. Do you know what computer you are using and whether it is Mac or PC or what OS you are using? As well as posting the file as above, can you also post an image showing the issue.
  5. What graphics card are you using? Are your graphics drivers up to date? Best to give full system spec, OS etc as this is likely to be hardware/driver related.
  6. When you talk about rendering crushing performance, what exactly do you mean by rendering? Vectorworks has different render modes, but only OpenGL mode exhaustively uses the graphics card. All the other modes are CPU bound and to be honest, so more cores is good and even a relatively basic graphics card would suffice. However, the general performance of the UI interface of VW2012 will be influenced by graphics performance. So you will need something which will handle high resolution over two monitors and stable compatible drivers. I have not looked for a while, but there use to be a list of tested cards/drivers on the NNA website. Here you go
  7. Do you run Outlook? FaceTime interferes with outlook, causing outlook to keep thinking its received mail. I wonder if VW2013, Outlook and FaceTime are in conflict for the same resources.
  8. Best practice is to import a Dwg into its own file then reference that file into your main VW file. This prevents all of the detritus from the Dwg file such as classes etc from infecting your working file. Just a thought, but if you re-imported a fresh dwg into same Dwg base file, the class via abilities will persist from previous settings.
  9. I would like this to go one stage further. At present, its only a hierarchy of name, but I would really like it to be a true hierarchical class structure where sub classes can take their properties from its parent class. So where an object can have an attribute by class, the class can be a subclass which takes its attribute from its parent. So a change to attributes in a single class (when a parent) can affect both objects of the parent and objects of the subclass, unless overridden in the subclass or object, the latter as can be done now.
  10. I just updated and paid special note to this issue. Im using 2011. All looks fine to me including after Safari update.
  11. I'm interested in this too as I'm not convinced by usefulness of retina display in Mac, unlike iPad. I'm actually a registered Apple iOS developer so have to consider retina display in iOS devices. But it's fairly straight forward as from the programming perspective, a normal iOS device display and a retina display have exactly the same resolution. Where the double resolution of a retina display can be accessed is via iOS filling in the blanks, such as rescaling images at higher resolution to fit or generating smoother text or lines. The only control that developer has over this is to specify their own 2x higher resolution images which will be used instead of iOS rescaling an existing image - you postfix your image or icon filename with @2x and your app is retina aware with iOS automatically using the higher resolution (@2x) image instead of the lower resolution version. On an iPad this works well, as most items on screen are text, lines or images that do look better at 2x scaling factor. But *if* retina on OSX works the same, which I think it probably does by looking at display controls on a retina displayed Mac, I'm not convinced how useful it will be for an app such as Vectorworks. The problem is that as far as VW is concerned, the resolution of normal and retina display will remain the same. It doesn't suddenly have 2880x1800 addressable resolution to play with instead of 1440x900. It still thinks its 1440x900 and all retina display does is smooth images, icons and lines. If this is the case, then my 17" MBP with 1920x1200 on a larger display is better option for me. Even that resolution is too small for my ageing eyes and external monitor helps greatly. RIP 17" MBP, for me, perfect size. Not sure if performance trade off of non 2x modes will affect VW performance in new rMBP making the non native resolutions workable on the smaller 15" display. IMHO
  12. They are probably still recovering from their self congratulatory celebrations
  13. Actually, seems like 10.8.2 bought its own share of wake up issues.
  14. Apparently there is a fix for a wake from sleep crash that is affecting a number of apps but I see you are running 10.8.2 which I thought contained the fix so may not be the same issue.
  15. It's a test to make sure you read and understood the license and read me. You passed
  16. dont under estimate the complexity in doing this. I use to develop large computer systems for a living and one of my projects was to port our 32 bit app to 64 bit. Our app was similar age to VW but was a server/server based app that inherrintly would run across multiple processors, so the complexities of having to rewrite algorithms to be thread safe or multi processor aware was not on the list. It took about 18 months to port, test and more importantly optimise data structures for 64 bit. Without optimisation the app ran slower than 32 bit version. For a ground up rewrite expect much more time. I worked on the system for just over 10 years. In that time, two ground up rewrites came and went without seeing the light of day. A third made it to production only for it to be replaced within a year by a much simpler system that offered about 20% of the functionality. Our >25 year old system outlived and out performed the lot. The only reason why they replaced it was because being so old it was perceived that maintaining it was expensive and slow.
  17. A common misconception... 32 bit address limit is a process limitation, RAM is shared amongst whole system. Iirc that Renderworks is 64 bit and being a separate process would not affect VW. Also, to confuse things, you have 64 bit address and 64 bit data. 64 bit address means that you can have bigger things, 64 bit data means that you move bigger things around, which may be faster or slower depending on what you want to move and to where. So 64 bit architecture can mean either - but in my book means both.
  18. Look under advanced of sheet layer viewport.
  19. 2010 seems to work fine on my < 1 year old Mac with Lion. Surprised if Mountain Lion broke anything as from an application viewpoint, its a very minor update. Would be interested to know if you get offered free upgrade to 2013 if you buy 2010-2012 upgrade prior to 2013 release. A 2 year upgrade cycle was always cheaper than 2 one yearly upgrades even without free grace period upgrade. But with VSS, that anomaly may have changed.
  20. With VSS now around, is there any change to the grace period offering free upgrade to 2013 on all 2012 products purchased now, including upgrades? Its always been a cheap way to keep up to date in the past, buying one version upgrade during grace period and getting second version upgrade for free. Not convinced that VW will have moved on enough from 2011 to warrant an upgrade. Sounds like 2012 was a retrograde step and glad I skipped that one. Nothing that I have seen of 2013 jumps out as a killer feature, unlike some others in the past.
  21. First create a problem then market a solution to fix it... Many a major company/product is founded on this strategy.
  22. With the boards recent spam attack resulting in a highly disjointed chronology of posts, just wanted to check that OP got the info they were looking for.
  23. One for the wish list: different line segments of poly line having different pen attributes - or at least dash styles.
×
×
  • Create New...