- User Since
- Mar 9 2013, 6:17 PM (319 w, 5 d)
@Brecht Van Lommel (brecht) we can keep this assigned to me for now. I have a bit of a triaging backlog now, so I don't know when I can get around to this.
I can not reproduce. You will have to come up with some better step to reproduce this issue.
This is not a bug. You are directly modifying the texture coordinated so they do not match the with automatically generated result. (This is also the case in 2.79)
I fail to see how the textures would not be distorted in this case.
Right, this is currently per design (and I agree that it is confusing).
Instead of all object losing their rigid bodies (T63576), the copies still have the settings but they do not animate.
You haven't really explained the issue in a way that makes this easy to reproduce and understand exactly what you are trying to describe.
At the moment you can only bind keys that have a ascii character: https://www.cs.cmu.edu/~pattis/15-1XX/common/handouts/ascii.html
@Richard Antalik (ISS) feel free to reassign if this is not for you.
I'm unsure if this is something that should be considered a regression. The behavior in 2.79 seems a bit buggy to as the animation resets on the start frame. So you haven't really "forzen" anything. The cache is just invalided it seems.
The image sequence is not packed. Could you provide it?
I can confirm that it seems like the reflection plane works in the viewport but not in the final render (Linux, AMD).
@Jeroen Bakker (jbakker) can you reproduce this?
As with the other report, I can't seem to reproduce this either. Is this also still an issue with the latest blender beta?
I can't reproduce this on my end. Does this still happen for you with the latest blender beta?
I can't reproduce this on my end with (Linux, AMD).
You do it with the Set Active Object as Camera shortcut (Ctrl Numpad 0)
@LazyDodo (LazyDodo) the open source nvidia drivers are not good (much to the fault of nvidia), so I'm not too surprised that is doesn't work.
@LazyDodo (LazyDodo) do you also have a Nvidia card? It works for me in the viewport textured view without these problems (linux, AMD).
@Bastien Montagne (mont29) anything we can do here?
@Sergey Sharybin (sergey) will other methods like the old one be available in the future?
I can't reproduce this on my end. I do not get any black borders. Is this still an issue for you with the latest build?
Thread 1 "blender" received signal SIGSEGV, Segmentation fault. 0x0000555557c84609 in psys_cache_vgroup (mesh=0x0, psys=0x7fffd55e1008, vgroup=2) at /home/zed/prog/blender/source/blender/blenkernel/intern/particle.c:2203 2203 MDeformVert *dvert = mesh->dvert; (gdb) bt #0 0x0000555557c84609 in psys_cache_vgroup (mesh=0x0, psys=0x7fffd55e1008, vgroup=2) at /home/zed/prog/blender/source/blender/blenkernel/intern/particle.c:2203 #1 0x0000555557c84e6a in psys_thread_context_init_path (ctx=0x7fffffffce80, sim=0x7fffffffd090, scene=0x7fffcd350008, cfra=1, editupdate=true, use_render_params=false) at /home/zed/prog/blender/source/blender/blenkernel/intern/particle.c:2345 #2 0x0000555557c867cc in psys_cache_child_paths (sim=0x7fffffffd090, cfra=1, editupdate=true, use_render_params=false) at /home/zed/prog/blender/source/blender/blenkernel/intern/particle.c:2757 #3 0x0000555557c88c30 in psys_cache_edit_paths (depsgraph=0x7fffcde2b408, scene=0x7fffcd350008, ob=0x7fffd58ad608, edit=0x7fffd27e0708, cfra=1, use_render_params=false) at /home/zed/prog/blender/source/blender/blenkernel/intern/particle.c:3333 #4 0x0000555558ac290e in PE_update_object (depsgraph=0x7fffcde2b408, scene=0x7fffcd350008, ob=0x7fffd58ad608, useflag=0) at /home/zed/prog/blender/source/blender/editors/physics/particle_edit.c:1612 #5 0x000055555873eef8 in drw_particle_update_ptcache_edit (object_eval=0x7fffd58b0608, psys=0x7fffd50dfa08, edit=0x7fffd27e0708) at /home/zed/prog/blender/source/blender/draw/intern/draw_cache_impl_particles.c:1398 #6 0x000055555873effe in drw_particle_update_ptcache (object_eval=0x7fffd58b0608, psys=0x7fffd50dfa08) at /home/zed/prog/blender/source/blender/draw/intern/draw_cache_impl_particles.c:1422 #7 0x000055555873fbaa in particles_ensure_procedural_data (object=0x7fffd58b0608, psys=0x7fffd50dfa08, md=0x7fffe89fa4c8, r_hair_cache=0x7fffffffd300, subdiv=0, thickness_res=2) at /home/zed/prog/blender/source/blender/draw/intern/draw_cache_impl_particles.c:1646 #8 0x000055555874631e in drw_shgroup_create_hair_procedural_ex (object=0x7fffd58b0608, psys=0x7fffd50dfa08, md=0x7fffe89fa4c8, hair_pass=0x7fffcdff1080, gpu_mat=0x0, gpu_shader=0x7fffd56dec18) at /home/zed/prog/blender/source/blender/draw/intern/draw_hair.c:138 #9 0x0000555558746993 in DRW_shgroup_hair_create (object=0x7fffd58b0608, psys=0x7fffd50dfa08, md=0x7fffe89fa4c8, hair_pass=0x7fffcdff1080, shader=0x7fffd56dec18) at /home/zed/prog/blender/source/blender/draw/intern/draw_hair.c:235 #10 0x00005555586dc223 in workbench_cache_populate_particles (vedata=0x7fffd583cd08, ob=0x7fffd58b0608) at /home/zed/prog/blender/source/blender/draw/engines/workbench/workbench_deferred.c:890 #11 0x00005555586dc391 in workbench_deferred_solid_cache_populate (vedata=0x7fffd583cd08, ob=0x7fffd58b0608) at /home/zed/prog/blender/source/blender/draw/engines/workbench/workbench_deferred.c:916 #12 0x00005555586d8da3 in workbench_solid_cache_populate (vedata=0x7fffd583cd08, ob=0x7fffd58b0608) at /home/zed/prog/blender/source/blender/draw/engines/workbench/solid_mode.c:52 #13 0x000055555868659e in drw_engines_cache_populate (ob=0x7fffd58b0608) at /home/zed/prog/blender/source/blender/draw/intern/draw_manager.c:1095 #14 0x00005555586877fe in DRW_draw_render_loop_ex (depsgraph=0x7fffcde2b408, engine_type=0x55555e02a680 <DRW_engine_viewport_eevee_type>, ar=0x7fffcdecdf08, v3d=0x7fffd5551f08, viewport=0x7fffc93fc168, evil_C=0x7fffeec58188) at /home/zed/prog/blender/source/blender/draw/intern/draw_manager.c:1569 #15 0x00005555586873ee in DRW_draw_view (C=0x7fffeec58188) at /home/zed/prog/blender/source/blender/draw/intern/draw_manager.c:1490 #16 0x0000555558bc9e37 in view3d_draw_view (C=0x7fffeec58188, ar=0x7fffcdecdf08) at /home/zed/prog/blender/source/blender/editors/space_view3d/view3d_draw.c:1431 #17 0x0000555558bc9ee7 in view3d_main_region_draw (C=0x7fffeec58188, ar=0x7fffcdecdf08) at /home/zed/prog/blender/source/blender/editors/space_view3d/view3d_draw.c:1452 #18 0x0000555558c93dc4 in ED_region_do_draw (C=0x7fffeec58188, ar=0x7fffcdecdf08) at /home/zed/prog/blender/source/blender/editors/screen/area.c:558 #19 0x00005555582166d4 in wm_draw_window_offscreen (C=0x7fffeec58188, win=0x7fffd27e3888, stereo=false) at /home/zed/prog/blender/source/blender/windowmanager/intern/wm_draw.c:596 #20 0x0000555558216c52 in wm_draw_window (C=0x7fffeec58188, win=0x7fffd27e3888) at /home/zed/prog/blender/source/blender/windowmanager/intern/wm_draw.c:732 #21 0x000055555821715e in wm_draw_update (C=0x7fffeec58188) at /home/zed/prog/blender/source/blender/windowmanager/intern/wm_draw.c:895 #22 0x0000555558213108 in WM_main (C=0x7fffeec58188) at /home/zed/prog/blender/source/blender/windowmanager/intern/wm.c:424 #23 0x0000555557b802c4 in main (argc=1, argv=0x7fffffffe098) at /home/zed/prog/blender/source/creator/creator.c:500
BLI_assert failed: /home/zed/prog/blender/source/blender/bmesh/tools/bmesh_intersect.c:1265, BM_mesh_intersect(), at '(_splice_ls_index) + (1) <= _splice_ls_totalloc'
@Campbell Barton (campbellbarton) any input on this?
This is because you have the plane object set as camera:
This setup creates a dependency cycle (you can see it in the output terminal window). We do not support cycles like these currently.
It seems to work fine with eevee so I guessing this might be a cycles issue.
@Brecht Van Lommel (brecht) who to assign this to?
@Brecht Van Lommel (brecht) I think we already had a report for issues like this? I can't find it now though...
Right, we do not support circular drivers like these.
This works in 2.79 (git), so I guess this is some deps problem perhaps.
@Brecht Van Lommel (brecht) I guess that the UV code has to be updated to take all objects in to account when using multi edit. Now at least the display seems to be isolated to the geometry if each individual object.
@Clément Foucault (fclem) I'm unsure if this is a render issue or a data update issue. I mean the object moves and is rendered but the shadows doesn't update. So feel free to reassign if this is not for you.
This should have been fixed a while ago with rB01a8216a4bc8968a108eec5fc50436f4a6ed02a9, but it seems like the issue is back now. I don't have any network drives to reproduce this with.
Can't reproduce this on linux either.
@Campbell Barton (campbellbarton) I can confirm that the toolbar tools stops working when I enable 3 button mouse emulation. Does the toolbar need to be reinitialized or something?
@Alexander Gavrilov (angavrilov) I'll go ahead and assign this to you as you have already posted a patch.
Sat, Apr 20
Fri, Apr 19
I can not reproduce this crash. Could you try the latest blender beta and see if it is fixed there? Additionally try installing the latest nvidia drivers.
I can reproduce this now, thanks @Stefano Bonicatti (smjert) !
The sample file from T63721:
@Dalai Felinto (dfelinto) yes? Is that not what this report is asking for too?
You are not using the official Nvidia drivers, we only support the official drivers. You should also probably use a newer ubuntu version.
@Brecht Van Lommel (brecht) can you reproduce this?
@Campbell Barton (campbellbarton) do we support this?
@Yu-sion (Yu-sion) It is not that hard: https://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git
Seems like a lot of people has issues now, so I'll raise the priority.
Your OSX version is too old. Can you try to update to the latest OSX release (Mojave)?
I'm guessing this might be color management related?
I'll go ahead and merge this in as the problem seems to be the same
@Pablo Vazquez (pablovazquez) can you reproduce this on your end?
I can confirm your observations on my end too. Thanks for the very thorough report.
@Philipp Oeser (lichtwerk) what do you think?
@Yu-sion (Yu-sion) are you able to build blender by yourself by any chance? If so you could try to git bisect search and find the commit that broke this for you.
@Adam (Adamsuper) are you using the latest drivers for your card?