Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG: QMB particles disappear after toggling gl_no24bit back and forth #604

Closed
hemostx opened this issue Nov 12, 2021 · 0 comments
Closed

Comments

@hemostx
Copy link
Contributor

hemostx commented Nov 12, 2021

ezQuake version:
3.6, happens back to 3.2.3 and 3.5*, so maybe even back to 3.1?

OS/device including version:
W10 20H2 GTX 1070 472.12
glsl/std alike

Describe the bug
When switching through gl_no24bit 0 gl_no24bit 1 gl_no24bit 0 at runtime (incl. required vid_restarts), the QMB particles nearly completely disappear when coming back to 24bit mode enabled.

To Reproduce

  • bare ezquake install (incl. media and particlefont!) with nquake's textures.pk3 and models.pk3 to have some reference
  • near default config, gl_part_trails 1 config.cfg.txt
  1. start a map and pickup some weapons (RL is a good one)
  2. shoot weapons where the config has QMB particle effects enabled. Enjoy the smoke puffs, tracers and other niceties.
  3. gl_no24bit 1;vid_restart
  4. we now have (hopefully) classic visuals. shoot the same weapons to witness the classic effects that ezquake correctly reverts to.
  5. gl_no24bit 0;vid_restart
  6. shoot the same weapons. Example results: boomstick impacts completely missing (tracers can appear though), rocket trail showing very sparse particles.
    no24bitbackto0-missingparts
    I have crashed a few times in that degraded state (screenshot), I can't get it to happen reliably though.
    qmb fail gl_no24bit
  7. reload/start a map and the QMB effects work again.

Expected behavior
Re-enabling 24bit textures should reinitialize QMB effects, as happens when reloading the map. The engine is able to fallback cleanly to particle effects but can't quite seem to go the other way without a more thorough reset like a map load.

@meag meag closed this as completed in d37f155 Nov 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant