3D Mouse Malfunction #54799

Closed
opened 2018-04-24 20:52:10 +02:00 by Brandon Farley · 17 comments

System Information
Windows 10 - NVIDIA GeForce 1050ti

Blender Version
2.8 - 10f0f4b
Worked: (2.79)

I have a 3dconnexion space mouse and whenever I try to move around in the viewport with it, it freezes until I move the regular mouse and the space mouse at the same time, but it skips to another part of the viewport.

https://youtu.be/8oqheDCG3DI

**System Information** Windows 10 - NVIDIA GeForce 1050ti **Blender Version** 2.8 - 10f0f4b Worked: (2.79) I have a 3dconnexion space mouse and whenever I try to move around in the viewport with it, it freezes until I move the regular mouse and the space mouse at the same time, but it skips to another part of the viewport. https://youtu.be/8oqheDCG3DI
Author

Added subscriber: @bfarley88

Added subscriber: @bfarley88

Added subscriber: @VukGardasevic

Added subscriber: @VukGardasevic

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Vuk Gardašević self-assigned this 2018-04-24 23:30:17 +02:00

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them.
But since replying to reports takes time, we have decided to limit bug reports to module team members.

For the time being, closing this report.

Thank you for the report. Currently we are aware of many issues in 2.8 and actively working to fix them. But since replying to reports takes time, we have decided to limit bug reports to [module team ](https://wiki.blender.org/index.php/Dev:Doc/Process/Module_Owners/List) members. For the time being, closing this report.
Member

Added subscriber: @MikeErwin

Added subscriber: @MikeErwin
Member

@bfarley88 I'm responsible for 3D mouse support, and will make sure this is not forgotten in 2.8.

Something to do with NDOF_MOTION events getting lost or not triggering a redraw in the viewport.

@bfarley88 I'm responsible for 3D mouse support, and will make sure this is not forgotten in 2.8. Something to do with NDOF_MOTION events getting lost or not triggering a redraw in the viewport.

Added subscriber: @mano-wii

Added subscriber: @mano-wii

@MikeErwin, this problem was probably caused by my commit -> 785e8a636a

I can't teste but here is a possible fix (that + #ifdef WIN32 can be removed if you prefer)

diff --git a/intern/ghost/intern/GHOST_System.cpp b/intern/ghost/intern/GHOST_System.cpp
index 4db2f0616d7..8a686dd7aa1 100644
--- a/intern/ghost/intern/GHOST_System.cpp
+++ b/intern/ghost/intern/GHOST_System.cpp
@@ -219,10 +219,12 @@ bool GHOST_System::getFullScreen(void)
 void GHOST_System::dispatchEvents()
 {
 #ifdef WITH_INPUT_NDOF
+  #ifndef WIN32
 	// NDOF Motion event is sent only once per dispatch, so do it now:
 	if (m_ndofManager) {
 		m_ndofManager->sendMotionEvent();
 	}
+  #endif
 #endif
 
 	if (m_eventManager) {
diff --git a/intern/ghost/intern/GHOST_SystemWin32.cpp b/intern/ghost/intern/GHOST_SystemWin32.cpp
index ccc90e363b7..745a9f659aa 100644
--- a/intern/ghost/intern/GHOST_SystemWin32.cpp
+++ b/intern/ghost/intern/GHOST_SystemWin32.cpp
@@ -1098,8 +1098,10 @@ LRESULT WINAPI GHOST_SystemWin32::s_wndProc(HWND hwnd, UINT msg, WPARAM wParam,
 							break;
 #ifdef WITH_INPUT_NDOF
 						case RIM_TYPEHID:
-							if (system->processNDOF(raw))
+							if (system->processNDOF(raw)) {
+								system->m_ndofManager->sendMotionEvent();
 								eventHandled = true;
+							}
 							break;
 #endif
 			
@MikeErwin, this problem was probably caused by my commit -> 785e8a636a I can't teste but here is a possible fix (that + `#ifdef WIN32` can be removed if you prefer) ``` diff --git a/intern/ghost/intern/GHOST_System.cpp b/intern/ghost/intern/GHOST_System.cpp index 4db2f0616d7..8a686dd7aa1 100644 --- a/intern/ghost/intern/GHOST_System.cpp +++ b/intern/ghost/intern/GHOST_System.cpp @@ -219,10 +219,12 @@ bool GHOST_System::getFullScreen(void) void GHOST_System::dispatchEvents() { #ifdef WITH_INPUT_NDOF + #ifndef WIN32 // NDOF Motion event is sent only once per dispatch, so do it now: if (m_ndofManager) { m_ndofManager->sendMotionEvent(); } + #endif #endif if (m_eventManager) { diff --git a/intern/ghost/intern/GHOST_SystemWin32.cpp b/intern/ghost/intern/GHOST_SystemWin32.cpp index ccc90e363b7..745a9f659aa 100644 --- a/intern/ghost/intern/GHOST_SystemWin32.cpp +++ b/intern/ghost/intern/GHOST_SystemWin32.cpp @@ -1098,8 +1098,10 @@ LRESULT WINAPI GHOST_SystemWin32::s_wndProc(HWND hwnd, UINT msg, WPARAM wParam, break; #ifdef WITH_INPUT_NDOF case RIM_TYPEHID: - if (system->processNDOF(raw)) + if (system->processNDOF(raw)) { + system->m_ndofManager->sendMotionEvent(); eventHandled = true; + } break; #endif ```

Added subscriber: @Daniel_Artistic

Added subscriber: @Daniel_Artistic

Added subscriber: @TobiasEinarsson

Added subscriber: @TobiasEinarsson

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

I believe this problem deserves attention. Reopening.

I believe this problem deserves attention. Reopening.
Author

I would be happy to test it out on my end and give feedback, since I own a 3d spacemouse, to let you know if the malfunction is still occuring on my end. Currently, there's still the same issue happening. It only responds to input when I'm either holding down any of the arrow keys or sliding the mouse around.

I would be happy to test it out on my end and give feedback, since I own a 3d spacemouse, to let you know if the malfunction is still occuring on my end. Currently, there's still the same issue happening. It only responds to input when I'm either holding down any of the arrow keys or sliding the mouse around.

This issue was referenced by 030297209f

This issue was referenced by 030297209f2508a704b8851fa5d7d9a6696561b5

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

@bfarley88, ok, I sent the patch that I believe corrects the problem (I think it will be in tomorrow's build, in buildbot).
Please report any strange 3D Mouse behavior that may have come up with that patch.

@bfarley88, ok, I sent the patch that I believe corrects the problem (I think it will be in tomorrow's build, in buildbot). Please report any strange 3D Mouse behavior that may have come up with that patch.

Added subscriber: @markH-1

Added subscriber: @markH-1
Sign in to join this conversation.
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
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#54799
No description provided.