Node Wrangler not reading my Image textures #82734
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#82734
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: Windows-10-10.0.17763-SP0 64 Bits
Graphics card: GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 452.06
Blender Version
Broken: version: 2.90.1, branch: master, commit date: 2020-09-23 06:43, hash:
blender/blender@3e85bb34d0
Worked: (newest version of Blender that worked as expected)
Addon Information
Name: Node Wrangler (3, 37)
Author: Bartek Skorupa, Greg Zaal, Sebastian Koenig, Christian Brinkmann, Florian Meyer
Short description of error
Texture is not being read by Blender Node Wrangler (BSDF; CTRL+SHIFT+T)
Exact steps for others to reproduce the error
Added subscriber: @Gocchin
Added subscriber: @rjg
Changed status from 'Needs Triage' to: 'Needs User Info'
Can you open the textures in other software? The screenshot indicates that the files are empty and this information is displayed by the file browser, which seems to be unrelated to Node Wrangler. I also can't reproduce this problem on my system.
Yes, It is completely fine with any other software, I tried different textures too.
My current Blender is downloaded from Steam btw, and it's the latest update too.
The files are only seen empty and Date modified set to that date in Node Wrangler File browser.
Here is the files seen in screenshot on desktop:
Do you have any special permissions or policies set for this directory or files? Could you try the same with a daily build of 2.92 ? Are any error messages displayed on the console (*Windows > Toggle System Console//)?
I do not, and I normally doesn't have a problem with node wrangler until today, I am using the latest GPU driver too, and has also restarted my PC. Still the same.
I tried for latest alpha 2.92 (from blender website) too. Results are the same. There is not a single text in console either as I use node wrangler.
It simply doesn't want to interpret my texture images properly in (CTRL+SHIFT+T)
Does that only happen with textures in this directory or every texture? Are you having the same problem when loading files in general e.g. import/export of models, manually adding a image texture or environment texture node or is this really only limited to node wrangler?
It happens in every texture, no matter the directory.
Problem is only limited to Node Wrangler importing image/textures (CTRL + SHIFT + T)
While the same images/texture can be imported manually (e.g. by dragging to node editor, by manually selecting image file)
Changed status from 'Needs User Info' to: 'Needs Triage'
Thank you for all the information.
Changed status from 'Needs Triage' to: 'Resolved'
Problem fixed to day as I turned on my PC.
Textures/images can't still be imported from that specific project folder, but fixed now as I moved it to entirely different folder.