uv unwrap node, weird values #99284

New Issue

Nahuel Belich · 2022-06-29T23:00:53+02:00

Nahuel Belich commented

2022-06-29 23:00:53 +02:00

System Information
Operating system: Linux-5.13.0-51-generic-x86_64-with-glibc2.31 64 Bits
Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01

Blender Version
Broken: version: 3.3.0 Alpha, branch: master, commit date: 2022-06-29 17:28, hash: 0ea282f746
Worked: (newest version of Blender that worked as expected)

Short description of error
similar to other bug i reported a few days ago ( https://developer.blender.org/T99239 ) although probably not the same issue, now with the new UVunwrap node trying to see what the node does, it returns really weird values

bugmem.mp4

Exact steps for others to reproduce the error
bug_uvnode.blend
turn on and off the modifier

**System Information** Operating system: Linux-5.13.0-51-generic-x86_64-with-glibc2.31 64 Bits Graphics card: NVIDIA GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.103.01 **Blender Version** Broken: version: 3.3.0 Alpha, branch: master, commit date: 2022-06-29 17:28, hash: `0ea282f746` Worked: (newest version of Blender that worked as expected) **Short description of error** similar to other bug i reported a few days ago ( https://developer.blender.org/T99239 ) although probably not the same issue, now with the new UVunwrap node trying to see what the node does, it returns really weird values [bugmem.mp4](https://archive.blender.org/developer/F13239478/bugmem.mp4) **Exact steps for others to reproduce the error** [bug_uvnode.blend](https://archive.blender.org/developer/F13239484/bug_uvnode.blend) turn on and off the modifier

Nahuel Belich commented

2022-06-29 23:00:53 +02:00

Added subscriber: @NahuelBelich

Iliya Katushenock commented

2022-06-30 05:55:57 +02:00

Added subscribers: @aleksijuvani, @mod_moder

Iliya Katushenock commented

2022-06-30 05:55:57 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Iliya Katushenock commented

2022-06-30 05:55:57 +02:00

Hello, @aleksijuvani (I hope I did not confuse the person responsible for the UV code)

Looks like there is still -NaN in the UV

Hello, @aleksijuvani (I hope I did not confuse the person responsible for the UV code) ![image.png](https://archive.blender.org/developer/F13240795/image.png) Looks like there is still -NaN in the UV

Aleksi Juvani commented

2022-07-02 13:28:09 +02:00

Added subscriber: @HooglyBoogly

Aleksi Juvani commented

2022-07-02 13:28:09 +02:00

@HooglyBoogly I took a look at this, and I see that when committing the patch you've changed how the Array<float3> uv arrays are constructed. The contents are now uninitialized whereas they should be zero-initialized.

@HooglyBoogly I took a look at this, and I see that when committing the patch you've changed how the `Array<float3> uv` arrays are constructed. The contents are now uninitialized whereas they should be zero-initialized.

Iliya Katushenock commented

2022-07-02 13:37:42 +02:00

In #99284#1383639, @aleksijuvani wrote:
@HooglyBoogly I took a look at this, and I see that when committing the patch you've changed how the Array<float3> uv arrays are constructed. The contents are now uninitialized whereas they should be zero-initialized.

Is it possible to avoid zero initialization in favor of write processing?

> In #99284#1383639, @aleksijuvani wrote: > @HooglyBoogly I took a look at this, and I see that when committing the patch you've changed how the `Array<float3> uv` arrays are constructed. The contents are now uninitialized whereas they should be zero-initialized. Is it possible to avoid zero initialization in favor of write processing?

Hans Goudey self-assigned this 2022-07-02 16:09:32 +02:00

Hans Goudey commented

2022-07-02 16:09:32 +02:00

Added subscriber: @Hans-6

Hans Goudey commented

2022-07-02 16:09:32 +02:00

@HooglyBoogly I took a look at this, and I see that when committing the patch you've changed how the Array uv arrays are constructed. The contents are now uninitialized whereas they should be zero-initialized.

Eek, I'm sorry about that. The syntax made it unclear that was the goal, but I should have asked you about it. I'll fix it then.

Is it possible to avoid zero initialization in favor of write processing?

This would be nice, and that was my thought when changing it. I'll make sure that isn't possible when I look at this.

>@HooglyBoogly I took a look at this, and I see that when committing the patch you've changed how the Array<float3> uv arrays are constructed. The contents are now uninitialized whereas they should be zero-initialized. Eek, I'm sorry about that. The syntax made it unclear that was the goal, but I should have asked you about it. I'll fix it then. >Is it possible to avoid zero initialization in favor of write processing? This would be nice, and that was my thought when changing it. I'll make sure that isn't possible when I look at this.

Hans Goudey commented

2022-07-02 16:11:01 +02:00

Removed subscriber: @Hans-6

blender-admin commented

2022-07-06 01:01:08 +02:00

This issue was referenced by faac25fefe

This issue was referenced by faac25fefedf4b3318d4f129ebda9efca16e48c5

Hans Goudey commented

2022-07-06 01:01:18 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Hans Goudey closed this issue

2022-07-06 01:01:18 +02:00

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

uv unwrap node, weird values #99284