I tried the following:
1. I export to .ase from max (in max everything looks perfect, and i also tried to scale it to different sizes)
2. I import it to scene builder. Drag it in the scene from library.
3. The I pubish it with maximum geometry, light and everything you can imagine.
4. And the result: index.html
See the edges of the door and sideskirt? From some angle and from far distance they look really bad. They are sometimes black and seem to break the geometry either. I think it's simiar to the problem, when the exported geometry's black edges shown trough opaque objects. I could avoid this problem by scaling it to different (smaller) size in max, but these don't wanna disappear.
What should I do? It's not scaled properly? I tried to follow the steps of documentation refering to prepare the 3D objects in max for export. And I lost the line somewhere where it say: set max unit size to feet/inch, then make a 2x2x2 cube. This cube has to be 2feet or 2inch wide?
Please, help me out. Thanks.

This message has been edited. Last edited by: SmokeDT,

Hi !!

Check this post about scaling objects for VET...
http://viewpoint.infopop.cc/eve/forums/a/tpc/f/75129280...911066231#8911066231

Cheers,

Anup

Really thanks!
I would like to try it now, but I'm working. I will try it as soon as I get home and post the result here.
Thanks again for your fast reply!

So. I followed those steppes and still looks the same, as you can see it here: index.html

But the hierachy of my scene look much different and that may cause the problem.
When I export the geometry and import it to scene builder then it looks something like this:

>3D Layer
>Runtime Camera
>proba03_Scene
>MAXInstance
>Shape03

When I publish it and view the .mtx file then it shows the scale transformation at <MTSInstance Name="proba03_Scene" > and no transformation at <MTSSceneParms...

Then when I scale it as you said, then the scale transformation at <MTSInstance Name="proba03_Scene" > disappears.

Although no matter what I do this always stays the same and it may cause the problem:

			<MTSInstance Name="MAXInstance" >
				<Transform>
					<Scale x="-1"  y="-1"  z="-1" />
					<Rotate x="90"  y="180"  z="0.00001" />
				</Transform>

Here is the .mtx link:
index.mtx

Any suggestion what should I do?

This message has been edited. Last edited by: SmokeDT,

Oh, and one more thing.
I tried to edit out the "proba03_Scene" "MAXInstance" instances with the scene builder from from the scene,
here is the result:
b.mtx

the instance named "Shape03" gets -1 transformation scale values.

This message has been edited. Last edited by: SmokeDT,

Oops =O

I forgot to press "Reset Transform" in max at the end.
Now it looks different, but not exactly perfect:
c.html
c.mtx
The top edge of the backdoor still looks bad. Can It be better?

This message has been edited. Last edited by: SmokeDT,

Yes! It can be better! See the perfect result here:
b.html

I spent days tring to find the best solution for exporting models from max. I've tried Deep Exploration, Polytrans, in every way you can imagine. None of them gave a good looking result, because the problem is in the auto anti-aliasing.
Here is what I've done:

1. export in .ase format from max (don't need any scaling of objects)
2. import it to Enliven, pubish it in uncompressed format (.mtx)
3. edit the .mtx file with simple notepad and change the following lines:

	<MTSSceneParms RenderMode="LightTexture"  ShowWidgets="0"  AntiAlias="1"  DoShadow="1"  RequiresClear="1"  BackColor="1 1 1"  BlendShadow="1"  BoundShadow="1"  ShadowY="-0.86856"  ShadowOpacity="0.85"  ShadowRadius="10"  ShadowColor="0 0 0"  AccumMax="12"  EdgeBias="1"  EdgeEffect="0"  SortRule="-1"  FilterMinimumMilliSecs="100"  Prelite="0"  PreliteColor="0 0 0.99" />

(I'm not sure if all of this parameters are needed, but this way its working perfect)

And also change the object's instance parameters:

 <MTSInstance Name="Shape03" > 

change to:

 <MTSInstance Name="Shape03"  AntiAlias="0" > 

With this solution your objects will get a delayed anti-aliasing and a perfect look.

This message has been edited. Last edited by: SmokeDT,

Good news! Congrats! Also, if you are ever wondering what all possible properties are available for a given tag (such as <MTSInstance>), check the "Verbose" box in the publish room and publish the mtx as uncompressed. When you look at the mtx in a text editor, you will see all possible properties for the tags in your scene are written in. This is a great way to see all the mtx properties at your disposal. Then you can look up whichever properties you are interested in in the MTX Reference.

Cheers!