Mesh & NURBS surfaces section incorrectly

[line-weight]

The top image shows two surfaces, sectioned using the clip cube. The one on the left is a mesh; the one on the right is a NURBS surface. In the OpenGL clip cube, the section is correct.

 

However, in a section viewport, they are not sectioned correctly, with an extra line joining the two ends of the line that represents the section through the surface. This is shown in the second image.

 

I have attached the file.

 

surfacesect.vwx

[Kevin McAllister]

It looks like the issue may have been fixed in VW2019. I opened your file, updated the viewport and the sections are correct 😕

 

Kevin

 

[line-weight]

Ho hum. I guess it's a bug in 2018 that will never be fixed, then.

 

Time for me to waste yet more productive time making a workaround.

 

It seems the same applies to subdivision surfaces.

 

Eurghh!!

 

[line-weight]

So I've just tried opening this file in 2017 - and the error is not there.

 

This means that this is another example of something that was broken in 2018, and we are now left with a 'final' version of 2018 where it's not fixed.

 

Whereas it has been fixed in 2019.

 

So, the software that I paid for can't do something pretty fundamental which means that I can't generate correct section viewports from a model without having to avoid certain object types (any kind of multiplanar 'surface' object seems to be out).

 

Can anyone from VW comment - given that the error is not present in either 2017 or 2019, it seems to me that the decision not to fix stuff like this in 2018 is a commercial rather than a technical one.

[Gadzooks]

48 minutes ago, line-weight said:

Can anyone from VW comment - given that the error is not present in either 2017 or 2019, it seems to me that the decision not to fix stuff like this in 2018 is a commercial rather than a technical one.

 

^^^^^^ Yes please.

 

 

Edit/Update

 

Just tried this with a section generated from Clip Cube and it works as it should (somebody test this please - could be I have that Friday feeling and everything is good!!)

 

Update

Sorry - must learn to read the OP thoroughly - you already said that.

 

 

Edited February 8, 2019 by Gadzooks

[PVA - Admin]

2 hours ago, line-weight said:

Can anyone from VW comment - given that the error is not present in either 2017 or 2019, it seems to me that the decision not to fix stuff like this in 2018 is a commercial rather than a technical one.

Not in this case, no. Even though they are progressive in version numbering, development is not always so linear. 2018 had significant display issues, caused by a system that was fixed in 20019 but was a completely different and older system in 2017. Even though a lot of it might look the same on the top, the guts change all the time as we try to make things faster.