Camera perspective, corrupt 3D view in one workspace tab. #67052

New Issue

CarlG · 2019-07-16T13:23:18+02:00

CarlG commented

2019-07-16 13:23:18 +02:00

System Information
Operating system: Linux-4.15.0-51-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: Radeon RX Vega (VEGA10, DRM 3.23.0, 4.15.0-51-generic, LLVM 8.0.0) X.Org 4.5 (Core Profile) Mesa 19.0.2

Blender Version
Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: 06312c6d2d
Worked: (optional)

Short description of error
Sometimes a 3D view can become corrupted and can't show camera view.
The viewport will not show anything.
Rendered viewport will flip between Path Tracing Sample counts but nothing will get done.
Rendering an image from the camera will work, suggesting it's not the camera itself that is erroneous.
Switching to other tabs with a 3D view will also work fine, suggesting it's that specific 3D view that is corrupted.

Exact steps for others to reproduce the error
In provided file:

Observe that in Shading.002 tab, everything works - camera perspective and user perspective view, solid and rendered.
Switch to Shading tab and you get a gray wall in camera perspective, while user perspective view works. Switching to rendered view while in camera perspective, the sample counter will just flip between a couple of numbers rather than complete.

I've had this happen a couple of times now, for no apparent reason - I can't reproduce on demand.
Clicking the add workspace quickly fixes it, but the first time I lost hours trying to figure out what was going on.
Trying to search for bugs here, all I got was the error message:
Unhandled Exception ("PhutilAggregateException")

Note: In my startup, I am using two linked math libraries (bunch of material node groups); one with failing image texture links and one with updated texture links. In the original work file (completely stripped down here), I was using linked blend containing objects in instanced collections and objects regularly instanced. Some objects have textures on multiple UVs (incl BastioniLab human). That's about the only "special" things I can remember about the real file.

CameraViewBuggyShadingInterfaceBug.blend

**System Information** Operating system: Linux-4.15.0-51-generic-x86_64-with-debian-buster-sid 64 Bits Graphics card: Radeon RX Vega (VEGA10, DRM 3.23.0, 4.15.0-51-generic, LLVM 8.0.0) X.Org 4.5 (Core Profile) Mesa 19.0.2 **Blender Version** Broken: version: 2.80 (sub 74), branch: master, commit date: 2019-07-11 13:50, hash: `06312c6d2d` Worked: (optional) **Short description of error** Sometimes a 3D view can become corrupted and can't show camera view. The viewport will not show anything. Rendered viewport will flip between Path Tracing Sample counts but nothing will get done. Rendering an image from the camera will work, suggesting it's not the camera itself that is erroneous. Switching to other tabs with a 3D view will also work fine, suggesting it's that specific 3D view that is corrupted. **Exact steps for others to reproduce the error** In provided file: * Observe that in Shading.002 tab, everything works - camera perspective and user perspective view, solid and rendered. * Switch to Shading tab and you get a gray wall in camera perspective, while user perspective view works. Switching to rendered view while in camera perspective, the sample counter will just flip between a couple of numbers rather than complete. I've had this happen a couple of times now, for no apparent reason - I can't reproduce on demand. Clicking the add workspace quickly fixes it, but the first time I lost hours trying to figure out what was going on. Trying to search for bugs here, all I got was the error message: Unhandled Exception ("PhutilAggregateException") Note: In my startup, I am using two linked math libraries (bunch of material node groups); one with failing image texture links and one with updated texture links. In the original work file (completely stripped down here), I was using linked blend containing objects in instanced collections and objects regularly instanced. Some objects have textures on multiple UVs (incl BastioniLab human). That's about the only "special" things I can remember about the real file. [CameraViewBuggyShadingInterfaceBug.blend](https://archive.blender.org/developer/F7612868/CameraViewBuggyShadingInterfaceBug.blend)

CarlG commented

2019-07-16 13:23:18 +02:00

Added subscriber: @CarlG

Sebastian Parborg commented

2019-07-17 11:51:38 +02:00

Added subscribers: @fclem, @Jeroen-Bakker, @ZedDB

Clément Foucault was assigned by Sebastian Parborg

2019-07-17 11:51:38 +02:00

Sebastian Parborg commented

2019-07-17 11:51:38 +02:00

I'm getting and assert:

BLI_assert failed: /home/zed/prog/blender/source/blender/draw/intern/draw_manager_data.c:1264, draw_view_matrix_state_update(), at 'is_negative_m4(viewmat) == !is_negative_m4(winmat)'

And if I print the winmat, we can see that in contains nan values:

 -nan 0.000000 -nan 0.000000
0.000000 -nan -nan 0.000000
0.000000 0.000000 -1.000020 -0.002000
0.000000 0.000000 -1.000000 0.000000

@fclem @Jeroen-Bakker any idea what might cause this?

I'm getting and assert: ``` BLI_assert failed: /home/zed/prog/blender/source/blender/draw/intern/draw_manager_data.c:1264, draw_view_matrix_state_update(), at 'is_negative_m4(viewmat) == !is_negative_m4(winmat)' ``` And if I print the winmat, we can see that in contains nan values: ``` -nan 0.000000 -nan 0.000000 0.000000 -nan -nan 0.000000 0.000000 0.000000 -1.000020 -0.002000 0.000000 0.000000 -1.000000 0.000000 ``` @fclem @Jeroen-Bakker any idea what might cause this?

Philipp Oeser commented

2019-07-17 12:05:44 +02:00

Added subscriber: @lichtwerk

Philipp Oeser commented

2019-07-17 12:05:44 +02:00

Probably totally unrelated, but I am getting this exact assert in #66745

Clément Foucault commented

2019-07-18 10:27:58 +02:00

Ok this is because the view3D is corrupted (somehow).

rv3d->camdx and rv3d->camdy are NaN in the file for this View3D leading to incorrect matrix calculation.

Workaround : The only way to reset them seems to be the "View Camera Center" operator.

Not sure how you ended up with this as theses values are clamped. Maybe zooming too much in camera view?

Not sure how to solve it either. Maybe some underflow/overflow protection at some level?

Ok this is because the view3D is corrupted (somehow). rv3d->camdx and rv3d->camdy are NaN in the file for this View3D leading to incorrect matrix calculation. Workaround : The only way to reset them seems to be the "View Camera Center" operator. Not sure how you ended up with this as theses values are clamped. Maybe zooming too much in camera view? Not sure how to solve it either. Maybe some underflow/overflow protection at some level?

Sebastian Parborg commented

2019-07-18 10:50:32 +02:00

@CarlG could you try to figure out what is causing this for you?
It will be quite hard for us to fix it if we do not have a way to reproduce it.

@CarlG could you try to figure out what is causing this for you? It will be quite hard for us to fix it if we do not have a way to reproduce it.

CarlG commented

2019-07-18 21:50:34 +02:00

Workaround : The only way to reset them seems to be the "View Camera Center" operator.
What does the above mean? How would I execute this?

I can try zooming around, way too far and see if something happens.
Sorry, but I have no idea how it happens, and considering it only happened a couple of times I doubt it's going to be easy for me to reproduce as well.

Currently I add a new Workspace, but that ends up last and without stepwise relocating (only first and last) it's kinda annoying :)
But again, only a couple of times and not in important projects.

Workaround : The only way to reset them seems to be the "View Camera Center" operator. What does the above mean? How would I execute this? I can try zooming around, way too far and see if something happens. Sorry, but I have no idea how it happens, and considering it only happened a couple of times I doubt it's going to be easy for me to reproduce as well. Currently I add a new Workspace, but that ends up last and without stepwise relocating (only first and last) it's kinda annoying :) But again, only a couple of times and not in important projects.

Clément Foucault commented

2019-07-19 00:55:49 +02:00

@CarlG "View Camera Center" is an operator. Search for it when in camera view after pressing F3 to invoke the search operator box.