Why a MTLLoader dosen't parse map_ka data?

Hi guys :slight_smile:
I’m testing performance now. Three.js and Babylon.js

I have loaded the same obj model.
The texture count of Babylon.js was measured to be twice that of Three.js.

I think the MTLLoader of Three.js does not parse map_Ka data in mtl file.

This is part of my mtl file.

newmtl rand
	Ns 10.0000
	Ni 1.5000
	d 1.0000
	Tr 0.0000
	Tf 1.0000 1.0000 1.0000 
	illum 2
	Ka 0.5882 0.5882 0.5882
	Kd 0.5882 0.5882 0.5882
	Ks 0.0000 0.0000 0.0000
	Ke 0.0000 0.0000 0.0000
	map_Ka texture\ob_floor_03.png
	map_Kd texture\ob_floor_03.png

map_ka Is there any reason not to parse the data?

From one of the unofficial standards:

The Ka statement specifies the ambient reflectivity using RGB values.
The Kd statement specifies the diffuse reflectivity using RGB values.

Kd values can be nicely mapped to the .color and .map property of MeshPhongMaterial. But there are no material properties that match Ka. In other words: Compared to Babylon.js, three.js does not allow to specify an ambient color for a material.

Okay… I understood. Thanks :smile: