Background Images issue when having opposite ones or Aligned to View. #69967

Closed
opened 2019-09-17 06:18:44 +02:00 by CobraA · 11 comments

System Information
Windows 10 64 Bits.
Graphics card GeForce GTX 1080 Ti.

Blender Version
Broken: version: and 2.81 Alpha hash: 28ee0f97c3

Short description of error
The Background Images or Empties have some issues, when you set two opposite ones you get their wireframes shown (Pic1).

If you enable Only Axis Alinged and go to Ortho View they appear as Wireframes(Pic 2) and there is no way to hide them without hiding the Empties themselves, i think this is should be considered as a bug even though there isn't any "technical" one but rather a missing functionality that makes empties or background images useless for working with model sheets.

Exact steps for others to reproduce the error

  • Have two Background images in each opposite view and enable only one side for each front & back (Pic1).
  • Enable Only Axis Aligned.
  • Turn off Display in Perspective(optional).
  • Go to Ortho View and Rotate you'll see the Background images wireframes(Pic2) floating around your model, no way to hide them except hiding the Empties.

A way to hide these wireframes without hiding the Background Images would do the trick and if users want these Wireframes for selection or whatever then a setting in their Properties.
Pic 1
aze.jpg
Pic 2
WW.jpg

System Information Windows 10 64 Bits. Graphics card GeForce GTX 1080 Ti. Blender Version Broken: version: and 2.81 Alpha hash: 28ee0f97c33b Short description of error The Background Images or Empties have some issues, when you set two opposite ones you get their wireframes shown (Pic1). If you enable Only Axis Alinged and go to Ortho View they appear as Wireframes(Pic 2) and there is no way to hide them without hiding the Empties themselves, i think this is should be considered as a bug even though there isn't any "technical" one but rather a missing functionality that makes empties or background images useless for working with model sheets. Exact steps for others to reproduce the error - Have two Background images in each opposite view and enable only one side for each front & back (Pic1). - Enable Only Axis Aligned. - Turn off Display in Perspective(optional). - Go to Ortho View and Rotate you'll see the Background images wireframes(Pic2) floating around your model, no way to hide them except hiding the Empties. A way to hide these wireframes without hiding the Background Images would do the trick and if users want these Wireframes for selection or whatever then a setting in their Properties. **Pic 1** ![aze.jpg](https://archive.blender.org/developer/F7752258/aze.jpg) **Pic 2** ![WW.jpg](https://archive.blender.org/developer/F7752256/WW.jpg)
Author

Added subscriber: @CobraA

Added subscriber: @CobraA
Member

Added subscriber: @JacquesLucke

Added subscriber: @JacquesLucke
Member

Please prepare a simple .blend file that allows us to reproduce the issue more easily. (make sure that the image is packed into the file)

Please prepare a simple .blend file that allows us to reproduce the issue more easily. (make sure that the image is packed into the file)
Author

Here is the blend file.
Cryogenic_Chamber.blend

Here is the blend file. [Cryogenic_Chamber.blend](https://archive.blender.org/developer/F7756070/Cryogenic_Chamber.blend)
Author

Any update on this? it's really bugging me down.

Any update on this? it's really bugging me down.
Member

Added subscribers: @ideasman42, @lichtwerk

Added subscribers: @ideasman42, @lichtwerk
Member

I would also think these frames of empty images can get in the way.
[and the way we present the Display Only Axis Aligned option in the UI would make me think these are working just like Display Orthographic & Display Perspective -- acting on both image and frame]
Not sure if this would be considered a bug (probably not), but confirming for now and let @JacquesLucke or @ideasman42 decide.

Not sure about a good solution regarding the opposing Front and Back issue [I think it is best to avoid another option here], but this would hide the frame for the Display Only Axis Aligned case:
P1207: T69967_snippet



diff --git a/source/blender/blenkernel/intern/object.c b/source/blender/blenkernel/intern/object.c
index 1378e862034..2fa9f3c95f9 100644
--- a/source/blender/blenkernel/intern/object.c
+++ b/source/blender/blenkernel/intern/object.c
@@ -2986,6 +2986,16 @@ void BKE_object_empty_draw_type_set(Object *ob, const int value)
 bool BKE_object_empty_image_frame_is_visible_in_view3d(const Object *ob, const RegionView3D *rv3d)
 {
   const char visibility_flag = ob->empty_image_visibility_flag;
+
+  if (visibility_flag & OB_EMPTY_IMAGE_HIDE_NON_AXIS_ALIGNED) {
+    float proj[3];
+    project_plane_v3_v3v3(proj, ob->obmat- [x], rv3d->viewinv[2]);
+    const float proj_length_sq = len_squared_v3(proj);
+    if (proj_length_sq > 1e-5f) {
+      return false;
+    }
+  }
+
   if (rv3d->is_persp) {
     return (visibility_flag & OB_EMPTY_IMAGE_HIDE_PERSPECTIVE) == 0;
   }
@@ -3028,15 +3038,6 @@ bool BKE_object_empty_image_data_is_visible_in_view3d(const Object *ob, const Re
     }
   }
 
-  if (visibility_flag & OB_EMPTY_IMAGE_HIDE_NON_AXIS_ALIGNED) {
-    float proj[3];
-    project_plane_v3_v3v3(proj, ob->obmat- [x], rv3d->viewinv[2]);
-    const float proj_length_sq = len_squared_v3(proj);
-    if (proj_length_sq > 1e-5f) {
-      return false;
-    }
-  }
-
   return true;
 }
 
I would also think these frames of empty images can get in the way. [and the way we present the `Display Only Axis Aligned` option in the UI would make me think these are working just like `Display Orthographic` & `Display Perspective` -- acting on both image and frame] Not sure if this would be considered a bug (probably not), but confirming for now and let @JacquesLucke or @ideasman42 decide. Not sure about a good solution regarding the opposing `Front` and `Back` issue [I think it is best to avoid another option here], but this would hide the frame for the `Display Only Axis Aligned` case: [P1207: T69967_snippet](https://archive.blender.org/developer/P1207.txt) ``` diff --git a/source/blender/blenkernel/intern/object.c b/source/blender/blenkernel/intern/object.c index 1378e862034..2fa9f3c95f9 100644 --- a/source/blender/blenkernel/intern/object.c +++ b/source/blender/blenkernel/intern/object.c @@ -2986,6 +2986,16 @@ void BKE_object_empty_draw_type_set(Object *ob, const int value) bool BKE_object_empty_image_frame_is_visible_in_view3d(const Object *ob, const RegionView3D *rv3d) { const char visibility_flag = ob->empty_image_visibility_flag; + + if (visibility_flag & OB_EMPTY_IMAGE_HIDE_NON_AXIS_ALIGNED) { + float proj[3]; + project_plane_v3_v3v3(proj, ob->obmat- [x], rv3d->viewinv[2]); + const float proj_length_sq = len_squared_v3(proj); + if (proj_length_sq > 1e-5f) { + return false; + } + } + if (rv3d->is_persp) { return (visibility_flag & OB_EMPTY_IMAGE_HIDE_PERSPECTIVE) == 0; } @@ -3028,15 +3038,6 @@ bool BKE_object_empty_image_data_is_visible_in_view3d(const Object *ob, const Re } } - if (visibility_flag & OB_EMPTY_IMAGE_HIDE_NON_AXIS_ALIGNED) { - float proj[3]; - project_plane_v3_v3v3(proj, ob->obmat- [x], rv3d->viewinv[2]); - const float proj_length_sq = len_squared_v3(proj); - if (proj_length_sq > 1e-5f) { - return false; - } - } - return true; } ```
Member

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

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

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
Campbell Barton self-assigned this 2020-01-15 16:18:13 +01:00

An issue with hiding the frame means these are hard to control/select.

We could hade some logic to hide the frame only when disable-selection is set, although this seems a bit arbitrary.

Closing since this is working as intended.

An issue with hiding the frame means these are hard to control/select. We could hade some logic to hide the frame only when disable-selection is set, although this seems a bit arbitrary. Closing since this is working as intended.
Author

In #69967#849899, @ideasman42 wrote:
An issue with hiding the frame means these are hard to control/select.

Closing since this is working as intended.

Sure ,this is not particularly a bug but should be a known issue and not just mark the report invalid.

And like what @lichtwerk have said it's getting in the way, so it's not arbitrary as the background images usabilty has changed and brought this problem.

We could hade some logic to hide the frame only when disable-selection is set, although this seems a bit arbitrary.

Yes, adding some logic to hide the frame only when disable-selection will solve it & make it similar to what we had in the 2.7.

> In #69967#849899, @ideasman42 wrote: > An issue with hiding the frame means these are hard to control/select. > > > Closing since this is working as intended. Sure ,this is not particularly a bug but should be a known issue and not just mark the report invalid. And like what @lichtwerk have said it's getting in the way, so it's not arbitrary as the background images usabilty has changed and brought this problem. > We could hade some logic to hide the frame only when disable-selection is set, although this seems a bit arbitrary. Yes, adding some logic to hide the frame only when disable-selection will solve it & make it similar to what we had in the 2.7.
Sign in to join this conversation.
No Label
Interest
Alembic
Interest
Animation & Rigging
Interest
Asset Browser
Interest
Asset Browser Project Overview
Interest
Audio
Interest
Automated Testing
Interest
Blender Asset Bundle
Interest
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
Interest
EEVEE & Viewport
Interest
Freestyle
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
ID Management
Interest
Images & Movies
Interest
Import Export
Interest
Line Art
Interest
Masking
Interest
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
Interest
Python API
Interest
Render & Cycles
Interest
Render Pipeline
Interest
Sculpt, Paint & Texture
Interest
Text Editor
Interest
Translations
Interest
Triaging
Interest
Undo
Interest
USD
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Interest
Video Sequencer
Interest
Virtual Reality
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
Module
Animation & Rigging
Module
Core
Module
Development Management
Module
EEVEE & Viewport
Module
Grease Pencil
Module
Modeling
Module
Nodes & Physics
Module
Pipeline, Assets & IO
Module
Platforms, Builds & Tests
Module
Python API
Module
Render & Cycles
Module
Sculpt, Paint & Texture
Module
Triaging
Module
User Interface
Module
VFX & Video
Platform
FreeBSD
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#69967
No description provided.