Page 1 of 2

mxs reference bug

Posted: Sun Jul 29, 2012 9:11 pm
by rickyinmotion
Small bug here. The right car is a mxsreference the left one a maxwell instance rotated at 180°
and below the result
No problem when I make render :roll:
Image

Re: mxs reference bug

Posted: Mon Jul 30, 2012 6:10 am
by JDHill
This is a problem in the Fire engine; we are working on it.

Re: mxs reference bug

Posted: Mon Jul 30, 2012 1:29 pm
by AlexP
I think that mxs references are rotated in C4D by 90 deg counterclockwise, aren't they? I've opened mxs reference in modo and there it seems to be ok.

Re: mxs reference bug

Posted: Mon Jul 30, 2012 1:54 pm
by JDHill
But do they render correctly in Maxwell Render? The problem should be specific to fire, and may be different for each host app, depending on its coordinate system.

Re: mxs reference bug

Posted: Mon Jul 30, 2012 9:38 pm
by AlexP
They render correctly as displayed, only when there is render instance of mxs reference it is rotated in fire, just that instance.
But still mxs reference is rotated 90 deg comparing to eg studio, just check top view in c4d and studio.

Re: mxs reference bug

Posted: Tue Jul 31, 2012 9:39 pm
by rickyinmotion
it seems that is broken in the final render as well
but another scenario, the mxs reference is rotated at 180° and it is broken,
no problem with the instance from the mxsreference and not be rotated.
Hoping that my explanatin are clear enough

Re: mxs reference bug

Posted: Wed Aug 01, 2012 5:53 am
by JDHill
The behavior should be dependent upon the actual MXS being used, so please provide a Cinema file, and the MXS you are referencing (jeremy at nextlimit dotcom), so we can be sure we are not missing any issues.

Re: mxs reference bug

Posted: Wed Aug 01, 2012 4:34 pm
by rickyinmotion
I sent you the scene
Thanks for your feedback

Re: mxs reference bug

Posted: Tue Aug 14, 2012 3:44 pm
by AlexP
Hi Jeremy,
Have you found where the problem with rotation is in both cases?

Re: mxs reference bug

Posted: Tue Aug 14, 2012 7:39 pm
by rickyinmotion
Exact, no news about my test scene :?

Re: mxs reference bug

Posted: Tue Aug 14, 2012 8:18 pm
by JDHill
Sorry, I have not been able to look at these properly until today. rickyinmotion, in your scene, I see what I described above -- that instances of MXS references can render incorrectly. This is the same issue we are currently working on; here, for example, are two versions of your scene rendered, where the left uses two MXS references, and the right uses one MXS reference, and one instance of that reference:
  • Image Image
AlexP, either I do not understand the problem, or my test is set up differently than yours, but I do not observe any 90° rotation when I make a reference of the MXS you sent:
  • Image

    Image

Re: mxs reference bug

Posted: Tue Aug 14, 2012 11:44 pm
by rickyinmotion
ok, thanks for your support and let's wait for a patch.
some news about hair with the maxon guy ? :roll:

Re: mxs reference bug

Posted: Wed Aug 15, 2012 12:03 am
by JDHill
I don't yet have any news for you on that.

Re: mxs reference bug

Posted: Wed Aug 15, 2012 3:11 pm
by AlexP
Jeremy, 90 deg rotation is observed in viewport, check top view in c4d and compare to studio. Your Z axis is on right side and X to bottom. On default top view Z is to top and X to right and indeed, imported mxs has same orientation as mxs reference. But Imported obj is ok, I mean it has same as in rhino orientation on top view viewport.

Re: mxs reference bug

Posted: Wed Aug 15, 2012 3:37 pm
by JDHill
Okay, I think I understand what you're referring to now. The problem is that a plugin does not control what Studio does when you put a camera into one of the "ortho" modes in Studio. This is not related to MXS references, you will find it is the same for any scene you write from Cinema (and other applications, though the behavior will be different, since the coordinate system used by each one is arbitrary). There has been a recent change to the Maxwell SDK which I believe may allow this to be compensated for -- I'll bring it up with the Studio developers.