"Visible Only" Button Missing for 2019

User: "nreindel"
Altair Community Member
Updated by nreindel

Hello everyone,

 

I'm working on geometry cleanup and meshing in Hypermesh Desktop 2019, and I've just noticed that the 'Visible Only On/Off' buttons are no longer in the menu that comes up from using shift/right click. Attached are the pictures of the menu in Hypermesh Desktop 2017 and 2019, respectively.

 

image.png.7d101418ba9aedd817be041bc927d3b1.png      image.png.2d669357d2d7512038585c76a77c017d.png

 

With this button missing, how do I toggle 'visible only' for selection?

Thank you,

 

Nathan

Find more posts tagged with

Sort by:
1 - 3 of 31
    User: "Rahul Rajan_21763"
    New Altair Community Member
    Updated by Rahul Rajan_21763

    'Strange' behaviors in HW are usually due to corruption of the session files. Deleting the session files should restore HW to their original state. 

    https://community.altair.com/community?id=community_question&sys_id=044688761b2bd0908017dc61ec4bcb69

     

    User: "QuyNguyenDai"
    Altair Community Member
    Updated by QuyNguyenDai

    Hello everyone,

     

    I'm working on geometry cleanup and meshing in Hypermesh Desktop 2019, and I've just noticed that the 'Visible Only On/Off' buttons are no longer in the menu that comes up from using shift/right click. Attached are the pictures of the menu in Hypermesh Desktop 2017 and 2019, respectively.

     

    <?xml version="1.0" encoding="UTF-8"?>image.png.7d101418ba9aedd817be041bc927d3b1.png      <?xml version="1.0" encoding="UTF-8"?>image.png.2d669357d2d7512038585c76a77c017d.png

     

    With this button missing, how do I toggle 'visible only' for selection?

    Thank you,

     

    Nathan

     

    I have 'Visible only on/off' on my Hypermesh Desktop 2019.

     

    User: "nreindel"
    Altair Community Member
    OP
    Updated by nreindel

    Thanks for the help. It actually ended up being a simpler solution that deleting settings files. Closing all sessions and restarting the computer fixed the issue.

     

    Cheers,

     

    Nathan