Crash occurring when a second UV Map is applied to a mesh and texture mode is enabled in the solid viewport setting #107832

New Issue

and removed

2023-05-11 19:15:56 +02:00

labels 2023-05-11 12:50:02 +02:00

Erik G. Riebling commented

Would a screenshot and/or a video recording suffice? I could also give you the crash report I got from my computer if needed.

Anyway, to answer your question regarding the "Textured viewport setting", I will quote from the same page you linked me.

Solid
This mode utilizes the Workbench Render Engine to render the 3D Viewport. It shows solid geometry but uses simplified shading and lighting without the use of shader nodes. Solid mode is good for modeling and sculpting, and is really useful with the multitude of options to emphasize certain geometric features.

Texture:
Show the texture from the active image texture node using the active UV map coordinates When an object has no active texture the object will be rendered with the settings in the Viewport Display Material panel.

If the texture setting is enabled while the solid viewport is active, the file will crash.

Would a screenshot and/or a video recording suffice? I could also give you the crash report I got from my computer if needed. Anyway, to answer your question regarding the "Textured viewport setting", I will quote from the same page you linked me. **Solid** _This mode utilizes the Workbench Render Engine to render the 3D Viewport. It shows solid geometry but uses simplified shading and lighting without the use of shader nodes. Solid mode is good for modeling and sculpting, and is really useful with the multitude of options to emphasize certain geometric features._ **Texture:** _Show the texture from the active image texture node using the active UV map coordinates When an object has no active texture the object will be rendered with the settings in the Viewport Display Material panel._ If the texture setting is enabled while the solid viewport is active, the file will crash.

system-info.txt

7.0 KiB

UVProblem.blend

98 KiB

Erik G. Riebling commented

2023-05-12 05:22:10 +02:00

The problem is even worse than I imagined. It extends into trying to view the second UV Map in the UV Editor. If the UV Editor is open with the second UV Map applied to the mesh, then the whole application crashes. This is bad because trying to edit the second UV Map is no longer possible. In fact, the crash messages for both errors are rather similar.

Application Specific Information:
validateVertexAttribute:724: failed assertion `Attribute at index 0: the attribute offset (192) + attribute size (8) must be <= the stride of the buffer (8) at buffer index 0.'

Application Specific Information:
validateVertexAttribute:724: failed assertion `Attribute at index 3: the attribute offset (192) + attribute size (8) must be <= the stride of the buffer (8) at buffer index 2.'

Right now, I cannot do anything with a second UV Map until this problem is fixed.

EDIT: I have found that it works as intended in version 3.1.0. Version 3.5.0 and onwards produces the error. I will update my original post as such.

The problem is even worse than I imagined. It extends into trying to view the second UV Map in the UV Editor. If the UV Editor is open with the second UV Map applied to the mesh, then the whole application crashes. This is bad because trying to edit the second UV Map is no longer possible. In fact, the crash messages for both errors are rather similar. Application Specific Information: validateVertexAttribute:724: failed assertion `Attribute at index 0: the attribute offset (192) + attribute size (8) must be <= the stride of the buffer (8) at buffer index 0.' Application Specific Information: validateVertexAttribute:724: failed assertion `Attribute at index 3: the attribute offset (192) + attribute size (8) must be <= the stride of the buffer (8) at buffer index 2.' Right now, I cannot do anything with a second UV Map until this problem is fixed. EDIT: I have found that it works as intended in version 3.1.0. Version 3.5.0 and onwards produces the error. I will update my original post as such.

Pratik Borhade added

and removed

2023-05-12 17:47:50 +02:00

labels 2023-05-12 06:30:09 +02:00

Germano Cavalcante commented

Please avoid text walls and provide clear steps on how to reproduce the problem (start blender, press this, then that and crash).

I cannot understand what needs to be done to reproduce the problem.

Would a screenshot and/or a video recording suffice?

That would help, sure.

A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Please avoid text walls and provide clear steps on how to reproduce the problem (start blender, press this, then that and crash). I cannot understand what needs to be done to reproduce the problem. > Would a screenshot and/or a video recording suffice? That would help, sure. A guideline for making a good bug report can be found at https://wiki.blender.org/wiki/Process/Bug_Reports

Germano Cavalcante added

and removed

2023-05-12 19:40:12 +02:00

labels 2023-05-12 17:48:00 +02:00

Erik G. Riebling commented

Alright then, it is easier for to showcase the problem through a screen recording. I actually have a couple showing the error in action. If you need more information, do let me know.

Screen Recording 2023-05-12 at 12.35.53 PM.mov

20 MiB

Screen Recording 2023-05-12 at 12.30.04 PM.mov

13 MiB

Germano Cavalcante commented

2023-05-12 23:43:00 +02:00

I strictly followed the steps shown in the video. To know:

Split the 3D View into two viewports (right and left)
Go to edit mode
In Mesh properties, add and select a new UV
In the right viewport go to the Edges menu and click on Mark Seams (all edges should be marked)
Go to the UVs menu and click on Unwrap
In the left viewport change the editor to UV Editor

But I couldn't replicate using the latest official release (3.5.1) or the latest daily builds.

Please try the latest daily build: https://builder.blender.org/download/

Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

I strictly followed the steps shown in the video. To know: - Split the 3D View into two viewports (right and left) - Go to edit mode - In Mesh properties, add and select a new UV - In the right viewport go to the `Edges` menu and click on `Mark Seams` (all edges should be marked) - Go to the UVs menu and click on `Unwrap` - In the left viewport change the editor to `UV Editor` But I couldn't replicate using the latest official release (3.5.1) or the latest daily builds. Please try the latest daily build: https://builder.blender.org/download/ Go to File → Defaults → Load Factory Settings and then load your file to see if you still can reproduce this issue.

Erik G. Riebling commented

2023-05-13 00:27:37 +02:00

I'm sorry to tell you this, but the error still persists. What's worse is that trying to view it in the Textured mode with the Solid viewport enabled causes the same crash as before. I even downloaded Blender 3.5.1 and everything.

May I give you the full Apple error report if it'll give you any insight?

I'm sorry to tell you this, but the error still persists. What's worse is that trying to view it in the Textured mode with the Solid viewport enabled causes the same crash as before. I even downloaded Blender 3.5.1 and everything. May I give you the full Apple error report if it'll give you any insight?

Germano Cavalcante added

and removed