Benson Shaw

Or “sticky” sorting by user? Vwx provides the complete library containIng all the objects in both systems, and the user can apply a curation or ordering via user editable sub folder. Maybe these folders even could load into upgrades as a pref or similar to workspace preservation. Or is that thought just a saved search like the Mac OS smart folder? Another way forward might be a Cursor switch floats into view when the complete library loads. Click for metric Related: however it is implemented, this property should also apply to any of the smart tools with mixed units. eg the various fasteners, steel profiles, gears & springs, etc. -B

Something to try: Surround that area of the site, or the entire site with a Grade Limits modifier no guarantees, but sometimes can fix this type of problem. -B

@angelojoseph, et al - v2020 Paver Madness file attached here: -B Paver Madness v2020.vwx

No the bit map is static. It will not have any vectors. I just wondered if that image to the left was the vectors and not the bitmap. A vector based pdf can be ungrouped and will usually have the 3 components: bitmap, page rectangle and a group with the vectors. The page rectangle and bitmap can be deleted unless needed for some other use. Hope your trace works out. -B

@Landartma um wait. maybe you have it? my experience is that a raster pdf does not ungroup to reveal components. A vector pdf ungroups to reveal a stack of several components, usually 3: a bitmap on top, a white rectangle (this is the paper/page and border) and, usually, at the bottom of the stack, another group containing (groups of) the vector geometry. in your image, you show the rectangle, and to the left, a “page“ of line work and text. is that “page” a group? or is that the bitmap? if it’s a group, ungroup it to access the vectors. if that is the bitmap, then resort to tracing or zamzar or other conversion technique. note that the pdf vectors are close, but not necessarily accurately placed or sized. eg circles may end up faceted, walls may have weird widths, text is lines rather than fonts, etc. hth -B

@angelojoseph i will try to find tgat file and reload! might take a bit. im away from the main cpu right now

Another approach, similar to the design layer view port (DLVP) method described above, is to draw the building on ordinal grid and make a symbol of it. Place an instance of the symbol on the drawing on its own layer. Rotate and adjust xyz as needed to align on the survey layer. Edit the building via the symbol definition in the resource manager. It will appear for edits in the ordinal position. The instance on the drawing will retain rotation and xyz position and will display the edits. Moving or rotating the instance on the drawing will not affect the symbol definition or its ordinal orientation in the symbol edit pane. Editing the symbol instance (dbl click) produces a similar edit pane with option to display/snap the objects surrounding the symbol instance. View changes, eg top plan, in this edit pane do not change the ordinal orientation of the symbol definition. As noted by others above, the survey and building (symbol or not) can be in separate files, (or at least on separate layers). Reference one file (or layer) into the other via DLVP. This is a great approach. Doesn't really matter which is referenced. I prefer keeping the terrain/survey in correct orientation and referencing the building. The DLVP reference needs to be updated to display edits made to its source file. As noted by @cberg, the rotate view feature is available. This affects the display rather than actually changing the geometry. Seems that many users do not like or trust the feature, but it exists for this situation. As usual in VWX, lots of ways forward! -B

@Andy Broomell dims in symbol name can work. I use it often. But as @Bruce Kieffer notes it's potentially a lot of work and can lead to some future confusion or errors, especially if a bunch of existing symbols need to be tracked down and renamed in old files. This naming concept is similar to classing in that it requires management with conventions/standards and patience. just riffing here, not critical of other’s comments - eg similar sized doors 12x24x.75 and 24x12x.75. which is vertical? or should thickness be first? I think symbol dims are good idea in the OIP, but a data tag could solve other problems. The name or data tag might also indicate left/right hinge, hinge type, knob style, finish, color, edge condition, shipping weight, . . . the symbol name could get very long and full of abbreviations. everything needs to display in an order that matches up logically with other symbols in the library. Symbol names do not auto update if the symbol dims or other details are changed. And, a personal peeve, the symbol name in the OIP is poorly placed (3rd item down?) and hard to read compared to OIP dimension fields. Should be at top and bold, perhaps as an editable field? -B

@unearthed - Agree! QGIS is great software and community. I use occasionally, and send em donations, too. Constant upgrades. Very good in app HELP. There are a ton of granular topic videos and text discussions accessible via internet search - eg search QGIS Clipping Layer. -B

@Kevin K - Soo, couple of things: 1. Wow! Really cool design and fantastic rendering. Is that RW? or Lumion? or? 2. Great that you worked through this and discovered features and faults! 3. This is total workaround city, but regarding a vertical door at edge of roof face. Would it work to place the drawing in TopPlan and cut a notch in the roof face (remove the bottom edge), then create the door wall and triangular cheek walls? Needs a bit of math or 3d guide objects so that the roof cut matches the desired height for the door wall. This at least keeps all the vwx smart objects without resorting to solid subtractions. My problems with this include that I don't work with walls that much, and don't like working with vwx mitred wall joins at those intersections of triangle to flat topped walls, so unjoin and adjust lengths, remove mitres, or draw new unjoined or . . . Plus how to represent the intersection at top of door wall with the sloped roof wall. Bury it in the roof? Stop at the lower edge of roof opening and model a filler soffit? Or? Framing choices ill defined. -B

also control over the opacity of greyed objects, classes, layers, including grey objects outside of edit spaces. often i find the grey is too transparent. lowest function the control could be global, perhaps a document pref - rather than a vwx pref which could cause unexpected render results when inactive files are opened later! or wishing for higher functionality, make greying more granular via render options (OGL and RW), VP layer/class overrides, dialog or OIP controls, etc depending on context. and, wishing, wishing - - control of the color. doesn't always have to be grey, does it? -B

just throwing this in here. Mesh objects, eg pyramids, have two edit methods: Reshape tool ( double click) - this gives access to the individual 3d polys that comprise the mesh. eg move a vertex and it disconnects that vertex and associated edges from surrounding polys. requires snap the other vertices to new location to complete the edit - lotta work! Reshape tool also facilitates adding new edges to a mesh. Select tool - drag a marquee around the vertex to move. this essentially selects ALL the vertices stacked at that location. drag to new location. all the associated faces stay connected and adjust/move with the selection. this is the best method for moving pyramid points. -B

@Robyn SA welcome to the forum! here is a rough idea. may need some refining: 1. Solid subtraction can work, but NURBS loft will be required. 2. Model the plain bottle, slice it in half to create a front and back side. probably best to store them on separate layers. 3. in front view screen plane draw 3 cutting surfaces, probably extrudes of 3 rounded “V” shapes: the low swoop, the high swoop and a middle one which represents the deepest intrusion. 4. duplicate the bottle front half and Solid Intersect it with the 3 surfaces. or use the Project tool with the. sourcecurves instrad of the surfaces. result either way is 3 NURBS Curves. 5. low and high swoop curves rest on bottle surface and need no edits. middle curve - duplicate and edit to move vertices to represent deepest part of the intrusion (pain in the neck, but the orig will help you orient the edits. 6. loft the three curves, rail mode -Edit: oops, i meant Ruled option in the Loft Surface dialog - and apply Fillet Edge (variable if needed) to smooth the deep part. 7. Solid subtract the swoop shape from the bottle half. 8. Fillet Edge at intersection of the bottle and the swoop volume. 9. if front and back bottle are same, mirror the front and Add Solids. if front/back are different, create appropriate v swoops and intersect or project to a dupe of the back side and repeat steps above. add the front and back bottles Note: your choice, but I like to duplicate source objects so I have easy access when needed, and some vwx modeling processes destroy the sources. dupes can be placed in separate layers and/or deleted later. post back with questions! -B

Certain site model edits, maybe any site model edit, causes the contour elevation labels to duplicate. Maybe simply opening the edit contours dialog? Sorry i can’t remember the specific trigger(s). I will try to test. regarding delete then finding them regenerated at reopen. - was there a Save action? did dupe labels propagate in both exist and proposed? The dupes are vexing (vextorworks!) -B

Methods described above are probably best, but, just in case . . . Another way to project the line onto the site model, assuming the dwg property line is 2d lines and/or polygons: •Select the dwg objects that comprise the property line. •Compose them to become a single object. •Duplicate in place if desired, otherwise the source object may be lost. •Then - Terrain>Send to Surface. Result is a 3d polygon residing on the surface of the site model. This is quick, but has no relevant data for the segments. -B