FS#73448 - [blender] btracer internal addon has some crash

Attached to Project: Community Packages
Opened by Bruno d'Arcangeli (arcangeli) - Friday, 21 January 2022, 15:26 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Sunday, 31 July 2022, 19:09 GMT
Task Type Bug Report
Category Upstream Bugs
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Felix Yan (felixonmars)
freswa (frederik)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
Internal addon "BTracer" crash with the "Particle Trace" function with:

[Btrace]
particles.particletrace: Operator
Error: SplineBezierPoints.add(): error with argument 1, "count" - Function.count expected an int type, not float

This work perfectly in the same condition / file with blender downloaded on blender.org.

I can send a blend file and/or a small tuto for this.
This task depends upon

Closed by  Sven-Hendrik Haase (Svenstaro)
Sunday, 31 July 2022, 19:09 GMT
Reason for closing:  Upstream
Additional comments about closing:  Closing this as upstream as it should be fixed upstream but I'd be happy to patch it downstream if a patch is provided.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 16 February 2022, 20:56 GMT
Please attach your test file or better provide steps how to reproduce it.
Comment by Bruno d'Arcangeli (arcangeli) - Monday, 21 February 2022, 15:04 GMT
Hi,
It's easy to reproduce.
Launch blender with the default scene in a terminal.
Click on the particles tab as in www.arcangeli.fr/btracer_1.jpeg
Click on the + as in www.arcangeli.fr/btracer_2.jpeg
Click on the < as in www.arcangeli.fr/btracer_3.jpeg
Click on the "Create tab" and on >Btracer as in www.arcangeli.fr/btracer_4.jpeg
Choose "Particle Trace" and click Run as in www.arcangeli.fr/btracer_5.jpeg

The addon work perfectly with official blender binaries from blender.org

Thanks for your help
Comment by Sven-Hendrik Haase (Svenstaro) - Sunday, 13 March 2022, 04:27 GMT
I can still repro this with blender 3.1.0 as well. I'm not sure about the relevant differences between our version and blender.org. While this does look like a packaging issue, could you perhaps still post this upstream with a link back to this issue? They might be able to help us sort out what the fundamental problem is here.
Comment by Sven-Hendrik Haase (Svenstaro) - Monday, 13 June 2022, 12:08 GMT
Do you want to bring this up as as bug upstream?

Loading...