Jump to content

Art V

  • Content Count

  • Joined

  • Last visited

Community Reputation

203 Spectacular

1 Follower

About Art V

  • Rank
    1000 Club

Personal Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You might be even more profitable if you would work in DWG as you would get to write more hours on the projects because it probably will take you more time to get the project done. ūüėČ That being said, using VW has made it possible to meet project deadlines that would not have been possible when using AutoCAD because VW was (and is) so much more efficient for certain things than AutoCAD. However, I do fully agree that the DWG compatibility needs further improvement as I too still need to "fix" DWG files too often to make them comply with client's or other (inter)national standards or to simply make them usable in AutoCAD as you have noticed. Some basic things are still missing in the import/export that simply makes VW a no go for certain projects even though from a drafting perspective VW can do the job but the DWG conversion is simply lacking too much on those basic missing things. But... given the differences between VW and DWG there will always be things that will need fixing by opening the DWG file in a DWG based program (AutoCAD/BricsCAD/Draftsight etc) and fix those things in there. The better the conversion is the easier it may be to fix those remaining things that cannot be easily translated and less time we have to spend on that. I don't expect perfect translations to DWG because after all there will be a point where VW will have to consider whether it is worth the investment in time and money to get those rare things translated 100% correctly, especially if there is no real equivalent in DWG. If you have ever seen a DGN to DWG conversion you'll know what I mean, as e.g. those are rarely usable from a layer management perspective even though Bentley and Autodesk have an agreement on using each others API's/code for importing/exporting into each other's file format.
  2. Yes, IGES/SAT is another option that I forgot. It can produce nice(r) geometry that is better than you may get when exporting to DWG even though SAT is basically what in DWG is called ACISOUT for exporting and ACISIN for importing. AutoCAD uses ACIS for its 3D, though it is a slighty different version than the standard ACIS from Dassault.
  3. These options are needed for printing/publishing as the PDFs and graphics need to look that way when printed, whether it is controlled through display options in the viewports or otherwise is ultimately not that relevant. The issue could be solved by having printing profiles similar to AutoCADs plotsyle tables so that next time you simply select a printing profile fr the desired output. That might actually be a more elegant solution than having to create multiple sheetlayers with viewport settings if you need to output in both full colour and grayscale for varous purposes.
  4. I took a look at the AMD Vega card as well and noticed they require a lot more power than an equivalent nVidia card, get hotter and are not faster in most cases. In a VRay benchmark the RTX2060 and RTX2070 beat the Vega cards by a considerable margin, and even the GTX-1070 Ti can't really keep up in that benchmark if I recall correctly. Are you getting a better OpenGL performance with the 2070 than with the old(er) card you have been using, or rephrased... does VW perfom noticably better with the 2070 than the other card?
  5. @Jim Wilson Thanks for the info, this is very useful to know for using it with VW. I'll have to do some more reading on the differences between the two for some of my other programs but I wanted to be sure that one or the other wouldn't end up being a bottleneck thing for VW performance if it does not make much difference for the other programs which one I choose.
  6. Oh my, within the next few weeks I need to work on a drawing where I have to use the hatch line scale in the advanced properties so I guess it is back to 2018 for that drawing. Hopefully this gets fixed in a SP for 2019 soon.
  7. This depends on the origin of the drawing or whether you need to export to DWG. In some cases you will need to have the lines to be grayscale as well for compatibility reasons with DWG files due to the way hatching works in DWG. So ideally there should be three options for B/W and grayscale printing/publishing: 1. pure B/W (lines and fills) 2. pure grayscale (lines and fills) 3. B/W lines and grayscale fills Workarounds do exist but the problem with workarounds is when people not aware of how to do this or that they have been used may get frustrated about the output or print the drawings incorrectly.
  8. Art V

    Issue with Text in VW.

    Even though VW 2019 isn't as bad as VW 2017/2018 when it comes to this you may still experience the issue as being aggravating more often than not. The "crazy" thing is that with the same drawing in VW2016 you won't experience this lag at all, it will be much more responsive than VW2017-2019 in this particular aspect. The VW graphics engine got a major overhaul in VW2017 and improvements were made in 2018/2019 but there is something in the new graphics engine that causes this. VW staff has been tracking and solving some of the issues causing lags but not all have yet been fixed. Not everyone seems to be suffering from this so I guess there is a hardware and/or (graphics) driver factor involved as well. So upgrading to 2019 while remaining on the same hardware may reduce your issue but whether it will be fully solved in your case is something you probably can only find out after the upgrade has been made.
  9. Art V

    Issue with Text in VW.

    What may also help is to turn off the visibility of design layers that have lots of objects/nodes and you don't need to see when working with text. My guess is that VW is detecting objects and trying to figure out possible snapping/tracking options which does slow down VW. The more objects there are visible and available for snapping the longer the snap/track acquisitions/calculations take and the slower VW gets. It is not just with text but also with selecting and moving objects.
  10. I get to upgrade my graphics card from a GTX-960 to a newer model and the choice is going to be between a GTX-1070 TI on sale or the new RTX-2060 for basically the same price, both should be quite a bit faster than the GTX-960 I have now and may (hopefully) solve some of the lag issues. The main differences are that GTX-1070 TI has a 8GB of RAM and a 256-bit interface and therefore a bit more bandwidth than the RTX-2060 with a 192-bit interface, the RTX has 6GB of memory. However the RTX-2060 is most of the time just as fast or even a bit faster than the GTX-1070 TI according to gaming site tests. VW isn't a gaming application, though it can be fun anyway and sometimes a gamble on how well it will do certain things :-), so I don't expect these test to translate 1 on 1 for VW. The RTX-2060 has built in support for raytracing etc. but I doubt that VW will be using this in the near future (i.e. next 3 years or so). What would be the better choice in this case for use with VW? GTX-1070 TI with a bit more memory and data bandwidth, but 2 years old already, or the newer GTX-2060 with newer tech on board which seems to have more processing power but has a bit less memory and bandwidth? @Jim Wilson do you already happen to have some info based on user experience on how well the GTX-2060 performs with VW, i.e. better, equal or worse to be expected than the 1070 TI? Thanks in advance for any insights
  11. Art V

    Issue with Import Images

    That sounds something is wrong with either your VW install or the JPEG is in a flavour that is not (properly) supported by VW. Especially with georeferenced/GIS files it may cause issues if the georeference/GIS formatting is not supported. Did you try importing the georeferenced file without geocoding sidecar file? If you are allowed to share one of those problem JPEGs I'm willing to have a look at it and see if it has issues on my end as well.
  12. One thing to keep in mind is that VW 3D objects and DWG 3D objects can be quite different and it could get converted in ways that will keep the appearance of the object but not necessarily the editability. E.g. some solids may get converted to meshed/triangulated surfaces etc. It can happen the other way around too as solid hatches can turn up as a bunch of filled triangulated areas in 2D at times. The ODA DWG libraries have become better in the past few years for 3D conversions but there will still be things that won't translate smoothly from one to the other. So it really depends on your 3D objects/models how usable the export will be. The more complex it is the more likely you will have issues. 2D exports are mostly fine, except from some things like text styles etc. that VW has not yet fully implemented even though it is in the ODA libraries. 3D is something I rarely bother to export to DWG unless it is simple stuff or if I really have to at the client's request. You could try exporting to Rhino3D format first and then from Rhino to DWG, but that requires having Rhino available. It can make things a bit better at the DWG end. It works th the other way too, if you have a messy 3D DWG file (i.e. lots of meshed/triangulate surfaces) then importing it into Rhino first, save it as a Rhino3D version that VW supports and then import the Rhino3D fill may give a (sometimes much) more usable 3D import than directly importing the DWG file.
  13. If you have ATTDIA set to 1 (on) and you do an edit of one of the attribute lines you get a dialog showing all the attributes for that item to be edited? If yes then it is ok, if not then they are probably just text items.
  14. Art V

    Drawing Setup

    For dealing specific georeferenced files that Vectorworks does not support (yet), e.g. MrSID, you may want to get a GIS program (e.g. QGIS, GlobalMapper or even ArcGIS if you want to spend the money on that one) to convert those files into a different georeferenced format. QGIS is free but can be (quite) slow or failing depending on the content so I also use GlobalMapper which can handle a lot of formats quite well and often a lot faster than QGIS if that is slow/failing with a file.
  15. Art V

    Need to draw a Boat

    @Jan-Burger TROOST I've had to deal with creating ship hulls, though relatively simple and not as complex as yachts, in VW and ran into various issues. As explained above nurbs and lofting are basically the way to go but it requires (quite) a bit of trial and error depending on the boat shape as things don't always work as expected. Rhino would be a better option for this (i.e. NURBS) if the boat is not extremely complex and it often imports well into VW. The more complex the boat model is the greater the chance that you would need additional tools. I also use it to "fix" 3D DWG files to get a cleaner import at times but sometimes they are just too messy to fix nicely. VW's unfolding does have its limitations, like the nurbs tools and I haven't been able to get a unfold of a double curved surface that looks proper. Otherwise you would be better of with specialized CAD software.


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.