Note: the custom UV option is only available when calling the operator
via a script. It's currently not exposed in the UI since it's intended
to be used by scripters
To test it:
bpy.ops.object.bake(type='UV', use_clear=True, uv_layer='MyNewUV')
Details
Details
Diff Detail
Diff Detail
Event Timeline
Comment Actions
This doesn't work so well for baking many objects,
Note: We could have an active 'bake' layer, like we do for render & clone, but thats a much larger change.
And this option you only use when automating bakes anyway... so think its fine.
+1
| source/blender/editors/object/object_bake_api.c | ||
|---|---|---|
| 559 | I think only this check is needed?
| |
| 1305 | think this is more clear? "UV layer to override active" | |
| source/blender/render/intern/source/bake_api.c | ||
| 622–629 | *picky*, preference for braces around both cases. | |
Comment Actions
- small changes from Campbell Barton
Note: I didn't change the CD_MTFACE test. At that point (object_bake_api.c:562) we don't know if the mesh is tesslated, thus we cover all basis.
By the way, do we you think we should wait for after 2.71? or to push it to master before the RC (aka now).
Thanks for the review by the way
Comment Actions
- no need for extra UV checks, as suggested by Campbell Barton
- Merge remote-tracking branch 'upstream/master' into bake-custom-uv
Comment Actions
I forgot to update my origin/master (aka github) before last arc diff, so other commits made their way in. Re arc diff'ing
Comment Actions
- Merge remote-tracking branch 'upstream/master' into bake-custom-uv
Adjustments after the bake-cage commit
(and fix a building warning)