feat(renderer): allow switching the hybrid path back to forward #946
No reviewers
Labels
No labels
Context: Bug
Context: Enhancements
Platform: Android
Platform: Linux
Platform: Web
Platform: Windows
Platform: iOS
Platform: macOS
Release
Target: CI
Target: CLI
Target: Dependency
Target: Engine
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
SakulFlee/Orbital!946
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/renderer-forward-fallback"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Phase 4d: expose a forward fallback for the hybrid renderer.
Renderer::set_deferred_enabled(bool)/deferred_enabled().clear-depth -> models -> [transparent] -> tonemap) is reused for the fallback.This gives a way to compare the forward and hybrid paths and a safe fallback for materials/scenes where deferred is not a good fit.
Verification
cargo fmt --all -- --checkcargo clippyfor the touched crates and all three example templates with--all-targets -D warningscargo test -p orbital_renderercargo checkfor the renderer, app and all three example templatesStacked on #945.
Refs #781.
Smart test results
Result: PASS
Scope: orbital_renderer, orbital_shader_pbr
Reason: directly changed crates
Elapsed: 1m 39s
Workflow run
Overall: 12 tests, 12 passed, 0 failed, 0 skipped
Nextest: 12 tests, 12 passed, 0 failed, 0 skipped
Doctests: no tests reported