Material Nodes broken on Blender 2.8 MacOS #61641

New Issue

Martin Ackerl · 2019-02-17T20:42:53+01:00

Martin Ackerl commented

2019-02-17 20:42:53 +01:00

System Information
Operating system: MacOS 10.14.3
Graphics card: AMD Vega64

Blender Version
Broken: 2.80, faa255c0a4e4-x86-64
Worked: 2.79b
Worked: 2.80, c6cbcf83d015-windows64

The MacOS Version of Blender 2.8 seems to have serious issues with material nodes.

When a node setup exceeds a certain complexity (which I am unfortunately not able to pin down) following errors happen:

The material is displayed in pink in Lookdev mode. (In my observation when a displacement vector is connected to the displacement socket of the material output)
Changes in the node setup will not be updated in the viewport - the updates only appear when the .blend is saved and Blender is restarted.
To reproduce it please just try to disconnect the diffuse texture from the Principled BSDF in the attached .blend

The same Node Setup works fine in Blender 2.79b. Also in the Windows version of Blender 2.8 everything works as expected. All on the same Computer.

material not updating.blend

**System Information** Operating system: MacOS 10.14.3 Graphics card: AMD Vega64 **Blender Version** Broken: 2.80, faa255c0a4e4-x86-64 Worked: 2.79b Worked: 2.80, c6cbcf83d015-windows64 The MacOS Version of Blender 2.8 seems to have serious issues with material nodes. When a node setup exceeds a certain complexity (which I am unfortunately not able to pin down) following errors happen: 1. The material is displayed in pink in Lookdev mode. (In my observation when a displacement vector is connected to the displacement socket of the material output) 2. Changes in the node setup will not be updated in the viewport - the updates only appear when the .blend is saved and Blender is restarted. To reproduce it please just try to disconnect the diffuse texture from the Principled BSDF in the attached .blend The same Node Setup works fine in Blender 2.79b. Also in the Windows version of Blender 2.8 everything works as expected. All on the same Computer. [material not updating.blend](https://archive.blender.org/developer/F6643283/material_not_updating.blend)

Martin Ackerl commented

2019-02-17 20:42:53 +01:00

Added subscriber: @martin.ackerl

blender-admin commented

2019-02-17 20:42:53 +01:00

#61642 was marked as duplicate of this issue

blender-admin commented

2019-02-17 20:42:53 +01:00

#61699 was marked as duplicate of this issue

blender-admin commented

2019-02-17 20:42:53 +01:00

#61611 was marked as duplicate of this issue

blender-admin commented

2019-02-17 20:42:53 +01:00

#61753 was marked as duplicate of this issue

blender-admin commented

2019-02-17 20:42:53 +01:00

#61720 was marked as duplicate of this issue

blender-admin commented

2019-02-17 20:42:53 +01:00

#61715 was marked as duplicate of this issue

blender-admin commented

2019-02-17 20:42:53 +01:00

#61721 was marked as duplicate of this issue

Moritz Brückner commented

2019-02-17 20:53:25 +01:00

Added subscriber: @moritzbrueckner1

Moritz Brückner commented

2019-02-17 20:53:25 +01:00

I ran into the same problems in Blender 2.8 Beta on Mac OS. I found out that the changes can be updated in the viewport by hitting undo, so perform a change in a material node twice and then hit undo once. It doesn't solve the problem, but it works.
Would be nice to have a stable 2.8 version for Mac soon :)

I ran into the same problems in Blender 2.8 Beta on Mac OS. I found out that the changes can be updated in the viewport by hitting undo, so perform a change in a material node twice and then hit undo once. It doesn't solve the problem, but it works. Would be nice to have a stable 2.8 version for Mac soon :)

Joan commented

2019-02-17 23:28:27 +01:00

Added subscriber: @JoanBetbese

Joan commented

2019-02-17 23:28:27 +01:00

Yes, I can confirm it too. In the latest update from the 15th the materials in EEVEE don't work and also when there are more of two group of texture nodes connected the material is displayed in pink too.

Joan commented

2019-02-17 23:35:45 +01:00

I hope this file helps too pine.blend

I hope this file helps too [pine.blend](https://archive.blender.org/developer/F6644800/pine.blend)

Sebastian Parborg commented

2019-02-18 14:51:31 +01:00

Added subscribers: @WilliamReynish, @ZedDB

Sebastian Parborg commented

2019-02-18 14:51:31 +01:00

@WilliamReynish can you confirm?

William Reynish commented

2019-02-18 15:14:59 +01:00

I can confirm that the result is pink here too on macOS. But it does update if I make changes to the shader, ie if I add a new shader and plug it into the Material Output socket it works fine.

Clément Foucault was assigned by Sebastian Parborg

2019-02-18 15:18:28 +01:00

Joan commented

2019-02-18 20:39:34 +01:00

The file I've send , the shaders themselves, works in Windows.
The latest version on macOS is from February 15 and doesn't work. I don't know which shaders you've changed but If I change the group shader with a BSDF principled it remains pink at least on this last build in an older one works fine. But the group it still doesn't work, at least on my imac or macbook.
It's something about macOS system. do you know the reason?
Thanks

The file I've send , the shaders themselves, works in Windows. The latest version on macOS is from February 15 and doesn't work. I don't know which shaders you've changed but If I change the group shader with a BSDF principled it remains pink at least on this last build in an older one works fine. But the group it still doesn't work, at least on my imac or macbook. It's something about macOS system. do you know the reason? Thanks

Peter Bartos commented

2019-02-18 21:04:40 +01:00

Added subscriber: @hrochodyl

Brecht Van Lommel commented

2019-02-20 12:58:23 +01:00

Added subscribers: @IboJurgens, @JacquesLucke

Brecht Van Lommel commented

2019-02-20 13:40:17 +01:00

Added subscribers: @scootoss, @MaxRichter, @mgchris

Brecht Van Lommel commented

2019-02-20 13:40:25 +01:00

Added subscriber: @blenderND

Brecht Van Lommel commented

2019-02-20 13:44:36 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-02-20 13:44:36 +01:00

I wasn't able to confirm this myself, but marking as high priority.

Can anyone run Blender from the terminal with these options, do some operations that make material nodes fail, and attach the terminal output here? Hopefully it contains some errors that we can look at.

/Applications/Blender/blender.app/Contents/MacOS/blender --debug --debug-gpu

I wasn't able to confirm this myself, but marking as high priority. Can anyone run Blender from the terminal with these options, do some operations that make material nodes fail, and attach the terminal output here? Hopefully it contains some errors that we can look at. ``` /Applications/Blender/blender.app/Contents/MacOS/blender --debug --debug-gpu ```

Scott Shelley commented

2019-02-20 13:57:10 +01:00

Here's the output from terminal...(see attachment).

Blender_terminal.rtf

Here's the output from terminal...(see attachment). [Blender_terminal.rtf](https://archive.blender.org/developer/F6670508/Blender_terminal.rtf)

Brecht Van Lommel commented

2019-02-20 15:35:53 +01:00

Added subscriber: @aurelieng

James Peterson commented

2019-02-20 16:21:33 +01:00

Appears to be a known OSX issue.

GPUShader: linking error:
ERROR: Implementation limit of 16 active fragment shader samplers (e.g., maximum number of supported image units) exceeded, fragment shader uses 17 samplers

Appears to be a known OSX issue. GPUShader: linking error: ERROR: Implementation limit of 16 active fragment shader samplers (e.g., maximum number of supported image units) exceeded, fragment shader uses 17 samplers GPUShader: linking error: ERROR: Implementation limit of 16 active fragment shader samplers (e.g., maximum number of supported image units) exceeded, fragment shader uses 17 samplers

Brecht Van Lommel commented

2019-02-20 17:10:33 +01:00

There's a new build, the previous one was from 5 days ago:
https://builder.blender.org/download/

Maybe this solves the issue, I'm not sure.

There's a new build, the previous one was from 5 days ago: https://builder.blender.org/download/ Maybe this solves the issue, I'm not sure.

Brecht Van Lommel commented

2019-02-20 17:26:55 +01:00

Added subscribers: @Nic-3, @fclem, @ethur, @GabrielMoro

Brecht Van Lommel commented

2019-02-20 17:27:04 +01:00

Added subscribers: @huckleberry, @dfelinto, @nacioss, @NahuelBelich

Earl R. Thurston commented

2019-02-20 18:20:15 +01:00

In #61641#624451, @brecht wrote:
There's a new build, the previous one was from 5 days ago:
https://builder.blender.org/download/

Maybe this solves the issue, I'm not sure.

I just downloaded and tested the Feb 20 version, and the problem I was experiencing (inability to change Material and see result immediately in viewport) is fixed now.

> In #61641#624451, @brecht wrote: > There's a new build, the previous one was from 5 days ago: > https://builder.blender.org/download/ > > Maybe this solves the issue, I'm not sure. I just downloaded and tested the Feb 20 version, and the problem I was experiencing (inability to change Material and see result immediately in viewport) is fixed now.

Gabriel Moro commented

2019-02-20 18:32:47 +01:00

My problem is fixed on todays release as well.

In #61641#624507, @ethur wrote:

In #61641#624451, @brecht wrote:
There's a new build, the previous one was from 5 days ago:
https://builder.blender.org/download/

Maybe this solves the issue, I'm not sure.

I just downloaded and tested the Feb 20 version, and the problem I was experiencing (inability to change Material and see result immediately in viewport) is fixed now.

My problem is fixed on todays release as well. > In #61641#624507, @ethur wrote: >> In #61641#624451, @brecht wrote: >> There's a new build, the previous one was from 5 days ago: >> https://builder.blender.org/download/ >> >> Maybe this solves the issue, I'm not sure. > > I just downloaded and tested the Feb 20 version, and the problem I was experiencing (inability to change Material and see result immediately in viewport) is fixed now.

Nicolas Besserer commented

2019-02-20 18:38:41 +01:00

Feb. 20 version seems to work so far ;)

Brecht Van Lommel commented

2019-02-20 18:43:02 +01:00

Changed status from 'Open' to: 'Resolved'

Brecht Van Lommel closed this issue

2019-02-20 18:43:02 +01:00

Brecht Van Lommel commented

2019-02-20 18:43:02 +01:00

Thanks for testing, let's consider this resolved then.

Martin Ackerl commented

2019-02-20 19:34:33 +01:00

Thank you all for your work, it's really appreciated! But unfortunately, even with Feb. 20 version in my submitted file material not updating.blend the material is still displayed in pink.
Or am I doing something wrong? Is there a limit of texture nodes per material on MacOS?

Thank you all for your work, it's really appreciated! But unfortunately, even with Feb. 20 version in my submitted file [material not updating.blend ](https://developer.blender.org/F6643283) the material is still displayed in pink. Or am I doing something wrong? Is there a limit of texture nodes per material on MacOS?

James Peterson commented

2019-02-20 20:38:15 +01:00

My issues is also resolved with the latest master branch.

I tested your file @martin.ackerl and seeing the same issue which resulted in the following:
GPUShader: linking error:
ERROR: Implementation limit of 16 active fragment shader samplers (e.g., maximum number of supported image units) exceeded, fragment shader uses 17 samplers

Doing a quick google search looks like this may be an OSX limitation in OpenGL

My issues is also resolved with the latest master branch. I tested your file @martin.ackerl and seeing the same issue which resulted in the following: GPUShader: linking error: ERROR: Implementation limit of 16 active fragment shader samplers (e.g., maximum number of supported image units) exceeded, fragment shader uses 17 samplers Doing a quick google search looks like this may be an OSX limitation in OpenGL

Martin Ackerl commented

2019-02-20 21:22:18 +01:00

Thanks @blenderND
These OpenGL problems on MacOS are really frustrating.

Thanks @blenderND These OpenGL problems on MacOS are really frustrating.

Joan commented

2019-02-20 21:50:45 +01:00

Yes, I can confirm it too, really appreciated! But the issues of pink material persist.
I tried to restart and check it out in my dual boot with a Linux OS but ... the material is pink too. I guess it depends on machine more than OS, right? :(
Thanks!

Yes, I can confirm it too, really appreciated! But the issues of pink material persist. I tried to restart and check it out in my dual boot with a Linux OS but ... the material is pink too. I guess it depends on machine more than OS, right? :( Thanks!

Brecht Van Lommel commented

2019-02-21 16:54:10 +01:00

There is indeed a limit on the number of image texture nodes that can be used, with the number depending on the graphics card and driver.

AMD Vega64 hardware supports 32 but macOS seems to limit it to 16 for some reason. Eevee needs 8, this shading node has 9 image texture nodes, so that exceeds the maximum.

There are some optimizations possible, we could automatically pack together some texture channels or use other tricks, but that's beyond what we would consider a bugfix.

There is indeed a limit on the number of image texture nodes that can be used, with the number depending on the graphics card and driver. AMD Vega64 hardware supports 32 but macOS seems to limit it to 16 for some reason. Eevee needs 8, this shading node has 9 image texture nodes, so that exceeds the maximum. There are some optimizations possible, we could automatically pack together some texture channels or use other tricks, but that's beyond what we would consider a bugfix.

Joan commented

2019-02-21 21:07:34 +01:00

{F6681180}I see. I tested that first file somebody shared and it worked as @brecht is saying. But what does happen with the other file I shared? (pine) I changed some shaders and reduced image textures nodes to 8 but it's still pink. I know it's maybe not an issue but if is there anyone to help, I'll appreciate it.
Thanks.

{[F6681180](https://archive.blender.org/developer/F6681180/pine1.blend)}I see. I tested that first file somebody shared and it worked as @brecht is saying. But what does happen with the other file I shared? (pine) I changed some shaders and reduced image textures nodes to 8 but it's still pink. I know it's maybe not an issue but if is there anyone to help, I'll appreciate it. Thanks.

Martin Ackerl commented

2019-02-22 08:08:17 +01:00

@JoanBetbese Probably not a big help, but on my iMac Pro it works if I disconnect at least one other image texture (counting 7 textures).

Joan commented

2019-02-22 08:55:23 +01:00

@martin.ackerl are you talking about the last file I uploaded? I’m gonna try it!
Thanks!

@martin.ackerl are you talking about the last file I uploaded? I’m gonna try it! Thanks!

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Material Nodes broken on Blender 2.8 MacOS #61641