Failed angle_normalized_v3v3() assertion when navigating viewport. #86563

New Issue

Kenzie · 2021-03-14T08:55:09+01:00

Kenzie commented

2021-03-14 08:55:09 +01:00

System Information
Operating system: Windows-10-10.0.19041-SP0 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51

Blender Version
Broken: version: 2.93.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: rBUnknown (debug developer build of recent master)
Worked: ?

Short description of error
When navigating the viewport I am often spammed with Warning! quat_to_mat4() called with non-normalized: size 1.00011063 ***report a bug***
Yes I am using a custom build for development, no I have not touched anywhere around the problem area and the problem has persisted for multiple updates from master over a little under the past month. The version was rebased from master a little under an hour ago and the only changes made are in -D10506

Normally this is just an annoying bit of console spam I ignored but just recently a Warning! quat_to_mat3() called with non-normalized: size 1.00011063 ***report a bug*** popped up and it asserted. I have attached a relevant log of the crash, hopefully this helps the maintainer for this area hunt down the problem. ViewportNavigationBugReport.txt

Exact steps for others to reproduce the error
It can be difficult to replicate it, it's mostly just luck, it seems that after you have been working for a while once you manage to navigate the viewport to just the right spot it starts to death-spiral.

**System Information** Operating system: Windows-10-10.0.19041-SP0 64 Bits Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 457.51 **Blender Version** Broken: version: 2.93.0 Alpha, branch: Unknown, commit date: Unknown Unknown, hash: `rBUnknown` (debug developer build of recent master) Worked: ? **Short description of error** When navigating the viewport I am often spammed with `Warning! quat_to_mat4() called with non-normalized: size 1.00011063 ***report a bug***` Yes I am using a custom build for development, no I have not touched anywhere around the problem area and the problem has persisted for multiple updates from master over a little under the past month. The version was rebased from master a little under an hour ago and the only changes made are in -[D10506](https://archive.blender.org/developer/D10506) Normally this is just an annoying bit of console spam I ignored but just recently a `Warning! quat_to_mat3() called with non-normalized: size 1.00011063 ***report a bug***` popped up and it asserted. I have attached a relevant log of the crash, hopefully this helps the maintainer for this area hunt down the problem. [ViewportNavigationBugReport.txt](https://archive.blender.org/developer/F9890409/ViewportNavigationBugReport.txt) **Exact steps for others to reproduce the error** It can be difficult to replicate it, it's mostly just luck, it seems that after you have been working for a while once you manage to navigate the viewport to just the right spot it starts to death-spiral.

Kenzie commented

2021-03-14 08:55:09 +01:00

Added subscriber: @KenzieMac130

Campbell Barton commented

2021-03-15 07:24:59 +01:00

Added subscriber: @ideasman42

Campbell Barton commented

2021-03-15 07:24:59 +01:00

Changed status from 'Needs Triage' to: 'Needs User Info'

Campbell Barton commented

2021-03-15 07:24:59 +01:00

This report is missing:

Last version that worked.
Exact steps to redo the error.
A blend file (unless there are simple steps to redo this from the default startup).

This report is missing: - Last version that worked. - Exact steps to redo the error. - A blend file (unless there are simple steps to redo this from the default startup).

Kenzie commented

2021-03-15 08:35:15 +01:00

In #86563#1129625, @ideasman42 wrote:
This report is missing:

Last version that worked.

Exact steps to redo the error.

A blend file (unless there are simple steps to redo this from the default startup).

I am not exactly sure what was the last version that worked. Last time I worked with blender in a debug developer build and this wasn't an issue for me was maybe around 2.92 Alpha?

It's hard to exactly narrow it down to an exact steps as this appears it might be some hard to replicate issue with floating points and camera movement. I know how much pain these can be so I figured providing the stack dump would be more useful.

Here is the file I have been working in where it seems to happen from time to time after navigating the viewport for a while. I have had the issues in other ones as well. I can say that the assertion happened after I have been navigating the viewport and already got the console to spam Warning! quat_to_mat4() called with non-normalized: size 1.xxxxxxx ***report a bug*** for a while the assertion hit after tabbing out. I have had trouble replicating it myself in the even same file though. issue1.blend

> In #86563#1129625, @ideasman42 wrote: > This report is missing: > > - Last version that worked. > - Exact steps to redo the error. > - A blend file (unless there are simple steps to redo this from the default startup). I am not exactly sure what was the last version that worked. Last time I worked with blender in a debug developer build and this wasn't an issue for me was maybe around 2.92 Alpha? It's hard to exactly narrow it down to an exact steps as this appears it might be some hard to replicate issue with floating points and camera movement. I know how much pain these can be so I figured providing the stack dump would be more useful. Here is the file I have been working in where it seems to happen from time to time after navigating the viewport for a while. I have had the issues in other ones as well. I can say that the assertion happened after I have been navigating the viewport and already got the console to spam `Warning! quat_to_mat4() called with non-normalized: size 1.xxxxxxx ***report a bug***` for a while the assertion hit after tabbing out. I have had trouble replicating it myself in the even same file though. [issue1.blend](https://archive.blender.org/developer/F9892215/issue1.blend)

Ankit Meel commented

2021-03-28 16:12:17 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2021-03-28 16:12:17 +02:00

Couldn't redo on macOS, 99dabc156a.
If D10506 has an issue, guess we'll investigate it when that patch lands. Which branch is that patch based on ?

Couldn't redo on macOS, 99dabc156ac4e843411f9cad71841bc4fb783295. If [D10506](https://archive.blender.org/developer/D10506) has an issue, guess we'll investigate it when that patch lands. Which branch is that patch based on ?

Kenzie commented

2021-03-30 15:42:50 +02:00

In #86563#1137392, @ankitm wrote:
Couldn't redo on macOS, 99dabc156a.
If D10506 has an issue, guess we'll investigate it when that patch lands. Which branch is that patch based on ?

It is based on master. A little outdated though.

> In #86563#1137392, @ankitm wrote: > Couldn't redo on macOS, 99dabc156ac4e843411f9cad71841bc4fb783295. > If [D10506](https://archive.blender.org/developer/D10506) has an issue, guess we'll investigate it when that patch lands. Which branch is that patch based on ? It is based on master. A little outdated though.

Germano Cavalcante commented

2021-05-06 14:32:08 +02:00

Added subscriber: @mano-wii

Germano Cavalcante commented

2021-05-06 14:32:08 +02:00

Changed status from 'Needs User Info' to: 'Archived'

Germano Cavalcante closed this issue

2021-05-06 14:32:08 +02:00

Germano Cavalcante commented

2021-05-06 14:32:08 +02:00

The value 1.00011063, although it indicates that the vector is not normalized, is not a serious problem as this value is still close to 1.0.
Unfortunately the stack dump doesn't help much. It only states that the problem is in viewrotate_apply, but do not show why the viewport does have unnormalized vectors.
The file is also old and has an undefined node:

Having that said, I do not think there is much we can do in this case.
So thanks for the report. If the problem persists please open a new report with the required information.

The value `1.00011063`, although it indicates that the vector is not normalized, is not a serious problem as this value is still close to `1.0`. Unfortunately the stack dump doesn't help much. It only states that the problem is in `viewrotate_apply`, but do not show why the viewport does have unnormalized vectors. The file is also old and has an undefined node: ![image.png](https://archive.blender.org/developer/F10056403/image.png) Having that said, I do not think there is much we can do in this case. So thanks for the report. If the problem persists please open a new report with the required information.

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

Failed angle_normalized_v3v3() assertion when navigating viewport. #86563