Page MenuHome

NewTek MDD format import/export add-on needs updating
Closed, ResolvedPublic


System Information
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 419.17

Blender Version
Broken: version: 2.80 (sub 74), branch: master (modified), commit date: 2019-06-19 13:06, hash: rB72690bbeca85
Worked: (optional)

Short description of error
The bundled NewTek MDD exporter is marked as 2.80 compatible but looks like it's not up to date with the last rounds of API changes.

Exact steps for others to reproduce the error
Enable the Import-Export: NewTek MDD format plugin.
Select the cube.
File->Export->Lightwave Point Cache (.mdd)
choose file, [Export MDD].

Traceback (most recent call last):
  File "G:\bdev\build_windows_Release_x64_vc15_Release\bin\Release\2.80\scripts\addons\io_shape_mdd\", line 152, in execute
    return, **keywords)
  File "G:\bdev\build_windows_Release_x64_vc15_Release\bin\Release\2.80\scripts\addons\io_shape_mdd\", line 72, in save
    me = obj_eval.to_mesh()
AttributeError: 'bpy_func' object has no attribute 'to_mesh'

Event Timeline

Gavin Scott (Zoot) edited projects, added Add-ons; removed BF Blender.
Philipp Oeser (lichtwerk) triaged this task as Confirmed, Medium priority.

I looked at this addon today because i wanted to test animation export. I needed to get some animation in bl 2.79 and to do so i used the MeshCache modifier. We have 2 options here either use MMD or PC2, im not really familiar with both. BUt i remember seeing a tutorial from quite some years ago which used MMD.

One thing i noticed is that MMD exports with the origin set to world matrix (0,0,0) and PC2 has an option for this. Is it standard that MMD has origin or widget in the center of the word? Because when importing it back into Blender the object now get double offset due to this.

I added the part from pc2 o mmd addon and got it to work. So question is should this be added to the default one?

This is the original scene in bl 2.80

This is how it imported in 2.79. Because origin on the original object is not at (0,0,0) it gets double the offset due to this

Notice how the PointCache expoter has more options