[VRAD] Added support for setting the number of ambient cubes per leaf. #981
+28
−5
Conversation
This file contains 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
Unusuario2
changed the title
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.
Description
In many cases where a big levels have a large portal leaf, ambient lighting become less accurate for bounced light. Allowing the user to increase the number of ambient cubes with the
-AmbientCubesPerLeaf Ncommand helps solve this issue.For users: The
-AmbientCubesPerLeaf Ncommand sets the number of ambient light cubes used for lighting calculations. N represents the number of ambient cubes you want VRAD to generate. VRAD will optimize the number of ambient cubes based on their RGB values (if they are very similar and close to each other, some ambient cubes will be deleted).