Jump to content

oli w

  • Posts

  • Joined

  • Last visited

Everything posted by oli w

  1. I have an issue where I import a dwg and it ignores all of the sheets and only imports the design layer. I created the dwg's myself in vectorworks export, and colleagues can reimport the same dwg's and all the sheet layers appear, so the problem is not with the file, but something in my copy of vectorworks. I can only assume that at some point I've changed a setting somewhere, but I can't for the life of me think what it could be? Any ideas? I'm running architect 2019
  2. We are having an issue where a title block will randomly disappear when printing a drawing - the drawing is showing properly on vectorworks, but when sent to the printer comes out without the title block. It's happening in a fashion that doesn't suggest a pattern, and sometimes the same drawing will print the title block, sometimes it wont. Has anyone come across this issue? Thanks
  3. I have an issue, which I've only had in 2017, where when you go into a viewport, it goes to a completely different part of the sheet layer than where the actual items shown in the viewport are located. This ends up wasting quite a lot of time just moving around the design layer hunting for what you need. Has anyone else got this issue and / or a solution?
  4. I always have my sheet layer items on none for the same reason. However things in a company always slip through the net. I'm just not sure what the purpose of this function is actually for - it seems counter productive to me as there's no reason I would want my sheet layer classes to match my viewport classes,
  5. If you don't press 'return to viewport' when on the design layer, and go straight to the sheet layer tab and choose a sheet, you end up with all the classes that were turned off on the design layer, being turned off on the sheet too. Why is this even a thing? I can see no advantage to this.
  6. I am also suffering from the problem. Brand new 4.2 GHz Intel Core i7 retina Imac, and it feels swamped, very jittery - if I select a number of items, on larger files it can take a few seconds to acknowledge the selection, and sometimes only tells me in object info, as opposed to visually updating with a box. This is on 2017, whereas 2016 is fine. It's also fine on older imacs in the office, which leads me to suspect issues related specifically to retina imacs.
  7. Is there a way to stop accidental groups of singular objects being created i.e. take a rectangle, and group it, or worse, a group of objects grouped repeatedly inside themselves. The amount of times I open a group to find someone has clearly pressed cmd G multiple times and have to ungroup repeatedly to get to the actual object/s inside the group, is infuriating!
  8. As per the title, virtually every time I open 2016 the 'Vectorworks 2017 is now available' box appears, which you have to close before you can use the program. How do you stop this?
  9. Hi Jim, Nothing worked - the 'solution' was to install service pack 4.
  10. Yes, it looks like the only way round this is recreating the viewport. It seems turning the setting off and on has no effect on the viewports with the issue.
  11. Hi, We have an issue on our copies of VW 2016 fundamentals, where one copy will allow different VW files to unstack by unticking the palette docking option, but on another copy the program says 'This function is unavailable in this version of vectorworks.' Both licences are fundamentals, so I am baffled as to how there can be a difference between the two copies.
  12. Hi, In VW 2016, when I click into the viewport, it goes to the centre of the page, rather than directly to the object I am looking at. This issue seems to happen on totally random viewports, even within the same document. Is there a new setting I'm not seeing?
  13. Hi, I'm creating an object (high level canopy) that needs to be dotted on the plan viewport, but solid on the ceiling plan viewport. Is there an easier way or doing this without simply duplicating the item and putting it on different classes?
  14. "The shift key no longer constrains to 90 degree increments for a start, but i keep finding lines i though i'd drawn straight are at random angles like 89.03 instead of 90, or i try to move / duplicate something in a straight line and when i let go of the mouse button it is no longer aligned, especially if you are not zoomed right in close, or the cursor appears to be snapping to a point but when you look closely it isn't." This is still a major problem for me Jim, incredibly frustrating trying to draw accurately currently. When is it likely to be solved?
  15. It's literally from the word go. Bigger files make it a bit worse but even brand new files give lag.
  16. NVIDIA GeForce GTX 775M 2048 MB graphics Jim
  17. Cheers Jim 1) That seems to have made a small improvement, although it's still definitely not as quick as the old version - I've got them open side by side and the difference is more than just noticeable. 2) Interesting, I can understand why this has been done, but I'm not sure it helps for general day to day use where you want to quickly change between line styles, in particular dashed lines. 3) Heres a screenshot of what happens - the vertical line you see is part of a rectangle underneath the line I'm drawing, making it a lot easier to see the polyline. http://imageshack.com/a/img836/8743/nucy.png 4)What I mean is when duplicating an exact distance e.g. 100mm repeatedly, normally I would go cmd D-cmd M enter, repeatedly. This is no longer possible, by the looks of things 5) I'll look into the reasons behind that, I assume we must have a customised worksapce.
  18. Our office has just upgraded to 2014, from 2011, and there's a number of small, but darn irritating changes which seem to be generally a bizzare move backwards: 1. Lag - I assume this is a hardware issue, but we are running 3.4Ghz i5 imacs, and even on brand new drawings the lag is significant and frustrating 2. Dashed line menu - used to be one, concise menu for changing line thickness and dashes in one, now 2 separate menus - why? 3. When drawing a polyline, or any line for that matter, when you used to zoom in and out everything else would fade/grey into the background, so on a long line you could see where the line you were drawing was, making it easy to join long polylines together - no longer does this 4. Duplicate - When using the command duplicate-move, you could hold down cmd between commands, so, for example, when duplicate-moving a number of times you could quickly repeat the command - now have to release cmd to press enter. 5. Polyline/polygon tab - defaulted now on polygon, which, personally, I never use, I virtually always use polyline, so this is an extra step to get to the tool I realise these are small issues, but over the course of the day, they add up to extra stress and a lot of time lost, and for the life of me I can't understand why they've made these changes. Does anybody know a) reasons b) how to get back any of this functionality?
  19. Thanks Dave, I forgot about this thread because I used the original file, and just increased the size 100 times, that seemed to produce a pretty good effect, but your file is an improvement again so Ill be using that in the future.
  20. Hi, I updated to sp3 last night, and the problem appears to have stopped....
  21. another point-the exact same thing renders fine in a earlier save from today, but then if i put the exact same object into the latest file, it comes out crazy. twice today I've gone back to an earlier file, had it work for a while, then at some point it'll stop working again. Im certain this isn't a memory issue, as the total file is around 120mb, and I have 12gb ram, and at no point is it getting even close to half filling that capacity
  22. The one with texture is opengl, the other is fqrw...
  23. Yeah it works in everything but renderworks...opengl is fine, bitmap etc fine...how do I attach images?Thanks
  • Create New...