Archimesh: fix floor creation #104446
No reviewers
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
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#104446
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "pioverfour/blender-addons:dp_archimesh_fix_mods"
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?
The option to create a floor was broken for a long time, because it
relied on the presence of a Diffuse BSDF in a new material, however it
has been replaced by the Principled BSDF long ago.
Additionally, use the data API to create the modifiers instead of the
ops API, and assign nodes to variables instead of getting them by
name, which will not work any more if the UI is translated.
LGTM... thanks a lot for the fix.
Do you have commit rights? If not, I can merge the Pull Request myself.
Thank you, I can commit :)
@pioverfour @ThomasDinges This Pull Request was merged in 3.5, but I guess it needs to be merged in addons git repo, is that correct? In this case, the commit must be cherrypick to addons git repo too.
@antoniov I don’t think it needs to be cherrypicked, but merged instead. I’ll do it from home tonight if somebody hasn’t until then!
Yes, the same workflow that applies to Blender applies to add-ons as well. https://wiki.blender.org/wiki/Process/Using_Stabilizing_Branch
Commit to the stabilizing branch (in this case 3.5), and merge to main afterwards.