Skip to content
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

Type Error at Blender Start #469

Open
2 tasks
ChaosOrdeal opened this issue Oct 6, 2022 · 4 comments
Open
2 tasks

Type Error at Blender Start #469

ChaosOrdeal opened this issue Oct 6, 2022 · 4 comments
Labels

Comments

@ChaosOrdeal
Copy link

I'm submitting a...

  • Bug report.
  • Feature request.

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.

  1. Start up Blender with Power Sequencer activated.
  2. 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.

@NathanLovato
Copy link
Contributor

Which version of Blender are you using?

@NathanLovato
Copy link
Contributor

Closing as no update was provided. Also, the version built into Blender seems to be working fine. I'd recommend using that one now.

@ChaosOrdeal
Copy link
Author

Closed for no version. . .

Try reading the original ticket again.

@NathanLovato
Copy link
Contributor

NathanLovato commented Aug 5, 2023

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.

@NathanLovato NathanLovato reopened this Aug 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants