ID 434200 - Mari does not store locator transformations created in a Projection node until the viewport is rotated

Problem summary
When a locator is created within a Projection node (to alter the projection values), if the locator is applied then removed before the Viewport is altered, the projected texture will reset to the original locator position.

Customer reported version
mari.4.6v3

Customer reported platform
windows10

Steps to reproduce

1) Create a new example head project

2) Select the 'Head_Geo' object and navigate to the Nodegraph

3) In the Nodegraph, create a Projection node, connecting the 'Output' to the 'Base Color' input of the 'Principled BRDF' shader node.

4) Open the Projection node properties and select an image to use as the projected texture

5) Also in the Projection node properties, within the 'Projection' sub-menu, click '+' to add a locator and 'P' to select it in the Viewport
6) Without rotating the geometry within the Viewport, transform the locator gizmo over the head and scale up/down to alter the projected map.

7) Delete the locator within the 'Objects' menu
Result: When the locator is deleted, the projected texture is reset to the original position.

8) Repeat steps 5-7, this time rotating the geometry within the Viewport, before deleting the locator.
Result: The projected texture will remain as expected

Expected behaviour
The locator should not require the Viewport to be rotated to retain the mapped projection, even when deleted.

Actual behaviour
When the locator is deleted and the Viewport not rotated, the mapped projection will snap back to the default position.

Workaround
Rotate the Viewport after applying the locator, if you are planning on deleting it before rotating in the Viewport.

Reproduced by support
This bug has been reproduced in:
Mari 4.6v3 - Windows 10
Mari 4.6v1 - Windows 10


Unable to reproduce bug in:
Mari 4.5v2 -Windows 10

Earliest version tested
- The Projection node did not exist before 4.6v1