Jump to content

Tamsin Slatter

Vectorworks, Inc Employee
  • Content Count

    1,408
  • Joined

  • Last visited

Posts posted by Tamsin Slatter


  1. Just now, neal-2002 said:

    No, I’m done with 2020....I’m back to using 2019 and ain’t moving till spring....doubt I’ll bother with next years VSS either..

    Fair enough, but we would be happy to look into this for you and may be able to resolve some issues.


  2. On 10/30/2019 at 5:36 PM, neal-2002 said:

    ive had the same issue with missing parts in open gl rendered elevations!!

    and viewports moving together too!!

     

    VW sort it out - ive just paid 3K for this mess!!

     

     

    Neil, did you ever send us the files so that we can investigate this? 


  3. Login to the student portal, using the account you set up last year and then request the extension from there (if you can't remember your password, there is an option to reset it on the login page). You'll need to include an image of your student card that shows your are still studying. Then, we'll review and extend as appropriate.

    student.myvectorworks.net


  4. Hi

    It looks like you are selecting the 3D from the 2D elevation library - the images are the same, but behave differently. Instead, you need to use the images from the 3D Image Props libraries.

     

    Good luck!


  5. Manually align the top two tags to have the distance that you want. Then select all the plants, run the command again, and it will use the distance between the top two as the uniform distance between them all.

    • Like 2

  6. Thanks for sharing Neal. You just beat me to it. 

    Glad you have a workaround with a combination of the OpenGL render. You can remove the colours from the OpenGL render and increase the quality too, so might be worth experimenting with that too.


  7. Thanks Neal. The team has your file and is doing some testing. I have a feeling this may be something to do with the way the Maxon engine handles the artistic edges, but we will come back and confirm for you.

    If you remove the sketchy edges from the Renderworks style, you will get a 360 panorama without the issues you are seeing.

    QuicktimeVR functionality was discontinued by Apple in Quicktime v 7 and that is why it is no longer available in the Vectorworks software.

    • Like 1

  8. It depends on the settings within that style - each option within a style is set to By Instance or By Style. You could edit the style, choose the options you want, and then set them to By Style. Then apply the style. The settings are fixed by the style and not changeable. Leave things you want to be able to change on each Sheet to By Instance.

    • Like 1

  9. Also, I am able to correctly export shapefile data without paying any attention to the user origin. Shapefiles use the coordinates within the georeferenced system, not the user coordinate system as far as I understand. 

    If you are seeing something different, please ask your local tech support team to work with you and submit bugs on your behalf, or you are welcome to post files here.


  10. When you import CAD data now, and you want to work with a georeferencing coordinate system, you don't use the Location tab. Instead, check the option This document contains georeferenced data. This will match the coordinates of the imported data to the georeferenced coordinate system.

    The Geolocate tool moves the internal origin to be close to the geometry, and therefore solve the problems that are caused by having geometry a huge distance from the internal origin. This was not possible before 2020, and made it difficult to work with such data.


  11. On 11/2/2019 at 5:17 AM, JeremyLondonRMLA said:

    However in either case I don't think it offers a solution or workaround to the issue I'm describing, where an imported CAD file generates an offset user origin, which subsequent shapefile imports and exports adhered to by default in previous versions of Vectorworks, but no longer do.

    Shapefile imports will georeference the design layer that is created on import, and respect the georeferencing setting within the shapefile OR use the georeferencing setting for the document. The import process can also apply the shapefile's georeferencing method as the document default if desired. The user origin IS irrelevant in this process. However, you can align the user origin with the origin of the projection method defined within the georeferencing system. There is a workaround defined in my other post, but the Align User Origin with Georeferencing system is a new command, that you will find under Tools > Origin > User Origin, following the release of SP2. Until then, the Stake workaround is the way to achieve this alignment.


  12. 3 hours ago, neal-2002 said:

    Im having issues where exporting my panoramic as white card render with sketch line added just isn't working, its only rendering the jpg as the current view and not the entire 360 view

    ..also doing the same under artistic renderworks

     

    And the old QT panoramic just isn't working either, just writes Zero Bytes...

    - so now I have no alternative for lined 3d 360's - spent all afternoon messing with this.. - all i want is a quick and dirty 360 image to show clients options and not having to render in best quality and then convert to B&W..

     

    Also

     

    saving Panoramics locally - opening 'index.html'  DO NOT open under the following browsers on my osX 10.13.6 - (ive moved back from 10.14 due to VW2020 being too slow and using up all the memory with far too many beachballs.....)

    Safari

    Firefox

    Chrome

    Brave

    or Chromium!!

     

     

    osX 10.13.6

    Hi Neal

     

    If you would like to submit this to the UK Technical Support team, they will do their best to help you. uktech@vectorworks.net. They will need example files and the spec of your system.

    • Like 1

  13. OK - I tested this as follows:

    1. Created a file with UK georeferencing.
    2. I used the Geolocate tool to search for my home postcode and place the internal origin in my street.
    3. I selected the single design layer and georeferenced it to match the document.
    4. I then used the option to Align User Origin with Georeferenced Coordinate System.
    5. I then used the Geoimage tool to create an image of my street.
    6. I traced over the roads with polygons, and added a record that included the street name.
    7. I traced over some houses and added a record which categorised the size of house and the poshness vs normalness of the occupants (! - well, it IS Friday).
    8. I added a GIS Stake close by, and adjusted its X and Y to give me an easy to remember whole number on the E and N.
    9. I then used the Geolocate tool to move the internal origin to the point of this stake. (I did this to help me ensure that the resulting shapefiles ended up in the correct location).
    10. I then exported the files, by record. I re-ran the export for each type of record, including the Stake record, so that I would have all the geometry and that all important coordination point. 
    11. This seemed to work just fine.

    I then imported the shapefiles into a blank document, and had the import process georeference the document according to the shapefile. Everything ended up in the correct place. A Stake placed over the 3D Locus designating my original stake point, showed the correct Easting and Northing. The only thing I had to do was use Geolocate to move the internal origin to my known point (the stake), just for completeness. As we learnt from the Design Layer Viewport referencing of GIS data, the location of the internal origin is important and needs to be consistent for coordinating across files.

     

    Now, I will test the export using the selection option instead of exporting everything by record...

     

    (P.S. Can't share my files on this one, as my neighbours might take exception to their posh vs normal classification!)

    • Like 3

  14. OK - I've got it to work. Referring to our other post (linked above) I've done the following:

     

    Create File One Ref

    1. Open blank file and ensure Georeferencing is set to EPSG 27700.
    2. Import DWG (in my case topo of Exeter in OS British National Grid X and Y coordinates). This file has the largest extents of geometry of my two reference files.
    3. Geolocate the internal origin to a known point on the imported geometry.
    4. Add a GIS Stake to show E and N in Meters of this point. It is important that the internal origin is in the same location within the geographic coordinate system across all files.
    5. Run the new Align User Origin with Georeferencing Coordinate System (coming soon in SP2 - but refer to steps in linked post for SP1 method).
    6. Now, the User coordinate system is aligned with the Georeferencing Coordinate System and the internal origin is in a known location within that coordinate system.

    Create File Two Ref

    1. Open blank file and ensure Georeferencing is set to EPSG 27700.
    2. Import DWG (in my case a detail area of Exeter, still in OS British National Grid X and Y coordinates). This file has the smaller extents of geometry of my two reference files.
    3. Run the new Align User Origin with Georeferencing Coordinate System (coming soon in SP2 - but refer to steps in linked post for SP1 method).
    4. Add a GIS Stake to show E and N in Meters of this point. Change the X and Y coordinates of this stake to the same as the location of the internal origin in File One above.
    5. Geolocate the internal origin onto the Stake created above. The internal origin is now in the same location as in file one.
    6. Now, the User coordinate system is aligned with the Georeferencing Coordinate System and the internal origin is in a known location within that coordinate system.

    Create Target File Three

    1. Open blank file and ensure Georeferencing is set to EPSG 27700.
    2. Create two design layers.
    3. Edit each Design Layer and check Georeferenced, to ensure that they are both georeferenced according to the document.
    4. Run the new Align User Origin with Georeferencing Coordinate System (coming soon in SP2 - but refer to steps in linked post for SP1 method).
    5. Add a GIS Stake to show E and N in Meters. Change the X and Y coordinates of this stake to the same as the location of the internal origin in Files One and Two above.
    6. Geolocate the internal origin onto the Stake created above. The internal origin is now in the same location as in file one and two.
    7. Now, the User coordinate system is aligned with the Georeferencing Coordinate System and the internal origin is in a known location within that coordinate system.
    8. On the two design layers you created above, create design layer viewports of files one and files two.
    9. In my testing, the files line up perfectly.

    I hope this helps.

    Archive.zip

    • Like 3

 

7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114

 

© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

×
×
  • Create New...