Error when highlight UV. #72044

Closed
opened 2019-11-29 13:52:20 +01:00 by Valentine · 16 comments

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: 26bd5ebd42
Worked: (optional)

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

OptWor.blend

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! :)

**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: `26bd5ebd42` Worked: (optional) **Short description of error** https://studio.youtube.com/video/ZFBS94CxP0I/edit [OptWor.blend](https://archive.blender.org/developer/F8178120/OptWor.blend) 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! :)
Author

Added subscriber: @ValeGoG

Added subscriber: @ValeGoG

Added subscriber: @Stan_Pancakes

Added subscriber: @Stan_Pancakes

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

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

Added subscriber: @lichtwerk

Added subscriber: @lichtwerk
Member

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 @Stan_Pancakes 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 @Stan_Pancakes said cannot be accessed...
Author

In #72044#821129, @lichtwerk wrote:
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 @Stan_Pancakes 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 :)

> In #72044#821129, @lichtwerk wrote: > 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 @Stan_Pancakes 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 :)
Author

In #72044#821060, @Stan_Pancakes wrote:
A bit unclear from the description what seems to be wrong, and the video link is invalid.

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

> In #72044#821060, @Stan_Pancakes wrote: > 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.

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.
Member

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?]

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?]
Author

In #72044#821193, @Stan_Pancakes wrote:
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.

image.png

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.

image.png
image.png

> In #72044#821193, @Stan_Pancakes wrote: > 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. ![image.png](https://archive.blender.org/developer/F8178468/image.png) 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. ![image.png](https://archive.blender.org/developer/F8178476/image.png) ![image.png](https://archive.blender.org/developer/F8178482/image.png)

Added subscriber: @ideasman42

Added subscriber: @ideasman42

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

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

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

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

This looks like it could be the duplicate of an issue recently fixed. Can you check if 2359979141 (or newer) fixes the problem?

Added subscriber: @iss

Added subscriber: @iss

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

Changed status from 'Needs User Info' to: 'Archived'
Richard Antalik self-assigned this 2020-01-23 01:33:05 +01:00

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to close the report.

Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to close the report.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
5 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#72044
No description provided.