Maya/Rf Scale

[Otuama]

A user has made a topic here:

http://www.realflowforum.com/viewtopic. ... 768#p48768

Can someone from NL give it a read and reply here or there?

[LuisMiguel]

Hi Otuama,

Thanks. I paste the same answer I put there.

There is an easier way to control the scales between platforms, I mean RealFlow and Maya or any 3d package. In this case you are exporting from Maya to RealFlow, and you want keep the scale you have in Maya and set a real scale more or less in RealFlow. So, you don't need to do nothing in Maya. You are right when you said that exporting from Maya and importing in RealFlow the relationship is 1cm (Maya)=1m (RealFlow), but in this case if you already have created the scene in Maya and exported to SD file, when importing the geometry in RealFlow, the geometry will be as you said, 6.7 meters. So, you'll need to set a global scale for your realflow scene to 0.01. Once you have simulated your scene in RealFlow, go to Maya and import the SD again. Now, the new imported sd will paste the keys for your object and you won't need to change the scale. In the case of fluid, the plugin will apply the scale factor when importing into Maya.

luisM.

[Otuama]

Hi Luis.

Just to let you know that in all of the fields in scale options, it isn't possible to enter a 0. For example, 0.01, 0.1 etc doesn't work.

Can you see if you have the same?

[tsn]

Can you see if you have the same?

Good find Otuama. Here on OS X it's not possible to enter a 0 as well. The smallest scale I can get is .1, but it's not possible to enter something like 0.01. As a workaround you can copy the desired scene scale from an ASCII/text document and paste it into the appropriate field. At least this works here on my computer.

[Otuama]

Yeah, pasting values with 0's works. Earlier when I said 0.1 didn't work, I meant typing the 0. So bad example because of course, .1 would have worked.

[LuisMiguel]

Hi,

Yeah, it is a bug. Basically the values you need to set is like .x, but you are right you can't set .01 for instance. We'll fix it.

Thanks for reporting.

luisM.