- User Since
- Mar 27 2019, 2:43 PM (82 w, 2 d)
Thu, Oct 22
Fixed some typo, formatting and coefficients explanation.
Wed, Oct 21
For example, distortion model does not exist on its own. It is highly coupled to a specific camera and its configuration used when shooting a footage. Currently such coupling exists in the Movie Clip datablock, with tools to estimate the distortion model done in Movie Clip Editor.
From this point of view, it seems logical to build a workflow based on use of movie clip datablocks. This solves the problem of non-reusable parameters stored in brush datablock, and solves problem of adding parameters to camera which are only usable by painting.
How from artists, matte painter, or accets creator point of view images that use camera view as a projection (we can name them Projector Projection that is more like a Light with color gel on it) images are related to Movie Clip? Or you only about datablocks, not about UX?
Tue, Oct 20
Can you clarify this point? @Ivan Perevala (ivpe) definitely can’t make own decision on final design. And If you know any plans in upcoming changes in this module please share them to Ivan.
If someone already working on refactoring this area in Blender and that code can interfere with that refactoring, we definitely need to bear in mind that upcoming changes to make this work usable in them too.
But if there is no plans for near future, and no Blender foundation coder[s] assigned to that tasks, Ivan as independent coder can only add new feature with maximal compatibility with existing code and current blender user experience.
Also sorry, English is not native for us, and ultimate word “decision” just mean, opinion that such way is more usable. :)
Mon, Oct 19
@Brecht Van Lommel (brecht)
Definitely for this moment camera projection is not so usable without preview.
And @Ivan Perevala (ivpe) have this Milestone 3 Preview.
Only issue that Camera Projection can be used without preview. But have preview without camera projection implemented have no reason. So this is only matter of priority.
And for this moment when code for camera projection is working, and we can brush up UX for this tool.
Fri, Oct 16
Thu, Oct 15
Wed, Oct 14
Tue, Oct 13
Wed, Oct 7
Tue, Oct 6
Wed, Sep 30
Tue, Sep 29
Sat, Sep 26
Jul 7 2020
Apr 29 2020
Apr 14 2020
Have same issue in Eevee, and had some reports from 3D scannig studios about limited ability of Blender working with Geo referenced data.
Definitely Blender lack of float precision.
Feb 27 2020
Same situation. Blender not crashing on debug mode. But only on normal.
Here is a logs. But without crashes, in case they can be useful.
Not fixed for 2/4x GTX1080ti
Operating system: Windows-10-10.0.18362-SP0 64 Bits
Graphics card: GeForce GTX 1080 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 442.19
Feb 26 2020
Nov 25 2019
Sorry, but is it possible speedup patch review? With old Preferences dialogue and old open window their position was not so important. But in 2.81/2.82 modal window is default and always adjusting their size highly impact workflow speed.
Nov 1 2019
2.8/2.81/2.82 crashing still not fixed
Oct 31 2019
Error happening on 64Gb and 128Gb RAM.
FBX and PLY same 33000000 poly open without problem.
Oct 25 2019
Please do not forget about UV projection mapping! How it will working with UDIM meshes.
Sep 30 2019
Sep 12 2019
Sep 5 2019
Let me add some notes, to may be rise priority a bit.
Aug 29 2019
Aug 28 2019
Aug 27 2019
Jul 11 2019
Crashes happen only with PNG and 16bit.
Create empty project.
Create in any paint app (photoshop, krita, gimp, etc.)
16384x16384px image in 16bit.
Fill with anything, like noise or gradinet.
Save as PNG in any compression.
Add material and use node.
Attach Texture to Color. And load this PNG.
Switch to Look dev or Eeevee.
Done. Blender crashed.
Mar 28 2019
Can confirm that monitors should be connected to different video cards.
And using only one GPU to render opengl fix this issue.