Vertex Paint... not painting in the ViewPort #49220

New Issue

Luca Crisi · 2016-09-01T13:34:31+02:00

Luca Crisi commented

2016-09-01 13:34:31 +02:00

Vertex Paint... is not painting in the ViewPort

OS: Windows 8.1 64 bit
GPU: nVidia GT740M

Not working Blender Version: 2.77a
Working Blender Version: 2.75

Said that i unwrapped the object and subdivided it a lot, when I try to vertex paint (using the draw brush) it in any color, nothing is painted.
But, the default "Col" Vertex Color group is being correctly created in the Object Data panel.

Possibly, the group contains the stroke info, but it's simply not drawn onto the mesh at paint time?

Vertex Paint... is not painting in the ViewPort OS: Windows 8.1 64 bit GPU: nVidia GT740M Not working Blender Version: 2.77a Working Blender Version: 2.75 Said that i unwrapped the object and subdivided it a lot, when I try to vertex paint (using the draw brush) it in any color, nothing is painted. But, the default "Col" Vertex Color group is being correctly created in the Object Data panel. Possibly, the group contains the stroke info, but it's simply not drawn onto the mesh at paint time?

Luca Crisi commented

2016-09-01 13:34:31 +02:00

Changed status to: 'Open'

Luca Crisi commented

2016-09-01 13:34:31 +02:00

Added subscriber: @BugFinder

blender-admin commented

2016-09-01 13:34:31 +02:00

#49221 was marked as duplicate of this issue

Sergey Sharybin commented

2016-09-01 14:44:18 +02:00

Added subscriber: @Sergey

Sergey Sharybin commented

2016-09-01 14:44:18 +02:00

Please don't use regressions project unless the thing worked in latest stable release. This project is used to indicate whether we've got show stoppers for the upcoming release.

As for the bug itself i can't reproduce it. Several things:

Test if 2.78 testbuild2 - works for you.
Test if latest buildbot build works for you.
Provide exact steps with .blend file included which indicates the problem.
http://download.blender.org/release/Blender2.78/

Please don't use regressions project unless the thing worked in latest stable release. This project is used to indicate whether we've got show stoppers for the upcoming release. As for the bug itself i can't reproduce it. Several things: - Test if 2.78 testbuild2 - [x] works for you. - Test if latest buildbot build works for you. - Provide exact steps with .blend file included which indicates the problem. - [x] http://download.blender.org/release/Blender2.78/

Luca Crisi commented

2016-09-01 14:54:04 +02:00

Added the duplicate because I erroneously reported this bug the first time as REGRESSION.

I will not install a NOT OFFICIAL release:
There are already enough bugs in the official ones!

Steps to reproduce the bug (do you really need a .blend file for this?):

Unwrap an object and subdivided it a lot
Try to vertex paint (using the draw brush) it in any color: nothing is painted.

The default "Col" Vertex Color group is being created in the Object Data panel...
Without the color data, of course.

Added the duplicate because I erroneously reported this bug the first time as REGRESSION. I will not install a NOT OFFICIAL release: There are already enough bugs in the official ones! Steps to reproduce the bug (do you really need a .blend file for this?): * Unwrap an object and subdivided it a lot * Try to vertex paint (using the draw brush) it in any color: nothing is painted. The default "Col" Vertex Color group is being created in the Object Data panel... Without the color data, of course.

Sergey Sharybin commented

2016-09-01 15:06:55 +02:00

There is no need to install anything, you can download. zip archive, unpack it to any location, perform required tests and then remove the testbuild once you're done. This is the only way we can know if something is still affecting upcoming releases or not.

I did exact same steps on a default cude and did not see any issues. There are lots of various settings in blender and the only reliable way to know if something is not caused by specific combinations of those settings is to provide .blend file.

Also, are there any errors printed to the console when you're painting?

There is no need to install anything, you can download. zip archive, unpack it to any location, perform required tests and then remove the testbuild once you're done. This is the only way we can know if something is still affecting upcoming releases or not. I did exact same steps on a default cude and did not see any issues. There are lots of various settings in blender and the only reliable way to know if something is not caused by specific combinations of those settings is to provide .blend file. Also, are there any errors printed to the console when you're painting?

Luca Crisi commented

2016-09-01 15:08:32 +02:00

It is supposed to be a red perimeter (or circumference) around the island mesh, since I vertex painted it all around it.

Instead, there is NOTHING.

And, yes, all the normals are facing UP

![Vertex NOT Paint.png](https://archive.blender.org/developer/F349682/Vertex_NOT_Paint.png) It is supposed to be a red perimeter (or circumference) around the island mesh, since I vertex painted it all around it. Instead, there is NOTHING. And, yes, all the normals are facing UP

Luca Crisi commented

2016-09-01 15:14:49 +02:00

Test File:

There should be a red paint on that RoundCube
But there isn't

Vertex NOT Paint 02.blend

Test File: There should be a red paint on that RoundCube But there isn't ![Vertex NOT Paint 02.png](https://archive.blender.org/developer/F349685/Vertex_NOT_Paint_02.png) [Vertex NOT Paint 02.blend](https://archive.blender.org/developer/F349684/Vertex_NOT_Paint_02.blend)

Luca Crisi commented

2016-09-01 16:10:09 +02:00

And... no. TestBuild 2 FAILED: Same result

And... no. TestBuild 2 **FAILED**: Same result

Sergey Sharybin commented

2016-09-01 16:33:24 +02:00

One more question from my side: are you painting with tablet or a mouse?

Luca Crisi commented

2016-09-01 16:45:15 +02:00

Just a simple mouse...
Shouldn't it work?

Just a simple mouse... Shouldn't it work?

Sergey Sharybin commented

2016-09-01 16:49:44 +02:00

Well, it should. Just troubleshooting route depends on whether it's a tablet or mouse.

What about errors in the console? Did you check for those?

Well, it should. Just troubleshooting route depends on whether it's a tablet or mouse. What about errors in the console? Did you check for those?

Luca Crisi commented

2016-09-01 17:02:30 +02:00

No... How do I do that?

Luca Crisi commented

2016-09-01 17:12:07 +02:00

Or maybe there's something hidden in my preference settings which prevent the correct behaviour...

I'd be not very surprised to learn that:
Some months ago I discovered with the help of a Developer, here, that a setting of mine was preventing the Scripts from automatically running.

And it turned ot to be a bug only present in the Windows version of Blender.

Or maybe there's something hidden in my preference settings which prevent the correct behaviour... I'd be not very surprised to learn that: Some months ago I discovered with the help of a Developer, here, that a setting of mine was preventing the Scripts from automatically running. And it turned ot to be a bug only present in the Windows version of Blender.

Luca Crisi commented

2016-09-01 17:13:41 +02:00

By the way... I posted another (completely different) bug.
Nearly at the same time of this one.

But no one seems to care about.

It's a bug in the File Save Screen not respecting the UI settings.

By the way... I posted **another** (completely different) bug. Nearly at the same time of this one. But no one seems to care about. It's a bug in the File Save Screen not respecting the UI settings.

Luca Crisi commented

2016-09-02 12:47:11 +02:00

Just found a WORKAROUND: Just remove Use OpenSubDiv from the SubSurf Modifier.
Hope it helps someone else facing the same issue.

Just found a **WORKAROUND**: Just remove `Use OpenSubDiv` from the SubSurf Modifier. Hope it helps someone else facing the same issue.

Sergey Sharybin self-assigned this 2016-09-02 12:59:23 +02:00

Sergey Sharybin commented

2016-09-02 12:59:23 +02:00

Ah, that's a good thing. Had OSD device set to None in the preferences, so that's why it worked for me.

Ok, now can see the issue and will try to solve!

Ah, that's a good thing. Had OSD device set to None in the preferences, so that's why it worked for me. Ok, now can see the issue and will try to solve!

Luca Crisi commented

2016-09-02 13:47:52 +02:00

Thank you, dear!