I think that the ! _MatchProperties command should keep the object History after reading the custom mesh settings from another object.
4 Likes
Hi @Rhino_Bulgaria
I just ran into this myself a couple of days ago. I didn’t even post about it but I’m glad you did.
Surely this can be fixed?
RM
1 Like
Yes, this seems like an oversight, the object ID is not changed after MatchProp, but the history record seems to get trashed. Most of the other MatchProp settings do retain the history, so I guess this is a bug. Looks like it exists in the WIP as well.
I filed a bug report:
https://mcneel.myjetbrains.com/youtrack/issue/RH-74866/MatchProperties-Custom-Mesh-Setting-breaks-history
3 Likes
In my opinion, History must not affect object properties other than when the actual geometry is being modified via surfacing or editing tools.
In the few quick tests I made here, I only see History being broken when matching custom mesh settings. Matching other properties does not seem to break the history - but I did not test everything. If you have examples of other ones that are not working please post the procedure.
I tested all options inside the “Match properties” panel and I can confirm that only matching the custom mesh settings destroys the history.
In another recent thread some people were asking for the command to not affect the History. I also agree with that one.
Hi @Helvetosaur
Thanks for making the report.
RM