Jump to content

Benson Shaw

Member
  • Posts

    4,296
  • Joined

  • Last visited

Reputation

1,272 Spectacular

Personal Information

  • Occupation
    Public Artist
  • Homepage
    www.bensonshaw.com
  • Location
    United States

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Not clear what/how should retract. A 3d flyover could help understand. Or add an image of existing similar product. or post your file. Is your pdf drawing a top view of a sloping roof, eg the center rectangle represents a ridge or valley? Are these intended to slide left to right into a stack, each panel independent and on its own track? (Weather tight could be an interesting problem) or do these independently slide up/down (paper direction) toward that ridge/valley? forum wants to help, but needs some detail. -B
  2. Will give it a whirl Monday or Tuesday. Thanks for suggestion. -B
  3. Not sure what this means? Can you elaborate? Maybe a Mac/Windows difference. I download LAZ, LAS, Shp from the NOAA Data Access Viewer>Elevation/Lidar: https://coast.noaa.gov/dataviewer/#/lidar/search/ For those not familiar Process is to marquee around the area of interest, Add to cart, go to cart, choose the file type and other parameters. Verify and complete the "order" (free - no charge). Return to viewer if desired - the marquee is preserved for entire session - order another format of the same area. Receive the data usually only after a few minutes. 3 emails per order - Order confirm, Link to the download, Order summary. Files are zipped, but decompress to folders containing the requested shp, laz or other, plus their support files. Shapefile contours import to vwx and georef reliably. LAZ and LAS generate a Corrupt File error in vwx and do not import/open. XYZ files import, but I'm finding their georef does not match the contours. Still toying with that. One zip with a LAZ attached. Can anyone open it? -B wa2016_pslc_king_Job978313.zip
  4. Dunno. Might be a way. You are probably aware, but just in case, one can hold down the spacebar and click any tool in any palette to replace Pan as the active temporary tool. This feature reverts to Pan at next access. I also would prefer default to Flyover (or other user choice) rather than Pan. -B
  5. @Dave Donley Excellent! Currently, I am unable to open NOAA .laz files. They produce a Corrupt File error. I agree with @Jeff Prince - much appreciated whenever fix is implemented. Earlier would be even better. -B
  6. Also, if the view can be set to see all hidden snap points as if the cube is clear, start your 3d poly on a visible face or edge or other snap point, press/hold the b key (activates the xray mode which allows access to surfaces and snaps beyond the “front” surfaces) hover/acquire/click the next snap point, continue holding the b key and hover/acquire/the next point, etc. Might still require the Flyover as described above for some of the snaps. AWK now, so not tested, but I think this old school approach works. Draw separate polys on the separate faces, rotate view as needed each time. Cut the cube to clipboard, or move it, eg to another layer, Select all the segments, Compose, replace the cube. -B
  7. It’s a super handy feature, but . . . When using the Edit VP option for Add Reference Crop Object, remember that the option remains checked next time the Edit dialog is opened. As long as the option is enabled, a green rectangle will be added to the design layer EVERY time a design layer is accessed via the Edit Viewport dialog. Result can be a bunch rectangles from different VPs which may then be visible in other viewports and likely need deletion. Or, a stack of rectangles will accumulate from repeated access via same VP. Delete one, and the rest of the stack remains, which can seem like the delete failed. Suggest be aware, or better, open the dialog again and uncheck the option until needed again. -B
  8. Some thoughts about this: General - 1. The tool is completely undocumented - No topics in HELP. No cursor or tool hints. No descriptions in the tool prefs palette. 2. Engage the tool and draw a Bridge Line. Defaults to Cover Weight 30. Ungroup it to see the 3 components: An 180° arc with line weight controlled by the Attributes Palette - this is the visible bridge . . . in front of . . . A 160°arc with line weight 150, and pen color same as vectorworks background color - this "blanks out" the crossing at the line/object being bridged. A diameter line across the arc with line weight 30, color same as vwx background - This covers the bit of leader/source line under the bridge. 3. If Manual Cover pref is enabled, the two "cover" objects' line weights adjust proportionally, with the straight segment adopting the Manual value. The Gaps - 4. Due to Vectorworks rounded line ends, the background diameter line covers a bit of area past its ends and outside the arc, causing those "gaps" on either side of the bridge object. If the Manual setting is large, even the rounded ends of the background arc could cause some of the gap area. 5. The gaps will be accentuated by the vwx Zoom Line Thickness pref - toggle it to explore. Possible bug - 6. In my tests, the "Pick Up Class" works in design layers, but not in the SLVP Annotation space (eg other leader lines). Working in the Annotation space, the Bridge Line object always acquires the active class attribute. Or, maybe I'm missing something. -B
  9. OK, Glad this is being addressed by @Vlado and others. The LIDAR surveys and subsequent contour shapefiles, point cloud LAS/LAZ files and xyz data files for this region of the USA are collected and created by the Pacific Northwest Lidar Consortium. These files are hosted and available for download at the NOAA Data Viewer Portal website: https://coast.noaa.gov/dataviewer Perhaps some of the info below about the PNLC data could help sort this. And I present a workaround. PNLC "About" page: http://pugetsoundlidar.ess.washington.edu/About_PSLC.htm PNLC Tech Spec document - collection and data processing info (Projection, etc): http://pugetsoundlidar.ess.washington.edu/Technical_Specifications_withAppendices.pdf LAZ files from https://coast.noaa.gov/dataviewer imported into vwx2023 Same files, either new download or reused from local OS folders refuse to import into my vwx2024 - Corrupt data notice. Try with the attached zips of folders from NOAA. One is .shp with contours (imports fine). The other is LAZ. Here is a workaround for vwx2023: To correctly fit the point cloud data into the Vectorworks drawing: On the NOAA site, determine an Area of Interest and, in a series of requests, use the same capture rectangle (the website preserves it until you log out or redraw it) and receive via email the LAS, LAZ, Contours shp. May as well grab the XYZ, too while you are there: 0. Collect Contour and Point data from NOAA Data Viewer>Elevation. Click the "Return to Viewer" button after each Cart entry to use same Area of Interest outline for each request. https://coast.noaa.gov/dataviewer 1. Import the contour .shp to vwx This set of contours is used as the standard for the point cloud. Contours port in at proper scale and location whether imported to a prior georef vwx, or by letting the .shp determine the georef. Adjust the vwx internal and user origins to suit, and geolocate an image to verify that all is in order. 2. Import the LAZ or LAS. Uncheck the Center on Import option. Point Cloud will locate far from the contours. Group it and move it to, or near the contours via OIP. This makes both visible/selectable on screen. Separate layers is best, Show/Snap Others. 3. The scale will be wrong no matter the layer scale or which import scale. Make a ratio of the x value of the contour and point cloud groups. 4. Rescale the point cloud by the ratio of the groups. Point cloud will jump away to a new location. 5. Move the point cloud group near to the contour group (again). eg zero out the OIP location values of the Point Cloud group. 6. Lock the contour group so it cannot move. In any view except, use the 3d Align command to center the point cloud group on the contour group. 7. Verify that the point cloud is correct scale and location: Superimpose a DTM from the point cloud on a DTM made from the contours. They will be quite close. I made a video a couple in vwx v2023: https://www.dropbox.com/scl/fi/vd7x044kscx1t5l33hmz7/Vectorworks-GIS-2.mov?rlkey=kqejswd63jac1bjutlqjer4zg&dl=0 An alternative control is to use the ASCII XYZ file instead of the contour .shp file. Or, just use the XYZ data to make the DTM. As noted by others, these LAS and LAZ files import correctly to Q and Arc, so wondering if vwx needs an adjust? I think, in general, LAZ and LAZ files port in correctly??? Perhaps these PNLC files are uniquely problematic for vwx? Attached find a .shp and a .laz (GeoID 18) collected today and describing an area in the northwest Seattle, WA, USA. Contours import as expected. LAZ does not import into vwx2024. (My 2023 is expired, so not able to test) Also tried a LAZ in GeoID09. Did not import. -B wa2016_pslc_king_Job978312.zip wa2016_pslc_king_Job978313.zip
  10. Good idea, but no. My smart options: Basic Palette, Enabled Tool options, 3d Tools Palette, Standard views. -B
  11. This may be unrelated . . . M1 MBP. Onboard screen only. MacOS 13.6 Ventura. VWX 2024 3.1 During a recent work session, my cursor cues and snaps were working as expected, then suddenly snaps stopped working. I tried a few things short of relaunch/reboot: move/zoom, group/ungroup, create new objects, toggle layer view, toggle tilde key, more. Turns out the Object Snap somehow became disabled. I do not believe I moused onto the menu bar snap area. Is there a key combo for snaps? I may have used the tilde key, but in this case it was not stuck. Clicked the Object Snaps icon to enable, and all snaps worked as expected. In a subsequent work session, the tilde key DID stick, causing the snaps off until I tested the key. -B
  12. Stupid workaround (tip o’ the hat to islandmon). Model a base unit symbol containing a short length of profile extrude pierced by a single slot. For any specific length, DAP or MBP. Add Solids. One or both ends may need ungroup and Split to create a fraction of the base unit. Or just dupe enough to create a full “stick”, convert that to Generic Solid. Save to resource library as converts-to-group symbol. Split as needed after insertion. -B
  13. @InchSw3 Welcome to the forum! Trouble shooting is easier if you add a signature to your post showing vwx version and some basics about your hardware: Click your name at upper right of the Forum window, choose Account Settings>Signature. Several things to consider about 2d color areas in Viewports: Your VP screenshot shows a red border which means needs to update. Select the VP>Object info Palette (OIP)>Click the Update button. Button shows red text when VP is out of date. Do an Update after every change to VP parameters to implement the parameter change. VP OIP has option checkbox to Display Planar Objects, about middle of the VP OIP. Check the box and update the VP. Your 2d colors should appear. Sheet layer has a default render dpi of 72, which is fast for tests, but too jaggy for presentation. Edit the Sheet Layer to increase the dpi when the VP shows desired colors and other effects. 300, 600, or even 1200 might be needed, but can cause slow render. VP Render modes, near bottom of OIP: Test your VP changes in the Shaded mode, it's usually fastest. In the Design layer, each "Carpet" could be exported as an image, and then image used to create a full scale texture, and the texture applied to a blank 3d shape corresponding to the particular carpet. This would show the colors in 3d views, (incl Top), but not in Top/Plan. or Each areas of same color, eg all the brown shapes, within one carpet could be extruded as a single command, to a shallow or zero height. Do this for each color in a carpet, then Group the extrudes for that carpet. This approach also shows color only in 3d views, but not in Top/Plan. #2 seems best bet. #5&6 are lots of work and probably not worth it for this, but something to explore as you learn Vectorworks. Post back as needed. Others may have other approaches. -B
  14. Long shot, similar to georef idea, but Maybe the source file of the mislocated objects is the problem? Rather than the target file? Here is one scenario : If the source file Unified View>Ignore layers of different scale is disabled, or if the Unified View is disabled, a view of several layers could show apparently properly located objects, even with one layer at different scale. But it would be a deception, and difficult to achieve! The different layer would be zoomed and panned, and objects arranged so that the contained objects appear proper size and location relative each other, AND to objects in the other layers. This would be a fragile arrangement - ANY change to view (pan/zoom/3d view) in any of the layers would destroy the deception. Anyway, Paste in Place from that off scale layer would produce your anomaly if layers in target file are all same scale and Unified View is enabled. Whew! Reminds me of a painter I met who was attempting to paint various shades of “white” on the various planes of his sagging plaster/lath kitchen ceiling. Goal was to have it appear a uniform color at night when the center, twin bulb incandescent fixture was only light source in the room. Wasn’t going well. -B
  15. @bcd Found same results by placing the text objects on a sheet layer, then Export or Print or Publish the sheet layer page to desktop. I placed screenshots of the pdf text areas onto the vwx sheet layer. Same result with drop & crop the pdf text areas onto sheet layer. MacOS print to pdf shows the bolds. Export or Publish (with or without subsets) from vwx misses the bold. Screenshot of Skia in FontBook shows extensive suitcase of bolds, condensed, etc, so bolds should not be OS inventions. -B
×
×
  • Create New...