Creating Armature > Single Bone makes 1st Mesh Object in Scene Invisible when Selected. #55871

New Issue

Gibran Kaleel · 2018-07-09T18:02:35+02:00

Gibran Kaleel commented

2018-07-09 18:02:35 +02:00

System Information
Windows 10 Pro x64 - 1703
GTX 970 (398.36 WHQL)

Blender Version
Broken: 2.8 Alpha a6340a5 (Also previous 2.8 versions.)
Worked: 2.79 seems to be Ok.

Short description of error
Armature > Single Bone is created in scene. 1st Mesh Object created becomes Invisible (Screenshot 1)

Exact steps for others to reproduce the error

Start with New & Empty scene. (Delete default cube if necessary, but if you keep it. That's the object that becomes invisible.)
Create 2-3 Mesh Objects. (eg. I've created 2 cubes and 1 UV Sphere.)
Create Armature > Single Bone. (Move it away from origin.)
De-Select All > Select 1st Mesh Object. (Alternatively you can directly select the 1st mesh object without de-select all. Result is the same.)
It becomes Invisible. (Only shows selection outline.)

Tested:

It doesn't matter if you select the 2nd or 3rd mesh objects right after creating the armature > bone. Only the 1st created mesh object becomes invisible. (Screenshot 2)
Happens in all 3 render engines. (Cycles/Eevee/Workbench)
Switching between Rendering Modes (Solid/LookDev/Rendered) brings back the invisible object to view. --- Selecting the 'Affected' object > Toggle In-Out of Edit Mode > Selecting another object > Makes the 1st (affected) object invisible again.
Switching between Shading Modes & Colors (Flat/Studio/MatCap - Single/Material/Random/Textured) brings back the object to view. --- Selecting the 'Affected' object > Toggle In-Out of Edit Mode > Selecting another object > Makes it invisible.
Toggle In-Out of X-Ray Mode, brings back the object to view. Selecting the 'Affected' object > Toggle In-Out of Edit Mode > Selecting another object > Makes it invisible.

Comments: I know this is not a Blocker or Crash. But reporting it for Future Reference in-case more user reporting is required when trying to reproduce this bug. If more information is required, I'll be happy to help. :)

Screenshot 1:

Screenshot 2:

**System Information** Windows 10 Pro x64 - 1703 GTX 970 (398.36 WHQL) **Blender Version** Broken: 2.8 Alpha a6340a5 *(Also previous 2.8 versions.)* Worked: 2.79 seems to be Ok. **Short description of error** Armature > Single Bone is created in scene. 1st **Mesh Object** created becomes **Invisible** *(Screenshot 1)* **Exact steps for others to reproduce the error** 1. Start with **New & Empty** scene. *(Delete default cube if necessary, but if you keep it. That's the object that becomes invisible.)* 2. Create 2-3 Mesh Objects. *(eg. I've created 2 cubes and 1 UV Sphere.)* 3. Create Armature > Single Bone. *(Move it away from origin.)* 4. De-Select All > Select 1st Mesh Object. *(Alternatively you can directly select the 1st mesh object without de-select all. Result is the same.)* 5. It becomes **Invisible**. *(Only shows selection outline.)* **Tested:** 1. It doesn't matter if you select the 2nd or 3rd mesh objects right after creating the armature > bone. Only the 1st created mesh object becomes invisible. *(Screenshot 2)* 2. Happens in all 3 render engines. *(Cycles/Eevee/Workbench)* 3. Switching between **Rendering Modes** (Solid/LookDev/Rendered) brings back the invisible object to view. --- Selecting the 'Affected' object > **Toggle In-Out of Edit Mode** > Selecting another object > Makes the 1st *(affected)* object invisible again. 4. Switching between **Shading Modes & Colors** (Flat/Studio/MatCap - Single/Material/Random/Textured) brings back the object to view. --- Selecting the 'Affected' object > **Toggle In-Out of Edit Mode** > Selecting another object > Makes it invisible. 5. Toggle In-Out of X-Ray Mode, brings back the object to view. Selecting the 'Affected' object > **Toggle In-Out of Edit Mode** > Selecting another object > Makes it invisible. **Comments:** I know this is not a **Blocker** or **Crash**. But reporting it for **Future Reference** in-case more user reporting is required when trying to reproduce this bug. If more information is required, I'll be happy to help. :) Screenshot 1: ![Select_Object_Invis_1.png](https://archive.blender.org/developer/F3897252/Select_Object_Invis_1.png) Screenshot 2: ![Select_Object_Invis_2.png](https://archive.blender.org/developer/F3897254/Select_Object_Invis_2.png)

Gibran Kaleel commented

2018-07-09 18:02:35 +02:00

Added subscriber: @JonDoe286

Campbell Barton commented

2018-07-10 09:07:37 +02:00

Added subscriber: @ideasman42

Campbell Barton commented

2018-07-10 09:07:37 +02:00

Could you upload blend saved in invalid state (can't redo here).

Gibran Kaleel commented

2018-07-10 09:20:56 +02:00

@ideasman42 Here you go. :) Also, it seems to happen the same with today's compile. 1112f49 Open the file in 2.8 and click on one of the other objects. The 1st Mesh Object 'Cube' goes invis. Changing rendering modes, toggling x-ray seems to fix it. But select 1st object and toggle edit mode and click something else, it happens again.

invisible_first_mesh_object.blend

@ideasman42 Here you go. :) Also, it seems to happen the same with today's compile. 1112f49 Open the file in 2.8 and click on one of the other objects. The 1st Mesh Object 'Cube' goes invis. Changing rendering modes, toggling x-ray seems to fix it. But select 1st object and toggle edit mode and click something else, it happens again. [invisible_first_mesh_object.blend](https://archive.blender.org/developer/F3904158/invisible_first_mesh_object.blend)

Campbell Barton commented

2018-07-10 09:42:22 +02:00

Changed status from 'Open' to: 'Archived'

Campbell Barton closed this issue

2018-07-10 09:42:22 +02:00

Campbell Barton self-assigned this 2018-07-10 09:42:22 +02:00

Campbell Barton commented

2018-07-10 09:42:22 +02:00

Still can't redo, string since nvidia normally works well with Blender:

OS: Linux 4.17.4-1-ARCH
REV: 10b976d2eb8a5de24c19bbb469005d59c6cd7c17
GPU: GeForce GTX 1080

Note that we're only accepting crashes at the moment, if this issue keeps happening after the 2.8 release-candidate, this can be re-opened.

It's too early to debug hardware spesific glitches.

Still can't redo, string since nvidia normally works well with Blender: * OS: Linux 4.17.4-1-ARCH * REV: `10b976d2eb8a5de24c19bbb469005d59c6cd7c17` * GPU: `GeForce GTX 1080` ---- Note that we're only accepting crashes at the moment, if this issue keeps happening after the 2.8 release-candidate, this can be re-opened. It's too early to debug hardware spesific glitches.

Gibran Kaleel commented

2018-07-10 10:19:09 +02:00

@ideasman42 Yeah, it's all good man. It's why I opened the task as *Low Priority. Just wanted to report my findings for when it's more widely reproducible. Later if this starts happening more obviously, then we'll always have some data to refer back to. Doesn't really affect my work since I don't use armatures much. Still, thought I should report it and let you guys know about it. :) There was another user who reported invisible objects in viewport. But that was from a fresh scene, nothing to do with bones being added. Maybe it's a Windows OS thing. Anyway, I'm sure this might fix itself as more compatibility code is added for openGL and graphics drivers. If not, we can always come back to it later. Cheers 'n Thanks again for looking into it.

@ideasman42 Yeah, it's all good man. It's why I opened the task as **Low* Priority. Just wanted to report my findings for when it's more widely reproducible. Later if this starts happening more obviously, then we'll always have some data to refer back to. Doesn't really affect my work since I don't use armatures much. Still, thought I should report it and let you guys know about it. :) There was another user who reported invisible objects in viewport. But that was from a fresh scene, nothing to do with bones being added. Maybe it's a Windows OS thing. Anyway, I'm sure this might fix itself as more compatibility code is added for openGL and graphics drivers. If not, we can always come back to it later. Cheers 'n Thanks again for looking into it.

Gibran Kaleel commented

2018-07-11 03:50:03 +02:00

@ideasman42 Hi Campbell. I know this is archived but I wanted to try and find a fix for the issue. And I think I did. :) Re-Assigning the default material to the object that becomes invisible after dropping a bone into the scene seems to fix the issue. Tabbing In/Out of Edit Mode and Selecting another object doesn't seem to cause it to go invisible again like before. Here's a video with the step-by-step.

Blender_2.8_Object_Invisible_Fix.mp4

Seems to be an issue with the default material getting removed from the first mesh object created whenever a bone is dropped into the scene. Even though the default cube shows default material applied in list. Re-assigning it seems to work. Strange...

Also note, if default cube is deleted and new mesh object is created. It still goes invisible. (As long as it's the first mesh object in scene.) Material panel might not show anything assigned. But assigning the default material fixes that too.

I know this doesn't affect my workflow since I currently don't have to work with armatures. But I can imagine someone trying to rig a character for posing or animation having trouble if this happens.

Again, Apologies for adding to an archived task. But someday if this bug becomes widespread among 2.8 users, and when we move to bug fixing/testing phase. I hope this info will be helpful. :)

BTW, This was my 1st video file share on the site. Please let me know if there is anything I could do better when sharing. Like upload to YouTube and share link, etc. This was a small file so uploaded directly. Installed a screen capture app so I can share steps for bugs & crashes. Seemed easier and more informative than screenshots.

system-info.txt

@ideasman42 Hi Campbell. I know this is archived but I wanted to try and find a fix for the issue. And I think I did. :) Re-Assigning the default material to the object that becomes invisible after dropping a bone into the scene seems to fix the issue. Tabbing In/Out of Edit Mode and Selecting another object doesn't seem to cause it to go invisible again like before. Here's a video with the step-by-step. [Blender_2.8_Object_Invisible_Fix.mp4](https://archive.blender.org/developer/F3909923/Blender_2.8_Object_Invisible_Fix.mp4) Seems to be an issue with the default material getting removed from the first mesh object created whenever a bone is dropped into the scene. Even though the default cube shows default material applied in list. Re-assigning it seems to work. Strange... Also note, if default cube is deleted and new mesh object is created. It still goes invisible. *(As long as it's the first mesh object in scene.)* Material panel might not show anything assigned. But assigning the default material fixes that too. I know this doesn't affect my workflow since I currently don't have to work with armatures. But I can imagine someone trying to rig a character for posing or animation having trouble if this happens. Again, Apologies for adding to an archived task. But someday if this bug becomes widespread among 2.8 users, and when we move to bug fixing/testing phase. I hope this info will be helpful. :) BTW, This was my 1st video file share on the site. Please let me know if there is anything I could do better when sharing. Like upload to YouTube and share link, etc. This was a small file so uploaded directly. Installed a screen capture app so I can share steps for bugs & crashes. Seemed easier and more informative than screenshots. [system-info.txt](https://archive.blender.org/developer/F3910017/system-info.txt)

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Creating Armature > Single Bone makes 1st Mesh Object in Scene Invisible when Selected. #55871