Jump to content

P Retondo

Member
  • Posts

    1,914
  • Joined

  • Last visited

Everything posted by P Retondo

  1. I've always wondered the same thing. It doesn't do anything I can detect.
  2. Those of us who have worked with VW for a long time have developed systems and workflows that depend on screen plane objects. You may work a different way, but bear in mind that others may not. For my part, I have no use at all for layer plane objects. As you point out, the power of screen plane objects is that they can be copied into a different view and used as geometry to inform design - transferring geometry from plan to section, for example. Think of it like having a layer of trace over your 3d view. If all your plan geometry is layer plane, you can't use it this way.
  3. Yes, I might even start using 2019 if this is fixed!
  4. After much experimentation, what has worked for me for many years is to set the stylus range on my large tablet to a smaller rectangle, about 5-6 inches diagonal. This is comfortable and very workable.
  5. It would be great if we could designate a unit type to each dimension object individually. I run into the problem where some of our site drawings have to be in decimal feet, and the rest of the drawings in feet/inches. As it stands now, changing the units preference changes everything globally, so I have to set up a separate file just for those sheets and viewports that need to be in decimal feet.
  6. There is a known issue that causes the preference to change from "Screen plane only." If you edit a crop in a sheet layer viewport, it will change the setting and it has to be changed back. This has been known now for at least 2 years, and as far as I know nothing has been done about it. I just automatically reset the preference every time I edit a crop.
  7. You should talk to your professor about updating the class standard to at least 2018. In the meantime, you can work in 2018 and export your files to 2017 version if they need to be submitted electronically. 2017 and 2018 are pretty similar.
  8. Mike, I think the current system is based on the idea that you may want to edit a symbol in the context of its placement in the drawing. Sometimes that is useful, sometimes not. So if you have toggled "show other objects while in editing modes" in settings, you will see all visible objects in relation to the symbol's placement, allowing you to snap to other objects that are not part of the symbol definition.
  9. P Retondo

    Lineweight

    Select the object, and go to the Attributes Palette to change color, lineweight, fill, etc. Make sure an object is selected, otherwise changes made in the Attributes palette will change your defaults for new objects you create. The above assumes you are talking about 2d objects. If you are working in 3d and displaying the masses in OpenGL rendering mode, you will not necessarily see the lines at the edges of an object.
  10. This is a constant annoyance and problem. As Kevin says, it has to do with 2d screen objects in views other than Top/Plan. When this happens, if you marquee-select, you can see the object highlighted and you just have to feel around blind for the snap points. By the way, I have isolated when VW switches from "Screen plane only" to some other 2d object creation mode. It happens when you edit a viewport crop in a sheet layer. I haven't found any other event that causes that particular problem. PS: still haven't found anything but the very rare occasion when layer plane objects are actually useful. 3d polys do most of the same things, except display with fills and hatches. PPS: in the same vein, screen plane objects in other than Top/Plan no longer display their line color. And objects with white fill have a black fill, with my hardware at least.
  11. I have been asking for years for this, but might as well do it again. When pasting between layers with different Z values, an option should pop up asking whether Z should be assigned relative to the source layer, or relative to the target layer.
  12. P Retondo

    Hardware check

    My XPS has a GT 750M, which is benchmarked way lower than your GTX1050ti. And I have no noticeable performance problem. It renders slower than my desktop because of the lower number of parallel processors, but otherwise is fine. Bear in mind that I don't use Spotlight objects - but it doesn't sound right that you should have that level of performance issues with your setup.
  13. P Retondo

    Hardware check

    It doesn't make sense. Bear in mind that I have not moved past 2017, even though I have licenses for 2018 and 2019, fearing the same kind of risk. (NNA, are you listening to the level of distrust expressed by many?) All the same, I would suspect some kind of anomaly. Perhaps Jim or someone at NNA can take a look at your file and attempt to run it on one of their machines. One thing I would look at based on your most recent comment: updating Renderworks viewports can take significant time, and if your file settings or actions are triggering unwanted viewport updates, maybe that is the cause of your performance problem.
  14. P Retondo

    Hardware check

    Dan, does your NVIDIA setting for VW look like this?
  15. Thanks for posting on this. I am looking forward to trying out this new feature, sounds like a dream come true (once the bugs are worked out!)
  16. Sorry, Joe, I am behind the times. Contours are, indeed, a site modifier type, as of VW 2016.
  17. You are not using site modifiers in the way they were intended. As far as I know, the site model doesn't work by direct manipulation of contours - it works through objects like pads, which then generate proposed contours. I think you are asking the site model to analyze the difference between two sets of contours, which (again, as far as I know) it is not designed to do. The site model is interpreting your contour polygon modifiers probably in the only way it understands, which is to treat them as pads - something far different from what you expect.
  18. Based on my experience with now dated versions of ACAD, AutoCAD and VectorWorks handle scaling and units differently. All VW objects, as I understand it, are stored in memory as 1:1 in the underlying unit (I think it is millimeters, correct me if I am wrong about that). Layer scales, as Mark points out, only affect graphical display of the attributes he mentions, plus font size. You cannot change the way a line looks while working in a design layer. You can scale attributes in a Viewport by using the "Advanced Properties" dialog box in the OIP. But I use this only for instances when I want to output the content of a drawing at different scales in different Viewports. It makes no sense to have an arbitrary rule that design layers must always be 1:1. There is no difference in the drawing experience or actual geometry of objects drawn in layers with different scales, except with respect to the presentation attributes Mark and I have mentioned. If you want to know how your dashed lines will look, or how much space a block of text will take, draw in a design layer scaled to the output desired for the drawing.
  19. You are looking at either grayed layers (most likely) or classes. Check your navigation palette: is your general class setting (at the top) Show/Modify Others (it should be)? Are any individual classes set to gray that shouldn't? In the general layer setting, you should see either Show/Snap Others or Show/Modify Others. Are any of your individual layers gray that shouldn't be? BTW, when you take a screen shot like this it would be helpful if you included the navigation palette. Also, it is sometimes important to know the VW version you are using.
  20. Jim, I don't understand your comment. My understanding is that ECC detects and corrects errors in memory transfer between RAM and storage, which would be at the operating system level, not at the application level. Is there something I am not aware of?
  21. My dream stair tool would be one that could create 3d stairs from a 2d plan of the desired treads. I have to do it manually in order to create the custom stairs that are needed, more often than not, so it seems like a not-so-difficult task to automate that process.
  22. I would go with a Xeon multi-core processor.
  23. P Retondo

    Hardware check

    I have an XPS laptop purchased a couple of years ago with NVIDIA GeForce GT750M. Works great. I believe the XPS 13 will not accept the external video card, but the XPS 15 will. It also has the integrated Intel card, you have to select the discrete (go to the Control Panel/Device Manager) adaptor to get VW to work well.
  24. For me, having the site modifiers behave exactly the way solid addition and subtraction work would be the simplest and most powerful implementation. Boundary overlap would not be an issue.
  25. This is a common problem, and the more complex the site modifications the worse it gets. Although Alan's solution is spot on from a pragmatic point of view, the situation is not always this simple. It seems to me that the site model is long overdue for an upgrade. Layers of successive modifications should be handled by the software like subtractive instructions to a milling machine. Simpler, faster, more intuitive.
×
×
  • Create New...