Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • EDuke32 EDuke32
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Richard Gobeille
  • EDuke32EDuke32
  • Issues
  • #147

Closed
Open
Created Apr 21, 2021 by Max Ylitalo@oasiz

2D inaccuracy with texture panning and firstwall

Screenshots are from polymer/classic/polymost and finally 2D.

Issue is that texture panning does not match what you see in 2D compared to 3D. Let's focus on the blue "seat" sector Red walls represent firstwalls being used visually. I believe this is caused by how the engine processes firstwalls and the alignment of R and panning.

The seat aligns when the firstwall is at the proper 0,0 panning position, this happens when the redwall is encountered before the green wall in clockwise rotation.

When the green wall appears first, it still considers redwall as the firstwall but what would've been .point2 before ends up being the actual firstwall in this case.

This can be replicated quite easily when X flipping sectors for geometry that has been aligned with clockwise rotation in mind.

On one shot, I drag the wall ever so slightly, this "fixes" the panning to be where it should be visually in 2D mode.

capt0124

capt0123

capt0122

capt0125

capt0126

Assignee
Assign to
Time tracking