Cycles viewport render border no longer shows scene behind with OpenGL #63064

New Issue

System Information
Operating system: Ubuntu 18.04
Graphics card: GTX 1080

Blender Version
Broken: 2.80 Hash: 42dd888b98
Worked: 2.79b.

Short description of error
Cycles Preview render removes all shading from the scene. This is very evident when using border renders to help isolate down sections to work on (which is key for working on large scale production scenes.

Exact steps for others to reproduce the error

Open attached blend file in blender 2.79
hit shift z in the 3d viewport
notice how you can see the building to the left
close blender 2.79, and open the attahced blend file in blender 2.8
hit shift z in the 3d viewport (blender 2.79 keymap)
notice how you cannot see the building to the left anymore?

This means that reframing whilst border rendering is no longer possible, nor is it possible to change the border render without guessing to work on a different area of the frame without having to go back to solid mode and then back to rendered mode. Going in and out of solid mode can be 20-30 seconds on production scenes so limiting the amount of switching is important.

example.blend

**System Information** Operating system: Ubuntu 18.04 Graphics card: GTX 1080 **Blender Version** Broken: 2.80 Hash: 42dd888b98 Worked: 2.79b. **Short description of error** Cycles Preview render removes all shading from the scene. This is very evident when using border renders to help isolate down sections to work on (which is key for working on large scale production scenes. **Exact steps for others to reproduce the error** 1. Open attached blend file in blender 2.79 2. hit shift z in the 3d viewport 3. notice how you can see the building to the left 4. close blender 2.79, and open the attahced blend file in blender 2.8 5. hit shift z in the 3d viewport (blender 2.79 keymap) 6. notice how you cannot see the building to the left anymore? This means that reframing whilst border rendering is no longer possible, nor is it possible to change the border render without guessing to work on a different area of the frame without having to go back to solid mode and then back to rendered mode. Going in and out of solid mode can be 20-30 seconds on production scenes so limiting the amount of switching is important. [example.blend](https://archive.blender.org/developer/F6896492/example.blend)

Added subscriber: @candreacchio

#93448 was marked as duplicate of this issue

#69517 was marked as duplicate of this issue

Added subscribers: @brecht, @lichtwerk

@brecht: I think this has been reported before? (cant find it atm).
Personally I find this distracting as well. Is there anything that keeps us from remaining in the same shading mode [that we were in before switching the "rendered"] for the rest of the viewport?
(think this is how 2.79 did it)

@brecht: I think this has been reported before? (cant find it atm). Personally I find this distracting as well. Is there anything that keeps us from remaining in the same shading mode [that we were in before switching the "rendered"] for the rest of the viewport? (think this is how 2.79 did it)

Added subscriber: @petrikas.m

Just wanted to confirm the importance of this bug, as it breaks my whole workflow. Just another real-life example. I work with product rendering and use mesh lights for lighting / reflections. Those lights are not displayed to the camera. I work with border rendering mostly permanently ON when it comes to lighting the scene, and framing only the product allows me to move the mesh lights and see how the reflections and lighting change in real-time.
In 2.80 I'm forced to double-window as the planes are no longer visible in the main-viewport. Working with two windows is very un-intuitive and slows down my workflow five-fold or even ten-fold, as I have to do a lot more zooming-in, panning, etc. To me, this is a deal-breaking bug which prevents me from using 2.80 altogether.

Just wanted to confirm the importance of this bug, as it breaks my whole workflow. Just another real-life example. I work with product rendering and use mesh lights for lighting / reflections. Those lights are not displayed to the camera. I work with border rendering mostly permanently ON when it comes to lighting the scene, and framing only the product allows me to move the mesh lights and see how the reflections and lighting change in real-time. In 2.80 I'm forced to double-window as the planes are no longer visible in the main-viewport. Working with two windows is very un-intuitive and slows down my workflow five-fold or even ten-fold, as I have to do a lot more zooming-in, panning, etc. To me, this is a deal-breaking bug which prevents me from using 2.80 altogether.

Added subscriber: @machieb

Would be great to have the behaviour form 2.79 back!

Added subscriber: @MartinZ

I can't wait till this is fixed as well. That makes work really inconvenient.

Any news on this? Any chance of it being fixed for 2.81?

Added subscriber: @CobraA

I add my vote for this too, it's much needed months and months passing by without any fix yet.

Added subscriber: @DanielPaul

Much need! This feature is one of the main reasons I switched to blender.

Added subscriber: @frameshift

Added subscriber: @AndreKR

Added subscriber: @pawel.palenica

Added subscriber: @TakingFire

Added subscriber: @Vyach

Sad regression.
Can we have be forced wireframe mode as temporary solution?

Sad regression. Can we have be forced wireframe mode as temporary solution?

Added subscriber: @slowburn

is there any update to this? it has been as a todo for years.

Will we «celebrate» a year?

In #63064#1128305, @Vyach wrote:
Will we «celebrate» a year?

*2 years, it's been reported in March 2019.

I still think this is a high-priority bug, rather than a "to-do", as it's a regression from 2.79.
And it was reported as a bug, but somehow it turned into an upcoming feature.

> In #63064#1128305, @Vyach wrote: > Will we «celebrate» a year? *2 years, it's been reported in March 2019. I still think this is a high-priority bug, rather than a "to-do", as it's a regression from 2.79. And it was reported as a bug, but somehow it turned into an upcoming feature.

Added subscriber: @dfelinto

@petrikas.m … right…
I assume, it can be done for newer Vulkan viewport.
But there is still 2.83 LTS and 2.93 LTS… Will they loose it?
@dfelinto can you comment situation?

@petrikas.m … right… I assume, it can be done for newer Vulkan viewport. But there is still 2.83 LTS and 2.93 LTS… Will they loose it? @dfelinto can you comment situation?

It has been about a year since i last checked in, and nearly 3 years since I originally made this task. Is this ever going to get done?

Added subscriber: @EAW

I updated the task to be clearer. A single linked commit in the Broken/Working version usually points to the commit that had been found to be the cause of the issue via bisecting, doesn’t appear to be the case for this task. I could be missing something though. It appears that the linked commit was just the first version that the issue was noticed. If I am wrong @candreacchio, and that indeed was the commit that caused this issue, please let me know.

Added subscriber: @evan-4

@evan-4, the issue was in between 2.79 and 2.8. As this bug was only reported once they opened up the bug reporting to the wider community.

As there were many changes between 2.79 and 2.8, then 2.8 becoming master and 2.79 being renamed... its hard to 'bisect' the exact issue.

@evan-4, the issue was in between 2.79 and 2.8. As this bug was only reported once they opened up the bug reporting to the wider community. As there were many changes between 2.79 and 2.8, then 2.8 becoming master and 2.79 being renamed... its hard to 'bisect' the exact issue.

Added subscriber: @muhuk

Added subscriber: @Ethanicus

poke
nobody cares?

poke nobody cares?

Added subscriber: @YegorSmirnov

This should be higher priority imo.

Hi guys,

Sorry for reviving this old issue, but someone could take a look on this one please?
It's been a long road since it was reported and still happens in 4.0 alpha.
It makes the work with render regions a lot slower than it used to be in 2.7x

Hi guys, Sorry for reviving this old issue, but someone could take a look on this one please? It's been a long road since it was reported and still happens in 4.0 alpha. It makes the work with render regions a lot slower than it used to be in 2.7x

@brecht poke
Is there someone, who can fix this?

@brecht poke Is there someone, who can fix this?

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Cycles viewport render border no longer shows scene behind with OpenGL #63064