Blender 2.8. In edit mode when you have hard scene (slow down processing) all your actions will applyes not at right moment (not at click but at moment when blender finn. caclucations) #63185
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
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#63185
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.17134 64 Bits
Graphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35
Blender Version
Broken: version: 2.80 (sub 53), branch: master, commit date: 2019-03-30 19:37, hash:
700346d377Worked: (optional)
Short description of error
I have scene where I put a lot boolean(and not only) modificators on one objects and when I enter into edit mode all processing erally slow (each action: movement, extrusion, etc..) And problem here in next: when you doing any action (and it took time to process it) and then press mouse button to apply action affect, but! it will not memorize position of the mouse when you pressed, and still continue doing (move to the cursor) And this really anoing because you need repeat all twice or more time. Or just seating and waiting with no mouse movement at all, when it will apply action effect.
So core problem is that: in edit mode any affect will applyes not at moment when you decide but by moment when CPU will finished calculetion of movement/action and will change your action to position where is going be mouse positioned at the moment of the end calculation... something like that.
Exact steps for others to reproduce the error
Create some worcload/heavy scene. For example by a lot subdivisions and booleans at object. When each your action will be like "under water gravity" slowed down. And then try to change(extrude/move vertext / anything) boolean part that will be used as cut area in the edit mode.
2019-04-01 17-39-35.mov
Added subscriber: @rs2128
#63699 was marked as duplicate of this issue
Added subscriber: @brecht
Please attach a .blend file and provide exact steps to reproduce the issue.
fFILE.blend
I create new file [not my original]. But here are it reproduce on my PC. If you PC more powerfull - you will don't see it. So please just increase subdivisions on the object [when you fill the same slowing down as in the video]
Here is how it looks like: https://mega.nz/#!cLBQHIIa!UYt3WhuyBA0twL6P5J29fC5jnK7X97zjwRmbRM2c5m4
Btw, I checked it whith pressing 'Enter' key - and it works fine. But with mouse - not.
STEPS: open file. Press G to move. Press Z to lock by Z axis. Move precisely to the ~zero position by mouse. Then press mouse to finish action and then move mouse upside without waiting long time.
Added subscribers: @WilliamReynish, @LazyDodo, @ZedDB
I can't reproduce this on my end, the file is even slower for me than in you video.
However, in you video you can see that the mouse cursor does not change right away when you left click but lingers around. On my end it changes quite fast after I left click (even if the scene is many times slower for me than in your video) so I can't get it to change position after I have clicked.
@LazyDodo @WilliamReynish can you guys see if this happens for you on Windows/Mac too?
Added subscriber: @info-27
This sounds like a similar issue to this bug: https://developer.blender.org/T63699
Is this still an issue?
@ZedDB - yeap
Added subscriber: @DanielBystedt
I tested this scene, but I can't reproduce this issue. Moving the polygon is slow, but there is no buggy behavior as per described above.
System Information
Operating system: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: GeForce GTX 1080/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 432.00
Blender Version
Broken: version: 2.82 (sub 6), branch: master, commit date: 2019-12-23 08:34, hash:
708045eb40🤔 I think @DanielBystedt, you know better what to do whith this task for further(if it will not reproduce by anyone)...
I've checked it just right now with (version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash:
26bd5ebd42) and it still reproduce.Then I've checked it on last fresh (version: 2.82 (sub 6), branch: master, commit date: 2019-12-23 08:34, hash:
708045eb40) and it still reproduce.Each time when I put stylus(alanog of press left buton on mouse) to ending action and then move it away (it stick to my movement until curson not changed his icon to crosshair from (G)move-icon)
It seems like because it too heavy and processing-calculate movement too long, it can't fast change to ending mode. And it still stick to the stylus movement until calculation will be finished. Maybe key of the issue in that I'm not use mouse? (just wacom-tablet) Try with tablet, maybe it helps to find reason 🙄
Sorry to hear you still have the issue. I can't reproduce the same thing on my computer.
I just want to confirm that I'm also using a tablet (wacom intous 5 touch)
Added subscriber: @iss
Changed status from 'Needs Developer To Reproduce' to: 'Confirmed'
I can reproduce this issue with these steps:
which leads to vertex not being moved to position, where you clicked LMB
Added subscriber: @pablovazquez
Added subscriber: @mont29
Cannot confirm that on linux.
Don't think we can do much here really? This is likely some problem where event handler gets wrong coordinates from the OS event system, due to heavy load.
This seemed to me like after click event was received, OS was polled for position or we wait for another position event. I wouldn't assume, that problem or limitation is on OS side, many apps can handle this.
But I am not familiar with our event system at all...