iOS10：Omni类型的SCNLight忽略衰减值？-iOS10:SCNLightoftypeOmniignoringattenuationvalues?

2  

I have managed to change the result after changing the values of attenuationStartDistance, attenuationEndDistance, and attenuationFalloffExponent, but only when using that huge intensity value. iOS 10 is definitely not ignoring these parameters.

我已经设法在更改attenuationStartDistance，attenuationEndDistance和attenuationFalloffExponent的值后更改结果，但仅在使用该巨大强度值时。 iOS 10绝对不会忽略这些参数。

However, it seems that iOS 10 is applying yet another attenuation on top the previous one. It is also attenuating the intensity value automatically, regardless of those parameters. Perhaps it's treating this new intensity parameter as if in a physically based renderer, even when it's not?

然而，似乎iOS 10正在应用另一个衰减在前一个上面。无论这些参数如何，它也会自动衰减强度值。也许它正在将这个新的强度参数视为基于物理的渲染器，即使它不是？

So, if you have a distant omni light source, it seems that you'll still need a big intensity for it to be bright enough from a distance, even if you disable the attenuation.

所以，如果你有一个遥远的全向光源，你似乎仍需要一个很大的强度，即使你禁用了衰减，它也能从远处获得足够的亮度。

EDIT

编辑

iOS 10 is indeed using a physically based lighting model as the new default! After loading a model, iOS 9 will have SCNLightingModelBlinn for the lightingModelName property of the material whereas iOS 10 will have SCNLightingModelPhysicallyBased. You can achieve iOS 9 behavior by changing the value of that property after loading your model.

iOS 10确实使用基于物理的照明模型作为新的默认值！加载模型后，iOS 9将为材质的lightingModelName属性提供SCNLightingModelBlinn，而iOS 10将具有SCNLightingModelPhysicallyBased。通过在加载模型后更改该属性的值，可以实现iOS 9的行为。

for(SCNMaterial * mt in model.geometry.materials)
    mt.lightingModelName = SCNLightingModelBlinn;