Bsurface addon don't work with new builds #42774
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#42774
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system and graphics card
gentoo amd64 gtx780 x2
Blender Version
Broken: latest (from builder.blender.org, for ex e240bd3)
Worked: 435eaa7 (from builder.blender.org)
Exact steps for others to reproduce the error
1- in edit mode paint gpencil strokes
2- push "Add Surface" button
3- get error "There aren't any strokes."
Changed status to: 'Open'
Added subscriber: @brothermechanic
#42799 was marked as duplicate of this issue
Added subscribers: @eclectiel, @JoshuaLeung, @Sergey
@eclectiel, mind looking into this one? :)
@JoshuaLeung, just wondering, are there some PyAPI changes in the gpencil to which all the addons now need to adopt?
It's not so much an API change, but rather that Grease Pencil gets created on Scene level instead of Object level by default now. At least the object_grease_scatter one we have handles this correctly, but unfortunately, not all of the ones out there are quite as vigorous.
BTW, I've now added an entry to the Python API changelog about this.
Added subscribers: @MassimilianoPuliero, @mont29
Added subscriber: @BrendonMurphy
hi, grease pencil is a widely used tool & important to many peoples workflows.
care should be taken when breaking release addons & popular tools.
as there is no maintainer & I am responsible for it's inclusion in Blender, i'll try to fix &/or try to negotiate fixes with other addons & Blender devs.
this addon should be fixed before 2.73 release as it's wide user base would be very disappointed.
Added subscriber: @ErickNyanduKabongo
Hi Joshua,
I m kind of understand you but can you make so that Grease Pencils gets created on object as default because many artists use GP to sketch on model and many add-ons rely on that ability for now retopo workflow will get really slow. Please bring those stroke back please.
Hmm... maybe I'll need to implement that switch to set where these get added after all. The impression I get is that for standard (non-old-addon usage), it's better that these are not attached to the object.
Added subscriber: @el_diablo
For now, one with commit rights could just change the try block on line 108 in mesh_bsurfaces.py to:
I'm not sure its good python there since I'm not python expert and don't know all the specifics of try/except/else blocks, but it seems to work.
EDIT:
Actually it should (maybe) use the last gpencil block created and not - [x], so I guess [-1]?
Here's a stop-gap patch to the addons themselves while I work on adding the toggle for setting whether gp datablocks are attached to the scene or to active objects.
gpencil_addons_patched-02.patch
It at least gets rid of the immediate problems, but at least from my tests, some other issues were cropping up. I'm not sure if those originated from this fix, or whether they were present in the addon.
This issue was referenced by blender/blender@fe4d0c234e
Changed status from 'Open' to: 'Resolved'
Closed by commit blender/blender@fe4d0c234e.
I've committed the switch to set where these are attached to.
So, for modellers/users of these addons, the only change to your workflow should be to just set "Data Source" from "Scene" to "Object" before starting to use those addons.
if you forget to do so before starting to draw:
I just test new build, it works!
Thank you.
Thanks a lot Johua,