Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Hello, your script enhanced may uv editor a lot. But I still want one feature. I want to auto select all the overlapping UV in 0-1 space which is useful for baking textures.
There is a feature "shift overlap" in 3ds max script "TexTools" do this. But I hope there is a script for maya, too.
Hello.
Im working on a reversed feature of what you are suggesting: the ability to move back offsetted shells into the default 0 -> 1 -range. It would be nice to have both that and the feature that you are suggesting so Ill take a look at that for the next version. Currently there is a lot of WIP but NSUV 1.5 will be released this summer.
This is a great idea, any update on this ?
Just auto select all overlapped uvs would be great.
Or maybe, among a uv selection, unselect the non overlapped, leaving the overllaped selected.
Thank you very much for the good work !
Hello,
Current status is this:
I've begun working on this feature but unfortunatly it has been put on hold for various reasons. I'm currently spending all time on the next version (v2.1) and unfortunately this feature will not be included. The feature turned out to be much more complex than anticipated, involving custom geometry classes and different intersection algorithms (math). It will continue to have a high priority after the 2.1 release but it will not be included until at least v2.2.
wdw89
Comments on this feature request:
Martin Dahlin said over 10 years ago:
wdw89 said over 10 years ago:
bad cow said over 8 years ago:
Martin Dahlin said over 8 years ago: