Stop-motion-OBJ not working in Blender 3.3 about stop-motion-obj

[neverhood311]

Well this is unfortunate. It looks like they changed the OBJ importer API from version 3.3 to version 3.6. Since Blender 3.3LTS is on its way out in a few months and I'm still trying to get the addon working for 4.0, I'm not going to make a special version for 3.3.

So you have three options, two of which involve some Python surgery.

Option 1: Switch to Blender 3.6. I realize this may not be possible with your circumstances, but this would be the quickest route.

Option 2: "Downgrade" your copy of Stop Motion OBJ to use the legacy OBJ importer. If you navigate to where the addon is installed on your machine (looks like C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\Stop-motion-OBJ\stop_motion_obj.py based on the error message you shared), open up stop_motion_obj.py in a text editor and find def loadOBJ near line 502. There are a few version checks in this function, two of which are checking for version 3.3. Anywhere it's checking for (3, 3, 0), you'll want to change it to (3, 6, 0). This means that it will use a different OBJ importer using the correct parameters. This should work, but it means you'll be using the legacy (slow) OBJ importer rather than the faster one.

Option 3: Fix the function call to match that of the 3.3 OBJ importer. Like in option 2, you'll need to find def loadOBJ near line 502. It's trying to pass in three parameters that exist in the 3.6 importer, but not in the 3.3 importer: global_scale, use_split_objects, and use_split_groups. If you remove these three parameters from the function call, it should work (I've tried it successfully with Blender 3.3). So after the 'surgery', it should read:

bpy.ops.wm.obj_import(
                filepath=filePath,
                clamp_size=self.obj_clamp_size,
                forward_axis=newForwardAxisStr,
                up_axis=newUpAxisStr)

Hope this helps!

[protovu]

Hi Justin,

Thank you for outlining the various options. Most kind of you.
Complicated for my little brain, but I will give these options a try.

Add to the mess.....I am a Blender Octane user, so upgrades there usually involve unwanted surprises that screw up files generated years back. Your addon case in point. I had to revert to Blender 2.9x to get results. Sub-optimal.
Ug.
Your Addon should be part of Blender, I think.

Best,

Rick