Jump to content

PVA - Admin

Vectorworks, Inc Employee
  • Posts

    12,808
  • Joined

  • Last visited

Everything posted by PVA - Admin

  1. You'd certainly think it could be dealt with in a better way than it currently is. Moving to 64bit will more mitigate these problems than actually solve them. The problem is that a lot of the time (80%-ish id say) when I get my hands on a file that is encountering out of memory errors, its usually some bizarre complication within certain kinds of geometry that is causing Vectorworks to NEED so much memory in the first place. This isn't to say "Oh users are just doing it wrong.", the large majority of the time they are doing everything as they should be. There are just a number of odd cases where changing your workflow could remove the problem entirely. (Creating sweeps when 3D Conversion Resolution is set to Very High for example, creates INSANELY complex objects that you would never suspect of causing major slowdowns and memory use, but fixing those solves the problem for the entire file.) Small things like this, which absolutely need to be fixed, make the memory limitations appear worse than they really are, and in themselves cause many of the memory leak symptoms users are seeing. This post sort of got out of hand, moral of the story: 1) 64bit will make many of these problems appear to have been resolved, but a few of the problems have another core issue that should be worked out as well. 2) Any time you get a file with Out Of Memory errors, we would like it sent to us so we can tear it apart until we find the culprit. I know it can be frustrating, but working through a file with tech support is the best way for us to identify specific issues and get them resolved. Chipping away at the much larger task of making Vectorworks as efficient and lean as possible.
  2. I'm not under any specific direction to do so really, but it seems like its extremely important that I do so. A lot of the time its easy to identify an issue and devise a workaround for it, then get focused on that and forget to submit the issue that was occurring in the first place. Hopefully getting these issues submitted and logged more thoroughly will get us away from the historical "Vectorworkaround" mentality, which -while very useful in the short term for getting projects finished quickly- isn't good for long-term development.
  3. To decrease the overall size of the previously huge installer, the libraries can now be downloaded and installed any time after the regular application has already been installed: http://kbase.vectorworks.net/questions/1170/Vectorworks+2014+Content+Library+Installation This has the added benefit of being able to add libraries later without having to do a full reinstall as was needed before.
  4. Does it appear in the layer lists for all viewports, or only some? If you create a new viewport from scratch, does it show in that viewports layer list as well?
  5. Looks like it should be up by the end of the day, now. Apologies for the delay!
  6. I've seen that on a few Windows machines from users. Normally it does not cause any problems, however I have had this help in some cases: http://kbase.vectorworks.net/questions/927/Run+As+Administrator
  7. For some reason it has yet to appear, it is still offering Vectorworks 2013. I'll check with them now and see what the delay is.
  8. Nothing involving OpenGL 4.1 specifically yet. We did just jump 1-2 slots up with our OpenGL engine, which is why the minimum requirements for graphics hardware now includes support for the OpenGL 2.1 standard. Having hardware that supports OpenGL 3.0 and above will be key in future versions, without question. (Especially once QuickTime goes and 64bit arrives.)
  9. Make sure to update your copy to VectorWorks 12.5.3: http://www.vectorworks.net/downloads/fundamentals/version12/12.5.3.php However if you have already done this, then the only thing I can recommend is running Vectorworks as an admin, it tends to resolve some memory issues for the older versions: http://kbase.vectorworks.net/questions/927/Run+As+Administrator
  10. On Windows I have used Rainmeter to good effect: http://lifehacker.com/5846468/the-best-system-monitor-for-windows
  11. I have seen this in some cases, but usually only from opening pre- Vectorworks 2008 files, not from rebuilt files as you are working with. What happens if you attempt to delete this invisible layer in a copy of your file?
  12. If you attempt to save a file, does it save properly, it is simply crashing when you close instead of closing normally?
  13. Please send that to tech@vectorworks.net with "ATTN Jim" for the subject please. We will take a look.
  14. Shouldn't be long now. QT is one of the major hurdles for going fully 64bit and I know they are actively working on getting off of it.
  15. Go ahead and resend to Tech@vectorworks.net with the subject "Attn Jim" and I'll have a look.
  16. If that is the case then the problem usually lies with the printer or with the printers configuration. Make sure to follow the steps here to create a custom page for that printer: http://kbase.vectorworks.net/questions/800/Page+Setup The default ones sometimes cause issues like you are experiencing. If problems continue, then the next steps would be checking for printer driver updates (uncommon for OS X) and/or updating printer firmware, steps for which you can normally get from the printer manufacturer.
  17. If you use the Move Page tool (found by clicking and holding on the Pan tool icon in the Basic palette) do you see that the page is aligned properly? If you export to PDF, do you see the same issue, or is it correct?
  18. Ray, would you be so kind as to send tech@vectorworks.net that .SHP file? ("ATTN: Jim" is fine for the subject) I am speaking with some others here to see if we can get something a little more automated worked out. The "Modify by Record Value" feature that was introduced a few versions back may hold the answer.
  19. I have not yet come across a way to do this, however I have been asked a number of times for a way to accomplish it. The closest I have seen is with Survey Input, but that pulls directly from a delimited text file to create contours at various elevations, not record data attached to the contours/polys themselves. If anyone comes across a method or script that does this, please let me know and I will add it to the kbase immediately. (Until then, i'll check with a few of the veterans here and see if they have come across something similar.)
  20. As to where you would find a symbol for this, I am not sure. But if you create one instance of the wave object, a Surface Array may let you create a larger wall of it rather easily compared to trying to duplicate along a number of curves to get a curved wall:
  21. At the very least, a "Do not show again." I would certainly agree with.
  22. As long as you have a version other than Fundamentals, you'll have the File > Import > Import PDF option. You may not see the option however if under Tools > Workspaces, you have Fundamentals/Standard selected, or another customized workspace.
  23. These were set up for maneuvering around with the Walkthrough tool activated. As to why Vectorworks doesn't have its own default configuration, I have no idea, my goal is simply to help users having problems with the device. Kevin: Were you able to specify a tool in Vectorworks to map those axes to successfully?
×
×
  • Create New...