support of obj specification question

[MB]

I am writing an application that writes .obj files.

The application writes, scale and origin arguments to the texture file location records.

for example, here is a line where the origin is offset by one unit in all directions for the file ambient.tga .

map_Ka -o 1 1 1 ambient.tga # texture origin (1,1,1)

here is the syntax from the wavefront obj specification.
-o u [v [w]] # Origin offset (default 0 0 0)
-s u [v [w]] # Scale (default 1 1 1)
-t u [v [w]] # Turbulence (default 0 0 0)

here is a matrial definition generated by the program and put in a .mtl file.
newmtl 27_*Default_Masonry_CMU
Ka 0.69999998807907 0.69999998807907 0.69999998807907
Kd 0.69999998807907 0.69999998807907 0.69999998807907
Ks 1 1 1
illum 2
d 1
Ns 20.0

map_Ka -s 100 100 100 -o 1 1 1 D:\_obj Export Test\OBJ_Export\assets\textures\stone-59_d100.png
map_Kd -s 100 100 100 -o 1 1 1 D:\_obj Export Test\OBJ_Export\assets\textures\stone-59_d100.png
map_Ks -s 100 100 100 -o 1 1 1 D:\_obj Export Test\OBJ_Export\assets\textures\stone-59_s100-g100.png
map_bump -s 100 100 100 -o 1 1 1 D:\_obj Export Test\OBJ_Export\assets\textures\stone-59_b030.png


It appears octane is ignoring the -s and -o arguments and bringing in the texture map at 1:1 regardless.

Could someone tell me if octane recognizes these arguments or not, and if yes, perhaps tell me how to write these obj records correctly.

many thanks

mark

[roeland]

No, Octane reads only the file name of textures from the MLT files. We don't read any of the other parameters.

--
Roeland