Import erroer with recent beta 3d9209a

[engetudouiti]

There have been many up-date, then I re-make scene, and export json data from DAZ (new beta)

and Import scene (with json) in blender 2.83 .

Now it show erroer message. if I try again, blender load the scene, but still show same erroler log.

Traceback (most recent call last):
File "C:\Users\TAKE\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\DAZ-importtool-git\error.py", line 214, in execute
self.run(context)
File "C:\Users\TAKE\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\DAZ-importtool-git\daz.py", line 48, in run
getMainAsset(self.filepath, context, self)
File "C:\Users\TAKE\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\DAZ-importtool-git\main.py", line 139, in getMainAsset
raise DazError(msg, warning=True)
File "C:\Users\TAKE\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\DAZ-importtool-git\error.py", line 77, in init
invokeErrorMessage(value, warning)
File "C:\Users\TAKE\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\DAZ-importtool-git\error.py", line 71, in invokeErrorMessage
bpy.ops.daz.error('INVOKE_DEFAULT')
File "C:\myprograms\blender283git\2.83\scripts\modules\bpy\ops.py", line 199, in call
ret = op_call(self.idname_py(), C_dict, kw, C_exec, C_undo)
RuntimeError: Error: Traceback (most recent call last):
File "C:\Users\TAKE\AppData\Roaming\Blender Foundation\Blender\2.83\scripts\addons\DAZ-importtool-git\error.py", line 57, in invoke
return wm.invoke_props_dialog(self, width=width, height=height)
TypeError: WindowManager.invoke_props_dialog(): takes at most 2 arguments, got 3

location: C:\myprograms\blender283git\2.83\scripts\modules\bpy\ops.py:199

Though I do not think those erroer is critical .Because At least it seems load daz scene.

(I need to test if it cause problem or not to confirm)

[Thomas Larsson]

Apparently the Blender devs removed the height keyword from wm.invoke_props_dialog. Don’t understand why.

I have now tested with Blender 2.83 beta and this problem does not arise anymore. But many meshes are quite corrupt, although there are no error messages. I didn’t find anything special in the release notes, so either this is a Blender bug or an undocumented API change

[engetudouiti]

I do not suprsirse, what have changed ^^;

but anyway, blender 2.83 seems becom most reliable version,

(real beta is 2.90), then 2.83 is announced as LTS.

But 2.83 sitll update frequently, so I do not know what LTS means

I suppose I follow 2.83 beta, and not use 2.82 anymore,.

which blender version you using to develop plug in? I hope to know. I actually keep 2.82 2.83, 2.90, 2.79 ^^;

(may use 2.90 too , but not expect you support it)

[Thomas Larsson]

I mostly work in the most recent stable version, viz. 2.82a, and occasionally check that things still work in 2.79. When 2.83 is released I will switch to that.

[engetudouiti]

I see, so I may better test with 2.82a . I tried again.

(I keep up-date git repo about 2.82 too,, but it seems not good idea,,)

[Noname]

@engetudouiti 2.83 is not released yet and will be LTS (Long Term Support) version. This means that new features will not land to that version only bug fixes. This is aimed for studios so they can focus / use in production / design their tool set on stable features during developments.

2.9X will be ongoing testing / development branch that will be updated with new features over time.

At least that’s how I do understand things, please do correct me if I’m wrong.

[engetudouiti]

At current I did not see erroer message anymore. though I do not test fully with recent 2.83