Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
openmw
openmw
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 526
    • Issues 526
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 37
    • Merge Requests 37
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • OpenMW
  • openmwopenmw
  • Issues
  • #5678

Closed
Open
Opened Nov 07, 2020 by AnyOldName3@AnyOldName3Maintainer

Non-stupid shadow texture lookup

Because reasons, which shadow map the shader selects for each fragment is chosen in a really inefficient way. If allow shadow map overlap = true is made mandatory, we can do what every other engine ever does and select based on the planar distance from the eye point and just pass the threshold distances to the shader instead of several sets of matrices and checking whether the fragment position in various spaces is within a certain region.

I thought I'd put this on the tracker a while ago, but apparently it's just been mentioned in the comments of other issues a lot of times.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: OpenMW/openmw#5678