Freezing Transforms Destroys Model

[jlindbergh]

Hi

I have a question about a strange problem I have when freezing transforms on a model I've got. Here's a screenshot of the outliner and the unfreezed model:

Only group1 contains any actual transformations. When freezing the transforms on group1 (used for scaling the whole model), the Facades-mesh seems to go completely nuts for no apparent reason (image below). Why is this happening?

I've tried troubleshooting this myself, but I don't think I've gotten any wiser so far.... Adjacent vertices in the two meshes viewed in the Component editor seems to lie very close to each other, but when printing getAttr for the components through a script I made I get something else completely. I did an experiment by selecting two adjacent vertices from the different meshes before freezing transforms (marked in yellow in the images). These are the results:

CODE
Selected: Facades_04.vtx[16]
Component editor says: 0.3074365 0.5139885 -0.0233852
getAttr script says: 49488.41016 -62455.98438 -4364.022949

CODE
Selected: Roof_04.vtx[9]
Component editor says: 0.3074436 0.5139975 -0.0233842
getAttr script says: 27.1997757 -18.41135788 -27.41038322

What data am I getting here? First, the getAttr is very different very from what's in the component editor! Second, how come the getAttr data I get from the vertices differ so much?

I'm attaching the script below. I was trying to print the coordinates of the selected components but I'm not that experienced in mel, so please correct me if I'm wrong! And if I did not make it clear in the above example: I'm running this script with only one vertex selected at a time.
[codebox]string $sel[] = ls -sl;
if (size($sel) < 1) {
print "No component selected";
};
for ( $component in $sel ) {
print ("getAttr script says: ");
$pos = eval("getAttr " + $component + "");
int $i = 1;
for ($k in $pos) {
print (" " + $k);
if ($i%3 == 0) {
print ("\n");
}
$i++;
}
}[/codebox]

I'm using Maya 8.5 in Ubuntu (Hardy) Linux. I'm using a nvidia 7800 GTX card with latest drivers installed via EnvyNG. I wish I could write more about the origin of the model, but unfortunately I can't, and I'm pretty much stuck with what I've got. I'll probably have to solve this by going around this problem in some way, but I'm really curious about what's really going on in maya internally.

Thankful for any enlightenment!
regards
/Johan

[gmask]

Why do you want to freeze the model?

I beleive the component editor is only giving you local values.

At any rate if you want the world space of a selected cv it's better to use this code.

CODE
xform -q -ws -sp

[jlindbergh]

QUOTE(gmask @ 07/29/08, 08:48 PM) [snapback]289014[/snapback]
Why do you want to freeze the model?

I beleive the component editor is only giving you local values.

At any rate if you want the world space of a selected cv it's better to use this code.

CODE
xform -q -ws -sp

Thanks for your answer.

The thing is that this small model is part of a much larger scene. And for this project it's absolutely necessary that this scene has all its vertex positions (ie. untransformed) inside the first grid quadrant [0,0]->[1,1]. If I can solve this for the smaller model it should be easy to fix for the whole scene.

When I move the group1 transform, the values in the component editor changes, so it actually seems like it displays world coordinates.

I tried inspecting the model with xform, but that only gives me values of transformations, not individual vertex values.

The theory I'm still having is that this is because the values I get from getAttr (whatever they are... help me out here ) are so different for the two adjacent meshes, and this causes precision errors when freezing*. But since I understand Maya uses double precision for calculation that shouldn't be a problem.. So I'm still quite puzzled.
If someone wants to take a look I'd be happy to send you the model!

regards
/Johan

*They're scaled with a uniform scale factor of 0.00631167

[gmask]

QUOTE(jlindbergh @ 07/30/08, 12:41 AM) [snapback]289033[/snapback]
I tried inspecting the model with xform, but that only gives me values of transformations, not individual vertex values.

you need to select a vertice and then run that command

QUOTE
*They're scaled with a uniform scale factor of 0.00631167

that's absurdly small.. it's pretty much not reccomended to try to work at a scale that small

[jlindbergh]

QUOTE(gmask @ 07/30/08, 04:26 PM) [snapback]289050[/snapback]
you need to select a vertice and then run that command

That's exactly what I did, but "xform -q -ws -sp" only seems to return the translation of the geometry even if I only select one vertex. Even tried it with a simple unit cube i randomly translated around a bit. Don't know if I was clear on that, but I am working with a polygon model here.
[edit] ah, I see...when I do "xform -q -ws -t" it works better with the vertex position!
QUOTE(gmask @ 07/30/08, 04:26 PM) [snapback]289050[/snapback]
that's absurdly small.. it's pretty much not reccomended to try to work at a scale that small

Ya, it is really small, and if I'd had anything to say about the creation of the original scene I wouldn't have had to scale it down in the first place. But still, I don't think it's too small when considering we're working with double presicion.

Aaanyway, I successfully worked around this by exporting the whole scene to COLLADA, reimported it, froze the transforms and whaddya know, the model didn't break! Why did it break before, in Maya-format? Beats me...