Tue, Feb 7
thanks for the report, but there is no bug here, it does *move* the sub-collection from on scene collection to another (view layers have nothing to do here, this tool is handling collections, not layer collections)... If you want to link it, use ctrl-drag, as the tooltip says.
Think this is because in the UV Editor, faces are actually selected by their center dot (unlike the 3D View).
@Chris Blackbourn (chrisbblend) : can you confirm?
Thank you, I have searched and could not locate it, sorry, my mistakes. You can close this task.
Hmmm… it may be even intended to leave ability to move collection from one scene to another. But the way is not intuitive.
I would prefer linking with sinple drag but moving with modifier key. Just because moving acts with additional «agent» — original scene.
Also when I have 2 scenes with same collection, the drag to new scene will not unlink collection from prevoius two.
Or i can`t reproduce bug. Sometimes bug will not appear with 2 collections…
Is there anyone of the devs able to solve this bug? https://developer.blender.org/T104008
Cant repro either
if you open the same scene i uploaded, it also happens in 3.3.3, so, it's the datablock that's broken, not the blender version.
in 3.3.3 what's broken is that if you delete a root point of a nurbs spline, the spline permanently turns into a poly spline and there's no turning back even if you convert the curve type to bezier or rebuild the segment.
i reported that issue in 3.3.0 and as far as i know it had a regression to a different datablock version, the dev back then told me it would stay as a regression because splines got broken in 3.3.0, but the issue was marked as fixed.
strangely enough, it doesn't happen in 3.4.1, so i can't connect if it is related. but shortly, yes, it works in 3.3.3.
opening that file in 3.4.1 results in zero extrusion depth and zero roundness despite having large numbers in both number fields.
here's 3.3.3 with the exact same logo as a nurbs curve, with an extrusion value and depth in roundness, with the 3.3.3 splash screen and the 3.3.3 version in the status bar.
As far as I can tell this does not work in Blender 3.3.3 can you confirm the version of Blender this worked?
Thanks, committed.
I made a slightly different fix in rBM9947
I suspect this is related to T103556: Regression: Cycles viewport pixels change if the UI is updated in a certain way.
Can you share .blend file?
Thanks for the review. I'll try to finish this in coming weeks. Will let you know if I stuck with any issue
I am not sure what you mean, everything seems to work for me:
This is the expected behaviour. As an object gets smaller, and further away from the origin, artifacts start to occur known as floating point rendering errors.
Hi, thanks for the report. This likely to appear due to clipping values. Increasing clip start value might fix the issue: https://docs.blender.org/manual/en/latest/troubleshooting/3d_view.html#depth-buffer-glitches
Can you check? Upload .blend file if that doesn't fix the issue
@Alice Cecile (alice_i_cecile), can you check again in fresh 3.5 build: https://builder.blender.org/download/daily/
What is likely happening is the center of the view-port is shifting while you're navigating.
I'm just finding out about this change now, and I know it has been committed already, but this feature was not obsolete.
In debug build I get crash with LMB.
@Iliya Katueshenock (Moder), do you use Right mouse select?
> blender.exe!BLI_listbase_count(const ListBase * listbase) Line 527 C++ blender.exe!DRW_view_data_create(ListBase * engine_types) Line 58 C++ blender.exe!DRW_viewport_data_create() Line 402 C blender.exe!drw_manager_init(DRWManager * dst, GPUViewport * viewport, const int * size) Line 536 C blender.exe!DRW_draw_select_loop(Depsgraph * depsgraph, ARegion * region, View3D * v3d, bool use_obedit_skip, bool draw_surface, bool UNUSED_use_nearest, const bool do_material_sub_selection, const rcti * rect, bool(*)(eDRWSelectStage, void *) select_pass_fn, void * select_pass_user_data, bool(*)(Object *, void *) object_filter_fn, void * object_filter_user_data) Line 2453 C blender.exe!view3d_opengl_select_ex(ViewContext * vc, GPUSelectResult * buffer, unsigned int buffer_len, const rcti * input, eV3DSelectMode select_mode, eV3DSelectObjectFilter select_filter, const bool do_material_slot_selection) Line 734 C blender.exe!mixed_bones_object_selectbuffer(ViewContext * vc, GPUSelectResult * buffer, const int buffer_len, const int * mval, eV3DSelectObjectFilter select_filter, bool do_nearest, bool do_nearest_xray_if_supported, const bool do_material_slot_selection) Line 2019 C++ blender.exe!mixed_bones_object_selectbuffer_extended(ViewContext * vc, GPUSelectResult * buffer, const int buffer_len, const int * mval, eV3DSelectObjectFilter select_filter, bool use_cycle, bool enumerate, bool * r_do_nearest) Line 2117 C++ blender.exe!ed_object_select_pick(bContext * C, const int * mval, const SelectPick_Params * params, const bool center, const bool enumerate, const bool object_only) Line 2551 C++ blender.exe!view3d_select_exec(bContext * C, wmOperator * op) Line 3061 C++ blender.exe!view3d_select_invoke(bContext * C, wmOperator * op, const wmEvent * event) Line 3080 C++ blender.exe!wm_operator_invoke(bContext * C, wmOperatorType * ot, const wmEvent * event, PointerRNA * properties, ReportList * reports, const bool poll_only, bool use_last_properties) Line 1519 C++ blender.exe!wm_handler_operator_call(bContext * C, ListBase * handlers, wmEventHandler * handler_base, wmEvent * event, PointerRNA * properties, const char * kmi_idname) Line 2553 C++ blender.exe!wm_handlers_do_keymap_with_keymap_handler(bContext * C, wmEvent * event, ListBase * handlers, wmEventHandler_Keymap * handler, wmKeyMap * keymap, const bool do_debug_handler) Line 2947 C++ blender.exe!wm_handlers_do_intern(bContext * C, wmWindow * win, wmEvent * event, ListBase * handlers) Line 3276 C++ blender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Line 3531 C++ blender.exe!wm_event_do_region_handlers(bContext * C, wmEvent * event, ARegion * region) Line 3833 C++ blender.exe!wm_event_do_handlers_area_regions(bContext * C, wmEvent * event, ScrArea * area) Line 3865 C++ blender.exe!wm_event_do_handlers(bContext * C) Line 4064 C++ blender.exe!WM_main(bContext * C) Line 644 C blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Line 589 C
3.5
Hi, thanks for the report. I can confirm.
Likely caused by rB19b63b932d2b: Fix transform gizmo not updating according to state
@Germano Cavalcante (mano-wii) ^
Hi, thanks for the report. Unfortunately the scenario described is too time consuming for us to track down.
This appears to be an issue particularly in your system. I'd suggest you to update Windows, touchpad drivers, etc.
Sure I will do upload youtube. Take a few days to show about crash or not.
Bake All take a longest processing no problem.
Looks good to me!
Panel Used By
| Dashboard | Restricted Dashboard |


