Jump to content

Benson Shaw

Member
  • Posts

    3,778
  • Joined

  • Last visited

Reputation

739 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. Yes! Tools>Records>Modify by Record! Duh. Couple years ago that's how I made those building outlines extrude to apex record height (but had to switch format from Number to Dimension). The 2d polylines and polygons all moved to z = ELEVATION record value. They remained 2d polys with OIP Plane designation as 3d. In the Modify by Record command dialog, I needed to switch from the empty record format (from .shp) to the full one (from .db). Still not clear on why that shp record format is empty. The Terrain formed via AEC>Terrain>Site Model from Source Data. Surprised (and pleased) that conversion to 3d poly not needed. Terrain skirt is empty along top of NE edge (from the low corner). In wire frame,Top, it looks like some of the mesh connects back through itself instead of to nearest neighbor. The old bridging problem. Otherwise looks really good. Super helpfull all. -B
  2. @jeff prince Ummm, sorry to be so dense, but I'm not getting there. Which file(s) did you import into vwx? In past, I have found that the shp file holds (refs?) all the geometry and data from all the associated files in the folder (directory). Import the shp, the contours arrive with attached records from a fully functional record format (the db). Perhaps I had to convert 2d to 3d. But I don't recall how they achieved the correct z. Automatic response to the record? My trials: New blank vwx in same directory as the Q files (5 of them). Import only the shp file. Result - 2d polys and groups on design layer, and a blank record format (no lines/items) in the RM. Ungroup - everything is 2d polylines and polygons. The 2d polys have the record attached, but record contains no data. OK, I start over in a blank file in same directory. Import only the db file (choose Options>All Files so that db can be selected). Same bunch of 2d polys and groups arrives, plus the record format, this time with data. Yay! Select all, Ungroup. Everything is 2d polylines and polygons. But how to proceed? Convert 2d to 3d? Import the other Q files? Contours retain the attached record data, but remain at z= 0. They do not automatically move in z to the record value for ELEVATION. Thanks for your insights! -B
  3. Wanted to add something here as a guess. But 1st a problem. I have the qgis files in a folder with a new vwx file. I can import the shp (comes in as 2d polys), and see a new Test1Rec record resource, but this record format has no items. No way for it to acquire data. Not sure why the folder of qgis files is not implanting the database when I import the shp file to a fresh vwx f ile. ??? Previous experience is that the shp file contains the db info. Perhaps a vwx2022 thang? When I open @J. Wallace vwx file, I see Test1Rec and testRec record resources - both have appropriate fields including ELEVATION. Anyway a possible problem/solution: in @J. Wallace vwx file Record format resources, the data elevation fields are formatted as Number>General. I think the elevation field value needs to be formatted as Number>Dimension in order for the 3d poly to respond to the record data. This tripped me up one time when needing vwx to extrude a gob of building outlines to their various recorded heights. Changing vwx data format from General to Dimension made the outlines extrude to the apex value from the shp data base. No such luck here. These contours maintain their z=0 after the reformat from gen to dim. Rats! Is there something to change in the QGIS db prior to export? Or some way to link the vwx elevation data record to the OIP Z value? -B
  4. I looked again and see some problems. 1. The pdf is raster rather than vector, so no snaps, no certainty of dimensional correctness, offsets, etc of geometry applied over the image. 2. The pdf is not scaled to match the called dimensions and scale bar. You can rescale via the Modify>Scale>Symmetric by Distance. But probably a do-over is better option. eg New blank vwx drawing. Set layer scale to match the announced scale of the pdf drawing (1"=20'). Import the pdf to this layer. It should display scale bar and called dimensions at or very close to correct new geometry. If needed, Rotate pdf for North alignment. 3. Then questions - Are the Prop segments drawn in Field or Plat context? Are the field locations denoting the prop boundary? or are they more metes and bounds type features close to the property segment points? Uncertainties in this pdf seem likely to cause imprecise documentation and other problems with location and construction of any new design features. Is a vector based survey file available? Or can you work with approximations based on this pdf? -B
  5. Glad this works better. Do you need to convert the 2d path to 3d poly? 2d poly>Send to Surface creates a new 3d poly projected onto the terrain surface. This new 3d poly can be a path for Edit>Duplicate Along Path. -B
  6. Is this what you mean? Drawing came in rotated, but I set to Top Plan unrotated. I created this property line by selecting the segments which were drawn on top of the pdf, Composed, right click>Create Objects from Shapes>Property Line. On the design layer, the default text is too small to see without lots of zoom. With the PL selected, I increased text size via Text Menu>Size>Set Size>Custom>600. In OIP, I chose some parameters - bearing vs azimuth, Report Curve as Segment Label, but others default. -B
  7. Do the loci have correct rotation? Eg if the desired panel array is tangent along a curving path? That would be fantastic! -B
  8. This is a guess, but Something to try in a duplicate file: A. Create a really simple symbol, eg an extruded rectangle. A 3d locus might even work. B. Once you have your solar panel symbols arranged in top view, select a bunch of them, Replace (OIP option), choose the really simple 3d symbol, Send to Surface. Leave them selected. C. Replace (OIP) with the solar panel symbol. idea is that the Send to Surface Command has to analyze lots of geometry to place correct point at surface. A simpler object might go faster? The Replace function might have less to “consider”. or this could be a case of too much overhead with complex terrain and symbol. Fix might require lower vertex count overall. Terrain-Simplify contour Polys. Solar panels - make a low detail version for most of them. Place high detail version only where close views will display. -B
  9. Did the column order get mixed up. Or a superfluous column replace a relevant one? This is a vague memory of response ( @jeff prince? @Alan w?) to setting up for comma delimited xyz points. -B
  10. Sometimes also helps to increase the ambient light setting -B
  11. OK, finally some updated MacBooks from Apple. Current and future vwx - Any comment on extra cores? 32 standard in the M1Max or upgrade to 64. Unified memory? everyone happy so far? redraws, renders, etc. I saw reports here of slower/same render times for simple scenes, but significant improvement with extra bounces and complex shaders. Even if not yet ready for latest OS and M1Max, vwx is likely to catch up quickly. My opinion. Mostly my files are less than complex. But that could change. Anything will improve my current kit. -B
  12. I think elevation VP has no default crop, but rather displays the extents defined by the section line prefs. Not sure if this works, but try Edit VP>Edit Crop, draw a crop object inside the extents. Then make the Crop invisible via OIP checkbox. -B
  13. @Alex M Try again without holding shift. Top or Top/Plan. With object selected, start the move via drag in any direction. Press Tab to activate the floating data bar (unless you have some other pref to activate). Press Tab again to activate the L field. Release the mouse button. Key enter the desired distance value. Tab again. Angle field activates. vwx creates a "bubble" at L radius (no red lines) showing the L radius and object located on L radius. Angle field indicates drag angle at activation point. This value does not update as cursor is moved, but does not create an angle lock at this stage. Choices here: A. End the Move without entering an angle value --- Drag around (can be outside the bubble) to move object to desired alignment. Dbl Click to complete move at angle aligned to click point and L radius. Note: Smart cursor activates snap angles & extensions, but Data Bar Angle field does not update. B. End the Move with an angle value --- Key enter an angle value. Press Return twice. Object moves to L/Angle location. More functionality via the floating data bar - experiment by tabbing into the extended fields while applying drags, clicks and returns. Move By Points instead of Drag is another workflow including with floating data bar input. I don't know what is intended by the Shift key bubble, or why click defeats the move set up. HTH -B
  14. I think? guess? suspect? that vwx can only unfold surfaces which are cylindrical, conical or flat/planar, or continuous aggregations of such areas. The surfaces can have holes of any shape, the edges can have notches. These surfaces would be developable in the sense that real world materials do not require any stretching or compression. Other software, eg for design and mfg of automobile body work, shipbuilding, magnet or press formed sinks and cookware, etc can probably predict the least wasteful config for start shape of flat material. Another unfold context is the various mapping projections - orange peel, cylinder, globe. Can anyone verify or extend any of this? -B
  15. @line-weight Do any of the options in this pref offer any relief? I never used the top one, but it might be helpful for this issue. -B
×
×
  • Create New...