Search Issue Tracker
Fixed in 5.6.0f3
Fixed in 2017.1.X, 2017.2.X
Votes
2
Found in
5.5.0b9
Issue ID
847499
Regression
No
Baking Lightmaps with 4096 Atlas Size Do Not Generate Lightmaps in 4096 Size
When Atlas Size of lightmaps are set to 4096 under Baked GI tab, Unity generates 4K maps and stores the information but by default, imports the lightmap as a 2K map. The workaround is to manually set the max size of all lightmaps to 4096 under import settings in inspector. When the user bakes the scene again, same steps should be followed.
Steps for reproduction:
1) Open the scene "4KTest"
2) In Lighting > Baked GI tab, choose "4096" as Atlas Size
3) Build the lighting
4) In Project tab, find the "4KTest" lighting data asset folder.
5) Choose the lightmaps and in inspector, observe that "Max Size" of lightmaps are set to 2048.
Notes:
- Tested in 5.4, 5.5 and 5.6.0a1
Comments (2)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [iOS] Application.deepLinkActivated does not get invoked while app is running when UIApplicationSceneManifest is added in Info.plist
- Inspector scroll area stretches when using components with nested serialized arrays on FBX model prefab instances
- Crash on ConstraintProjectionTree::projectionTreeBuildStep when ConfigurableJoint uses JointProjectionMode.PositionAndRotation and connected Rigidbody switches from kinematic to non-kinematic
- ScriptableObject asset is accessed during the lookup of Build Profiles when opening the Build Profiles Window
- [Multiplayer TPS Sample] Grenade launcher explosion misses the Player when the Collider count exceeds HitColliderBuffer
moz
Sep 04, 2017 15:03
Still not fixed in 5.6.0f3.
Shawn-Halwes
May 08, 2017 20:11
Same in v5.6.0p3