RMB cancel of translation of an object-offset array leaves the array in a visually undeterminate state #83724

New Issue

s12a · 2020-12-13T16:11:28+01:00

s12a commented

2020-12-13 16:11:28 +01:00

System Information
Operating system: Linux-5.9.12-1-default-x86_64-with-glibc2.17 64 Bits
Graphics card: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.39.0, 5.9.12-1-default, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.4

Blender Version
Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-12-12 18:07, hash: 4797c13e8f

Short description of error
A curve object (named "Cage") has been duplicated in a circular pattern using an Array modifier and an Empty object as an object offset. The Empty object is parented to the curve object. If I try to move "Cage" (the parent object) with G and canceling the operation with RMB, the object-offset duplication pattern appears to be visually destroyed, as shown in this image:

However, hitting Tab twice to enter/leave the Edit mode, brings back the object in a correct state.

Oddly enough, saving the file Ctrl+S with the object in an apparently destroyed state and reloading it also brings back the object back to normal. So, this appears to be a strictly viewport update glitch and therefore likely to be a true bug.

Exact steps for others to reproduce the error
In the attached blend file:

Grab G the Object called "Cage" and move it around without confirming the operation
Cancel the operation with RMB => Object is destroyed
Select the object and hit Tab twice => Object is repaired

cages_array-update-bug.blend

**System Information** Operating system: Linux-5.9.12-1-default-x86_64-with-glibc2.17 64 Bits Graphics card: AMD Radeon (TM) RX 480 Graphics (POLARIS10, DRM 3.39.0, 5.9.12-1-default, LLVM 11.0.0) X.Org 4.6 (Core Profile) Mesa 20.2.4 **Blender Version** Broken: version: 2.92.0 Alpha, branch: master, commit date: 2020-12-12 18:07, hash: `4797c13e8f` **Short description of error** A curve object (named "Cage") has been duplicated in a circular pattern using an Array modifier and an Empty object as an **object offset**. The Empty object is parented to the curve object. If I try to move "Cage" (the parent object) with `G` and canceling the operation with `RMB`, the object-offset duplication pattern appears to be visually destroyed, as shown in this image: ![destroyed-cage.png](https://archive.blender.org/developer/F9506631/destroyed-cage.png) However, hitting `Tab` twice to enter/leave the Edit mode, brings back the object in a correct state. ![ok-cage.png](https://archive.blender.org/developer/F9506636/ok-cage.png) Oddly enough, saving the file `Ctrl+S` with the object in an apparently destroyed state and reloading it also brings back the object back to normal. So, this appears to be a strictly viewport update glitch and therefore likely to be a true bug. **Exact steps for others to reproduce the error** In the attached blend file: - Grab `G` the Object called "Cage" and move it around without confirming the operation - Cancel the operation with `RMB` => Object is destroyed - Select the object and hit `Tab` twice => Object is repaired [cages_array-update-bug.blend](https://archive.blender.org/developer/F9506641/cages_array-update-bug.blend)

s12a commented

2020-12-13 16:11:28 +01:00

Added subscriber: @s12a

s12a commented

2020-12-13 16:32:29 +01:00

Rotate R and Scale S operations on the same object are also affected by this RMB-cancel bug, it turns out.

Rotate `R` and Scale `S` operations on the same object are also affected by this `RMB`-cancel bug, it turns out.

s12a commented

2020-12-13 16:49:41 +01:00

Transform operations with numerical input are also affected by this visual glitch, but after the operation is confirmed the object returns to its normal state.

Steps from the previously attached .blend file:

Select "Cage"
Press G
Enter X, then 1 => Object is destroyed
Confirm with Enter or LMB => Object is repaired

Transform operations with numerical input are also affected by this visual glitch, but after the operation is confirmed the object returns to its normal state. Steps from the previously attached .blend file: - Select "Cage" - Press `G` - Enter `X`, then `1` => Object is destroyed - Confirm with `Enter` or `LMB` => Object is repaired

Robert Guetzkow commented

2020-12-15 13:22:14 +01:00

Added subscriber: @rjg

Robert Guetzkow commented

2020-12-15 13:22:14 +01:00

You have a dependency cycle in your project. The position of the cage array elements depend on the location of the empty, whose location depends on the cage as it is parented to it. If you parent the cage to the empty, instead of the empty to the cage, you can move the empty around and everything follows.

Robert Guetzkow commented

2020-12-15 13:22:46 +01:00

Changed status from 'Needs Triage' to: 'Archived'

Robert Guetzkow closed this issue

2020-12-15 13:22:46 +01:00

s12a commented

2020-12-15 13:38:34 +01:00

After arranging the parent-child relationship differently, it does indeed work correctly. I guess there was an expectation that the program would have tried to cope with the issue more consistently or warn the user.

Robert Guetzkow commented

2020-12-15 13:46:59 +01:00

@s12a A warning is printed to the console (Window > Toggle System Console), which is easy to miss. We're planning to display warning and error messages more consistently in the future.

@s12a A warning is printed to the console (*Window > Toggle System Console*), which is easy to miss. We're planning to display warning and error messages more consistently in the future.

s12a commented

2020-12-15 13:56:59 +01:00

I confirm those messages appearing in the console, although on Linux I had to launch Blender from the terminal to see them (no Window>Toggle System Console option here).

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

RMB cancel of translation of an object-offset array leaves the array in a visually undeterminate state #83724