Preview node output missing. #105354

New Issue

Guido · 2024-06-14T02:24:35+02:00

Guido commented

2024-06-14 02:24:35 +02:00

System Information
Operating system: macOS-14.5-arm64-arm-64bit 64 Bits
Graphics card: Metal API Apple M2 Max 1.2

Blender Version
Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-06-07 20:58, hash: 4690c69a6528
Worked: (newest version of Blender that worked as expected)

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

Short description of error
Preview node output missing in blender 4.2 mac silicon m2

Exact steps for others to reproduce the error
After working with nodes and missing the ability I searched if I accidently removed the shortcut, but no for some reason it's missing in the new version for Blender 4.2.

**System Information** Operating system: macOS-14.5-arm64-arm-64bit 64 Bits Graphics card: Metal API Apple M2 Max 1.2 **Blender Version** Broken: version: 4.2.0 Beta, branch: blender-v4.2-release, commit date: 2024-06-07 20:58, hash: `4690c69a6528` Worked: (newest version of Blender that worked as expected) **Addon Information** Name: Node Wrangler (3, 54) Author: Bartek Skorupa, Greg Zaal, Sebastian Koenig, Christian Brinkmann, Florian Meyer **Short description of error** Preview node output missing in blender 4.2 mac silicon m2 **Exact steps for others to reproduce the error** After working with nodes and missing the ability I searched if I accidently removed the shortcut, but no for some reason it's missing in the new version for Blender 4.2.

Screenshot 2024-06-13 at 3.16.47 AM.jpg

1.3 MiB

Guido added the

labels 2024-06-14 02:24:36 +02:00

Pratik Borhade commented

2024-06-19 11:13:30 +02:00

@Nurb2Kea hi, blender/blender#122978 looks related

@Nurb2Kea hi, https://projects.blender.org/blender/blender/issues/122978 looks related

Guido commented

2024-06-19 11:42:29 +02:00

Means nothing else than it's not in the latest Node Wrangler build, therefore the other user LOIC BRAMOULLE can't get it to work.

Now the question is why the devs removed it from the lates version ???
And I'm waiting for an answer for that from Bartek Skorupa, Greg Zaal, Sebastian Koenig, Christian Brinkmann, Florian Meyer !

Means nothing else than it's not in the latest Node Wrangler build, therefore the other user LOIC BRAMOULLE can't get it to work. Now the question is why the devs removed it from the lates version ??? And I'm waiting for an answer for that from Bartek Skorupa, Greg Zaal, Sebastian Koenig, Christian Brinkmann, Florian Meyer !

Damien Picard commented

2024-06-19 12:02:15 +02:00

Hi @Nurb2Kea, none of these people are active in the development of Node Wrangler any more.

The reason Preview Node Output was removed from Node Wrangler is that it is now built-in and new Blender builds have it on by default. It was renamed to “Connect to Output” though.

More details at blender/blender!122016

If you search for "Connect to Output" in the Keymap preferences, do you see it come up?

Hi @Nurb2Kea, none of these people are active in the development of Node Wrangler any more. The reason Preview Node Output was removed from Node Wrangler is that it is now built-in and new Blender builds have it on by default. It was renamed to “Connect to Output” though. More details at blender/blender!122016 If you search for "Connect to Output" in the Keymap preferences, do you see it come up? ![image](/attachments/d4322a28-3c08-457b-91db-04002169182a)

image.png

60 KiB

👍 1

Guido commented

2024-06-19 13:39:57 +02:00

Here you can see what you get when you search!
Because the problem is when you use the previous blender settings when starting blender 4.2 for the first time.

That is the main problem with it.

If you use the scripts folder path to install all 3dparty addons to be able to use this location for all blender versions, then when the next blender version comes, I can use this script folder path location to run the addons, but what about all the online extensions now, that don't come with blender anymore.
First I have to figure out what online extensions (blender native addons) I had enabled and what changes to the settings did I make.
Then start the new blender version use all the settings from previous, then download all the online extensions and change their settings if needed.
And this again , and again , and again ..... for each coming version of blender.

-Even better:
If you do it like most professional users and copy the blender 4.1 folder from Application support and rename it to 4.2, then you'll have fun figuring it all out the hard way.

This works since I use blender 2.93 !

This isn't a proper solution, and I guess noone have thought about it beforehand...!

@dfelinto would be the person to talk to about this extensions mess. He and Pablo, I guess, presented it via youtube and such.

For example:

Install extensions & legacy addons in a scipt path + both with little changes, in blender 4.1
Then install blender 4.2 and try to get the same experience as in 4.1.
Not possible if you use the settings from 4.1 or copy the folder of 4.1 and rename it.
Then try, when you managed 4.2 to work again like 4.1 to port this to the 4.3 alpha....

PS: Be aware :: Could take up to a working day amount of time...to test this!

Where did these extensions get installed? .....in 3 different locations.
First: script folder set in preferences
Second: Applications support folder (folder 4.1, 4.2, ...)
Third: In the package contents of the blender app

Node wrangler gets installed here, carver there,....
(It feels like Pipi Longstockings: I make the world the way I like it! )

Also there is the question why this changes to Node Wrangler aren't communicated with the community? I'm bugtracking and fixing if possible for years now and I'm daily update my info on the blender coder chat and watch the daily commits to see the changes, so why do I have no idea about this change, made somewhere in the dark...?

(If you are not a customer, you're the product).

EDIT: Ahhh and if you look at the first image in this report you see that I didn't seach the blender keymaps but the keymaps of node wrangler. And there you won't find anything, not ever you !

Here you can see what you get when you search! Because the problem is when you use the previous blender settings when starting blender 4.2 for the first time. That is the main problem with it. - If you use the scripts folder path to install all 3dparty addons to be able to use this location for all blender versions, then when the next blender version comes, I can use this script folder path location to run the addons, but what about all the online extensions now, that don't come with blender anymore. - First I have to figure out what online extensions (blender native addons) I had enabled and what changes to the settings did I make. - Then start the new blender version use all the settings from previous, then download all the online extensions and change their settings if needed. - And this again , and again , and again ..... for each coming version of blender. -Even better: If you do it like most professional users and copy the blender 4.1 folder from Application support and rename it to 4.2, then you'll have fun figuring it all out the hard way. This works since I use blender 2.93 ! This isn't a proper solution, and I guess noone have thought about it beforehand...! @dfelinto would be the person to talk to about this extensions mess. He and Pablo, I guess, presented it via youtube and such. For example: - Install extensions & legacy addons in a scipt path + both with little changes, in blender 4.1 - Then install blender 4.2 and try to get the same experience as in 4.1. Not possible if you use the settings from 4.1 or copy the folder of 4.1 and rename it. - Then try, when you managed 4.2 to work again like 4.1 to port this to the 4.3 alpha.... PS: Be aware :: Could take up to a working day amount of time...to test this! Where did these extensions get installed? .....in 3 different locations. First: script folder set in preferences Second: Applications support folder (folder 4.1, 4.2, ...) Third: In the package contents of the blender app Node wrangler gets installed here, carver there,.... (It feels like Pipi Longstockings: I make the world the way I like it! ) Also there is the question why this changes to Node Wrangler aren't communicated with the community? I'm bugtracking and fixing if possible for years now and I'm daily update my info on the blender coder chat and watch the daily commits to see the changes, so why do I have no idea about this change, made somewhere in the dark...? (If you are not a customer, you're the product). EDIT: Ahhh and if you look at the first image in this report you see that I didn't seach the blender keymaps but the keymaps of node wrangler. And there you won't find anything, not ever you !

Screenshot 2024-06-19 at 1.01.51 PM.jpg

39 KiB

Screenshot 2024-06-19 at 1.26.06 PM.jpg

39 KiB

Screenshot 2024-06-19 at 12.52.52 PM.jpg

620 KiB

Screenshot 2024-06-19 at 12.52.52 PM.jpg

Jaro commented

2024-07-13 00:49:23 +02:00

This is a big downgrade in functionality. You can't connect to output without having the node selected nor can you keep everything connected and just use a preview node since it deattaches the current output. Nor can you scroll through outputs previewing each one since it only takes the top one.

Sometimes it feels like people developing the features are entirely disconnected from people using said features.

This is a big downgrade in functionality. You can't connect to output without having the node selected nor can you keep everything connected and just use a preview node since it deattaches the current output. Nor can you scroll through outputs previewing each one since it only takes the top one. Sometimes it feels like people developing the features are entirely disconnected from people using said features.

👍 1

Pratik Borhade commented

2024-07-15 06:16:02 +02:00

You can't connect to output without having the node selected nor can you keep everything connected and just use a preview node since it deattaches the current output

Hi, not really able to confirm this. Can you make separate report at: https://projects.blender.org/blender/blender/issues

Where did these extensions get installed? .....in 3 different locations.

Not really confusing. AFAIK separation is actually needed:

Some essential (mostly IO) extensions/add-on has been moved inside blender repo so they will be present inside installation directory.
Legacy add-ons in: 4.2/scripts/add-ons (because they don't have .toml file, instead they have init.py)
New extensions in 4.2/extensions

> You can't connect to output without having the node selected nor can you keep everything connected and just use a preview node since it deattaches the current output Hi, not really able to confirm this. Can you make separate report at: https://projects.blender.org/blender/blender/issues > Where did these extensions get installed? .....in 3 different locations. Not really confusing. AFAIK separation is actually needed: - Some essential (mostly IO) extensions/add-on has been moved inside blender repo so they will be present inside installation directory. - Legacy add-ons in: 4.2/scripts/add-ons (because they don't have `.toml` file, instead they have init.py) - New extensions in 4.2/extensions

Dalai Felinto commented

2024-07-15 10:50:09 +02:00

This is a non-bug. When parts of the node wrangler were moved into a core feature they got new names. Custom keymapping of these operators need to be manually re-set by the users.

This will be mentioned on the release notes.

This is a non-bug. When parts of the node wrangler were moved into a core feature they got new names. Custom keymapping of these operators need to be manually re-set by the users. This will be mentioned on the release notes.

👎 1

Dalai Felinto closed this issue

2024-07-15 10:50:10 +02:00

Blender Bot added

and removed

labels 2024-07-15 10:50:12 +02:00

Guido commented

2024-07-15 11:24:21 +02:00

What a shame on information for the betatesters!

Guido commented

2024-07-17 00:49:43 +02:00

This is a non-bug. When parts of the node wrangler were moved into a core feature they got new names. Custom keymapping of these operators need to be manually re-set by the users.

This will be mentioned on the release notes.

Now that it is released, you @dfelinto can show/tell me where it is mentioned + instructions for the operators to be manually re-set by the users.

Thanks in advance

> This is a non-bug. When parts of the node wrangler were moved into a core feature they got new names. Custom keymapping of these operators need to be manually re-set by the users. > > This will be mentioned on the release notes. Now that it is released, you @dfelinto can show/tell me where it is mentioned + instructions for the operators to be manually re-set by the users. Thanks in advance

Guido reopened this issue

2024-07-17 00:49:45 +02:00

Blender Bot added

and removed

labels 2024-07-17 00:49:46 +02:00

Sign in to join this conversation.