Node Wrangler Broken Whole Project:( #87936

New Issue

mugwort · 2021-04-30T11:45:47+02:00

mugwort commented

2021-04-30 11:45:47 +02:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: AMD Radeon HD 6670 ATI Technologies Inc. 4.5.13399 Core Profile Context 15.201.1151.1008

Blender Version
Broken: version: 2.83.13 Release Candidate, branch: master, commit date: 2021-02-23 08:50, hash: blender/blender@7b00b67dfd
Worked: (newest version of Blender that worked as expected)

Addon Information
Name: Node Wrangler (3, 36)
Author: Bartek Skorupa, Greg Zaal, Sebastian Koenig, Christian Brinkmann, Florian Meyer

Short description of error

Hi, I tried to use node wrangler to add a PBR texture on a material, no error appeared but it did not create any nodes on the material.
Now when I transferred my project to USB to try Node Wrangler on my laptop it seems to have broken every material in the project (i.e. pink) even though there are supposedly no textures attached: https://i2.paste.pics/1cadb52c6ed0af8589dda5962c23f072.png
Seems it set something telling that the materials are dependent on textures even though its actually failed to add any texture nodes or anything..
i mean wtf is going on here https://paste.pics/b82a9b1feafa33312f9093f5948e412f
even the material preview background has been lost!!!

here's the .blend before i broke the project by trying to run NW which i luckily managed to recover from the .blend1 https://www.dropbox.com/s/8e9h95vgl2ab5gp/MERIVA.blend?dl=0

heres the project after i ran NW and it broke all the materials https://www.dropbox.com/s/sgzlmt689fkjd7r/MERIVAbroken.blend?dl=0

please let me know whats gone on here and whether you can fix it!!

Thank you

Exact steps for others to reproduce the error
[Please describe the exact steps needed to reproduce the issue]

Run NW on the original .blend on just one material (the glossy bonnet material) with a 2K pbr texture.

[Based on the default startup or an attached .blend file (as simple as possible)]

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: AMD Radeon HD 6670 ATI Technologies Inc. 4.5.13399 Core Profile Context 15.201.1151.1008 **Blender Version** Broken: version: 2.83.13 Release Candidate, branch: master, commit date: 2021-02-23 08:50, hash: `blender/blender@7b00b67dfd` Worked: (newest version of Blender that worked as expected) **Addon Information** Name: Node Wrangler (3, 36) Author: Bartek Skorupa, Greg Zaal, Sebastian Koenig, Christian Brinkmann, Florian Meyer **Short description of error** Hi, I tried to use node wrangler to add a PBR texture on a material, no error appeared but it did not create any nodes on the material. Now when I transferred my project to USB to try Node Wrangler on my laptop it seems to have broken every material in the project (i.e. pink) even though there are supposedly no textures attached: https://i2.paste.pics/1cadb52c6ed0af8589dda5962c23f072.png Seems it set something telling that the materials are dependent on textures even though its actually failed to add any texture nodes or anything.. i mean wtf is going on here https://paste.pics/b82a9b1feafa33312f9093f5948e412f even the material preview background has been lost!!! here's the .blend before i broke the project by trying to run NW which i luckily managed to recover from the .blend1 https://www.dropbox.com/s/8e9h95vgl2ab5gp/MERIVA.blend?dl=0 heres the project after i ran NW and it broke all the materials https://www.dropbox.com/s/sgzlmt689fkjd7r/MERIVAbroken.blend?dl=0 please let me know whats gone on here and whether you can fix it!! Thank you **Exact steps for others to reproduce the error** [Please describe the exact steps needed to reproduce the issue] Run NW on the original .blend on just one material (the glossy bonnet material) with a 2K pbr texture. [Based on the default startup or an attached .blend file (as simple as possible)]

mugwort commented

2021-04-30 11:45:47 +02:00

Added subscriber: @mugwort

Riccardo Giovanetti commented

2021-05-01 16:03:17 +02:00

Added subscriber: @Harvester

Riccardo Giovanetti commented

2021-05-01 16:03:17 +02:00

Here on:
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31

Blender Version: 2.83.13, branch: master, commit date: 2021-03-09 07:21, hash: blender/blender@bb50046730

Please, download the final release of Blender 2.83.13 LTS . Currently, your "broken file", on my 2.83.13 version, displays a pink background (obviously, because the link to the two images you used for the World setup are broken, and that's expected) but the Material preview is properly rendered (no pink background scene). Perhaps, something is wrong with your Blender installation or setup. You can try to reset Blender to its default setting from the menu File | Defaults | Load Factory Settings, and check if this fix the issue. In the negative, try the current version of Blender 2.83 LTS or a newer one (2.92 or 2.93).
The Node Wrangler add-on works properly.

Here on: Operating system: Windows-10-10.0.18362-SP0 64 Bits Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 462.31 Blender Version: 2.83.13, branch: master, commit date: 2021-03-09 07:21, hash: `blender/blender@bb50046730` Please, download the final release of [Blender 2.83.13 LTS ](https://www.blender.org/download/lts/). Currently, your "broken file", on my 2.83.13 version, displays a pink background (obviously, because the link to the two images you used for the World setup are broken, and that's expected) but the Material preview is properly rendered (no pink background scene). Perhaps, something is wrong with your Blender installation or setup. You can try to reset Blender to its default setting from the menu File | Defaults | Load Factory Settings, and check if this fix the issue. In the negative, try the current version of Blender 2.83 LTS or a newer one (2.92 or 2.93). The Node Wrangler add-on works properly.

mugwort commented

2021-05-02 14:23:22 +02:00

Yo,

Thanks for this! I'd been running 2.83.13 because the zip install of 2.92 was giving a graphics driver error and crashing on open... but I've now used the windows installer and 2.92 seems to work all good.

I've opened the project in the new blender and tried the addon again but again as soon as I press principled texture setup it just doesn't create any nodes:(

I will try on my university laptop and let you know how it goes.

Many thanks,
Tony

Yo, Thanks for this! I'd been running 2.83.13 because the zip install of 2.92 was giving a graphics driver error and crashing on open... but I've now used the windows installer and 2.92 seems to work all good. I've opened the project in the new blender and tried the addon again but again as soon as I press principled texture setup it just doesn't create any nodes:( I will try on my university laptop and let you know how it goes. Many thanks, Tony

mugwort commented

2021-05-02 15:01:44 +02:00

Update - I tried on my uni laptop and the same thing so i think im doing something wrong😌

I have the shader editor open underneath the 3D view, I press ctrl shift T, select 5 PBR textures and nothing:(

no nodes get generated

Where am i lost?

Update - I tried on my uni laptop and the same thing so i think im doing something wrong😌 I have the shader editor open underneath the 3D view, I press ctrl shift T, select 5 PBR textures and nothing:( no nodes get generated Where am i lost?

mugwort commented

2021-05-02 15:10:32 +02:00

This is the state of the logs after I run it on the laptop https://i2.paste.pics/2531830daac12b95e28d08b7039cf5e4.png

Riccardo Giovanetti commented

2021-05-02 16:35:29 +02:00

I don't know how to tell you without hurting your nerves, but even in Blender 2.92.0 the Node Wrangler works fine here. So, I suggest you to open the Blender Console from the menu Window | Toggle System Console and watch there for any error or message related to the Node Wrangler add-on.

One thing that might give issues is if you are linking images from another hard disk than the one where the blend file opened inside Blender is located (eg. the file is in C:\whateverdir\file.blend and the images are somewhere on the D:\ drive) using the "Relative path" option in the Blender File Browser (check the options clicking on the little gear in the top right). In such case the relative path fails and you can fix it simply by unchecking the Relative Path option before importing the images, so to use an absolute path instead.

I don't know how to tell you without hurting your nerves, but even in Blender 2.92.0 the Node Wrangler works fine here. So, I suggest you to open the Blender Console from the menu Window | Toggle System Console and watch there for any error or message related to the Node Wrangler add-on. One thing that might give issues is if you are linking images from another hard disk than the one where the blend file opened inside Blender is located (eg. the file is in C:\whateverdir\file.blend and the images are somewhere on the D:\ drive) using the "Relative path" option in the Blender File Browser (check the options clicking on the little gear in the top right). In such case the relative path fails and you can fix it simply by unchecking the Relative Path option before importing the images, so to use an absolute path instead.

mugwort commented

2021-05-02 17:07:00 +02:00

Yooo no bother me nerves av taken worse😅

I've toggled the console and there's no errors there, also tried unchecking relative path even though its on the same drive and still no luck...

Only thing i could think is a problem with the textures maybe?

here's the blend

https://www.dropbox.com/s/f247cv5xs2bybej/MERIVA.blend?dl=0

and heres the textures...

https://www.dropbox.com/s/l6iyzykvp2d141y/metal_sheet_vbiiegp.zip?dl=0

could you maybe give it a go on the old gloss_mistymorning material there be's on the bonnet as ive been trying and let me know if works on your end

Really appreciate it!!

Yooo no bother me nerves av taken worse😅 I've toggled the console and there's no errors there, also tried unchecking relative path even though its on the same drive and still no luck... Only thing i could think is a problem with the textures maybe? here's the blend https://www.dropbox.com/s/f247cv5xs2bybej/MERIVA.blend?dl=0 and heres the textures... https://www.dropbox.com/s/l6iyzykvp2d141y/metal_sheet_vbiiegp.zip?dl=0 could you maybe give it a go on the old gloss_mistymorning material there be's on the bonnet as ive been trying and let me know if works on your end Really appreciate it!!

Riccardo Giovanetti commented

2021-05-03 11:08:04 +02:00

I put your meriva.blend file inside a project folder, added a \textures folder inside it and copied there the image textures from your reference. The Node Wrangler add-on worked fine adding the set of images to both materials' Principled BSDF shader node. So, the issue is not caused by the images. I tested your file (created in Blender 2.83) in Blender 2.83.13, as well as in Blender 2.92.0 stable release, with the same results.

Try to do this:

open Blender,
reset it to the default settings from menu File | Defaults | Load Factory Settings (this will reset both the blend startup file as well as the Preferences),
then go to the Preferences | Add-ons and activate the Node Wrangler add-on (keep the Blender console always open so you can view any warning or error message there).

Follow my instructions above to create a project folder together with the \textures sub-folder and the images inside it, then open the blend file and test the add-on again.

After this I don't know what else to suggest you to do, so it might be better to forward this issue to the add-on's developers for further investigations.

I put your meriva.blend file inside a project folder, added a \textures folder inside it and copied there the image textures from your reference. The Node Wrangler add-on worked fine adding the set of images to both materials' Principled BSDF shader node. So, the issue is not caused by the images. I tested your file (created in Blender 2.83) in Blender 2.83.13, as well as in Blender 2.92.0 stable release, with the same results. Try to do this: - open Blender, - reset it to the default settings from menu File | Defaults | Load Factory Settings (this will reset both the blend startup file as well as the Preferences), - then go to the Preferences | Add-ons and activate the Node Wrangler add-on (keep the Blender console always open so you can view any warning or error message there). Follow my instructions above to create a project folder together with the \textures sub-folder and the images inside it, then open the blend file and test the add-on again. After this I don't know what else to suggest you to do, so it might be better to forward this issue to the add-on's developers for further investigations.

mugwort commented

2021-05-04 16:39:17 +02:00

UPDATE!!!

I was being dumb 🥲🥲🥲

Apologies for being a nuisance to all, I didn't have the Principled BSDF node selected:((((

On a real though, I was following a YT vid and did the same presses but because my material already had a normal node (which was selected) when I pressed the tings everything broke.

For real though you should look into what your plugin does if anything other than the Principled BSDF node is selected because it seems to fuck things up😌😳

UPDATE!!! I was being dumb 🥲🥲🥲 Apologies for being a nuisance to all, I didn't have the Principled BSDF node selected:(((( On a real though, I was following a YT vid and did the same presses but because my material already had a normal node (which was selected) when I pressed the tings everything broke. For real though you should look into what your plugin does if anything other than the Principled BSDF node is selected because it seems to fuck things up😌😳

Riccardo Giovanetti commented

2021-05-04 18:30:23 +02:00

The add-on is made only for the Principled BSDF shader node, nothing else. If you run it and 1) you haven't selected anything or 2) you have selected a node which is NOT the Principled BSDF, the add-on will show a message on the screen or in the bottom bar that you HAVE to select a Principled BSDF node for the add-on to work.

Therefore, if it is as you stated above, I would consider this not a bug and this report can be closed. Please, confirm, thank you.

Regards.

The add-on is made only for the Principled BSDF shader node, nothing else. If you run it and 1) you haven't selected anything or 2) you have selected a node which is NOT the Principled BSDF, the add-on will show a message on the screen or in the bottom bar that you HAVE to select a Principled BSDF node for the add-on to work. Therefore, if it is as you stated above, I would consider this not a bug and this report can be closed. Please, confirm, thank you. Regards.

mugwort commented

2021-05-04 19:03:53 +02:00

i can confirm😌😌😌

thank you Riccardo <3

i can confirm😌😌😌 thank you Riccardo <3

Germano Cavalcante commented

2021-05-05 01:02:57 +02:00

Added subscriber: @mano-wii