Page MenuHome

  Error when highlight UV.
Needs Information from User, NormalPublic

Description

System Information
Operating system: Darwin-18.6.0-x86_64-i386-64bit 64 Bits
Graphics card: AMD Radeon Pro 560 OpenGL Engine ATI Technologies Inc. 4.1 ATI-2.9.26

Blender Version
Broken: version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: rB26bd5ebd42e3
Worked: (optional)

Short description of error
https://studio.youtube.com/video/ZFBS94CxP0I/edit

I am writing with the help of Google translator.
  Error when highlight UV.

Exact steps for others to reproduce the error
  How to reproduce the error:

  • Select an editable object.
  • Editing mode.
  • Go to the UV window.
  • Select the desired scan and switch from the vertex mode to the polygon mode.
  • Correct the scan.
  • Select vertex selection mode.
  • Go to the 3D view window and use the cursor to go over the object and select it using the L button.

Thank you for your help! :)

Event Timeline

A bit unclear from the description what seems to be wrong, and the video link is invalid.

Philipp Oeser (lichtwerk) lowered the priority of this task from 90 to 30.Nov 29 2019, 3:26 PM

It is not clear what "scan" means here (as well as what the actual error is, what would be the expected behavior vs. the 'faulty' behavior?), video would help, but as @Stanislav Blinov (radcapricorn) said cannot be accessed...

It is not clear what "scan" means here (as well as what the actual error is, what would be the expected behavior vs. the 'faulty' behavior?), video would help, but as @Stanislav Blinov (radcapricorn) said cannot be accessed...

https://www.youtube.com/watch?v=ZFBS94CxP0I&feature=youtu.be

I copied the wrong link)
scan = UV.
In Google translator UV is translated as a scan. I thought it would be clear :)

A bit unclear from the description what seems to be wrong, and the video link is invalid.

Ты же по русски понимаеш? :D

Yes, I do, but "scan" doesn't have anything in common with "unwrapping". Blame Google Translator, I guess it thought you were talking about a CRT display :D (it just hit me that it can be the same word in Russian indeed).

Anyway, unable to reproduce the crash here. But, what I'm noticing is that in this and your previous report, the View Clip Start is set to a very low value (0.00001 cm). Try increasing that to 0.1 or maybe even 1cm.

To all: the issue appears to be that after adjusting the UVs in the UV editor and attempting to pick linked with L in the 3D viewport, Blender crashes. I'm unable to reproduce this crash on a
GTX980Ti though.

Also cannot reproduce here.

Does this also happen in a fresh build from https://builder.blender.org/download/
[just had a nasty bug fixed for MacOS -- maybe that had these kinds of sideeffects, too?]

Yes, I do, but "scan" doesn't have anything in common with "unwrapping". Blame Google Translator, I guess it thought you were talking about a CRT display :D (it just hit me that it can be the same word in Russian indeed).
Anyway, unable to reproduce the crash here. But, what I'm noticing is that in this and your previous report, the View Clip Start is set to a very low value (0.00001 cm). Try increasing that to 0.1 or maybe even 1cm.
To all: the issue appears to be that after adjusting the UVs in the UV editor and attempting to pick linked with L in the 3D viewport, Blender crashes.

Do you have this parameter?
If I change the values from the standard from my own then in editing mode I start to see polygons which I should not see.


Philipp Oeser (lichtwerk) raised the priority of this task from 30 to 90.Dec 17 2019, 12:37 PM
Campbell Barton (campbellbarton) changed the task status from Needs Triage to Needs Information from User.EditedWed, Jan 15, 8:46 AM

This looks like it could be the duplicate of an issue recently fixed.

Can you check if rB2359979141862cdffa8072f7dd8fc1e67ee228cf (or newer) fixes the problem?