Switching between viewport shading modes causes models to become invisible if they use vertex colours (Pose mode) #72823

Closed
opened 2019-12-31 17:58:33 +01:00 by Fox · 10 comments

System Information
Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: blender/blender@26bd5ebd42

Addon Information
Name: Rigify (0, 6, 0)
Author: Nathan Vegdahl, Lucio Rossi, Ivan Cappiello, Alexander Gavrilov

Short description of error
I'm working with a model that uses vertex colours for its texture. I have to use the Workbench render engine to display them (setting Color to Vertex, unsurprisingly). When I parent a rig to the model it behaves as expected except that switching between viewport modes results in the model becoming invisible in the "rendered" viewport mode. Making changes, saving the file, then restarting Blender causes the model to reappear again (until one switches modes again).

It may be related to the selected object as it's also possible for the bones to become invisible with only the connecting joints visible (resulting in the appearance of a bubble cloud, for want of a better description). That may be intentional though as it seems to be something to do with toggling X-ray:
Screen Shot 2019-12-31 at 16.14.34.png
The bones stay looking like that in wireframe mode regardless of whether X-ray is on or not. Again, that may be how it's supposed to work.

Exact steps for others to reproduce the error
The mesh in question is generated by this site . It creates a Wavefront OBJ file with vertex colours, something the format doesn't officially support. I then open the file in MeshLab and export it as Stanford PLY, which*does// support vertex colours. I then import that model into Blender.

The model is a bit blocky so I use a Smooth modifier which I then apply (factor 2.0, repeat 3, all other settings default).

Align the model with the face part of the default human rig, parent them with automatic weights.

Enter pose mode:
Screen Shot 2019-12-31 at 16.50.41.png

Switch to solid viewport shading, enable X-ray mode to see the bones. Select one or more.
Switch back to rendered viewport shading.
Screen Shot 2019-12-31 at 16.53.21.png

Here's the file I was working on:
myface.blend

**System Information** Operating system: Darwin-17.7.0-x86_64-i386-64bit 64 Bits Graphics card: NVIDIA GeForce GT 750M OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.32.0 355.11.10.10.40.102 **Blender Version** Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: `blender/blender@26bd5ebd42` **Addon Information** Name: Rigify (0, 6, 0) Author: Nathan Vegdahl, Lucio Rossi, Ivan Cappiello, Alexander Gavrilov **Short description of error** I'm working with a model that uses vertex colours for its texture. I have to use the Workbench render engine to display them (setting Color to Vertex, unsurprisingly). When I parent a rig to the model it behaves as expected except that switching between viewport modes results in the model becoming invisible in the "rendered" viewport mode. Making changes, saving the file, then restarting Blender causes the model to reappear again (until one switches modes again). It may be related to the selected object as it's also possible for the bones to become invisible with only the connecting joints visible (resulting in the appearance of a bubble cloud, for want of a better description). That may be intentional though as it seems to be something to do with toggling X-ray: ![Screen Shot 2019-12-31 at 16.14.34.png](https://archive.blender.org/developer/F8253533/Screen_Shot_2019-12-31_at_16.14.34.png) The bones stay looking like that in wireframe mode regardless of whether X-ray is on or not. Again, that may be how it's supposed to work. **Exact steps for others to reproduce the error** The mesh in question is generated by [this site ](https:*cvl-demos.cs.nott.ac.uk/vrn/). It creates a Wavefront OBJ file with vertex colours, something the format doesn't officially support. I then open the file in MeshLab and export it as Stanford PLY, which*does// support vertex colours. I then import that model into Blender. The model is a bit blocky so I use a Smooth modifier which I then apply (factor 2.0, repeat 3, all other settings default). Align the model with the face part of the default human rig, parent them with automatic weights. Enter pose mode: ![Screen Shot 2019-12-31 at 16.50.41.png](https://archive.blender.org/developer/F8253576/Screen_Shot_2019-12-31_at_16.50.41.png) Switch to solid viewport shading, enable X-ray mode to see the bones. Select one or more. Switch back to rendered viewport shading. ![Screen Shot 2019-12-31 at 16.53.21.png](https://archive.blender.org/developer/F8253582/Screen_Shot_2019-12-31_at_16.53.21.png) Here's the file I was working on: [myface.blend](https://archive.blender.org/developer/F8253585/myface.blend)
Author

Added subscriber: @Flamekebab

Added subscriber: @Flamekebab
Member

Added subscriber: @EitanSomething

Added subscriber: @EitanSomething
Member

Changed status from 'Needs Triage' to: 'Needs User Info'

Changed status from 'Needs Triage' to: 'Needs User Info'
Member

Is this still an issue with 2.83?

Is this still an issue with 2.83?
Author

As far as I can tell no, it's now fixed! Fantastic!

As far as I can tell no, it's now fixed! Fantastic!
Member

Changed status from 'Needs User Info' to: 'Needs Triage'

Changed status from 'Needs User Info' to: 'Needs Triage'
Member

I’m just going through all the bugs from 2.80 to 2.82 to see if they have been inadvertently fix to get a better picture of the number of bugs. Sorry for any inconvenience

I’m just going through all the bugs from 2.80 to 2.82 to see if they have been inadvertently fix to get a better picture of the number of bugs. Sorry for any inconvenience

Added subscriber: @mano-wii

Added subscriber: @mano-wii

Changed status from 'Needs Triage' to: 'Resolved'

Changed status from 'Needs Triage' to: 'Resolved'
Germano Cavalcante self-assigned this 2020-05-01 02:26:30 +02:00

If I understand correctly, the problem seems to have been fixed.
So closing as resolved.

If I understand correctly, the problem seems to have been fixed. So closing as resolved.
Sign in to join this conversation.
No Milestone
No project
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender-addons#72823
No description provided.