Well, I barely scratched the surface of Korman, and yet just knowing it's here I'm finally in the mood for building again ! And today I've had tons of cool ideas for my current Age...
I directly tried exporting two of my current Ages to CC. Alas, the two of them caused different export errors. But in both cases I just setup the World info and threw a spawnpoint and colliders - I didn't bother disabling some lighting or whatever.
- Show Spoiler
Traceback (most recent call last):
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\operators\op_export.py", line 102, in execute
e.run()
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\convert.py", line 67, in run
self._export_scene_objects()
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\convert.py", line 193, in _export_scene_objects
export_fn(sceneobject, bl_obj)
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\convert.py", line 211, in _export_mesh_blobj
self.mesh.export_object(bo)
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\mesh.py", line 258, in export_object
if drawables:
UnboundLocalError: local variable 'drawables' referenced before assignment
Looks like it's something with Blender's object modifiers. I use a LOT of them: edge split, boolean, subsurf, displace, etc. Might be that it's confusing Korman somehow.
- Show Spoiler
Traceback (most recent call last):
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\operators\op_export.py", line 102, in execute
e.run()
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\convert.py", line 67, in run
self._export_scene_objects()
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\convert.py", line 193, in _export_scene_objects
export_fn(sceneobject, bl_obj)
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\convert.py", line 211, in _export_mesh_blobj
self.mesh.export_object(bo)
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\mesh.py", line 255, in export_object
drawables = self._export_mesh(bo)
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\mesh.py", line 274, in _export_mesh
self._export_static_lighting(bo)
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\addons\korman\exporter\mesh.py", line 324, in _export_static_lighting
bpy.ops.object.plasma_vertexlight_autobake()
File "C:\Games\Tools\Blender\Blender275a\2.75\scripts\modules\bpy\ops.py", line 189, in __call__
ret = op_call(self.idname_py(), None, kw)
RuntimeError: Operator bpy.ops.object.plasma_vertexlight_autobake.poll() failed, context is incorrect
Aaaand another bug with context-dependent operators. In this Age, I baked light to vertexcolor a while ago. Maybe I should let Korman do that ?
EDIT: Solved, it seems it was something with the blend file itself. If you run into this issue, start from Blender's default scene, use File→Append to fetch all your objects from your previous Blender file. Just re-setup the Age properties and it will export fine.
Either way, these Ages barely export under normal conditions. My 2.7 port of PyPRP handled them, but I always had to split some meshes using over 0x8000 vertices, and apply a few modifiers before doing so. So they'll probably require some rework at some point.
Still, I look forward to being able to export directly from Korman, without going through all the loops PyPRP required. For now, I'm making good progress from within Blender, with just an occasional export using PyPRP to see how things are going.
- Me showing off Show Spoiler
It's been a while since I made so much progress on an Age...