Blender Git Statistics -> Developers -> muxed-reality
Peter Kim (muxed-reality)
Total Commits : 298
Master Commits : 40
Branch Commits : 258
First Commit : October 13, 2020
Latest Commit : December 9, 2021
Commits by Month
Date | Number of Commits | |
---|---|---|
December, 2021 | 1 | |
November, 2021 | 0 | |
October, 2021 | 17 | |
September, 2021 | 11 | |
August, 2021 | 54 | |
July, 2021 | 43 | |
June, 2021 | 25 | |
May, 2021 | 25 | |
April, 2021 | 4 | |
March, 2021 | 10 | |
February, 2021 | 5 | |
January, 2021 | 7 | |
December, 2020 | 1 | |
November, 2020 | 52 | |
October, 2020 | 43 |
Commit Distribution
Path | Number of Commits |
---|---|
xr-controller-support | 246 |
xr-actions-D9124 | 119 |
master | 40 |
temp-lineart-contained | 8 |
lineart-shadow | 8 |
soc-2021-porting-modifiers-to-nodes_all | 4 |
soc-2021-porting-modifiers-to-nodes-decimate | 4 |
Favourite Files
Filename | Total Edits |
---|---|
wm_xr_session.c | 97 |
wm_xr_intern.h | 68 |
rna_xr.c | 66 |
WM_api.h | 46 |
GHOST_XRSession.cpp | 43 |
wm_xr_draw.c | 41 |
wm_xr_operators.c | 41 |
wm_event_system.c | 28 |
DNA_xr_types.h | 26 |
GHOST_XrSession.h | 25 |
File Changes
Action | Total | Per Commit |
---|---|---|
Added | 37 | 0.1 |
Modified | 1 029 | 3.5 |
Deleted | 12 | 0.0 |
Code Changes
Action | Total | Per Commit |
---|---|---|
Lines Added | 14 664 | 70.2 |
Lines Removed | 7 405 | 35.4 |
Latest commits
December 9, 2021, 07:29 (GMT) |
Fix incorrect copying of XR action map items After using MEM_dupallocN() on the original item, the bindings ListBase for the new item needs to be cleared and each binding copied separately. |
October 26, 2021, 06:05 (GMT) |
Cleanup: Remove unused parameter |
October 26, 2021, 04:42 (GMT) |
Cleanup: Improve description for XR absolute tracking |
October 26, 2021, 04:41 (GMT) |
XR: Only show ref space warnings in debug-xr mode This avoids spamming the console for users who have not set up a tracking space/boundary for their headsets. |
October 26, 2021, 04:38 (GMT) |
XR: Fix potential crash when toggling session |
October 26, 2021, 04:37 (GMT) |
XR: Versioning for session draw flags, base scale |
October 26, 2021, 04:35 (GMT) |
XR: View adjustments for variable viewer scale This adjusts some calculations and visibility flags for XR viewports in order to account for a possible scale factor in the XR view matrix. This scale factor can be introduced via the XR session settings base scale, which allows a viewer to begin their session at a specific reference scale, or the XR session state navigation scale, which allows a viewer to adjust their scale relative to the reference scale during the session. Reviewed by Severin as part of D11501, but requested to be committed separately. |
October 26, 2021, 04:34 (GMT) |
XR Controller Support Step 5: Navigation Adds navigation transforms (pose, scale) to the XR session state that will be applied to the viewer/controller poses. By manipulating these values, a viewer can move through the VR viewport without the need to physically walk through it. Add-ons can access these transforms via Python (XrSessionState.navigation_location/rotation/scale) to use with custom operators. Also adds 3 new VR navigation operators that will be exposed to users as default actions in the VR Scene Inspection add-on. While all three of these operators have custom properties that can greatly influence their behaviors, for now these properties will not be accessible by users from the UI. However, other add-ons can still set these custom properties if they desire. 1). Raycast-based teleport Moves the user to a location pointed at on a mesh object. The result can optionally be constrained to specific axes, for example to achieve "elevation snapping" behavior by constraining to the Z-axis. In addition, one can specify an interpolation factor and offset. Credit to KISKA for the elevation snapping concept. 2). "Grab" navigation Moves the user through the viewport by pressing inputs on one or two held controllers and applying deltas to the navigation matrix based on the displacement of these controllers. When inputs on both controllers are pressed at the same time (bimanual interaction), the user can scale themselves relative to the scene based on the distance between the controllers. Also supports locks for location, rotation, and scale. 3). Fly navigation Navigates the viewport by pressing a button and moving/turning relative to navigation space or the VR viewer or controller. Via the operator's properties, one can select from a variety of these modes as well as specify the min/max speed and whether to lock elevation. Reviewed By: Severin Differential Revision: https://developer.blender.org/D11501 |
October 13, 2021, 11:56 (GMT) |
October 12, 2021, 07:36 (GMT) |
Fix build error due to conflicting types |
MiikaHweb - Blender Git Statistics v1.06