-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop-motion-OBJ not working in Blender 3.3 #190
Comments
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 Option 3: Fix the function call to match that of the 3.3 OBJ importer. Like in option 2, you'll need to find
Hope this helps! |
Hi Justin, Thank you for outlining the various options. Most kind of you. 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. Best, Rick |
Hoping you can help, as this is a great Addon.
Win10
Latest Addon version, 2.2
Simply not behaving correctly.
By comparison, ages ago I used this addon with Blender 2.x ( the 2.1 version of the addon).
When importing the mesh, I would see the import indication of 4 separate 6's in a square configuration.
Then once imported , the mesh would behave as expected. I would be able to adjust the start frame time, and other settings.
Perfect.
Just now trying with Blender3.3 and not seeing the import 6's (if that is meaningful with this version) and even though I follow the correct
I get the following error:
Python: Traceback (most recent call last):
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\Stop-motion-OBJ\panels.py", line 320, in execute
meshCount = loadSequenceFromMeshFiles(seqObj, mss.dirPath, mss.fileName)
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\Stop-motion-OBJ\stop_motion_obj.py", line 880, in loadSequenceFromMeshFiles
mss.fileImporter.load(mss.fileFormat, file, False)
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\Stop-motion-OBJ\stop_motion_obj.py", line 466, in load
self.loadOBJ(filePath, streaming)
File "C:\Users\User\AppData\Roaming\Blender Foundation\Blender\3.3\scripts\addons\Stop-motion-OBJ\stop_motion_obj.py", line 502, in loadOBJ
bpy.ops.wm.obj_import(
File "C:\Program Files\BLENDOCT 3\BlenderOctane\3.3\scripts\modules\bpy\ops.py", line 113, in call
ret = _op_call(self.idname_py(), None, kw)
TypeError: Converting py args to operator properties: : keyword "global_scale" unrecognized
This: Sequence > empty Mesh appears in the outliner.
The text was updated successfully, but these errors were encountered: