Display as behaviour in rendered view inconsistent between Eevee and Cycles #72453

New Issue

Wouter Stomp · 2019-12-14T22:01:03+01:00

Wouter Stomp commented

2019-12-14 22:01:03 +01:00

System Information
Operating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19

Blender Version
Broken: version: 2.82 (sub 4), branch: master, commit date: 2019-12-06 21:10, hash: 7c2217cd12

Short description of error
When objects are set to display as wire or bounds, in the rendered view in eevee they are shown as wire or bounds respectively, but in Cycles they are fully rendered.

Exact steps for others to reproduce the error
For any object, under object properties -> viewport display, set display as to "bounds" or "wire". Subsequently when the viewport is set to rendered view, the object is shown as bounds or wire in Eevee, but in Cycles the object is fully rendered. The Cycles way would be the preferred way in my opinion.

**System Information** Operating system: Darwin-19.2.0-x86_64-i386-64bit 64 Bits Graphics card: AMD Radeon Pro 5500M OpenGL Engine ATI Technologies Inc. 4.1 ATI-3.4.19 **Blender Version** Broken: version: 2.82 (sub 4), branch: master, commit date: 2019-12-06 21:10, hash: `7c2217cd12` **Short description of error** When objects are set to display as wire or bounds, in the rendered view in eevee they are shown as wire or bounds respectively, but in Cycles they are fully rendered. **Exact steps for others to reproduce the error** For any object, under object properties -> viewport display, set display as to "bounds" or "wire". Subsequently when the viewport is set to rendered view, the object is shown as bounds or wire in Eevee, but in Cycles the object is fully rendered. The Cycles way would be the preferred way in my opinion.

Wouter Stomp commented

2019-12-14 22:01:03 +01:00

Added subscriber: @blenderrocket

blender-admin commented

2019-12-14 22:01:03 +01:00

#72493 was marked as duplicate of this issue

Philipp Oeser commented

2019-12-16 13:33:53 +01:00

Added subscribers: @WilliamReynish, @fclem, @Jeroen-Bakker, @lichtwerk

Philipp Oeser commented

2019-12-16 13:33:53 +01:00

Hm, unsure about the actual design in this case.

Note that discussion in #62557 (object display as wire , invisible when overlay is turned off ) is a bit related.

Will leave up to @WilliamReynish, @Jeroen-Bakker and @fclem to decide...

Hm, unsure about the actual design in this case. Note that discussion in #62557 (object display as wire , invisible when overlay is turned off ) is a bit related. Will leave up to @WilliamReynish, @Jeroen-Bakker and @fclem to decide...

Jeroen Bakker commented

2019-12-16 14:05:46 +01:00

Just for completeness https://devtalk.blender.org/t/about-cycles-in-2-79-and-2-8-and-bound-bounding-box/3154/7

Not sure we can accept it as a bug. IMO it should be marked as a TODO as there is no clear design for it. @blenderrocket prefers something different than what seems to be requested in the devtalk post.

Just for completeness https://devtalk.blender.org/t/about-cycles-in-2-79-and-2-8-and-bound-bounding-box/3154/7 Not sure we can accept it as a bug. IMO it should be marked as a TODO as there is no clear design for it. @blenderrocket prefers something different than what seems to be requested in the devtalk post.

Philipp Oeser commented

2019-12-17 09:34:14 +01:00

Added subscribers: @BoShi, @MarcinTwarowski

B commented

2019-12-17 17:50:12 +01:00

IMO it should be marked as a TODO as there is no clear design for it

how it so not clear if we in 2.79 use this function accros cycles, internal render etc and contept is workin - why we cant take contept of how it work in cycles from 2.79 but bow not clear for the sake of eevee? And because of some on cant figure out how this must work in eevee we have broken contept of work in cycles. Nice.
it already now not working because in eevee objects NOT shown but in cycles it work (rendering) but when object have 1 000 000 poly I WANT that object display in viewport again *in viewport outside of "region of render" keep those millions of poly as bounding box.
please those who make decision or simply not understand about what i talking here are video https://devtalk.blender.org/t/about-cycles-in-2-79-and-2-8-and-bound-bounding-box/3154

i came here from #72493 because the person who manages the tasks here decided #72493 duplicate of #72453 - although this is not so.

>IMO it should be marked as a TODO as there is no clear design for it how it so not clear if we in 2.79 use this function accros cycles, internal render etc and contept is workin - why we cant take contept of how it work in **cycles** from 2.79 but bow not clear for the sake of eevee? And because of some on cant figure out how this must work in eevee we have **broken** contept of work in cycles. Nice. it already now not working because in eevee objects NOT shown but in cycles it work (rendering) but when object have 1 000 000 poly I WANT that object display in viewport again **in viewport* outside of "region of render" keep those millions of poly as bounding box. please those who make decision or simply not understand about what i talking here are video https://devtalk.blender.org/t/about-cycles-in-2-79-and-2-8-and-bound-bounding-box/3154 i came here from #72493 because the person who manages the tasks here decided #72493 duplicate of #72453 - although this is not so.

Brecht Van Lommel added this to the Render & Cycles project 2023-02-07 19:08:06 +01:00

Philipp Oeser removed the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Display as behaviour in rendered view inconsistent between Eevee and Cycles #72453