Hypermesh 2017.1 Midsurfacing Error

Burner2k
Burner2k Altair Community Member
edited October 2020 in Community Q&A

I hope I'm not the only one with this issue. Last week, my HW program was updated to 2017.1 and I've been noticing some issues with Mid-surfacing function. I usually set my mid-surfacing extraction options to 'Sorted Result' and choose one of the options. This feature worked with no issues in v2017 and prior. However in the latest version, I am noticing some unusual results. First time I do it with a component, it works as intended. If I follow with same mid-surfacing command, the extraction happens but I see no new mid-surface. Instead, I see the previous mid-surface sorted component 'show or unhide' itself with the new mid-surface not to be seen. No new comp with new mid-surface is created as well. If I chose, a different naming convention from 'sorted component', same thing as before except that previous created mid-surf component is getting deleted. 

 

The work around I found is to set the extraction options to 'result in Midsurface comp' and then manually rename the component. Obviously this gets tedious. I just wanted to find out if others are facing similar issues. 

Tagged:

Answers

  • Rahul Rajan_21763
    Rahul Rajan_21763 New Altair Community Member
    edited May 2017

    Hi,

    Thanks for reporting this issue to us.I too able to replicate this issue in 2017.1.We will raise this issue to the development team. 

  • Burner2k
    Burner2k Altair Community Member
    edited August 2017

    Hello,

    I think Altair has released an update to the Hyperworks application 2017.2. Does the update contain resolution to the above Midsurfacing error in HyperMesh? I want through the release notes presentation and I was able to spot any references to the above. 

  • Rahul Rajan_21763
    Rahul Rajan_21763 New Altair Community Member
    edited August 2017

    This is planned for HW 2018.0 release.So this is still not fixed in 2017.2.

Categories