- User Since
- Jun 18 2009, 8:24 PM (534 w, 5 d)
Tue, Sep 10
Jan 15 2019
this works on my end now
Dec 12 2018
OK, that's not at all the behavior I expected but if it is indeed on purpose and setting rest position myself when exporting is how it is supposed to be done, then the bug instead is that FBX (now fixed), Collada etc are all using the API wrong and so was I.
Dec 11 2018
Dec 9 2018
Dec 8 2018
Bisect points to this commit breaking my game exporter output. I'm getting crazy bone transforms, as pictured:
Aug 21 2018
been a while since tested good and no reports of issues, can this be merged?
Aug 8 2018
@Brecht Van Lommel (brecht) thanks for reviewing, fixed missing NULL checks.
Aug 6 2018
OK. I have updated the revision title/summary to reflect the test result.
Aug 4 2018
@Antonio Vazquez (antoniov) hm, I see. I thought it was the same bug, since it matched what I was seeing, but it must be separate. This does fix my MP22 and possibly other non-Wacom tablets when drawing on GP objects though. Assuming the patch doesn't cause any regressions (I haven't noticed any at least), it'd still be good to merge.
Aug 1 2018
Yes, both are the same diff.
I've fixed a seemingly identical bug to this locally affecting my Monoprice MP22. I compared it to my tablet test program and it looks like the primary issue was not specifically reactivating things on focus, and potentially violating wintab spec by initializing in an invalid state (apparently you have to open with context disabled if using certain flags, then enable after)
Oct 27 2015
Sep 5 2015
Everything looks good again, thanks!
Sep 4 2015
Oh, clarification about the composite issue: the highlight on the eyes is a render layer.
Mar 10 2015
Jun 12 2014
Has anyone touched this issue since 2012? Latest builds still can't take IME input, and it'd be really nice to not need to copy & paste.
Jun 3 2014
this bug can also be interpreted as "textured solid is broken and replaced with a dupe in the shading mode dropdown"