Whether the Progressive Lightmapper exports machine learning training data to the Project folder when it performs the bake. ( Editor only).
When this is set to true
, the Progressive Lightmapper exports separate data for direct lighting, indirect lighting, directionality, Ambient Occlusion, Texel Validity, normals, positions, albedo, emission, a coverage mask, and the final lightmap. This data is useful when training machine learning (ML) networks When this is set to false
, the Progressive Lightmapper does not export this data.
The direct and indirect textures are exported before filtering, but after markup of invalid texels. The lightmap and directionality are exported after filtering and compositing. Ambient Occlusion exports with an exponent of 1. It does not take the indirect/direct exponent into account. To be able to export valid data for Directionality and Ambient Occlusion, they must first be enabled.
Normals and positions are exported in both object space (os) and world space (ws). Normals are normalized, positions are not. Some textures are marked as "supersampled". This means that the Editor exports the values without downsampling them, if they have a supersampling multiplier that is higher than 1.
All textures have the coverage mask as their alpha channel.
To change the name of the export folder, see trainingDataDestination.
See Also: Lighting Settings Asset, trainingDataDestination.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.