Jump to content

jeff prince

  • Posts

  • Joined

  • Last visited

Everything posted by jeff prince

  1. Just a guess, try exporting to DWG and importing that into a new file. It’s a handy trick for creating 2D line work from 3D models, so I suspect it may work in this case, while preserving the desired look.
  2. You are correct sir. Site models should be built from Top/Plan view. @Mark AcetoIf that’s not it, post the import file and describe how you did the site model creation and what VWX version used.
  3. This is easily accomplished... provided you import your DWG into a Vectorworks file first. DWG references don't rotate off the XY plane 😞 VWX reference viewports will though 🙂
  4. Just a quick follow up, I can't look at the file because it was saved in 2022 and I just uninstalled it from my workstation for safety and sanity's sake.
  5. I'm away from my workstation now so I can't look at your file till tomorrow. 1st thing I do with a survey is rotate it around in 3D so I can determine what data will be useful. Then, I grab it and put it on a separate design layer to segregate it from the less useful info. Sometimes, and in the case of the file you posted earlier, you will find 2D data such as points that have text describing their elevation. The stake tool can quickly recreate these 2D points as 3D data. From there, you can select your loci, stakes, and 3d polys and use the create site model command. I would advise taking a few classes on Vectorworks University to learn this before playing around too much and developing bad habits. The required workflow can be confusing to new people, but with a little practice it gets easier. Small errors can cause big problems with site models. 3D loci or stakes make superior models compared to contour lines. Basically, contour lines are interpretations of points your surveyor collected. These guesstimate contour lines typically have a bunch of vertices which do not add accuracy to your model and only serve to slow your computer down, though your site and data are pretty simple...so that is just general advice to keep in mind for the future.
  6. The provided survey will produce a site model. You just have to grab the loci to use as source date. If you also want to use the line features, convert them to 3d polys first, then use as site model data. There are several points that look to define the top of fence, you probably don't want to use those in your site model, but you could use them to develop a 3D fence. Many of the points outside the parcel of interest do not have any 3d value, but could be used to develop neighboring structures manually. Hope it helps,
  7. They should be named Up, Down, Left, and Right with respect to how they lay on a sheet. That and we should have the ability to add interior elevation marker to the annotation space of a viewport and generate the elevations from our 3d models instead of the current broken workflow.
  8. Export your .xls file to tab or comma deliminated values before importing. That's usually a sure fire way to identify .xls import issues, especially with new versions.
  9. I don't think that works either. Design takes place away from the desk as your responsibilities increase, it doesn't go away... unless you take on 100% admin roles within an organization.
  10. @willofmaine I appreciate you looking into these workflows. I've been dragging my feet on actually using 2022 due to the changes to Plant Objects. I haven't fully embraced Materials yet due to random oddities encountered during trials of the feature. It seems that 2023 will be out before I will be able to "trust" 2022, meanwhile my Service Select "pay us" reminders keep coming. Feels like skipping 3 to 4 releases is starting to make more sense...
  11. Me too 🙂 I think you need to contact Vectorworks Support. Perhaps it has something to do with your "add prefix" setting? Once you have imported the file, Vectorworks will present a dialog box with a button for "details". Clicking this will create a text report on how the import went. Perhaps the source of this problem will be identified there?
  12. Everything imported fine for me, see attached. Also, when you import, be sure to set your Classes/Layers like the attached image, choosing the "layers" radio button instead of "classes" is typically highly undesired 🙂 imported.vwx
  13. Upload the DWG here and I’ll take a look at it.
  14. @Matt Hall Customize the datatag definition to do math based on data from the space object. See attached. Hope it helps. math in tag.vwx
  15. Vectorworks cloud services is far from the best for drone to 3D processing. I would advise using Recap, Agisoft, or other suitable professional software.
  16. There are a few ways to do this, I'll recommend the easiest 🙂 Since the garage is a separate structure, put it on a separate layer. You could then set the layer elevation for the house and garage independently. This gives you some flexibility if you use layer based wall heights as well since the garage will likely require something different than the house.
  17. Option 1 - Don't use BIM sheet numbers. Option 2 - Don't use BIM sheet numbers as Vectorworks Sheet Numbers. Create BIM sheet numbers when needed by adding the BIM prefix to the sheet number with a tagging tool and formula.
  18. I just watched one of those VSS Coffee Breaks titled "Auto Coordination, Back References, Hyperlinks..." During the part about the interior elevation marker, the presenter mentioned it was "a bit of a convoluted workflow" in regards to having to create the viewports from a design layer, but having to create a duplicate markers on the sheet layers to facilitate back referencing. It's not convoluted... it is a poorly realized and should be fixed. In reality, I rarely have a practical need for the tool as a landscape architect. However, my students and those I consult in BIM do. They are constantly confused by this workflow. You can create a section from annotation space of a viewport on a sheet layer. You can use a data tag in the same fashion and it can extract data from design layer objects. But when you try to create interior elevation viewports from a sheet layer, the software chastises you about not being able to sense walls from a sheet layer. The only solution I can tell people is "Vectorworks has a lot of idiosyncrasies when it comes to most things, one day they may fix it. Also, be prepared for them to break workflows by reinventing objects such as Plants forcing you to update your entire library". I don't like saying such things. However, if I am not honest they will think I do not know what I am doing because it fails such a basic common sense test. In regards to the response I received during the seminar, I just searched this specific forum for instances of people wanting this tool to be improved in this same way. I'm hardly the first to make mention of it. Imagine the frustration building architects must have over this kind of thing. Come on Vectorworks you can and should do better! Less gimmicks and more refined workflows. You can do it 🙂
  19. Yes. Not to trash the Nomad team, but it has a long ways to go to be useful for site work, construction admin, and useful AR compared to the competition. I’ve been hopeful of ipad VWX for a while. Some thoughts from a while back…
  20. An image of the problem is worth 1000 words, uploading a file exhibiting the issue is priceless…
  21. When using custom textures (images, sketches, slope analysis, etc), you simply size your texture to the same proportions of the site model. Magically, no fussing with texture alignment. I learned this the hard way, much like you have 🙂 I’ll have to dig out some examples. Another trick for non animated renderings is to have textures at different resolutions for the views you need. Big birds eye renderings can use small textures, close ups of areas can use models cropped just to the area of interest with higher rez textures to speed up operations. Animation is a different story, and likely better done in a different program.
  22. Except your Z value will still cause problems for those of us who use Z= sea level…
  • Create New...