Blender 2.8 Beta Mac OS Bugs #61642

New Issue

Moritz Brückner · 2019-02-17T20:43:51+01:00

Moritz Brückner commented

2019-02-17 20:43:51 +01:00

System Information
Operating system: Mac OS
System: MacBook Pro 13" 2017
Graphics card: Intel Iris Pro 650

Blender Version
2.80 Beta for Mac OS

It seems there are three problems wich I encountered on the 2.8 Beta:

1.) The first problem occurred when I tried to open an HDRI File. I could load the HDRI file in a fresh new file as long as I loaded the image file in the devlook viewport mode into the world shader node. Switching to the rendered viewport setting afterwards worked. But as soon as I loaded the hdri file into the world shader node while having the viewport in rendered mode it didn't worked. I read that other users also had this Problem.

2.) Another problem I ran into was, that material changes while displaying rendered viewport with eevee didn't effect the viewport. Also the material preview wasn't affected by the changes. Somehow the changes worked after using the undo command! As a workaround I did two changes in a material node f.e. changing the roughness twice, then doing one undo command and the first change was shown in the rendered viewport.

3.) also had some problems that objects wouldn't show textures even with the proper uv unwrapping and mapping. Even on simple objects like a cube or a plane. However after some time fiddling around with the problem, magically after switching between editing and object mode at some point the textures appeared. I think there could be some kind of texture-display error concerning the edit mode.

Otherwise great work! im really looking forward to the 2.8 stable release!

Greetings from Germany,

Moritz

Exact steps for others to reproduce the error
Based on the default startup file.

**System Information** Operating system: Mac OS System: MacBook Pro 13" 2017 Graphics card: Intel Iris Pro 650 **Blender Version** 2.80 Beta for Mac OS It seems there are three problems wich I encountered on the 2.8 Beta: 1.) The first problem occurred when I tried to open an HDRI File. I could load the HDRI file in a fresh new file as long as I loaded the image file in the devlook viewport mode into the world shader node. Switching to the rendered viewport setting afterwards worked. But as soon as I loaded the hdri file into the world shader node while having the viewport in rendered mode it didn't worked. I read that other users also had this Problem. 2.) Another problem I ran into was, that material changes while displaying rendered viewport with eevee didn't effect the viewport. Also the material preview wasn't affected by the changes. Somehow the changes worked after using the undo command! As a workaround I did two changes in a material node f.e. changing the roughness twice, then doing one undo command and the first change was shown in the rendered viewport. 3.) also had some problems that objects wouldn't show textures even with the proper uv unwrapping and mapping. Even on simple objects like a cube or a plane. However after some time fiddling around with the problem, magically after switching between editing and object mode at some point the textures appeared. I think there could be some kind of texture-display error concerning the edit mode. Otherwise great work! im really looking forward to the 2.8 stable release! Greetings from Germany, Moritz **Exact steps for others to reproduce the error** Based on the default startup file.

Moritz Brückner commented

2019-02-17 20:43:51 +01:00

Added subscriber: @moritzbrueckner1

Brecht Van Lommel commented

2019-02-17 22:11:59 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-02-17 22:11:59 +01:00

Please create one report per bug.

seems like a duplicate of #61641, so does not need another report. 1) might be the same underlying issue as 2).

For 3) we need exact steps to reproduce the problem, preferable based on an attached .blend file.

Please create one report per bug. 2) seems like a duplicate of #61641, so does not need another report. 1) might be the same underlying issue as 2). For 3) we need exact steps to reproduce the problem, preferable based on an attached .blend file.

Moritz Brückner commented

2019-02-17 22:23:03 +01:00

Yeah, I saw the other thread after reporting the bug, the problems seem familiar. I think the third problem is also related to the first and second one. I ran into problem 3 by this steps:

Fresh new file
Creating a mesh f.e. a cube
Doing proper UV unwrap
creating a new material with a principled BSDF shader for that cube
adding a texture node and connecting it with the color input form the shader node f.e. wood.jpeg
switching viewport to rendered (render setting is set to eevee)

No changes happen. I also recognized that the material sample in the little preview window is also somehow white (no shading) and the texture isn't displayed. Hope that helps somehow.

Yeah, I saw the other thread after reporting the bug, the problems seem familiar. I think the third problem is also related to the first and second one. I ran into problem 3 by this steps: 0. Fresh new file 1. Creating a mesh f.e. a cube 2. Doing proper UV unwrap 3. creating a new material with a principled BSDF shader for that cube 4. adding a texture node and connecting it with the color input form the shader node f.e. wood.jpeg 5. switching viewport to rendered (render setting is set to eevee) No changes happen. I also recognized that the material sample in the little preview window is also somehow white (no shading) and the texture isn't displayed. Hope that helps somehow.

Jacques Lucke commented

2019-02-18 11:46:21 +01:00

Added subscriber: @JacquesLucke

Jacques Lucke commented

2019-02-18 11:46:21 +01:00

@moritzbrueckner1, before providing more information, please create one report per bug. Otherwise this will become a mess to track.

Then, prepare .blend file(s) that make it as easy as possible for us to reproduce the issues.

@moritzbrueckner1, before providing more information, please create one report per bug. Otherwise this will become a mess to track. Then, prepare .blend file(s) that make it as easy as possible for us to reproduce the issues.

Brecht Van Lommel commented

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

I'm going to assume this all these recent macOS bugs are about the same issue.

Brecht Van Lommel commented

2019-02-20 17:28:02 +01:00

Closed as duplicate of #61641

Brecht Van Lommel closed this issue

2019-02-20 17:28:02 +01:00

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

Blender 2.8 Beta Mac OS Bugs #61642