[2017] Opensubdiv bug

RGhost77 · ‎05-06-2016

Hello! Can someone confirm this bug?

(my config: gtx770, win7, geforce driver 365.10)

Royal Ghost | veda3d.com

jens.diemer · ‎05-09-2016

I can't see the video...

Jens

------------------------------------------------------------------------------------------------------------------
https://github.com/jedie/3dsmax_bugs | https://github.com/jedie/3dsmax_patches

RGhost77 · ‎05-09-2016

Royal Ghost | veda3d.com

jens.diemer · ‎05-09-2016

I confirm this...

It's not needet to convert to poly!

Just put a opensubdiv with GPU to a teapot...

Also "funny": Put opensubdiv on a GeoSphere: You can't select it in viewport, If GPU is enabled...

Jens

------------------------------------------------------------------------------------------------------------------
https://github.com/jedie/3dsmax_bugs | https://github.com/jedie/3dsmax_patches

Anonymous · ‎05-09-2016

@jens.diemer wrote:

Also "funny": Put opensubdiv on a GeoSphere: You can't select it in viewport, If GPU is enabled...

Turn on 'Adaptive' and you can select it again. 😉 And btw, i can confirm this bug.

RGhost77 · ‎05-17-2016

Submitted:

BSPR-24235 Broken opensubdiv modifier (gpu mode)

Royal Ghost | veda3d.com

RGhost77 · ‎07-29-2016

Arrgg... SP2 doesn't fix it

Royal Ghost | veda3d.com

spacefrog_ · ‎07-29-2016

Besides the disappearing mesh display after you apply a material, what's the actual problem ?

I can't get that out of the video, i can select everything just fine, with or with out GPU display mode

And IMHO titles for bug reports like "xyz is broken" are not really meaning- or useful ...

Josef Wienerroither
Software Developer & 3d Artist Hybrid

Anonymous · ‎07-29-2016

The selection bug seems to be fixed now. Disappearing mesh with OpenSubdiv/GPU is still happening if you use a single material.

Using a Multi/Sub material as workaround and the problem is gone.Using Performance mode works too.

Maybe it`s a GPU related bug, i`m using a GTX970?

Alfred.DeFlaminis · ‎07-29-2016

Hello,

Thank you all for taking the time to detail this problem. It has already been logged in our bug tracking system, and I appreciate the effort in listing the steps to reproduce the bug so that I may expand the entry. I can confirm that this is unintended behavior for the modifier.

Please hit the "Accept as Solution" button if my post fully solves your issue or answers your question. This lets me know that I was effective in helping you, and thank you for doing so.

Best Regards,

RGhost77 · ‎09-30-2016

Service Pack 3... not fixed.

p.s. It that true, really no one does not use GPU acceleration of opensubdiv?! Or maybe opensubdiv at all

Royal Ghost | veda3d.com

Alfred.DeFlaminis · ‎09-30-2016

Hello @RGhost77,

Yes it seems this wasn't addressed in the latest service pack, but I do see some developer communications regarding this issue so I know that there has been some discussion about it. I know that's not much help here. I do think people are using it as this thread has something like 268+ views at the time of this post. I think that users are finding the workaround posted by @Anonymous and just working around it.

After our last communications, I did some more testing with this issue. It's definitely a Nitrous issue as changing to say Direct3D does solve the problem. Another thing that worked for me (in Nitrous 11 so no need to revert) is to simply switch to object color shaded mode when working on these objects. Sure, it's not a fix... but it's far less painful that having to work in D3D or restarting Max to switch between display drivers. (Image below.) I guessed this would work because I knew that Nitrous was at the heart of this particular issue. Hopefully this helps a bit, certainly it's faster than making MSO's for your mats just to model.

Best Regards,