Still looking for exactly the same function in 2021… For high-performance projects lightmaps are still needed!
Hi,
I tried changing that setting to higher values than 64 and in all cases it worked worse than with the default value (64) (Some ‘contaminated’ shadows that wasn’t there before). Have you tried it and are you sure it keeps the same good quality (or even better) in your projects?
- Create or improve your lightmap:
- tick Generate Lightmap UVs
- Set your desired resolution. This is the Min Lightmap resolution. You can later increase that resolution but you cannot make it smaller. It is the minimum size.
- Set source and target index. In this case I want to improve the lightmap layout. I already have a rough layout in channel 1. I want this to be rearranged. Source and Target are both 1.
- Hit Apply. If apply is greyed out you need to tick “Generate Lightmap UVs” or make any change to your settings.
- Now you need to actually set your lightmap size and the channel. You can set a larger value for the size but it cannot be less than the minimum lightmap size set above.
Don’t forget to set the Lightmap Coordinate Index. It’s your target lightmap uv index from above.
Old thread but still relevant; is there a way to change the min_lightmap_resolution using a editor_utility_blueprint OR Python code?
The default value of 64 results in much lost UV space for objects with a high polycount (see third post with the two pictures in this topic). Changing this value by hand is time consuming. Leaving it at 64 results in much larger override resolutions thus larger texture memory and longer lightmap calculation times.
Using dataprep, you can set the override using ‘compute lightmap resolution‘ in a editorUtilityScript. Would be nice if the same could be done for the min_lightmap_resolution