Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • mesa mesa
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,865
    • Issues 2,865
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 893
    • Merge requests 893
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Mesa
  • mesamesa
  • Issues
  • #877

Closed
Open
Created Sep 18, 2019 by Bugzilla Migration User@bugzilla-migration

line rendering with --with-osmesa-bits=32

Submitted by burlen

Assigned to mes..@..op.org

Link to original bug (#71363)

Description

Created attachment 88859 rendered with osmesa --with-depth-bits=32

when runnning VTK regression suite on an OSMesa classic build with --with-osmesa-bits=32 (and only 32 - 8,16 and none work) 80 regressions show bad line rendering. I'm attaching some images that are illustrative. There's a thread on the mesa-dev mailist about this issue.

Attachment 88859, "rendered with osmesa --with-depth-bits=32":
chart-osmesa-bad

Version: git

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking