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
  • #77

Closed
Open
Created Jun 12, 2020 by Dino Bollinger@dibollingerDeveloper

Engine: Polymer has major issues rendering surfaces in NAM

This goes back to the very first versions of Polymer, and maybe the levels were badly designed.

The following screenshots were taken in the first level of NAM:

  • Polymost: https://imgur.com/gTauq6o
  • Polymer: https://imgur.com/hHR96Ux

These floors seem to be rendered as parallax skies rather than grass. The sky also appears to be oddly shifted down.

Additionally, level geometry is visible through parallax skies in Polymer:

  • Polymost: https://imgur.com/bnCtivN
  • Polymer: https://imgur.com/rf5K4gJ

I know that Polymer isn't really maintained anymore, but this may be useful for projects that are based on Polymer, e.g. the experimental Direct3D 12/Vulkan renderer from ICD, should that ever go anywhere.

Edited Jun 12, 2020 by Dino Bollinger
Assignee
Assign to
Time tracking