Page 1 of 1

Texture problem when using -bitmaps flag

Posted: Wed Jun 04, 2008 1:56 pm
by bjorn.syse
Hi everyone, I have this problem when using with the following workflow:

1. I model and export an MXS using Rhino 4.0 on Windows.
2. I render this MXS on OSX using a batch script (thus using the command line interface for MXCL)

One of the materials I am using, have textures referenced with a windows path in the material.

These problems occur:

1. First, the problem was a "Connection failed" error, probably resulting from the path beeing something OSX could not connect to.

I tried to solve this, by using the flag -bitmaps: in mxcl, to explicitly point out where to look for bitmaps. This worked, but a new problem occured:

2. The texture placement, I had tweaked in Rhino using "Texture projections" was disregarded, and the textures were placed in a default manner (see the pictures).

Image

Image 1: Correct texture placement (render direct from Rhino/Windows)

Image

Image 2: Default, non-intended texture placement (render using -bitmaps flag on OS X)

So, my question is, am I right using the -bitmaps flag, or is there a better workflow for using Windows and Mac OSX in coalition?

Best regards

- Björn

Posted: Wed Jun 11, 2008 10:28 am
by bjorn.syse
Can someone comfirme this texture placement error when using -bitmaps flag with mxcl.exe?