Problems in 2.8 in viewport matcaps as well as render of certain files - Since last two week builds #62783

New Issue

Ahmad Bilal · 2019-03-20T16:21:52+01:00

Ahmad Bilal commented

2019-03-20 16:21:52 +01:00

System Information
Operating system: Windows 10
Graphics card: AMD RX Vega 64

Blender Version
Broken: blender-2.80-9099305771ec-win64 - I downloaded two seperate builds on 17th & 18th (both having this issue) , one of them I deleted so not quoting that build id
Worked: blender-2.80-798d2cadc307-win64 - This version from around 4th March is not having this issue

Short description of error
I'm currently using 2.8 that I downloaded on around 4th March, which is working fine for me. Few days ago (on 17th & 18th) I downloaded two latest versions of those dates. But when I opened my main project file in them, not just my render but even my matcap is showing as messed up in eevee.

I carefully matched the render settings (and all subsettings inside them, and their values), but they are exactly the same. Nor was the light moved. nothing was changed.

Here are the screenshots:
Working on March 4th Build:

Not working on 18th March Build (I deleted the 17th March Build, but it was same)

The normal cube is working fine in 18th March build:

Exact steps for others to reproduce the error
Attaching my blend file, see for yourself
Test.blend

**System Information** Operating system: Windows 10 Graphics card: AMD RX Vega 64 **Blender Version** Broken: blender-2.80-9099305771ec-win64 - I downloaded two seperate builds on 17th & 18th (both having this issue) , one of them I deleted so not quoting that build id Worked: blender-2.80-798d2cadc307-win64 - This version from around 4th March is not having this issue **Short description of error** I'm currently using 2.8 that I downloaded on around 4th March, which is working fine for me. Few days ago (on 17th & 18th) I downloaded two latest versions of those dates. But when I opened my main project file in them, not just my render but even my matcap is showing as messed up in eevee. I carefully matched the render settings (and all subsettings inside them, and their values), but they are exactly the same. Nor was the light moved. nothing was changed. Here are the screenshots: Working on March 4th Build: ![Blender1.png](https://archive.blender.org/developer/F6859703/Blender1.png) Not working on 18th March Build (I deleted the 17th March Build, but it was same) ![Blender2.png](https://archive.blender.org/developer/F6859707/Blender2.png) ![Blender3.png](https://archive.blender.org/developer/F6859709/Blender3.png) The normal cube is working fine in 18th March build: ![Blender4.png](https://archive.blender.org/developer/F6859712/Blender4.png) **Exact steps for others to reproduce the error** Attaching my blend file, see for yourself [Test.blend](https://archive.blender.org/developer/F6859714/Test.blend)

Ahmad Bilal commented

2019-03-20 16:21:52 +01:00

Added subscriber: @SomeAB

Sebastian Parborg commented

2019-03-21 11:34:45 +01:00

Added subscriber: @ZedDB

Clément Foucault was assigned by Sebastian Parborg

2019-03-21 11:34:45 +01:00

Sebastian Parborg commented

2019-03-21 11:34:45 +01:00

The commit that causes this seem to be 86646dab7c

However in this case is seems like that change had the opposite effect. Now object scale matters:

With object scale not applied:

Applied (correct shading):

Before that commit the shading of this object was the same with un-applied scaling as with applied scaling. But now the shading changes.

The commit that causes this seem to be 86646dab7c However in this case is seems like that change had the opposite effect. Now object scale matters: With object scale not applied: ![new.png](https://archive.blender.org/developer/F6859992/new.png) Applied (correct shading): ![old.png](https://archive.blender.org/developer/F6859995/old.png) Before that commit the shading of this object was the same with un-applied scaling as with applied scaling. But now the shading changes.

Ahmad Bilal commented

2019-03-21 18:47:45 +01:00

I did not understand that very well sebastian (I'm not specifically asking you to explain though). Just suggest to me as to what I should do as end user.

Stick to the March 4 version for now, and watch this thread for fix to be applied before upgrading?
Or download a new blender version, and recreate my file?
Anything else

I did not understand that very well sebastian (I'm not specifically asking you to explain though). Just suggest to me as to what I should do as end user. 1. Stick to the March 4 version for now, and watch this thread for fix to be applied before upgrading? 2. Or download a new blender version, and recreate my file? 3. Anything else

Sebastian Parborg commented

2019-03-21 19:43:00 +01:00

I guess you could just stick to the old version for now.

Ahmad Bilal commented

2019-03-21 23:11:47 +01:00

Than any ETA on this? Because there are other bugs that were fixed after 4th March and might hinder my workflow. Plus, I would be missing out on new features added since then.