Spikes when using tablet #85733
Labels
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
16 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#85733
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce RTX 3070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 461.40
Blender Version
Broken: version: 2.92.0 Alpha
Worked: version: 2.91.2, branch: master, commit date: 2021-01-19 16:15, hash:
5be9ef417703Short description of error
Known affected tablets:
Using the tablet randomly produces pikes.
Exact steps for others to reproduce the error
wacom_bug.mp4
LassoBug.mp4
scrape_error.mp4
Added subscriber: @thornydre
#85918 was marked as duplicate of this issue
#85920 was marked as duplicate of this issue
#85917 was marked as duplicate of this issue
#85913 was marked as duplicate of this issue
#85894 was marked as duplicate of this issue
#85849 was marked as duplicate of this issue
#85758 was marked as duplicate of this issue
#85871 was marked as duplicate of this issue
#85832 was marked as duplicate of this issue
#85813 was marked as duplicate of this issue
#85814 was marked as duplicate of this issue
#85810 was marked as duplicate of this issue
#85825 was marked as duplicate of this issue
#85788 was marked as duplicate of this issue
#85727 was marked as duplicate of this issue
#85740 was marked as duplicate of this issue
Added subscriber: @filedescriptor
I cannot reproduce this on Linux. Might be Windows-specific.
Added subscribers: @IvanKoziichuk, @MassimilianoPuliero, @PabloDobarro
Pikes when using Wacom tabletto Pikes when using tabletPikes when using tabletto Spikes when using tabletAdded subscriber: @wannes.malfait
I got the same problem on windows with a HUION tablet, when drawing annotations.
Can anyone confirm if this is an issue in 2.92 beta?
Does the issue occur if the Tablet API is set to Windows Ink?
Changed status from 'Needs Triage' to: 'Needs User Info'
My task was from version 2.92 beta
https://developer.blender.org/T85740
I got this in both API
This comment was removed by @IvanKoziichuk
Your original report said that Windows Ink is turned off (presumably in the tablet's preferences utility). Just a sanity check but did you turn it back on when testing with Blender set to use Windows Ink?
Checked, doesn't help. It's the first time when I got some troubles with tablet on Blender.
p.s. All people who use tablets in 90% turning Windows ink off in the system because this function generates many troubles.
p.p.s First I think it was trouble on my side, try all options in all combination, nothing helps. Then I go to create a report.
Another sanity check, is Windows being run in a VM or over Remote Desktop?
No and no. It's the main OS on my pc.
This comment was removed by @IvanKoziichuk
As in, it only happens in specific section of the tablet? Do you have a mutli-monitor setup?
oo... I got 1 more symptom. Wait, show in the video.
https://drive.google.com/file/d/1uyWuyj56ma9Ji1EFpsjtek9ST7dD-bxw/view?usp=sharing
I got this in some vertical line in the middle of the screen. If we Divide the screen into blocks 2x2 it happens among 2 upper blocks.
UPD New information below
Only one monitor. I tried to change the work area of the table, doesn't help.
Maybe this can help. Just trying to find this "dead" zone. Spike happens on this red line.
From Vertical line - spikes go to Left
From Horizontal line - spikes go to Up
@IvanKoziichuk could you test this build ? I don't think it will fix the issue but it tests an important assumption in the code.
Note to self: above build changes negation handling for GetMouseMovePointsEx to check the msb of the lower 16 bits instead of checking if the 32 bit number is greater than the largest 16 bit number possible.
Of course, I can, no problem.
No, not fixed :(
One more detail: Spikes happens not always.... Like it depends on the angle. If I try to draw a straight horizontal or vertical line everything is okay.
@IvanKoziichuk another build , I expect this build to make the issue go away, but if this is the fix I am not sure we will implement it.
The above build disables high frequency mouse input (smooth lines).
Edit: If you change scale and layout, does the area where the jump occurs change?
@IvanKoziichuk Thank you for your feedback on this task, but try to keep the number of successive replies to a minimum (e.g. by editing a previous comment). Every new comment will notify all the subscribers of this task.
@filedescriptor Omg, Sorry. I don't know how works notifications on this forum, Thank You for your advice.
@PrototypeNM1 No, Scale not changed. Going to test build.
UPD> It's 100% link on new Build? Cuz the same name of the archive and bug still exist.
UPD> Than bug still here. I'm not changing scale.
UPD> I don't know if this would be useful but spike creating depends on direction too. You can see this in the video below.
https://drive.google.com/file/d/1qswIaKDkcKhC0Whjj_GsGyUOXDEFODwr/view?usp=sharing
To clarify, when you change the scale the the cursor jump stays around the same areas of the screen, or you have not changed the scale? Sorry for my confusion, it looks like you were answering the latter but the former is what I needed to know.
Edit: Yes, I reused the same link as before with an updated file (also same name as before).
@IvanKoziichuk [another test build]] (same link). If the issue remains could you paste the console log [ https:*developer.blender.org/paste/edit/form/default/ | at this link, and copy the resulting link here?
This console?? Or I must find some other console?
UPD> Bug not gone. :(
That's the one. I don't see any logged output, did you take the screenshot after recreating the bug?
Also please copy/paste the text into the paste link instead of taking a screenshot.
@PrototypeNM1 This screenshot after generating bug. My console didn't generate any information, that's why I asked about the right console.
Added subscribers: @MarekTrejbal, @DarkKnight
Guys, on Blender 2.92 this bug existing too. I just checked the Release candidate. Same symptoms, the console don't generate any information after recreating the bug too.
@IvanKoziichuk [another test]], please paste the console log [ https:*developer.blender.org/paste/edit/form/default/ | at this link, and copy the resulting link here.
This build is logging all mouse movement, so expect a lot of text.
Added subscribers: @PMA33, @Alaska
And done.
https://developer.blender.org/P1975
Yeap, console register mouse jump.
How it looks in the console:
" GetMessagePos, 11571281, 1718, 468
New test, if this works then I should be able to put together a fix.
Edit: re-uploading as there was an issue, if you see this the upload hasn't finished yet.Edit 2: re-upload finished.
Sorry. not fixed, plus now we get and diagonal spikes.
In console:
"GetMessagePos, 15257296, 1715, 710
GetMouseMovePointsEx, 15257281, 63828, 64819
GetMouseMovePointsEx, 15257281, 63826, 64817"
And screen:
But it says that you are closer to the problem
UPD:
And sometimes I got this in the console:
"Python: Traceback (most recent call last):
KeyboardInterrupt
location: :-1"
Sorry. don't see your new message. Going to test again.
"It's ALIVE!". Yes, it works! Well done!
Added subscriber: @dfelinto
Changed status from 'Needs User Info' to: 'Confirmed'
@thornydre @PMA33 @MarekTrejbal @MassimilianoPuliero @wannes.malfait if you could test this build to see if the issue is fixed for your tablets it would help increase confidence that everyone's bug has the same cause.
Tomorrow I can bring this build to a few people with tablets for testing and give you to know about results.
I can confirm that the last build works good :).
Yes, the problem is gone with this build for me :)
I still have the problem on my
win10 gtx2070super // Wacom Intuos Pro 4
2.91.2, branch: master, commit date: 2021-01-19 16:15, hash:
5be9ef4177@PrototypeNM1
It works fine with 2.93 alpha #85733 test build from graphicall.
Thank you
@MassimilianoPuliero Did you use this build?
Sorry I saw it late.
Yes, the build works fine thank you, I also edited the comment above https://developer.blender.org/T85733#1116271
Added subscriber: @PrettyFireNOI7
Nice! The first time I was using the wrong build too, that's why I asked. XD
@PrototypeNM1
(the appearing of the overshot vertical lines on Suzanne upper head) (the monkey mesh had been applyed a 4-level-subdivision modifier)
Much appreciate the new build.
While I did some test in weight paint mode and maybe there is still some reason casuing glitches (possibly too rare cases and I couldn't find a reproducible reason for those spikes(I just kept drawing random lines)):
Thanks again for the work. ;)
Added subscriber: @Lillya
The issue has been solved for me too, using a Huion H950P.
I don't know if wintab is supposed to work on this build too, but I noticed that there's a new problem, on the start of every stroke the pressure is always 100%, causing these dots:
jGWvaU69Mk.mp4
It looked good but it is true that if you try very hard the glitch is still there.
@MarekTrejbal @PrettyFireNOI7 can you recreate the issue in the last build and paste the console log at this link , and copy the link here?
@Lillya that sometimes occurs due to the way Wintab interacts with Windows mouse input, the only fix is to use Windows Ink instead.
Here is the console link .
Added subscribers: @fjg3d, @PrototypeNM1, @Harti, @Otilla
Console log : P1977
There is some movement me trying to open the console window at the beginning of the log and trying to switch programme window at the end.And following pictures showing my progression during the log process:
I can confrim this too,with wacom driver and windows ink off/on(both tested) and I did a bug report here #85844.
@MarekTrejbal @PrettyFireNOI7 updated build to test, I believe this will resolve your remaining cursor jump issues.
The option "Use Windows Ink" in the driver settings seems not working as expected and doesn't affect glitches problem.
I also still have the error with that graphical build.
Edited
@PrettyFireNOI7 @fjg3d [updated build ]] and [ https:*developer.blender.org/paste/edit/form/default/ | paste link for the system console.
P1978 for:
P1979 for:
Or it's better to combine mutiple into one log if there would be more test log after?
blender-2.92: test build.log
Added subscribers: @Vyach, @lichtwerk, @HooglyBoogly
Added subscriber: @SergienkoEugene
Added subscribers: @JulienKaspar, @JulianZorzenon, @Systematic
Added subscriber: @ElioH
Added subscribers: @Anthony_T, @pratik-2, @PratikPB2123
[Console Output P1981 ](https://developer.blender.org/P1981)
The issue seems to only happen when Blender is full screen (either Windows10 'Maximize window' or Blender's 'Toggle fullscreen'). If I make the Blender window smaller than full screen, the vertical strokes don't appear. also pasted console output
Edit: This comment refers to sculpt mode.
Added subscribers: @toot-4, @dupoxy
Added subscriber: @warcanin
Removed subscriber: @dupoxy
Removed subscriber: @HooglyBoogly
All: this build reverts changes to that caused this issue. Please +1 if this fixes things for you or comment if there is still an issue.
@PrototypeNM1
It works fine for me.
@PrototypeNM1, +1
Added subscriber: @BEASTIC-2
Added subscriber: @nicholas-14
@nicholas-14 Rishel (nicholas_rishel)
here are some stroke on your version
Here are the same (setting) with version 2.91
It solves the spikes but there is still the pressure problem,
Added subscriber: @fanazepam
@PrototypeNM1
Looks good for me.
@PrototypeNM1
Windows Ink is working fine;
Wintab still has the pressure issue, which wasn't present in 2.91.
No more spikes, but similar pressure problems as warcanin.
After restart, with windows ink set in prefs pressure sensitivity seems to be ignored altogether as if the strength pressure button is off (even when its on). so strokes have even pressure throughout.
Wintab has some pressure but too heavy at the start of a stroke.
tested on Sculpt mode and GP.
Added subscriber: @Aubert
Changed status from 'Confirmed' to: 'Resolved'
Resolved by
cd9dbe317d.Added subscriber: @carlos13eab