From 476fb84b0d6582da1e0a187f29ae5686fa381b07 Mon Sep 17 00:00:00 2001 From: Adam Johnson Date: Sat, 20 Jun 2015 17:44:43 -0400 Subject: [PATCH] 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. --- korman/exporter/material.py | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/korman/exporter/material.py b/korman/exporter/material.py index d5979cf..ef8c2a2 100644 --- a/korman/exporter/material.py +++ b/korman/exporter/material.py @@ -238,8 +238,10 @@ class MaterialConverter: pl_env = plDynamicEnvMap pl_env = self._export_dynamic_env(bo, hsgmat, layer, bl_env, pl_env) 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 def _export_dynamic_env(self, bo, hsgmat, layer, bl_env, pl_class):