Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
mesa
mesa
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 2,315
    • Issues 2,315
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 639
    • Merge Requests 639
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Mesa
  • mesamesa
  • Issues
  • #1283

Closed
Open
Opened Sep 25, 2019 by Bugzilla Migration User@bugzilla-migration

HyperZ related rendering issue in ARK: Survival Evolved

Submitted by Elliot Thomas

Assigned to Default DRI bug account

Link to original bug (#102955)

Description

Created attachment 134449 The back buffer of apitrace frame 1017, showing red lines along what looks like primitive edges.

Hi,

I've been poking "ARK: Survival Evolved", trying to get it playable. The game is notoriously buggy, particularly under Linux, however the biggest issue I've had seems to be a Mesa/Radeon bug.

Blocky "pixelated" lines are drawn across what look like edges (see attached). These lines are most frequently red, black or cyan in colour, and seem to disappear when the scene complexity is lower (like when looking at the floor or an area with no foliage or rocks).

Setting R600_DEBUG=nohyperz resolves the issue.

I've tested an apitrace of the game on both Mesa git, and 17.2.1 on a desktop with a POLARIS10 (RX580 8GiB), running the latest amd-staging-drm-next kernel, and on a laptop with both Intel integrated graphics and a HAINAN (Sun XT? 8670M), running a stock Archlinux kernel.

Both AMD cards have this rendering issue with HyperZ enabled. The Intel card renders without this particular problem (if slowly), and llvmpipe (eventually) renders without issue too.

Apitrace (~600MiB!): https://drive.google.com/open?id=0B6RX1ZACoaJ5UmhDWDM3ZC03eUk

Desktop: Linux 4.13.0-rc5-43dd6fde5df4 #3 (closed) SMP PREEMPT Thu Sep 21 19:15:33 BST 2017 x86_64 GNU/Linux Mesa 17.3.0-devel (git hash #52ed3bca) libdrm 2.4.83, LLVM 5.0.0

Laptop: Linux 4.12.13-1-ARCH #1 (closed) SMP PREEMPT Fri Sep 15 06:36:43 UTC 2017 x86_64 GNU/Linux Mesa 1.7.12, libdrm 2.4.83, LLVM 5.0.0

The corruption does look somewhat like that of this bug, but applied to terrain as well. https://bugs.freedesktop.org/show_bug.cgi?id=74784

Attachment 134449, "The back buffer of apitrace frame 1017, showing red lines along what looks like primitive edges.":
ark-frame-1017-backbuf

Version: git

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mesa/mesa#1283