Full Scene Geo Refresh WIth Sculpt Tools over 200 objects

[Anonymous]

Okay spent an hour messing with this and found a weird bug. With a lot of objects in a scene, switching to or from a sculpting tool will force a full scene refresh. After some experimentation I found there is an exact threshold for this. Once a scene exceeds 200 meshes this starts happening. Try it on a new scene with 200 cubes, activating a sculpt brush on one doesn't refresh the whole scene. Duplicate one so you have 201 total and then it does.

See the video:

 The refresh isn't so bad with just cubes but this is really painful and slow with even reasonable light geo, and especially when some of it is textured. 

This is with 2018.2 and 2018.3 on Linux. Latest NVIDIA driver. Tried with completely clean prefs too.

Any ideas?

[sean.heasley]

Hi @Anonymous

Thanks for posting this along with a video and steps to reproduce!

I was able to reproduce this issue and I'm on a Windows machine so it looks like this is across all versions of Maya.

Like you said, the issue isn't too bad when working with basic primitives but I'm curious how it is with one of your scenes.

When you get a chance, can you please post another video of this impacting your scene file so I can add it to a report I'll pass along to the devs so they can work on a fix?

Please let me know if anything changes!

[sean.heasley]

Hi @Anonymous

Just wanted to check in to see how things were going. When you get a chance can you please post a video of this affecting your scene file?

[Anonymous]

Yes I will add another video tonight. Thanks Sean.

[Anonymous]

Here's an example with a scene of ~1000 objects (~180k polys). The delay is more noticeable than with the cubes.

At some point I noticed that assigning a new shader to the object first would actually prevent this from happening - as though you need 200+ objects with the same shader as the object being sculpted to trigger the refresh. But I can't seem to reproduce that now.

[sean.heasley]

Hi @Anonymous

Thanks for attaching the video!

I went ahead and logged this with our dev team as a known issue with repro steps so they'll be able to work on a fix for a future update!

[Anonymous]

Thanks Sean.

This one might be worth forward to them as well. This scene has just over 1000 meshes, a total of 160000 polys, and as you can see the delay for the refresh is much worse than the previous videos. All the geometry is sharing a shader (blinn), and most of it is hidden. Not sure if that helps any further but thought it was worth sharing as an example of how bad this can get.

edit:

It seems like the more hidden objects there are, the worse this issue is. If I unhide everything the effect is closer to the previous 2 videos. Same goes for isolate select.

[sean.heasley]

Hi @Anonymous

Thanks for adding this! The note on amount of object hidden effecting the refresh should help them a lot with finding what's causing the issue!