In Polymating 1.4 the workflow is much more opinionated and users can do projection in a more personal manner. Polymating will no longer be tested on Blender version below 5.0 after this update comes to live although this version works on Blender 4.5 at the time of this writing.

Interface change:

• Improve the interface for vertex groups locking, it is now able to read multiple lock groups. With greater power comes greater responsibility as multiple group locking will add overhead proportional to both the number of vertices and the number of lock groups each vertex belongs. This might be improved later on.
• The menu for Polymating will now be able to be called through search.
• The panel for the View 3D region can now be hidden through preferences settings.

Projection Behavior update:

• Vertex locking are now more aggresive, as it no longer get bypassed by nearest solver and persist through solver changes.
• Projection now skips hidden vertices, including vertices that gets hidden with mask modifier, you might want to be careful when excluding the vertices using manual hiding because once the vertices are unhidden the projection will take effect immediately.
• Projection now respects masks made within the sculpt mode and this masks will persist through object mode and edit mode, this allows for a more unopinionated workflow when working with specific vertices. Though this mask system has a different behavior than what you get when using hidden or vertex locking, as it has locking behaviour on the sculpt mode and in edit mode it does not project.

Performance update:

• Hidden vertices are partially evaluated to determine whether projection affects them. This means that when working with a mesh containing hidden vertices, those vertices introduce only a partial performance overhead, rather than doing the full calculation. This way you can work on a larger polycount base.

• Now Polymating can project the active object unto itself.
• Projection now works on shape-keys
• When the vertex group locking pointers are set but no axis enabled, the projection will affect only the vertices from the vertex group

1.2.4
- added localization for Simplified Chinese (zh-CN) and Indonesian (id)
- solver properties optimization
- directories optimization
- added readme section #Adding Language

1.1.2
- implemented better cache for the vertex locking
- fix some runtime issue when enabling and changing the axis of the locked vertices

1.1
- it is now possible to use collection for reference on all solvers
- force Project are now Nearest and On-Hit Limit are now a deprecated solver
- on-hit and Multi-hit are now deprecated solvers and have been implemented into Raycast
- added reference switch to choose between a single reference object or a collection
- added configurable rays length when choosing Raycast for the solver
- fix some jumpy jitter problem when doing the projection
- fix some issue with the vertex locking where the new vertices that is added at runtime doesn't get locked
- fix some performance issue related to cache

• Separation of logic from mode handler
• added FORCE_PROJECT solver
• added ON_HIT_LIMIT solver
• added ON_HIT solver
• added MULTI_HIT solver
• global overlay properties
• projection threshold optimization
• preferences ui and viewport ui optimization
• added multiple error handling functionality to ease fidgety user and accidental clicks that can disturb user interaction
• version branching in preparation for the development of multi-threading and asynchronous process
• version branching in preparation for localization
• added ray_cast logic specifically made for edit-mode for better performance
• added Vertex Locking as experimental features
• added options to choose between default logic and ray_cast
• preferences ui optimization

Fix preferences issue, when migrating from addon to extension folder structure

• added toml
• blender 4.3 optimization