Timeline for How to find all objects in the Camera's view with Python?
Current License: CC BY-SA 4.0
23 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2021 at 2:50 | comment | added | S. Magnusson | I updated the script to better handle intersections more accurately outside the frustrum: blender.stackexchange.com/questions/104989/… | |
| Jul 21, 2020 at 15:19 | history | edited | batFINGER | CC BY-SA 4.0 |
Took liberty to update for 2.8
|
| Jul 10, 2020 at 1:16 | comment | added | ideasman42 | Updated the multiplication for 2.8. | |
| Jan 11, 2020 at 2:16 | history | edited | ideasman42 | CC BY-SA 4.0 |
Update for 2.8
|
| Jan 10, 2020 at 21:00 | comment | added | satishgoda | @ideasman42 Worked well. Although for Blender 2.8 I had to change '*' to '@' for multiplying Matrix and Vector types. | |
| Aug 29, 2019 at 13:37 | history | edited | ideasman42 | CC BY-SA 4.0 |
edited body
|
| Mar 2, 2018 at 0:29 | comment | added | ideasman42 | What do you mean by "20% in the camera view" ? | |
| Mar 1, 2018 at 16:54 | comment | added | Moritz Hinderer | @ideasman42 how can I modify your code, so it only selects an Object when it is for at least for example 20% in the camera view? I couldn't figure it out... | |
| Nov 7, 2017 at 7:42 | vote | accept | nantille | ||
| Jan 23, 2016 at 6:39 | history | edited | ideasman42 | CC BY-SA 3.0 |
deleted 36 characters in body
|
| Jan 23, 2016 at 1:27 | comment | added | ideasman42 |
There was an error in clip_segment_in_planes, now fixed.
|
|
| Jan 23, 2016 at 1:26 | history | edited | ideasman42 | CC BY-SA 3.0 |
deleted 44 characters in body
|
| Jan 21, 2016 at 13:24 | comment | added | nantille | very cool answers both of you, I'll try all this between today and tomorrow, thank you ! | |
| Jan 21, 2016 at 12:06 | comment | added | o.g. | ok, they are not the same and it may be better to clearly check by planes. As for padding, op stated that "he will not mesh the curves" unless in view, so we can assume the bbox goes only for the naked spline. - Thus the need for padding bbox or camera planes (probably simpler) to compensate for a "future" mesh, slightly larger than the initila bbox. | |
| Jan 21, 2016 at 11:43 | comment | added | ideasman42 | 1) its just a different way to test - using planes instead of projection, wouldn't say its the same though. 2) As for padding the bound-box, curve bevel is taken into account, but perhaps render subdivision levels change the bound-box slightly - so you may want to do this, it depends on your exact use case - YMMV. | |
| Jan 21, 2016 at 11:04 | comment | added | o.g. |
2 questions: 1. isn't this what basically bpy_extras.object_utils.world_to_camera_view is giving as a factor (0-1 inside screen)? and 2. the bbox should be a bit larger (with a tolerance or so) so that it considers the result with bevel radius? or is that already there ?
|
|
| Jan 21, 2016 at 10:47 | history | edited | ideasman42 | CC BY-SA 3.0 |
added 320 characters in body
|
| Jan 21, 2016 at 5:59 | history | edited | ideasman42 | CC BY-SA 3.0 |
added 97 characters in body
|
| Jan 21, 2016 at 5:51 | history | edited | ideasman42 | CC BY-SA 3.0 |
added 97 characters in body
|
| Jan 21, 2016 at 5:12 | history | edited | ideasman42 | CC BY-SA 3.0 |
added 38 characters in body
|
| Jan 21, 2016 at 4:33 | history | edited | ideasman42 | CC BY-SA 3.0 |
added 16 characters in body
|
| Jan 21, 2016 at 4:27 | history | edited | ideasman42 | CC BY-SA 3.0 |
added 46 characters in body
|
| Jan 21, 2016 at 4:22 | history | answered | ideasman42 | CC BY-SA 3.0 |