Mesh appears completely messed up when switching to wireframe with "draw all edges" enabled on a skinned mesh #36514

Closed
opened 2013-08-19 16:35:35 +02:00 by Hadrien Brissaud · 13 comments

%%%--- Operating System, Graphics card ---
MACOS10.8.4
NVIDIA GeForce GT 650M 512 Mo

- Blender version with error, and version that worked ---

2.68a

- Short description of error ---

Mesh looks completely messed up when switching to wireframe with "draw all edges" enabled. It seems to happen only with an armature-bound mesh. Sometimes (?), maximizing the view (shift+spacebar) fixes the mesh drawing.

- Steps for others to reproduce the error (preferably based on attached .blend file) ---

Select the geometry and check "draw all edges" in object tab
Switch to wireframe display
May or may not appear broken to you, sounds like a graphics card thing

Hadrien

%%%

%%%--- Operating System, Graphics card --- MACOS10.8.4 NVIDIA GeForce GT 650M 512 Mo - Blender version with error, and version that worked --- 2.68a - Short description of error --- Mesh looks completely messed up when switching to wireframe with "draw all edges" enabled. It seems to happen only with an armature-bound mesh. Sometimes (?), maximizing the view (shift+spacebar) fixes the mesh drawing. - Steps for others to reproduce the error (preferably based on attached .blend file) --- Select the geometry and check "draw all edges" in object tab Switch to wireframe display May or may not appear broken to you, sounds like a graphics card thing Hadrien %%%

Changed status to: 'Open'

Changed status to: 'Open'

#38518 was marked as duplicate of this issue

#38518 was marked as duplicate of this issue

%%%My mistake, it does not depend on "draw all edges" being on or off, rather on "wire".%%%

%%%My mistake, it does not depend on "draw all edges" being on or off, rather on "wire".%%%

%%%Looks fine here. mesh is also valid/

  • Can you check if this happens on a different computer?
  • Can you see if this is related to the VBO user preference?
  • Could you upload an image of what you see?%%%
%%%Looks fine here. mesh is also valid/ - Can you check if this happens on a different computer? - Can you see if this is related to the VBO user preference? - Could you upload an image of what you see?%%%

%%%Confirmed, on OS X with NVidia GT 650M. Only happens when VBO is enabled.

The mesh shows scrambled, like the vertex locations are ok but they are connected randomly. Also, when saving in wireframe mode it opens ok, but when you toggle to solid draw mode and back it shows wrong again.%%%

%%%Confirmed, on OS X with NVidia GT 650M. Only happens when VBO is enabled. The mesh shows scrambled, like the vertex locations are ok but they are connected randomly. Also, when saving in wireframe mode it opens ok, but when you toggle to solid draw mode and back it shows wrong again.%%%

%%%I look at this for quite a while but couldn't understand what's going on here. Even with the OpenGL state and VBO contents identical it can still render correct in one case and incorrect in the other. I guess there's a particular order of operations that triggers a bug in the OpenGL driver, but I haven't found yet what that is.%%%

%%%I look at this for quite a while but couldn't understand what's going on here. Even with the OpenGL state and VBO contents identical it can still render correct in one case and incorrect in the other. I guess there's a particular order of operations that triggers a bug in the OpenGL driver, but I haven't found yet what that is.%%%

Added subscriber: @ClaasKuhnen

Added subscriber: @ClaasKuhnen

◀ Merged tasks: #38518.

◀ Merged tasks: #38518.
Member

Added subscriber: @MikeErwin

Added subscriber: @MikeErwin
Member

Added subscriber: @Blendify

Added subscriber: @Blendify
Member

any news

any news

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'

I can't redo this anymore on the same computer I tested this before, but now with OS X 10.10. Both Blender 2.68a and 2.76 work fine now, so I'm going to assume this was a graphics driver bug that is now fixed.

I can't redo this anymore on the same computer I tested this before, but now with OS X 10.10. Both Blender 2.68a and 2.76 work fine now, so I'm going to assume this was a graphics driver bug that is now fixed.
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
6 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#36514
No description provided.