Hey Martin, I am afraid that the software is not aware of this concept assuming this is only revealed when drawing into the texture editor viewport. You can still deduce it by scripting. what about this: - get the texture projection elements - create a bitmap matching the uv space (minmax u for columns, minmax v for rows, using a precision number to calculate the stepping) - iterate over the samples coordinates using their rounded (using the precision number) u and v values as indices of the bitmap - if the bit is already positive, it means the sample is overlapping - from the samples, retrieve the geometry components its should be quite efficient (compared to some bbox collision systems) and straightforward in python to write. -- jo
Le mercredi 31 octobre 2012, Martin a écrit : > Hi list, > > Overlapping UVs aren't good for baking textures, so we need to check if > the UVs are overlapping in any way and fix them. > > We are doing it manually right now. I mean, if the UV plane turns red, it > is overlapping. It's quite simple, but really tedious when you have > thousands of UV samples and lots of scenes and objects to check. > > Is it possible to make this task faster and more accurate? > > Any ideas? > > Thanks > > M.Yara >
