Jump to content

unearthed

Member
  • Posts

    587
  • Joined

  • Last visited

Reputation

183 Spectacular

Personal Information

  • Occupation
    Landscape Architect and Ecologist
  • Homepage
    https://www.growplan.co.nz/
  • Hobbies
    landscape, botany, QGIS and spatial statistics
  • Location
    New Zealand

Recent Profile Visitors

7,494 profile views
  1. Are there raster images (.jpgs, or .png etc) in your drawing? I'm using VW 2018 (but this has been an issue in vw since I started in 2004) where an image file extends beyond the viewport, that all of the image data is exported/pubished to the pdf - this does not seem to be a thing regarding vector data. So I split images into tiles and put each tile in its own class - it's a really slow kludge, but sometimes necessary. It is the nature of some compression algorithms to result in a file becoming larger - sometimes. VW is very inneficient with its handling of hatches, and with stipples it is even worse.
  2. The yellow ellipse is the viewport and the image information in it is only 1Mb or so, but the aerial is much larger. In my experience VW somehow includes all the image data for the whole raster file (although not in a readable way, it is just somehow embedded in the file, leading to bloated .pdfs). I have not opened your file as I'm running 2018, and I don't do photoreal so your cameras and their data won't mean much to me. If I have a particularly problematic file I use pdf995, but VWs publish/export is a lot better than it used to be. I cannot
  3. A long term fundamental flaw of VW (and as far as I know still existing in the latest versions – I’m on 2018) is that where an image file extends beyond the view port, that all of the image data is exported/pubished to the pdf. So I split images into tiles and put each tile in its own class - it's a really slow kludge, but sometimes necessary. If I have a very graphical page I normally export that page as a 300 dpi jpg and bring it back into vectorworks, again a kludge which defeats the purpose of owning a CAD in the first place. What it means is even with highly graphical content I can normally produce documents with up to 10 pages in 7-10Mb.
  4. How is one supposed to rotate a hatch to 90° (or any other precise degree) to a space? The side rotate handles seem a very coarse - and never accurate - way to do this. There seems to be no way to make the rotation setting reletive to adjacemt onjects. This is 2D only
  5. From what VW version to what VW version? /or other CAD format? At nearly 60Mb people don't want to waste bandwidth and find they can't open it.
  6. Yes, It would be interesting to see if this still exists, and how widely it exists.
  7. Thanks Pat, I tried it with Arial too, the same differing result.
  8. I have just noticed an inconsistency in font sizes (and possibly kerning and line height) between text boxes and worksheets – see image. In both instances I am using the same font – Calibri at 12.0 plain/unbolded (I specifically set the .0), and yet my textbox text is about 11.25 size. I'm not looking for an answer (I doubt there is one), just giving a heads up to anyone else who may encounter this, like is it still a thing in the current all singing all dancing VW2025? I am using VW 2018 on Windows.
  9. Thanks Zoomer, I agree I don’t see VW supporting Linux ever. I’ll digest that what you’ve written (and your comments on other threads here) alongside my other reading. As far as I can tell (at least theoretically) I think I can run all my other software on Linux either directly or via wine. Alongside will definitely be what I do for a while until very comfortable with whatever Linux I use I only use VW in quite simple ways, and don’t use any rendering functions or any 3D outside of terrain model. I’ve not seen anything that is more than I need on from 2018. So many versions of Linux! I need to do some serious reading, esp. on Manjaro.
  10. Like many others I am definitely not looking forward to the upcoming forced change to windows 11, and have been reading about Linux. I've seen a number of posts across the last two decades on here about people running VW on various Linux versions, and varying levels of complexity but success like EricsW in this 2021 thread that includes Linux KVM. So who here has had success running VW on Linux of any version including virtual machines like EricsW’s solution? I’m still on 2018 and for my use see no benefit to go beyond this (increasingly my workflow is in Rebelle and QGIS/R - but vectorworks is still a useful tool for making sheet sets, and for plant counting and orders - it is still the only CAD with an integrated (good enough) spreadsheet). I will never use ‘Service Select’ or any other ‘saas’, a; it’s being party to the parasitic rent-seeking mindset, and b; I often end up being places with poor connections and had enough of this when I tried the Sketchup saas and found it seriously wanting. And I’m not interested in dongle approaches either.
  11. I have some 3D locus points the sixth field is a comment (in VW as cmt:). Entered the comments manually into my GPS and then converted the gpx points to .shp in QGIS, and amazingly VW was able to read that. What I want to do is have queue just pop up a label that contains the relevant comment for each of my 3D locus points. I understand that with VW 3D locus point functionality is crippled (or nonexistent) and I have to convert to a in order to expose object text data for labelling to show. I converted the 3D locust points to Stake Objects the cmt: field and its contents are lost. The convert to state object drop down doesn't appear to have any selection or combination to carry over to see empty field and its contents. Image is QGIS and VW fields for the data. Has anyone resolved this? Output fields are only these: Stake #: segment type: segment length: segment angle: segment radius: egment sweesz segment rise: clockmode: polyline ID: tag:
  12. Just coming back to this as a note to my future self. In some earlier versions of VW (2018 at moment) setting the flyover tool reliably works before exporting, whereas View>Set 3D view is unreliable.
  13. What is the file size of your textures? - I presume they are images. Can the textures be put in their own class and turned off when you're moving/manipulating the model? Are there a lot of non-printing sub-elements in your model? Is whole file on your desktop?
  14. I've been using VW since 2004 (currently stopping on 2018) and every few releases my experience has included an inability to export useful .pdfs. I then retern to using pdf995 (not ideal - but better than having nothing to send my clients).
  15. Thanks so much Jesse! that works perfectly And thanks to Pat Stanford for how to change point number.
×
×
  • Create New...