Can confirm with 32bit builds on my laptop.
Sun, Mar 26
Operator requires an execution override to work properly:
When called from the Dynamic Context Menu (spacebar), it works just fine
Sun, Mar 19
Yes, that's exactly what I said --
Sat, Mar 18
@Ian Bruce (ian_bruce), i'm not sure what we can do with that knowledge. We are not drivers developers and are not involved into any distro development process. Guess this info better be directed to distro maintainers to ensure they ship proper drivers for OpenCL support (Blender is not the only program on planet which will benefit from that ;)
It turns out that these compiler warnings --
Mon, Mar 13
The two separate compiler errors involved here (neither is actually a Blender issue) are now the subject of two Debian bug reports. Patches are available upstream for both problems, as mentioned above.
It turns out that the "invalid argument type 'X *' to unary expression" compile errors are the result of a known bug in LLVM. It is said to be fixed in LLVM-v5; see here:
I've applied the patch at rB8794a43 just because i prefer explicit NULL comparisons my self.
This same problem (actually, several problems) has been reported here; it's not distribution- or hardware-specific:
Mon, Mar 6
Can confirm, this is a quite specific issue though, windowing is a bit complex so i don't know if this will be a trivial fix.
Feb 9 2017
I am also experiencing a similar error with my R9 280X running opencl-mesa 13.0.4-1 and ocl-icd 2.2.10-1 on Arch Linux x86_64 4.9.8-1 (Blender version 2.78.a).
Feb 2 2017
Thanks for the report, but we do not maintain any of the builds apart from the ones you can get from blender.org sites.
Jan 25 2017
Thanks for the report, but we simply don't officially support MESA OpenCL implementation yet.
Jan 23 2017
Thanks, I checked it with the latest builds and it works.
Jan 21 2017
Fix is commited, please check the buildbot soon to check if it solved your case.
Jan 20 2017
Thanks in advance for fixing it.
Jan 19 2017
Though netrender is currently unmaintained and removed for 2.8, this seems to be a simple fix.
Sep 29 2016
Think so. Please correct me if i'm wrong :)
Sep 27 2016
@Sergey Sharybin (sergey), so seems this patch can be closed?
Sep 17 2016
In new bild the problem fixed
Sep 10 2016
This is supposed to be fixed in current master, please check again.
Jul 12 2016
This is an issue with .deb package provided by your distro, which we do not maintain in any sense.
Jun 22 2016
Please do not assign bugs to random users.
Jun 21 2016
May 19 2016
Compiled from Master, it is working well now!
So, looks like it was indeed blender reading badly those valuators stuff in the end - at least not the same as xinput --test code does it. ;)
I opened a report bugs.freedesktop.org
May 15 2016
Yeah, I know missing coordinates is perfectly valid, the problem is not there. The problem is that, when only Y coordinate change, the event reports two available valuators, starting from valuator 1 (that is, it reports Y data and pressure data, even though there is no pressure data and valuator is set to zero).
May 11 2016
I have contacted Nikolai Kondrashov, DIGImend founder and main developer. I shared with him the next file showing Evtest, Xinput and Blender output while drawing on Blender:
May 7 2016
That's right, I have not noticed weird behavior in other programs on Linux when pressure sensitivity is enabled. Also, texture paint and curve draw are working really well on Windows 7 with the same hardware. So I discard hardware problems.
I'll see if I can report somewhere issues related to the driver on Linux.
Yep, you did good.
You let me know if I followed well the steps:
OK, so created a temp branch to help us, here are the steps to use it:
Yes, I can compile from master. But give me some instructions or text to read if I have to enable any debug option because I have not much idea about that.
Are you able to build blender yourself? Otherwise, trying to debug this by distance making testbuilds is going to be horribly long… :/
Thank you Bastien. But unfortunately I do not notice any change in the behavior of my tablet with this build when pressure sensitivity is enabled. I still have the same problem.
May 6 2016
Yes, I’m aware some drivers only give partial data in events, had to fix this about two years ago for pressure, but at that time at least x/y coords were OK. Looking at your video, this is no more the case.