Mudbox scale issue

[bottleofram]

Hi folks,

Any mudbox users around? How do you deal with scale difference issue? An object in mudbox, or rather the exported object, is about 10 times larger than the scales i'm used to in softimage (1 unit = 10cm). As far as i can tell there's no way to adjust this via preferences, so for now i'm going to compensate by parenting an object to a null with 0.1 scale in soft while working and deal with transforms latter, but this is not ideal. Perhaps there's a batter way...

Also, any known interop issues to be aware of?

Thanks

[Maximus]

I used Mudbox really few times and this was one of the biggest annoying thing i've found which made me quit it.
When you export something from softimage it will import in mudbox realy small, you cant even work with brushes and sculpt tools Mudbox gets clunky and slow, parameters like Strenght/brush size are totally out of control and without any precision.

So i had to scale it up like 10 times or more, and bring back to soft and scale it down 10 times or more. Painful workflow. They should fix this.

[Daniel Brassard]

So what I gather from your comments is that Mudbox base unit is 1 meter.

Which would explain why object modeled in Softimage ( with it's unit based of 10 cm) would indeed translate to an object 10 time smaller in Mudbox and anything started in Mudbox would be ten time bigger!

Good to know! (1 meter divide by ten is 10 cm)

Dan

[bottleofram]

Upon some more testing...

You can set units as far as UI preferences go in mudbox but ultimately they have no effect on the fbx export and you have no manual control either (this, of course, leads to problems regarding one-click workflow). However, it does have an effect on obj export, BUT! for the correct scaling here you need to set mudbox units on decimeters. And you guys can guess which units it doesn't offer you as an option... Yup, it's decimeters.

So, unless i'm missing something, neither fbx nor obj can be exported/imported correctly (and this is important since mudbox brushes are very scale dependent).

Other than this, one-click interoperability seems to work quite well - i had no other issues so far. Maps are generated and connected back in soft very nicely and the problem arises when you scale down the objects and freeze transforms. I'm working with 32bit exr's so my maps became overblown and the values need to be scaled down as well.

I can probably automate this through scripting but man, why am i not surprised to find two autodesk applications not working well together?

[Rork]

I can probably automate this through scripting but man, why am i not surprised to find two autodesk applications not working well together?

Even worse...

When using two different releases, the SendTo functionality doesn't work anymore. You always have to use 2012<>2012, or 2013<>2013 etc.
So you cannot skip a version while upgrading the other.

[Falam]

I can probably automate this through scripting but man, why am i not surprised to find two autodesk applications not working well together?

Even worse...

When using two different releases, the SendTo functionality doesn't work anymore. You always have to use 2012<>2012, or 2013<>2013 etc.
So you cannot skip a version while upgrading the other.

I use Mud pretty extensively, the send to feature is really only good for sending simple objects back and forth, don't even attempt topology changes, and if you do, bon voyage.