Make Dupli-Face tool manual entry confusing
Open, NormalPublic

Description

System Information
Operating system and graphics card

Windows 7 64 Bit. Nvidia 760 GTX

Blender Version
Broken: (example: 2.69.7 4b206af, see splash screen)
Worked: (optional)

Broken since minimum 2.76

Short description of error

The manual entry for Make Dupli-Face tool is confusing. The explanation does not involve to use the tool at all. The link from the Make Dupli-Face operator in the menu leads to 404. The purpose of the tool itself cannot be figured out.

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

The manual for the Make Dupli Face tool describes a workflow that does not involve to click at the Make Dupli-face tool at all. http://docs.blender.org/manual/ja/dev/editors/3dview/object/properties/duplication/duplifaces.html

It's basically two steps. Parenting, and then simply change from "None" to "Faces" in the Duplication panel in the Properties editor. And that's it. Nothing else. The Make Dupli-Face tool, for which the manual page is, is not touched at any point.

And what the tool is really meant for is not to find out. When i perform a Make Dupli-Face at a cube, then this cube becomes a child. Another cube. The parent doesn't render anymore, just the child. And that's basically it.

And so this tool riddles me. It seems to do nothing. It is not involved in the described process at all. What do i miss here? How is it meant to work? What should happen when i click at the menu item? Is this operator a disfunctional obsolete fragment from the past? Or does it have a use?

Details

Type
To Do
Bastien Montagne (mont29) triaged this task as "Normal" priority.
Bastien Montagne (mont29) changed Type from Bug to To Do.

The manual entry for Make Dupli-Face tool is confusing. The explanation does not involve to use the tool at all. The link from the Make Dupli-Face operator in the menu leads to 404. The purpose of the tool itself cannot be figured out.

This was fixed in rBAe2b5a9e68c29a40adeb70d2a108c06064662d93f

I will take a deeper look at the rest later.

Ok, it should go to the correct URL in the next available version.