Jump to content

Benson Shaw

Member
  • Posts

    4,285
  • Joined

  • Last visited

Reputation

1,263 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. 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
  2. @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
  3. 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
  4. @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
  5. No posts in a while. Finally thinking of upgrade from MacOS Ventura to MacOS 14.3.1 Sonoma. Are we fully compatible now for vwx2024? Thanks -B
  6. I guess it depends on where the level line is (roof face axis). I put it on the gutter line. -B RoofPuzzleVideo(1).mov
  7. @bob cleaver TOTALLY not short shrift, and you are totally welcome. The forum’s a pleasure. I’m learning all the time and giving back when possible. Now, if we could just get this command added to the fix list . . . -B
  8. Function definitely does not work! If Pad from Grade Limits worked as designed it would: 1. Create uniform grading at designated slope from pad to grade limits. 2. Create a level pad shaped by intersection with slope faces. 3. Place that pad at elevation of balanced cut/fill. It accomplishes 1 and 2, but completely misses 3. Hence the workaround. Workaround is time consuming! True, but other methods to accomplish 1,2,3 would also be time consuming. If working at mm precision for pad elevation, I think fewer than 10 attempts should resolve it . . . Workaround is imprecise. mmmm I think it is as precise as patience allows. Seems the slopes are correct as long as the value is keyed in at each attempt. The pad elevation and therefore Cut/fill balance are limited by construction precision, rather than vwx decimal precision. A millimeter deeper cut or 1deg steeper slope might flip the fill from import to export. Balance point is somewhere between at about 8 decimal points. Remove from program? Interesting idea. Or maybe disable it but show grayed out text in the menu with a “We’re working on it” notice? Add a date stamp or count down so we see interval to the fix. Also, just curious, @ landscape architects, is this a must have feature? use it on every project? Is there a common method without the command? Did it work in some distant, earlier versions? I have not seen earlier discussions here. -B
  9. @aage.langedrag, @Katarina Ollikainen, et al. Problems with the Create Planar Pad from Grade Limits are discussed in this previous thread: https://forum.vectorworks.net/index.php?/topic/111998-creating-a-planar-pad-from-grade-limits-but-planar-pads-without-elevation/ But it went to wider issues, so starting new here. The big fail is that the command creates a pad at seemingly random elevation, instead of at a z value that would balance the cut/fill inside the Grade Limits. OK, I even suggested moving the DTM up/down to the pad elevation and recreate pads repeatedly to find balanced cut/fill then move entire assembly back to original z. Sorta works but fraught. I find now that a different command controls the pad elevation in the Pad from Grade Limits: Create Objects from Shapes > Site Modifier > Pad > set the elevation. Delete that new pad. Create Pad from Grade Limits will now match that elevation. Perhaps others have discovered this already, but offering here for the brain trust to pick at. Might help with fixing the bug. Video and file attached. Note: Pad via Objects from Shapes defaults to elevation 0, which explains why many tests of the Pad from Grade Limits creates a pad at z = 0. -B Pad from Grade Limits(2).mov Pad from Grade.vwx
  10. Bump Does anyone know what is reported by the volume calcs of a Pad inside a Grade Limits? -B
  11. @MGuilfoile That file name looks strange - like it's a repeat paste? Is Loft File 02.vwxLoft File 02.vwx correct file name? The forum definitely accepts vwx files, pretty much any version and from any OS. A file used to be refused if over a size threshold, but haven't seen any limit lately. Try again if you have the patience - drag/drop the file (the icon of the file) into that area for attachments just below the text area of each post. -B
  12. Maybe a ripple somewhere in the surface? Shelling greater than 4 inches creates a self intersecting volume, causing calculation fail? Sometimes a workaround is to shell to a value that DOES work, then, while the shell is selected, adjust the value in OIP (as opposed to starting a new shell at a higher value). 4 to 40 seems a stretch, but might work. Post a file! -B
  13. Aaargh! My opinion based rant: This concept trivializes the powerful and multi use Class and Layer components of Vectorworks. I suspect this is some legacy of early days in Vectorworks to help those transitioning from other software, confronting for first time ever “something” beyond class. Anyway, it is an assertion, merely rhetoric with some truth or usefulness to it, but very limited in outlook. I think as training and core concept knowledge it is at best a tip for someone struggling. It is not even close to worthy of Core Concept mastery status nor inclusion it the cert tests. Individual designers and offices will adapt the Vectorworks Layer and Class system to meet their individual workflows and efficiencies, which may be quite successful even though different from the expected dogma. Layers and Classes are two of several amazing sorting mechanisms in Vectorworks. One could also include Data Vis, Saved Views, Referenced files, Resource Manager items, various Styles, and more. All can be used in combination to sort, isolate, organize or otherwise aid in design, presentation, build, maintenance, archiving of our work. Layers and Classes are remarkable, flexible, and not at all limited to What or Where! One can use layers OR classes to sort for What, Where, When (Project phases? Design iterations?). Some would even include How (CNC paths?) or Who/Why (Specs? Notes?). And, about another question based on an assertion, with a dogmatic answer: Which is the MOST IMPORTANT palette? *(Spoiler Alert, can you guess? - the test writers and curators want answer spelled backwards below) My answer - The Palette I am currently working with. All the others are non important at this moment. OK. End of Rant. Knock me down if you like. -B *(PIO)
  14. Site model. Single Grade Limits. Single Planar Pad inside the Grade Limits. Elevation of Pad causes both Cut and Fill. Cut/Fill values in OIP are same if Site Model is selected or if Grade Limits is selected. This makes sense. Cut/Fill values if Pad selected are not same as SM or GL values. What volumes are reported if Pad is selected? -B
  15. Regarding original topic about the Pad from Grade Limits: I call this the Move the Mountain to Mohamed Workaround. Problem - Planar Pad from Grade Limits command places pad at z=0 instead of at z=Value where desired slope produces cut/fill balance. Solution - Move the DTM and all extant site mods down (usually) by that z Value, run the command, make adjustments to balance the cut/fill, return DTM and all its modifiers up to original z. Needed: 3d Marker at an Anchor point, eg one end of a 3d Poly at one corner of the DTM. Estimate of distance to move the DTM down. Midway between Grade Limits (GL) high and low points. This was only OK. Better estimate uses Center of Mass of the patch of terrain mesh enclosed by the GL. To find this, duplicate the DTM to a blank layer. Crop it to outline of the GL, Ungroup. Delete components except the mesh. Apply Model>Volumetric properties. Note the Center of Mass z value. This is the estimate. Delete the little patch of mesh. Value of desired slope. Process: Place the Marker at Anchor point. Move the DTM (and Site Mods) straight down by estimate value. Use Move 3d for this. Select the GL and run the command. Update the DTM. Update the Cut/Fill calculation. Note the cut/fill values. Close enough? Select and move everything back up to the anchor point via Move By Points. Update again. Not close? A choice: 1. Adjust the pad up or down, eg 1mm increments. Update each time. Repeat until balance achieved. This also changes the slope (maybe unnoticeable), but easy because DTM and Calc updates both available in Pad OIP. 2. Delete the Pad. Adjust the DTM up/down in increments. Update DTM. Select the GL. Run the command. Update DTM and Calcs. Repeat as needed. Slope refreshes to desired value each time. Move the assembly up to Anchor Point via Move by Points. Repeat this process for each Grade Limits on the DTM. Might be a good idea to move completed Pads to a storage layer that does NOT affect the DTM, so they do not confuse current work. Return all Pads (or Duplicates) to effective layer when all are adjusted and the DTM is at the original Anchor position. Update the DTM. -B
×
×
  • Create New...