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 98
    • Issues 98
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Richard Gobeille
  • EDuke32EDuke32
  • Issues
  • #233
Closed
Open
Created Jan 01, 2022 by Dino Bollinger@dibollingerDeveloper

Duke3D: No screenfade effect when exiting a level in Polymost/Polymer

In the Classic Mode renderer, after hitting a nukebutton, the game slowly fades out to black, and fades back in on the bonus screen. This also occurs when beating a boss monster. Note that this means that the cutscenes more easily be accidentally skipped, as the fadeout normally prevents inputs from the player being carried over to cutscenes or the bonus screen.

In Polymost or Polymer, this transition is missing, and the game instead immediately jumps to the bonus screen. Note that this problem is very old, even occurring in eduke32 builds from 2007, before the versioning system was introduced.

(Issue originally raised by: https://forums.duke4.net/topic/11841-no-fade-effect-in-polymost/)

Edited Jan 01, 2022 by Dino Bollinger
Assignee
Assign to
Time tracking