Jump to content

Pat Stanford

Moderator
  • Posts

    12,530
  • Joined

  • Last visited

Posts posted by Pat Stanford

  1. @willofmaine I am not seeing this on my 16" MacBook Pro on Best Performance. Since this is driving you batty, can you take a few minutes to do a test please?

     

    Go to System Preferences:Users & Groups and create a new user. Log into that new user. Launch VW. Create a new blank file and do something that normally would not redraw until you zoom. Does it do so in this user?

     

    Open a drawing that normally requires zoom to get it to redraw. Change something and see if the zoom is required.

     

    The above tests will help determine if it is a problem with the file or with VW or with your User account.

     

    If you have already tried the above. Sorry about that.

    • Like 1
  2. As it was explained to me, in the current state, Materials were set first for objects that are likely to be "site built" and that having additional data about the area/volume/weight/etc. could provide value. Since the majority of doors/windows are purchased as complete units rather than as an assembly of pieces to be assembled on site, they were left for later.

     

    Materials do not have to be an all or nothing item. Using Materials on the components of a wall for instance might prove to be very useful in calculating the area or volume of each material in estimating. The use of materials in a concrete floor in a "second story" garage for a house on a hillside might prove very useful in calculating the weight the structure below has to support. The fact that they can not also be used to apply textures to a door is secondary.

     

    I don't know if trusses are Material Aware, but if they are it would provide an additional way to add the weight of the truss to a lighting position.

     

    One of the Beta testers believes that materials should be data only and that the attributes and textures have been added actually detract from their usefullness. That is what Classes are for.

     

    If Materials don't help your workflow, don't use them, but also keep an eye open for when they may provide value.

    • Like 4
  3. I have very bad eyes and a very low requirement for quality, so I think that even your original image looks very good.

     

    Yes there is a time difference if you go to higher standards. One possibility is to set the sheet layer resolution to something low to match the resolution you are running your monitor at so you are not calculating extra pixels while you are working. Then once you get it set the so you are ready to do the final, set the layer resolution up.

     

    Running at 150 dpi vs 300 dpi should take 1/4 of the time. Running at 100 dpi vs 300 dpi should take 11% of the time.

     

    HTH. Good Luck in finding your balance.

    • Like 1
  4. Hi Tom, thanks for sending the file. Much easier to see what is happening in your file than to try and create a sample. Answering here so it goes into the communal memory.

     

    You have your Autohybrid set to Use 2D Attributes of the Contained Object(s). I think this should actually be named Use 2D Attributes of the Sectioning Object(s). See the Fill section in the attached screen shot. Since this is not a Section, I think the lines are getting put into some kind of "virtual class" that is not the class of the objects and therefore not being properly overridden in the Viewport. In VW, Inc. terms, I would bet this is Working as Designed (WAD) rather than being a bug. Certainly worth submitting a Wish on if it bothers you.

     

    The work around is to set the Autohybrid to Use Class 2D Attributes. See the Line section in the attached screenshot. This will make the objects in the viewport actually use the class of the Autohybrid and allows the Class Override in the viewport to work.

     

    If you don't want to have to change all 29 instances manually, this can be changed in a worksheet relatively easily. Create a Worksheet. Create a Database using Type is AutoHybrid. Set the Column A Formula to Records:AutoHybrid:Below Cutplane Fill. Set the Column B formula to Below Cutplane Pen. Set Column A to SUMmarize.

    Select the only cell still showing click the Disclosure Triangle and change it to Use Class 2D Attributes. Repeat in Column B.

     

    image.thumb.png.ba88ed31c2e6e5b3fa35e31ada26d4f2.png

    • Like 1
  5. Are you running the latest Service Pack (I think it is SP5)? If you are, can you post a file showing the issue?

     

    And the usual trouble shooting steps:

    If you are using a Custom Workspace, try using one of the default workspaces. If that helps, then rebuild you custom workspace.

    If you are using a template that can come forward from previous versions, consider rebuilding your template.

    Try and temporarily move or rename your user folder and restart VW. If this helps, then you can keep using the new User Folder that VW automatically creates. If it does not help, then you delete the new one and restore the old User Folder and Restart VW.

  6. Disappearing objects are most often associated with Class Visibilities. 

    Do you happen to have the class of the Slab set to invisible? If it is the active class the slab will show, but when you switch to a different class it will become invisible.

  7. The PNG you uploaded is only 96 DPI, so it will be very difficult for anyone to really help based on the image. Can you export a high resolution PDF? 

     

    Also, what are the actual dimensions of the viewport? A very small viewport even at 300 dpi will still look pixelated when expanded to a larger size.

     

    What rendering mode are you using?

    • Like 1
  8. Be careful buying an older version of VW.  

     

    VW2016 will have basically zero "trade-in" value towards a newer version of VW and if you are on a Mac, the most recent version of the OS that it will run on is 10.12 (Sierra). 

     

    I would hate to see you spend money on an older version of VW and then find that you have to upgrade VW at near full price if you have to get new hardware. Unless you get a really good deal on the older version and consider it a sunk cost with basically no residual value, you might want to rethink your purchase plans.

     

    OS compatibility for VW versions are located at the following two links: 

     

     

  9. Hi Jeff,

     

    I am not intending to be negative, but based on the people posting here on the list, you seem to have more problems than most others. I am trying to think what we can do to help remedy that.

     

    I can think of five main reasons for this. Or maybe it is a combination of these five and others.

     

    1. Hardware issues. This may be the least likely reason, but it is always a possibility.

    2. Installation issues. If your installation somehow got corrupted, or your user folder has corruption, or a workspace that has been brought forward a number of versions, that could cause problems that others are not seeing.

    3. Usage Style. Perhaps your usage of VW just happens to hit more problem areas in VW than other users.

    4. Care about details. Perhaps you care more about details or workflow than others on the forum. From some of the people I know on the list, this is also likely not the case.

    5. Thought pattern. I like VW. Even though I don't get to use it that much, VW and I "think" in similar fashion. This makes it relatively easy for me to figure out what is happening a lot of the time. If you don't "think" like VW, then I could imagine it being a very frustrating experience to use it.

     

    Can you point to one of the above items or add others that you think exacerbate your issues?

     

    I can tell from you post you are frustrated, but it does not give us very much to go on to help you with your current problem, or to help make Enhancement Requests to try and make things better for the future.

     

    There are people here on the forum who are paying attention and who do care that you are having issues.

     

    Let us know what we can do to help.

    • Like 1
  10. Pure guess on my part, but I don't expect there will be a version of VW2021 released (except possibly to beta testers) that will be M1 native or even a universal binary. Too many possible things to go wrong to put it out for general consumption.

     

    Another pure guess is that there is a version running in Maryland that is as close to a native M1 app as they can achieve based on the libraries they are using.

    • Like 3
  11. I am working from memory here, so apologies if I am wrong. I just tried this in VW2021 and did not see the behavior I am remembering, so either it has been changed, or I am just not doing the tasing correctly.

     

    In my memory at least some types of objects moved back to their original creation location when they were edited. I don't think it was all objects, but I can't remember which types.

     

    Basically, going back to the original 2D objects the 3D was created from (By Edit Solid/Enter Group) at some point you ended up with objects that were at a different point in space than where the 3D object was. Like it was storing the creation and some form of position translation that you could not easily access. If you went back far enough in the history eventually you would get objects that were back to where they were when the object was originally created.

     

    Am I being clear enough?  Maybe someone who has a better recollection of this will chime in.

     

    HTH

  12. Cut and Paste in Place is the best way to get an object out of a group.

     

    How would VW know where you want to object to go (if say the object is in a group, in a group, in a group, in a viewport annotation) unless you go to that point and Paste in Place?

     

    ;-)

     

×
×
  • Create New...