Black matcap when object located on a curve #37663

New Issue

So3Datel · 2013-11-30T11:08:35+01:00

So3Datel commented

2013-11-30 11:08:35 +01:00

System Information
Windows 8x64
nVidia GTX 560 1GB

Blender Version
Broken: Blender 2.69

Sorry for my English, I use the Google translator

a short video (58 seconds).
I place an object on a curve, and then the object with the applied Mattsap becomes black
https://www.youtube.com/watch?v=rfIMdqdNFtw
Matcap_Bug.blend

**System Information** Windows 8x64 nVidia GTX 560 1GB **Blender Version** Broken: Blender 2.69 Sorry for my English, I use the Google translator a short video (58 seconds). I place an object on a curve, and then the object with the applied Mattsap becomes black https://www.youtube.com/watch?v=rfIMdqdNFtw [Matcap_Bug.blend](https://archive.blender.org/developer/F34691/Matcap_Bug.blend) ![2013-11-30_12-06_Blender.jpg](https://archive.blender.org/developer/F34692/2013-11-30_12-06_Blender.jpg)

So3Datel commented

2013-11-30 11:08:35 +01:00

Changed status to: 'Open'

So3Datel commented

2013-11-30 11:08:35 +01:00

Added subscriber: @AxelMening-4

So3Datel commented

2013-11-30 11:14:56 +01:00

Blender 2.69 r60995

Brecht Van Lommel changed title from ~~Black Matkap when object located on the curve~~ to Black matcap when object located on a curve

2013-12-01 14:53:40 +01:00

Brecht Van Lommel commented

2013-12-01 14:54:42 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2013-12-01 14:54:42 +01:00

I couldn't redo the problem yet on OS X. It seems in the video it works for a moment then stops working when you change the matcap, I tried this but still found no problem.

Does it show any error in the Window menu > Console?

I couldn't redo the problem yet on OS X. It seems in the video it works for a moment then stops working when you change the matcap, I tried this but still found no problem. Does it show any error in the Window menu > Console?

So3Datel commented

2013-12-01 15:21:06 +01:00

I asked other people to check this error on their computers, but no one responded.
If you tell me what to see or where to check for error messages, I'll do it. But I do not see any error messages.
Here's a video, it's about how I noticed it, I did the caterpillar to the tank, according to this principle, and matkap became black. On other objects Matcap works perfectly.
https://www.youtube.com/watch?v=1V1D-00efxE

I asked other people to check this error on their computers, but no one responded. If you tell me what to see or where to check for error messages, I'll do it. But I do not see any error messages. Here's a video, it's about how I noticed it, I did the caterpillar to the tank, according to this principle, and matkap became black. On other objects Matcap works perfectly. https://www.youtube.com/watch?v=1V1D-00efxE

Philipp Oeser commented

2013-12-01 15:57:37 +01:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2013-12-01 15:57:37 +01:00

I can confirm this on my laptop (havent checked my workstation)
This happens on object duplication types "frames", "verts" & "faces" (so doesnt really have to be on a curve) when you change the matcap and stays black even when changed back to the "original". [will try to have a look at code as well...]

my opengl specs

renderer: 'Mesa DRI Intel(R) Sandybridge Mobile '
vendor: 'Intel Open Source Technology Center'
version: '3.0 Mesa 9.2.3'

I can confirm this on my laptop (havent checked my workstation) This happens on object duplication types "frames", "verts" & "faces" (so doesnt really have to be on a curve) when you _change_ the matcap and stays black even when changed back to the "original". [will try to have a look at code as well...] **my opengl specs** renderer: 'Mesa DRI Intel(R) Sandybridge Mobile ' vendor: 'Intel Open Source Technology Center' version: '3.0 Mesa 9.2.3'

So3Datel commented

2013-12-01 17:35:23 +01:00

one guy with Win 7 x64 said that he's okay. He repeated an example of the video and it all works fine.
Sorry if this is a bug only on my machine

one guy with Win 7 x64 said that he's okay. He repeated an example of the video and it all works fine. Sorry if this is a bug only on my machine

Brecht Van Lommel commented

2013-12-01 17:54:31 +01:00

It seems we have it confirmed on two quite different configurations now, so there is most likely some sort of bug involved, like an invalid OpenGL state.

So3Datel commented

2013-12-01 17:57:51 +01:00

https://www.youtube.com/watch?v=J2xLy2M_G7E

So3Datel commented

2013-12-01 17:59:06 +01:00

thanks guys))

Sergey Sharybin self-assigned this 2013-12-02 10:03:41 +01:00

Sergey Sharybin commented

2013-12-02 10:03:41 +01:00

@brecht, can redo the issue here. Will look into it, but maybe i'll need some tips from you.

So3Datel commented

2013-12-02 10:11:53 +01:00

Sergey you speak Russian?
if I understand you correctly, and if you need something from me, I'll try to help

Sergey you speak Russian? if I understand you correctly, and if you need something from me, I'll try to help

Sergey Sharybin commented

2013-12-03 09:04:20 +01:00

@AxelMening-4 i indeed speak russian. Nothing needed from you at this point, i've tracked the issue down, but need @brecht's advice on how to best solve the issue.

@brecht, the issue is caused by GLSL used from inside of OpenGL list in function draw_dupli_objects_color. For some reason, shader doesn't work correct here on both integrated intel and nvidia optimus cards. My guess is that this happens because GLSL is being de-initialized after the object was drawn so shader can not access textures when called from the displist. And this actually applies to both matcap and regular GLSL viewport. Will submit patch which works here in a minute.

@AxelMening-4 i indeed speak russian. Nothing needed from you at this point, i've tracked the issue down, but need @brecht's advice on how to best solve the issue. @brecht, the issue is caused by GLSL used from inside of OpenGL list in function `draw_dupli_objects_color`. For some reason, shader doesn't work correct here on both integrated intel and nvidia optimus cards. My guess is that this happens because GLSL is being de-initialized after the object was drawn so shader can not access textures when called from the displist. And this actually applies to both matcap and regular GLSL viewport. Will submit patch which works here in a minute.

blender-admin commented

2013-12-03 17:14:16 +01:00

This issue was referenced by blender/blender-addons-contrib@4627516884

This issue was referenced by blender/blender-addons-contrib@462751688449108899a821f500cffc03658d6e3d

blender-admin commented

2013-12-03 17:14:16 +01:00

This issue was referenced by 4627516884

This issue was referenced by 462751688449108899a821f500cffc03658d6e3d

Sergey Sharybin commented

2013-12-03 17:14:35 +01:00

Changed status from 'Open' to: 'Resolved'

Sergey Sharybin closed this issue