Data Transfer Modifier don't work. #46469

Closed
opened 2015-10-13 11:38:33 +02:00 by Andrew · 15 comments

In blender 2.76, 2.76 RC2/RC3 Vertex data do not transfer when using modes: Nearest face interpolated, nearest face vertex. The rest seems work just fine. Nearest face interpolated produce the best results, pls fix it.

In blender 2.76, 2.76 RC2/RC3 Vertex data do not transfer when using modes: Nearest face interpolated, nearest face vertex. The rest seems work just fine. Nearest face interpolated produce the best results, pls fix it.
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @AndrewShi

Added subscriber: @AndrewShi

Added subscriber: @mont29

Added subscriber: @mont29

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, **small and simple** .blend and/or other files to do so if needed, etc.

No news since one week…

No news since one week…

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2015-10-21 08:22:14 +02:00

Added subscriber: @Tzolkat

Added subscriber: @Tzolkat

I can confirm this issue. I have limited rigging experience and have mostly been working on assets rigged by others, but I can try to make a .blend if it is absolutely necessary.

Steps to reproduce:

  1. Create and rig a mesh, confirm that vertex groups and weights for the bones exist.
  2. Create a second mesh and fit it over the rigged/skinned one.
  3. Select the mesh to transfer to, then shift-select the mesh to transfer from.
  4. Select data transfer, vertex groups.
  5. Select 'nearest face interpolated' for the vertex mapping.
  6. Select the object that was supposed to have weights applied.
  7. Switch to weight paint mode and observe that no weights were transferred.

Affects versions: 2.76 RC1, 2.76 RC2, 2.76 RC3, 2.76, 2.76a, 2.76b.

I can confirm this issue. I have limited rigging experience and have mostly been working on assets rigged by others, but I can try to make a .blend if it is absolutely necessary. Steps to reproduce: 1) Create and rig a mesh, confirm that vertex groups and weights for the bones exist. 2) Create a second mesh and fit it over the rigged/skinned one. 3) Select the mesh to transfer to, then shift-select the mesh to transfer from. 4) Select data transfer, vertex groups. 5) Select 'nearest face interpolated' for the vertex mapping. 6) Select the object that was supposed to have weights applied. 7) Switch to weight paint mode and observe that no weights were transferred. Affects versions: 2.76 RC1, 2.76 RC2, 2.76 RC3, 2.76, 2.76a, 2.76b.

Did you try the latest build from our buildbot? Otherwise, yes, please attach a .blend file to reproduce the issue.

Did you try the latest build from [our buildbot](https://builder.blender.org/download)? Otherwise, yes, please attach a .blend file to reproduce the issue.

I can still reproduce this issue in the latest version I could find from build-bot, 8c84a18.

From what I can tell, it behaves more unpredictably than just not working. In the model I'm working in, which I can't publish, the entire mesh gets weighted to a single bone which is not even nearby. That may have been a glitch, but in any case, it doesn't look like certain vertex mapping modes are working correctly when transferring vertex weights by any method I know of, including the modifier.

I'm attaching a simple .blend file I made which I'm able to reproduce the issue with: data_trans_test.blend

I can still reproduce this issue in the latest version I could find from build-bot, 8c84a18. From what I can tell, it behaves more unpredictably than just not working. In the model I'm working in, which I can't publish, the entire mesh gets weighted to a single bone which is not even nearby. That may have been a glitch, but in any case, it doesn't look like certain vertex mapping modes are working correctly when transferring vertex weights by any method I know of, including the modifier. I'm attaching a simple .blend file I made which I'm able to reproduce the issue with: [data_trans_test.blend](https://archive.blender.org/developer/F254212/data_trans_test.blend)

Changed status from 'Archived' to: 'Open'

Changed status from 'Archived' to: 'Open'

Triple sigh Bug confirmed, regression due to typo in new looptri changes (which affects computation of mapping between two meshes)… Kinda sad initial author did not do his share of the work, we could have had this fixed in 2.76b :(

*Triple sigh* Bug confirmed, regression due to typo in new looptri changes (which affects computation of mapping between two meshes)… Kinda sad initial author did not do his share of the work, we could have had this fixed in 2.76b :(

And thanks @Tzolkat for the file, btw. :)

And thanks @Tzolkat for the file, btw. :)

This issue was referenced by 1e361880a9

This issue was referenced by 1e361880a9bcfba136a556c4201ca96dbdd88eb1

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
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
4 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#46469
No description provided.