Summary

Title:Ornatrix does not handle scale conversion between scenes with different system units
Category:Crash/Critical
Status:Fixed
Posted By:Bipolar ( David Karapetyan )
Date Created:8 November 2017

Problem

Description:

Hello,

 

we are currently working on a large environment scene project, which needs to have system units set to meters. At the same time, small assets for the scene are being made in scenes with system units set to centimeters. It's generally not an issue, because pretty much every renderer and plugin handles scale conversion correctly. Ornatrix, however, seems to have problems with it.

 

Here's an asset in the asset creation scene (CM as system units):

And here is the same asset merged (happens with xRef too) in the environment scene (M as system units):

 

We are very worried about this, because without a fix, we can not finish our project, and we just don't have time or resources to re-do all the grooming on all the assets from scratch.

 

The issue appears to be caused specifically by lack of scale conversion on the "Ox Edit Guides" modifier, as with this modifier disabled, all other length parameters appear to be converted correctly. We can privately send you a scene to reproduce the problem if needed. Would it be possible to get a fix for this as soon as possible?

 

Thank you very much in advance!

Steps to Reproduce:

Hello,

just a quick update. It appears that "Ox Strand Curling" is another modifier, which does not get its scale converted correctly. Its magnitude appears to be a lot stronger in Meter syste units scene. It is getting a bit confusing, because some values on some modifiers do get converted correctly, while others do not. Frown

Hi David,

Thank you for the report. Which version and build of Ornatrix are you using? We fixed this issue a few months back, we tested several scenes and it was working fne (the scale conversion). If you are using an older build, can you please update and try again? If the problem still persist in the latest nightly build please send me the problematic scene to Jeordanis.F@Ephere.com.

Jeordanis Figuereo (Product Designer. EPHERE Inc.)

Hello,

Thank you very much for a quick response, we really appreciate it. The build we are using is 5.2.5.12692 from 22 October. I am seeing there is already a new build posted since, labeled as 5.2.6.12896. I've just tested this build, and unfortunately the issue still persists.

 

I will pack the scene up and mail it to you as soon as I can. Thank you!

Actually this issue should be fixed in 5.2.5.12692. We will take a look into this ASAP! Thank you.

Jeordanis Figuereo (Product Designer. EPHERE Inc.)

Thank you!

I forgot to mention that I am working on Max 2016 SP4, in case it could be related to Max version.

Hi,

 

sorry if I am pushing it too hard, but is there any chance we could get an ETA for the fix, so we can plan ahead with our project?

 

Thank you in advance :)

Hi,

I'm not sure but I was able to reproduce this and created a ticket. Usually we fix bugs really quick, let's wait a couple of days, I will keep you posted.

Jeordanis Figuereo (Product Designer. EPHERE Inc.)

Yes, I already received your mail too. Thank you again!

Hello,

are there any news on this?

Thanks in advance.

Hi,

Not yet, but we are working on it. Please wait a bit more.

Jeordanis Figuereo (Product Designer. EPHERE Inc.)

Hi David,

This bug has been solved and the fix will be available in the next nightly build (13162+) please give it a try.

Jeordanis Figuereo (Product Designer. EPHERE Inc.)