Jump to content

TessF

Member
  • Posts

    39
  • Joined

  • Last visited

Everything posted by TessF

  1. If you are still looking, I would be interested.
  2. Hi all, I have just installed VW2024 and updated today for the latest. I used to be able to draw a complex closed shape or shapes, then offset them with the offset tool to the outside if I clicked outside all the shapes, or to the inside if I clicked inside any of the shapes. If any lines overlapped, it would refuse to do anything till I resolved that, which works. I knew to resolve the issue if nothing happened. Now I have so shapes that I could dearly like to offset 300mm outwards. I have cut the main shape Into smaller, simpler shapes, and this corrects it for most. I made sure there were no cutouts. This one shape persists in offsetting inwards. Obviously I can do workarounds, but this should not be necessary. Any ideas?
  3. Hi I recently installed VW2024, (on a Mac Studio) and needed to update. The menu in VW offers a "Check for updates", from which you can start the updater. However, it seems you have to quit the updater in order to quit VW so that the updater can run. This seems a bit silly. Either allow one to quit VW while the updater, opened from VW is updated, or tell the user to quit VW and redirect them to the updater in Applications folder. Thank you
  4. Bur where di you run the repair function FROM if V is closed?
  5. Hi dtheory, Thanks for the reply. It turned out to be a poor installation, so uninstalling and reinstalling solved it. I couldn't have run the "repair" because that requires VW to be open, and it wouldn't, but it is a useful thing to know about.
  6. This issue doesn't seem to have been quite addressed elsewhere. I have just acquired a Mac Studio, running Sonoma. I installed Vectorworks 2024. If I try to open the program, the opening screen comes up, it thinks for a bit, then closes right back down. I thought about installing updates 1 & 2, but you can only install those from Vectorworks, so I can't as it won't open. I checked storage, and I have a whopping 1.1TB used for System Data - trying to clear that now. I have about 650GB available - is this enough to run VW2024? Any ideas? Thanks System info: Mac Studio 2023, Chip: Apple M2 Max, Memory: 96GB, MacOS: Sonoma 14.0
  7. I have a workaround. - Copy and paste the Landscape area with all settings as you want them. - Reduce the copy to a landscape area that is smaller than the area you want to copy the info to. (I usually delete all but 3 vortices, and form those into a small triangle. Then I can copy that as many times as I like to do the below process, and it fits in all of the shapes easily. Usually) - Move the copy to be inclosed by the new area (which can be an existing landscape area or a polygon). All defining vortices and edges must be inside the new shape (because the shapes will add, spoiling your new shape.) - If adding to an existing landscape area, send it behind the new area. If adding to a polygon, it doesn't matter if it is in front or behind, it will take the characteristics and class of the landscape area. - Do an "Add surface" with both selected. - The resultant combo will have the characteristics of the edited landscape area, plants and all. A bit of a cumbersome workaround, but I find it beats editing each landscape area especially if you have a range of plants in it, each with their own spacing and percentages..
  8. Update: Restarting VW did it. A huge relief - I use it constantly. Thanks again for replies!
  9. Thanks for the reply! I will give that a try and report back. I am also restarting VW now that I have a moment.
  10. I upgraded my version of 2022 a day or two ago, which has been showing the Resource Manager just fine - until this morning. Now the resource manager has decided to go completely awol. How do I fix this? Not even sure how to delete and reinstate the RM. Thanks
  11. Hi, I am pretty anal about some thing in my drawings. One of those is the correct display of units. Metres should show as "m", NOT "M"! But there seems to be no way to control this. Some files it displays correctly others it doesn't. And there is no way to change it within a file. I found one of my existing files which displayed the unit correctly as m lower-case, created a scale bar, copy pasted into a file which was displaying it as M upper-case. It immediately converted to upper-case. Please can this be corrected? It has been bugging me for years, and it is a really small thing in terms of programming surely? The international standard for units was set for a reason - that is clarity and consistency across languages and cultures. I prefer to stick to this. Thank you Tess
  12. Actually I understand scale perfectly well. Yes, it is just a preset zoom, and whenever you draw a line defined as 1m long it will measure at 1m regardless of zoom or layer scale. But the object measurements in symbols change. If I draw as a 1m by 1m square, create symbol, then moved it to a new file, it might show as a 6x6m (by VW measurement - so not scale related). So the proportions are great, but if I measure the object in VW it gives me a new size. It did turn out to be a world/page issue - but it took me a while to work out how to convert a symbol from page definition to world definition. But thanks.
  13. Ok, so I answered my own question. But I still take exception. It was the world-base/page-base issue. However, when I changed the symbol to World-base, which gives it the correct size according to the dimensions defined in the symbol components, it will keep the symbol as shown, but change the component measurements. This should not happen - components should stay the dimensions they were created at. Converting from Page to World base should show the symbol at the correct dimensions, not at the current page dimensions. To change the actual size of a symbol, it is easy to convert it to group - it will maintain dimensions shown - then back to symbol with new dimensions. But converting from world to page or vice versa should not do that.
  14. When I great a new symbol, I am very careful to draw it to the scale I want. I have been finding that if I create a symbol it will be beautiful in creating, then when I insert it into the drawing, it appears completely out of scale - usually about 9 or 10 times too big or too small - and this is unpredictable. The Object info scaling is set to 'None". If I then try to edit the symbol in order to make it the right size, the measurements demurely tell me it is the correct size as is.????? Using VW2021, iMac.
  15. How does one choose whether the dimension is inside or outside? The arrows I can control, but in some files it will allow me to drag the digits inside or outside the curve, others it will limit me to the side of its choice. Very frustrating.
  16. Thanks. Maybe VW will build that function in sometime? *hint, hint* to any VW development people out there?
  17. That makes a new hatch from an existing hatch albeit with locally mapped characteristics. I would like something that will take a shape made of lines that I have drawn and convert it to a hatch. So if I manually draw lines in the shape of a tuft of grass, can I convert that into a hatch consisting of repeats of that tuft of grass? Is this an available function in VW, or does one have to use the VERY clunky hatch editor to create a completely newly designed hatch?
  18. How does one define the local hatch so that it will offer the "New hatch from locally mapped hatch" option? I am assuming this is a right-click function?
  19. It seems to have resolved. Not sure whether that was it or not but I haven't had the problem for a while. Thanks!
  20. I have things disappearing too. Imported a pdf onto a layer - the selection box remained visible, but the pdf was invisible/ Everything often disappears when the plan is rotated. This is getting frustrating beyond belief. What is up w 2020?
  21. How do you do this on Mac? That "BING!!!" is driving me batty. Well, battier.
  22. Thanks Pat - I am trying that and will report back. Do you know if I have to restart VW?
  23. I am finding that VW2020 is malfunctioning a lot on my system. Objects shown in one place, but when selected, the highlight is offset substantially - ie more than the size of the object it self. Objects disappear off the screen, but if I do a select-all, it shows me a highlight for that object. Several other little malfunctions occur from time to time, and the program shuts itself down way more often than any previous version I have worked with. I haven't worked with 2018, and very little with 2017 or 2019, but 2016 seemed reliable and solid. I like a lot of the functions in later versions though, and am not keen to go back. But the frequency with which I find 2020 crashes or malfunctions, requiring a restart (which usually fixes the malfunction) is becoming quite problematic, and reducing my productivity substantially. Anyone else find this? Is the re a fix? I am working on an iMac with High Sierra, 10.13.6, 40GB memory and over 2.75TB available on my hard drive. Should I be using a later version of MacOS? Doing something differently? UPDATE - other little problems: - objects that are there and visible on the design layer, marked as visible in the viewport, but stop showing up in the viewport - when trying to create a detail viewport: the system asks me to return to top/plan view before creating a detail viewport, when I am already in top/plan view, unrotated. - insistence that a viewport has more than one drawing label when there is only one Some of the issues seem to resolve when I un-rotate plan, for instance the selection offset. If I create a new viewport showing the same portion of the plan, some of the disappeared objects will show up again - in the new and the old viewports. At least until next time. Insert image from URL
×
×
  • Create New...