F2 addon crash #41871
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#41871
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
MacBook Pro, OSX 10.9.4, NVIDIA GeForce GT 650M 1024 MB
Blender Version
Broken: 2.71.6 f2c8209
Short description of error
The F2-Addon produces the following error if there is a material slot with no material assigned to it on the edited mesh.
Exact steps for others to reproduce the error
Create a cube - delete the material slot - add a new one but do not assign a material to it - try to use F2-Addon in Edit-mode
Changed status to: 'Open'
Added subscriber: @MauroPfister
Added subscriber: @lichtwerk
I can confirm this, patch attached{F114152}
Added subscriber: @Sergey
@lichtwerk, the patch seems good. Do you mind committing it to the addons repo?
This issue was referenced by
36a8b39da3
Changed status from 'Open' to: 'Resolved'
Closed by commit
36a8b39da3
.OKi, I commited
36a8b39da3
(hope this went through OK? - havent had an 'official commit in ages [especially none since switch to git...])