Node Wrangler Force Update Traceback Error #48094
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
7 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#48094
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
Windows 10 64bit, MSI GeForce 730
Blender Version
Broken: 2.77a abf6f08
Worked: 2.77
Short description of error
Using Node Wrangler switch node shortcut shift-s, or menu causes a traceback error as shown below. The replaced node still seems to work fine... Doesn't seem to have problems, although the popup is rather annoying.
Changed status to: 'Open'
Added subscriber: @BlenderHead
#48724 was marked as duplicate of this issue
#48152 was marked as duplicate of this issue
blender/blender#48138 was marked as duplicate of this issue
#48488 was marked as duplicate of this issue
#48220 was marked as duplicate of this issue
Added subscriber: @Blendify
Seems to be caused by
1c9d5a8507Added subscriber: @JimwwSmith
Figured it out.
In line 1897, I changed 'force_update(context)' to 'hack_force_update(context, nodes)' as that was how it was used elsewhere in the file.
Added subscriber: @BrendonMurphy
hack_force_updateis old code, replaced recently by the simplerforce_updatemethod. Maybe27da8e1fwas lost in the 2.77a release?? This is the current version of the add-on straight from git, and it does indeed have the new function.@BrendonMurphy maybe you know what's going on?
Changed status from 'Open' to: 'Resolved'
Spoke with Brendon and Cambo on IRC, looks like that commit just got missed for 2.77a. If there's a 2.77b, it'll be fixed in there. Otherwise just download the latest version and replace your current one (
/2.77/scripts/addons/node_wrangler.py) with that.Removed subscriber: @JimwwSmith
Thanks Greg.
It definitely works now. Great tip and addon.
Thanks Greg.
It definitely works now. Great tip and addon.
Thanks Greg.
It definitely works now. Great tip and addon.
Added subscriber: @ajlanaltug
Added subscribers: @GregZaal, @gandalf3, @DenisBelov
Added subscriber: @Leroy-Xie
Added subscriber: @martinjh99
Can someone delete #48488 then as it is a duplicate of this one. Thanks
Added subscribers: @VukGardasevic, @Acolyte