Browse Source

We're not actually going to support CEMs

After discussion in #writers IRC and observing how Blender's image
environment maps work, it makes more sense to rely on our superior
implementation of dynamic maps.
pull/8/head
Adam Johnson 10 years ago
parent
commit
476fb84b0d
  1. 6
      korman/exporter/material.py

6
korman/exporter/material.py

@ -238,8 +238,10 @@ class MaterialConverter:
pl_env = plDynamicEnvMap pl_env = plDynamicEnvMap
pl_env = self._export_dynamic_env(bo, hsgmat, layer, bl_env, pl_env) pl_env = self._export_dynamic_env(bo, hsgmat, layer, bl_env, pl_env)
else: else:
raise NotSupportedError() # We should really export a CubicEnvMap here, but we have a good setup for DynamicEnvMaps
# that create themselves when the explorer links in, so really... who cares about CEMs?
self._exporter().report.warn("IMAGE EnvironmentMaps are not supported. '{}' will not be exported!".format(layer.key.name))
pl_env = None
layer.texture = pl_env layer.texture = pl_env
def _export_dynamic_env(self, bo, hsgmat, layer, bl_env, pl_class): def _export_dynamic_env(self, bo, hsgmat, layer, bl_env, pl_class):

Loading…
Cancel
Save