Copy Uv Set From One Object To Another

[blambert27]

I'm still having trouble finding how to simply copy UVs across two identical objects.
I have a UVset on one model I wish to copy to a new UV set on the other, WITHOUT upsetting any existiing UV sets.

polyTransfer gets rids of existing sets and overwrites them all, or so it seems. polyClipboard on a face-by-face basis craches. And the docs are useless on how to use Copy UVs and Paste UVs between objects

Has anyone got a good solution please?

Thanks

BL

[failure]

What exactly have you tried to do to make you conclude that transfer doesn't work?

[blambert27]

I have a model with threeUVsets, 'map1' and u'vset02' and 'uvset03',
I want to keep map1 and uvset02, and then perhaps copy some UVs from another identical model into uvSet03, (or even create an extra uvSet04 if need be)

I select the model I wish to copy UVs from, and then the above model and then polyTransfer UVs.
ALL my UV sets are then overwritten by the data from this model.

There are NO options for which sets to presrve and which to overwite.

If the object I wish to copy from has just its 'map1', or mismatches the target in any way (regarding uvSet names or number of them ), then the original model's uvSets are cleared of data too.

BL

[failure]

delete all uv sets from source object except the one you want to copy ( and map1 which you cannot delete ) and then do the transfer. Obviously you'll need to copy content of both map1's into other sets because you can't delete map1 consequentially it will always be transfered.

[blambert27]

Nope....

On my source : map1 uvSet03
On my target : map1 uvSet02 uvSet03

... it still deletes all UV data from the uvSet02 on the target. The set name is still there but all data gone

[failure]

Ok, try to run this quick and dirty hack:

CODE
string $source = "pSphere1";
string $destination = "pSphere2";

int $nfaces[] = polyEvaluate -face $source;

for( $i = 0; $i < $nfaces[ 0 ]; ++ $i ){

   polyClipboard -copy -uv ( $source + ".f[" + $i + "]" );
   polyClipboard -paste -uv ( $destination + ".f[" + $i + "]" );

}

If you need to do a lot of transfering it'd be best to download one of the uv transfering scripts from repository.

[blambert27]

Sorry, tried that before, from my first mail....

'...polyClipboard on a face-by-face basis crashes...'

It bombs out on heavier objects (~5000+ polys), even if I add a polyClipboars -cl to clear the clipboard each time

[joojaa]

one can copy the arrays diirectly too asuming the tropology is the same!

[blambert27]

Yeh, that way works, I've found it a little tricky to script it cleanly though. I basically use the connection editor to connect the uvSet[#] to the desired uvSet[#] for the target shape. You need to have some uvs to start with though, (ie no empty uvSet). We may need to get a clean script that can take, say 5 inout surfaces and copy their map1 uvSets to NEW uvSets on our hero model.

My inital post reason was in surprise that this isn't easy to do with the tools that are there.

[failure]

mel is a tool that is there

[blambert27]

I'm not knocking Maya here..... I've been using it for six years+ since version 1.0 and use it for everything...... so please don't misinterpret what I'm writing.

I was merely saying that for the general user, the function I'm needing is not there 'out-of-the-box'.

I can probably write a script that does this eventually, and am doing so now, but I was after a robust and quicker fix as there a other modelers here who have asked me if this transferring is possible a need to use it ASAP.

[joojaa]

Thing is that because productin environmants vary so much theres no way any software firm cankeep up with ALL users demansds, so what they do instead is cobcetrate on the CORE, not the toolset persee. So thisway even a very different job than was originaly designed can be doeb becase the core is done well.

NOW herein lies mayas geratness its CORE is fabulous. Its jut that the tools on top of that core are limitted, whereas other progs liek MAX is primariliy about teh toolset, wich is on a core that leaves to be desired. NOw from the end users point the max method appears superficialy better, while it is in reality hands down worse. Because it can only tackle problems that the tools were meant for mostly.

Theres a lot of functionality in maya you wont find in the menus! Thats why highend has a script repository. This goes ver close to mayas core philsofy so its not supprising at all. The general idea of mayas design s that the studio where you work HAS a TD around to do tools for the animators, in house.

But yeah you cant say maya does not have a functionality IF its not in the menu but stll its there. It does.

[blambert27]

Of course it does, I totally agree with you, I'm constantly using MEL to write loads of poly tools for how I work here and don't have a single bad word to say about how Maya can be customised.

IMHO though, the tool in question I wrote about is one of those functions that could and should be in there as a standard tool, as its there in other packages, and thats the problem.... if you have a user who is fresh to Maya and native in one of those other packages, its frustrating for them.

I'm writing an uber UV -transfer UI though, so will make everyone happy!

Thanks for replies

[joojaa]

Yes maybe one of the best testaments of mayas superiority in many areas is This melscript.

But sure it takes usrss som time to get used to the idea that most tools come form a community of people in your own business rather than the install package.

[blambert27]

that script is great, if you use the new unfoldUV afterwards it looks awesome

[doug-wilkinson]

If someone could post a script or instructions on how to write it, i would be happy to write it.

Simply saying, you need to copy the array from one object to another doesn't mean anything.

I hope that we can all takle this prolblem togeather.

p.s. also, adding the image warp funtion in maya 7 and not being able to naitively transfer uvs int a specific set is kinda dumb. It would be nice to map something, then take it into a 3d paint program and if you need to adjust UVs in there, you can do so. then Bring back to maya, transfer UVs into a new set and then warp the current texture so you don't loose any work.

[joojaa]

copy the default uvest to an

[joojaa]

Oh and by the way... if the object truly is the same tropo then you can just switch the new object back over the one you have bound ist far easier!

Oh and copying arrays refeers to the node refernce if you look at the node ref for a mesh node it all becomes clear as to what arrays im refeering to. (yes they can be directly manipulated!)

[doug-wilkinson]

QUOTE(Joojaa @ 02/23/06, 01:17 PM) [snapback]229124[/snapback]
copy the default uvest to an

[joojaa]

Yes it does! i just tested it yesterday on 7.01 and it works fine. All you need to do is make sure you dont have namimg clasheds thatwould do overwirtes! The only thing that works a bit nastily is the default uveset wich works a bit unexpecedy at times.

Ofcourse the target mesh must have a EMPTY uvset created so that transfeer will do the overwrite. Otherwise who knows what might hapen (i didnt realy have time to enforce and anlyze this behaivour).

Thing is this is how i tested this. I made 2 cubes added number of sets to the other cube that differed form the original. Then i copied the target of trasfer cubes befault map to safety, and set that cubes defout map to the currentSet. The I ensured that both cubes had Sets with same names by creating them to target cube(and renamed ones that did exist on both so not to overwirte them), went on to trasfer. AND viola the cube that had 1 set now had that 1 set and all the other sets fom cube 2, 3 sets were ok and correct And amptly named. Now, this by nature demontrates you can move isolated sets, see if i wonly would have wanted to trasfer one of the 2 sets form the other cube to the firts one i can allways delete the extra sets at thispoint! Even if this wouldt work form less sets to more (it does) you can allways move the more sets to the less and back, a bit of shufling but doable.

Yes my intial code dint work becaus id dint realize maya allways copied over ALL same named sets, thing is tough under some mysterious conditions maya does indeed redo the sets itself but not allways.

But hey your oviously not using the same maya as i am. But yeah ill post code as soon i i can get out of the liibrary basements im trapped (doing reserch) at currently. Not that you opparticulary deserve the code but.