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

New Issue

Carlo Andreacchio · 2019-03-28T22:34:51+01:00

Carlo Andreacchio commented

2019-03-28 22:34:51 +01:00

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)

👍 1

Carlo Andreacchio commented

2019-03-28 22:34:51 +01:00

Added subscriber: @candreacchio

blender-admin commented

2019-03-28 22:34:51 +01:00

#93448 was marked as duplicate of this issue

blender-admin commented

2019-03-28 22:34:51 +01:00

#69517 was marked as duplicate of this issue

Philipp Oeser commented

2019-03-29 09:55:29 +01:00

Added subscribers: @brecht, @lichtwerk

Philipp Oeser commented

2019-03-29 09:55:29 +01:00

@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)

Philipp Oeser changed title from ~~Blender 2.8 - Cycles Preview render removes all shading from the scene~~ to Blender 2.8 - Cycles border render removes all shading from the scene

2019-03-29 09:55:50 +01:00

Brecht Van Lommel was assigned by Sebastian Parborg

2019-03-29 11:26:34 +01:00

Mindaugas Petrikas commented

2019-05-09 12:32:18 +02:00

Added subscriber: @petrikas.m

Mindaugas Petrikas commented

2019-05-09 12:51:20 +02:00

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.

Marcus Papathoma commented

2019-05-09 13:36:44 +02:00

Added subscriber: @machieb

Marcus Papathoma commented

2019-05-09 13:36:44 +02:00

Would be great to have the behaviour form 2.79 back!

Martynas Žiemys commented

2019-08-20 14:45:02 +02:00

Added subscriber: @MartinZ

Martynas Žiemys commented

2019-08-20 14:45:02 +02:00

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

Martynas Žiemys commented

2019-09-10 10:18:23 +02:00

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

Philipp Oeser commented

2019-09-10 11:16:34 +02:00

Added subscriber: @CobraA

CobraA commented

2019-09-26 08:20:02 +02:00

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

Daniel Paul commented

2019-09-26 16:29:14 +02:00

Added subscriber: @DanielPaul

Daniel Paul commented

2019-09-26 16:29:14 +02:00

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

Sam Van Hulle commented

2019-09-27 23:53:30 +02:00

Added subscriber: @frameshift

André Hänsel commented

2019-11-03 11:56:36 +01:00

Added subscriber: @AndreKR

Brecht Van Lommel was unassigned by Dalai Felinto

2019-12-23 16:34:46 +01:00

Brecht Van Lommel changed title from ~~Blender 2.8 - Cycles border render removes all shading from the scene~~ to Cycles viewport render border no longer shows scene behind with OpenGL

2020-01-27 12:34:14 +01:00

Pawel commented

2020-01-28 23:04:56 +01:00

Added subscriber: @pawel.palenica

Braden Currah commented

2020-04-08 22:45:40 +02:00

Added subscriber: @TakingFire

Vyacheslav Kobozev commented

2020-08-09 11:39:12 +02:00

Added subscriber: @Vyach

Vyacheslav Kobozev commented

2020-08-09 18:40:47 +02:00

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

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

slowburn commented

2021-02-23 01:46:46 +01:00

Added subscriber: @slowburn

Carlo Andreacchio commented

2021-03-11 07:28:21 +01:00

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

Vyacheslav Kobozev commented

2021-03-11 17:42:15 +01:00

Will we «celebrate» a year?

Mindaugas Petrikas commented

2021-03-11 18:03:01 +01:00

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.

Vyacheslav Kobozev commented

2021-03-12 00:38:35 +01:00

Added subscriber: @dfelinto

Vyacheslav Kobozev commented

2021-03-12 00:38:35 +01:00

@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?

Carlo Andreacchio commented

2022-03-04 02:04:15 +01:00

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?

Evan Wilson commented

2022-03-04 05:23:53 +01:00

Added subscriber: @EAW

Evan Wilson commented

2022-03-04 05:23:53 +01:00

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.

Carlo Andreacchio commented

2022-03-04 06:27:15 +01:00

Added subscriber: @evan-4

Carlo Andreacchio commented

2022-03-04 06:27:15 +01:00

@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.

Atamert Ölçgen commented

2022-03-07 19:53:19 +01:00

Added subscriber: @muhuk