Please, this is not enough information to fix a bug.
@Aaron Carlisle (Blendify), yes, so just the osd rename left.
One of these days I'll learn to to read slower, lol.
0.01 is higher then the cut off value so I would not see a problem here.
I am working to figure out if it is a driver issue.
What’s the status here?
Own stupid copy/paste mistake...
No news over a week, archiving for now, we can always reopen when/if requested data are provided.
This change may actually cause problems for me. I had observed an issue on the Refraction BSDF where a few tiles on the refractive surface would take a few orders of magnitude longer to render when their facing was almost perpendicular to the camera, and they would often take much longer to render than the rest of the image.
actually just saw that python has already been taken care of and only need to commit the OSD fix
@Campbell Barton (campbellbarton) could you commit this
Sorry for not responding earlier, there were a number of other things to work on. Sergey, is this still relevant or do your latest changes to SSS take care of this?
Adding bam status to test on commit rBAM75bb629 , Now is reporting modified and deleted files, which is wrong:
First experimental builds available, see this post
Uuuuh… this seems very similar to T46731 in fact. :|
Please follow our bug report guidelines next time and provide all the infos that we ask you to provide! Without info we can do nothing.
This is a known limit with projection paint (when one vertex is behind the camera in perspective mode).
There isnt really a good solution for this (besides splitting geometry before calculating the projection).
Fix return Object
sry, was adding as place holder while doing initial script rewrite. Will return when I have source to go with task.
Thu, Nov 26
This seems to be an issue in official 2.76b release which was then fixed later in git. So you might want to double-check the issue with latets builds from builder.blender.org.
It should now be fixed with builds being prepared at builder.blender.org (was a mistake in python compiled for linux release env).
putting everything together