You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following error is generated thrice at Blender start:
Warning: TypeError('bpy_struct: item.attr = val: POWER_SEQUENCER_OT_speed_up_movie_strip.speed_factor expected an int type, not float')
What is the expected behavior?
No errors at start.
Tell us the steps to reproduce the bug, and if possible share a minimal demo of the problem.
Start up Blender with Power Sequencer activated.
Error (above) is generated.
Feature request
Describe the problem you're trying to solve.
Tell us which solutions you've explored, the solution you would pick, and why you think it would be the best for everyone.
Other
Win 10 x64
EVEYTHING is as up-to-date as it gets, but I am not running any alphas nor betas.
I imagine that fixing the types or making explicit type conversions would correct this error.
The text was updated successfully, but these errors were encountered:
This was closed because the original report said there was an error, but there was nothing looking like an error on my end. I asked for more information and never got an answer or clarification, so it's natural to close in this kind of situation.
Now I see, it is if you run with a command-line window, which I suppose happens on Windows, you'll see warnings.
They don't break anything, so I won't bother with them, but if someone wants to contribute a fix for that, that'd be welcome.
I'm submitting a...
Bug report
The following error is generated thrice at Blender start:
Warning: TypeError('bpy_struct: item.attr = val: POWER_SEQUENCER_OT_speed_up_movie_strip.speed_factor expected an int type, not float')
What is the expected behavior?
No errors at start.
Tell us the steps to reproduce the bug, and if possible share a minimal demo of the problem.
Feature request
Describe the problem you're trying to solve.
Tell us which solutions you've explored, the solution you would pick, and why you think it would be the best for everyone.
Other
Win 10 x64
EVEYTHING is as up-to-date as it gets, but I am not running any alphas nor betas.
I imagine that fixing the types or making explicit type conversions would correct this error.
The text was updated successfully, but these errors were encountered: