Timeline for Run code after texture baking is complete (multiple objects)
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 7, 2022 at 23:50 | vote | accept | Cessen | ||
| Apr 7, 2022 at 23:50 | answer | added | Cessen | timeline score: 0 | |
| Apr 6, 2022 at 21:56 | answer | added | X Y | timeline score: 0 | |
| Apr 6, 2022 at 17:23 | history | edited | Cessen | CC BY-SA 4.0 |
Added another attempt based on comments on this question.
|
| Apr 6, 2022 at 17:17 | comment | added | Cessen |
@XY: I just tested, and unfortunately img.bindcode does not change at all with baking. Also, just to clarify: checking img.pixels[0] definitely wouldn't work, because there is no guarantee that any of the pixels change. Imagine, for example, that the user re-bakes just to be sure, but the resulting baked image is exactly the same. Anyway, I'll add this as "Attempt 4" in the question.
|
|
| Apr 6, 2022 at 1:45 | comment | added | Cessen |
@XY: if img.bindcode is guaranteed to change whenever a bake finishes, then it would basically be like attempt #3, just without the first problem. In which case I could probably make it work by manually calling bpy.ops.object.bake() for each object, rather than baking them all with a single call. So it might work! I'll give it a try. (Having said that, it seems hacky and brittle, much like attempt #3 itself.)
|
|
| Apr 5, 2022 at 23:56 | comment | added | X Y | Is it work if check the img.bindcode or img.pixels[0] are changed ? | |
| S Apr 5, 2022 at 23:10 | review | First questions | |||
| Apr 6, 2022 at 2:42 | |||||
| S Apr 5, 2022 at 23:10 | history | asked | Cessen | CC BY-SA 4.0 |