Repository navigation
feat(project): generate sky and environment lighting defaults - #77
Merged
Merged
Conversation
JeanPhilippeKernel
force-pushed
the
feat/project-rendering-defaults
branch
from
October 5, 2026 08:47
c750fac to
9a35f2a
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New projects now explicitly include the engine's sky authoring defaults and environment-lighting policy in
projectConfig.json: atmosphere mode, intensity 1, white RGBA tint, zero yaw, qualitystandard, and a 384 MiB integer budget. Environment maps remain optional asset UUIDs.Additional rendering properties survive configuration serialization. Existing project files are not migrated, and renaming preserves their rendering settings and legacy sky data. The project configuration guide documents quality tiers, memory units, compatibility, and scene ownership.
Closes #74
Closes #75
Closes #76
Validation:
dotnet build Panzerfaust.csproj --no-restoresucceeded.git diff --checkpassed.NuGet's vulnerability metadata check remained unavailable. Visual UI behavior and opening a generated project in the engine editor have not been verified. Verification harnesses ran from temporary directories and are not included in this PR.