Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
EDuke32
EDuke32
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 91
    • Issues 91
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Richard Gobeille
  • EDuke32EDuke32
  • Issues
  • #136

Closed
Open
Opened Nov 05, 2020 by Dino Bollinger@Doom64hunterContributor

Engine: Wrong sprite rendering order in classic mode, where sprites are in close proximity to maskwalls

Found by MetHy.

Sprites that are in close proximity to a maskwall appear to suffer from some sort of rendering issue where they are drawn behind sprites that are further away. It doesn't seem to matter how far the camera is away from the sprite.

This does not occur in Polymost.

Examples: duke0006 duke0008

In addition, sprites may also be drawn in front of a maskwall when they are actually behind it. Happens in Rednukem as well:

duke0007

Test Map: MASKWALL.map

The RR instance can be reproduced in the first level, near the hidden moonshine.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: terminx/eduke32#136