Artifacts due to intersecting polygons?

Hey there. I’ve been having a bit of a problem with my 3D model.

White lines/artifacts appear along the edges where my meshes meet each other:

http://i.imgur.com/e2Z6K.png

I was hoping this was due to the engine only rendering one side of the mesh,

but placing a black plate behind the white areas doesn’t help :confused:



Does anyone have an idea on how this can be fixed?

Is there some graphics setting that can be set to fix this?



Regards, MrAdam.

Make proper models. Intersecting meshes are not good anyway, you get issues with shadows, shaders and basically everything. Don’t compose your models of base shapes but create it via extrusion and seaming. A car like this should be one hull mesh and if you add other meshes they should definitely not overlap.

I did not create the model, our 3D artist did.

The model itself is proper, as this only appears on android, and not on the desktop.

Probably the issue happens because we use 16-bit floats for the position in the Android vertex shader.

I added an issue in the tracker for this: http://code.google.com/p/jmonkeyengine/issues/detail?id=483

Any chance a test case showing the issue? Also does it happen with a particular android device or all of them?

@Momoko_Fan said:
Probably the issue happens because we use 16-bit floats for the position in the Android vertex shader.
I added an issue in the tracker for this: http://code.google.com/p/jmonkeyengine/issues/detail?id=483
Any chance a test case showing the issue? Also does it happen with a particular android device or all of them?

It happens on all Android devices (We've tested several models running from 2.2 - 4.0.3)

Merging the meshes as suggested in another topic didn’t help.

As you can see on the image pixel-holes are appearing even in solid meshes like the tires :confused:

@mradam said:
Merging the meshes as suggested in another topic didn't help.
As you can see on the image pixel-holes are appearing even in solid meshes like the tires :/


the best way is to do testcase, as Momoko_Fan mentioned. Then developers/community could test it, and make a fix.