Viewport glitching in Blender 2.80 after opening a 2.79b .blend file #62846

New Issue

Thomas Gijsbers · 2019-03-22T16:22:11+01:00

Thomas Gijsbers commented

2019-03-22 16:22:11 +01:00

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35

Blender Version
Broken: version: 2.80 (sub 50), branch: blender2.7, commit date: 2019-03-20 01:34, hash: 47ba487e05
Worked: (optional)

Note that the .blend file was made in 2.79b and the bug happened after opening it in this 2.80 beta.

Short description of error
[Please fill out a short description of the error here]
Blender 2.80 shows the scene either as an empty solid gray square, or (in the case of the screenshot) a weird deformation of the skybox. I have tried both the Cycles and Eevee render engines, Eevee doesn't seem to render anything at all, while cycles glitches for me.

2.79b

2.80 (sub 50)

Exact steps for others to reproduce the error

Start the Blender 2.80 executable.
Open the "House Bake Scene.blend" file I have attached to this post using "Open...". (I recommend you also download "House Bake Scene.blend1" and put it in the same folder. It is probably not necessary)
Set the render engine to either "Eevee" or "Cycles" in the "Render Engine" under the "Scene" tab.

House Bake Scene.blend1

House Bake Scene.blend

**System Information** Operating system: Windows-10-10.0.17763 64 Bits Graphics card: GeForce GTX 1060/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 417.35 **Blender Version** Broken: version: 2.80 (sub 50), branch: blender2.7, commit date: 2019-03-20 01:34, hash: `47ba487e05` Worked: (optional) **Note that the .blend file was made in 2.79b and the bug happened after opening it in this 2.80 beta.** **Short description of error** [Please fill out a short description of the error here] Blender 2.80 shows the scene either as an empty solid gray square, or (in the case of the screenshot) a weird deformation of the skybox. I have tried both the Cycles and Eevee render engines, Eevee doesn't seem to render anything at all, while cycles glitches for me. ![blender_AZMJlw2rhC.jpg](https://archive.blender.org/developer/F6865657/blender_AZMJlw2rhC.jpg) 2.79b ![blender_vaLXj70Eok.png](https://archive.blender.org/developer/F6865659/blender_vaLXj70Eok.png) 2.80 (sub 50) **Exact steps for others to reproduce the error** 1. Start the Blender 2.80 executable. 2. Open the "House Bake Scene.blend" file I have attached to this post using "Open...". (I recommend you also download "House Bake Scene.blend1" and put it in the same folder. It is probably not necessary) 3. Set the render engine to either "Eevee" or "Cycles" in the "Render Engine" under the "Scene" tab. [House Bake Scene.blend1](https://archive.blender.org/developer/F6865675/House_Bake_Scene.blend1) [House Bake Scene.blend](https://archive.blender.org/developer/F6865674/House_Bake_Scene.blend)

Thomas Gijsbers commented

2019-03-22 16:22:11 +01:00

Added subscriber: @t-bender

Thomas Gijsbers changed title from ~~Viewport not showing any meshes or objects, despite the Scene Collection showing items.~~ to Viewport glitching in Blender 2.80 after opening a 2.79b .blend file

2019-03-22 16:22:59 +01:00

Brecht Van Lommel commented

2019-03-22 16:50:18 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2019-03-22 16:50:18 +01:00

Clip End in the 3D view sidebar is set to inf, that's not a valid value. Was that set intentionally? It can only work for Cycles to use a very high clip end without artifacts, and even then it should be a regular number instead of inf.

Brecht Van Lommel commented

2019-04-04 05:51:33 +02:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2019-04-04 05:51:33 +02:00

Brecht Van Lommel self-assigned this 2019-04-04 05:51:33 +02:00

Brecht Van Lommel commented

2019-04-04 05:51:33 +02:00

Closing report since clip end is set to an invalid value and we have no information on how it ended up that way.

Thomas Gijsbers commented

2019-12-25 15:19:56 +01:00

In #62846#646379, @brecht wrote:
Clip End in the 3D view sidebar is set to inf, that's not a valid value. Was that set intentionally? It can only work for Cycles to use a very high clip end without artifacts, and even then it should be a regular number instead of inf.

I'm sorry for the very late reply. I forgot to turn on notifications. I hope this bug report can still be of some use. :P

Yes, the clip end was set to inf on purpose, to preview faraway objects in the viewport.

'inf' is a valid value in Blender 2.79, and is set automatically when you enter a very high number (10e^n) in the 'Clip End' text-bar. Blender 2.8x doesn't seem to accept this value, likely because that part of the source code was rewritten.
I didn't know that was what was causing the issue. Seems to be a mild compatibility issue, nothing more.

> In #62846#646379, @brecht wrote: > Clip End in the 3D view sidebar is set to inf, that's not a valid value. Was that set intentionally? It can only work for Cycles to use a very high clip end without artifacts, and even then it should be a regular number instead of inf. I'm sorry for the very late reply. I forgot to turn on notifications. I hope this bug report can still be of some use. :P Yes, the clip end was set to inf on purpose, to preview faraway objects in the viewport. 'inf' is a valid value in Blender 2.79, and is set automatically when you enter a very high number (10e^n) in the 'Clip End' text-bar. Blender 2.8x doesn't seem to accept this value, likely because that part of the source code was rewritten. I didn't know that was what was causing the issue. Seems to be a mild compatibility issue, nothing more.

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

Viewport glitching in Blender 2.80 after opening a 2.79b .blend file #62846