Search the Community

Showing results for tags 'import'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements
    • Announcements
  • General
    • Troubleshooting
    • General Discussion
    • Architecture
    • Site Design
    • Entertainment and Previsualization
    • Vision
    • Rendering
    • Workflows
    • Buying and Selling Vectorworks Licenses
  • Feedback
    • Wishlist - Feature and Content Requests
    • Known Issues
    • Wishes Granted
  • Customization
    • Marionette
    • Resource Share - Marionette
    • Vectorscript
    • Python Scripting
    • SDK
    • 3rd Party Services, Products and Events
  • Solids Modeling and 3D Printing
    • Subdivision
    • Resource Share - Subdivision
    • Solids Modeling
    • 3D Printing
  • Vectorworks in Action
  • Archive
    • Resource Sharing
    • Machine Design
    • Terms of Service and Community Guidelines

Calendars

  • Community Calendar

Categories

  • Knowledgebase
    • Tech Bulletins
    • Troubleshooting
    • How To
    • FAQs

Categories

There are no results to display.


Found 11 results

  1. Hi there. We use VW2017 to add electrical engineering features to architect issued plans. In a rather big project we get multiple 500 MB - 1 GB plans from the architect that we have to import and save as VW documents to be able to work on them. This happens a few times a week and it surely adds up time before we can work with those plans. As of now we are using the biggest baddest iMacs and VW2017 for the planing and even they slightly buckle when importing those plans. Trying out different MacPro and Mac minis we determined, that during the import process it's the clockspeed and the usage of real CPU cores that truly makes the difference. For example a MacPro 2009, 4-Core 2.66 GHz XEON on 8 GB RAM, SATA2 SSD with 10.11.6 and VW2017 will have around 2min 30sec to import a 10 MB .ifc file. We tested it with the standart GT120 (512 MB VRAM) and a GTX760 4GB and there practically no difference between them. GPU seems to make no direct impact at that point. Also it shows only the real cores under pressure, so no hyperthreading during import. So there are a few questions that need confirmation: Is the observation correct, that it is the clockspeed and the physical cores that really count during import? Can VW2017 actually use more than 4 Cores? How is it in WIndows 10 64bit? Will 32 GB RAM bring a significant boost against 16 GB RAM? Would a RAM disk containing the file to be converted bring a significant difference? We threw round a few suggestions and thats what we would go, if the before mentioned points can be confirmed: AMD Black Edition FX 9590 4.7 GHz 8-Core on a FX990 Chipset board, AMD RX480 (8GB VRAM), SSD, 16 GB RAM (or 32 if it really makes a difference) In the end we are aiming for the setup that will allow us to max out on the import process (within reason of course). Thanks for your input, your tips are really appreciated! Best Regards Thomas Alt
  2. Hi guys, I'm new to marionette. Is it possible to load an excising 2D Polygone to my marionette wrapper to modify it? (especially extrude) thanks, steven Vectorworks 2017 Spotlight (German Edition)
  3. Another example for a Marionette productivity-tool. The Attached Marionette Network imports all .skp Files from a chosen or predefined folder as Symbols. Limitations: - No special characters like äöü (I think a limitation of the vectorscript function) - No Sub-Folders This is a fore-taste of a couple of nodes I did the last weeks for import/export data or mass-modification of resources. So stay tuned ... :-) DomC BatchImport SketchUp.vwx
  4. I have an .stp file that I need to import, but it is over 300mb. Any ideas on how I could reduce file size for better performance?
  5. Is the Revit import feature in 2017 intended to allow us to bring in entire Revit models, or just single objects (families)? I'm trying to import a Revit model that a consultant generated right now, and all I'm getting is the title page of their drawing set. The help file has no real information so far either.
  6. I like to deconstruct my larger more complicated scripts into smaller files. It helps me stay organized. I'm trying to get imported functions to use global variables that I have created but, it's not working the way I like and I'm not sure why. I have a main script that defines the global variables. The main script also imports demo.py and calls the function draw. The demo.py script is basically an if/else test. I've imported another file named shapes.py which has functions to draw shapes. -If the global variable 'w' is less than 6 call function myrectangle() from shapes.py -If the global variable 'w' is greater than 6 call function myoval() from shapes.py -if the global variable 'w' is equal to 6 print "Hello World" in a Alert Box. When i try to run i get: NameError: global name 'x' is not defined. I thought that if I had global variables defined in the main script i would be able to use them in the imported functions. Am I doing something wrong? main.py import vs import demo w=vs.PLineLength h=vs.PBoxWidth x = 0 y = 0 y = y-h/2 demo.draw() demo.py import vs import shapes def draw(): vs.PenSize(2); if w < 6: shapes.myrectangle() elif w > 6: shapes.myoval() elif w == 6: vs.AlrtDialog('Hello world.') shapes.py import vs def myrectangle(): vs.Rect(x,y, x+w,y+h) def myoval(): vs.Oval(x,y, x+w,y+h)
  7. Because of barkest question about psd files not showing in the resource browser and the windows version not even seeing psd files I checked the supported import/export formats. The Mac version of Vectorworks supports import of TGA, PSD, SGI files whereas the Windows version does not. The Mac version also exports to PSD, TGA and OpenEXR and the Windows version not. I don't mind if Windows or Mac only formats (e.g. MacPaint) are not supported by the other platform, but platform independent formats should be supported equally on both Mac and Windows versions of Vectorworks for import/export so that in mixed environments both versions can use the same source files or export to the same file formats.
  8. I tried a bit with C4D Material Import. 1. C4D R18 with Materials from their Presets. 2. C4D R16 with Materials from their Presets. 3. C4D R18 with Materials that came from a VW RW Textures by Export to C4D. Having a Tex Folder with Textures beside. Only the 3rd attempt worked in some way. I get Image Textures but in wrong Scale (Export was VW cm > C4D mm > VW m) I get Reflections if C4D uses legacy mode only. I get Transparency. So I need help what is the exact Environment thought for this import. Or what parameters I have to apply to be successful. And what is not supported Concerning : Image Textures in C4D > Location, Path Assignments, Mapping Material Settings in C4D > Channels and their Sub Obtions VW 2017 help isn't that informative at this point.
  9. I have a DWG file from a surveyor which has information drawn in both Model Space and Paper space (title block, annotations, legends, general notes, etc). I am able to import the Model Space info, but I cannot figure out how to import the Paper space info. What am I doing wrong? Thanks.
  10. Text style import and export, where text keeps the assigned text style. Font substitution is not an issue. The reason for this request is that often project specifications or standards require the use of predefined text styles. Currently texts in dwg files exported from Vectorworks do not have proper text styles, this makes roundtrip workflows between DWG based software and Vectorworks very cumbersome if not impossible for practical reasons.
  11. Still no DGN import Even though it is really nice that Landmark can also import Revit files, Microstation is still quite often used in civil engineering related fields (not just road design etc. but also landscape and GIS) so being able to import DGN files would be really useful. At the moment probable even more-so than Revit import. So please please add DGN import to at least Landmark, though VW Architect could probably use it as well as Microstation does have a BIM module as well.