Disable lightmapper_rd
module in non-editor builds (and in Android editor)
#82521
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.
This is consistent with
xatlas_unwrap
, which isn't enabled in non-editor builds and the Android editor either. There is currently no way to use the lightmapper in a non-editor build anyway, as it doesn't expose any methods (and even if there was, there would be no way to perform UV2 unwrapping in the exported project).This reduces binary size of a stripped Linux x86_64 export template build by ~164 KB (compared against fe8a58b).
This also moves the PrimitiveMesh texel size project setting so that it's defined when the module is disabled, and adds a property hint to it.
In the future, if we decide to make this functionality available in non-editor builds, it should also be made available with
xatlas_unwrap
as a build-time option (similar to #73003).I tested this PR in a project with existing baked lightmaps and it works as expected (no errors, it renders correctly).
lightmapper_rd
module is included in export templates, even though it can't be used #72544.