August 14, 2020, 15:57 (GMT) |
Fix warning when compiling on Linux with WITH_XR_OPENXR enabled |
August 14, 2020, 15:52 (GMT) |
Merge branch 'master' into soc-2020-outliner |
August 14, 2020, 15:18 (GMT) |
Merge branch 'blender-v2.90-release' |
August 14, 2020, 15:03 (GMT) |
Fix constant lighting change in VR view when rotating head We have to explicitly enable fixed world space lighting. This was in fact already done, but overridden by the code to sync the 3D View shading settings to the VR view. |
August 14, 2020, 15:03 (GMT) |
Fix undefined behavior with --debug-xr Mistake in cb578ca1048d3. Before that, the extension vector was static, to make sure the extension name strings wouldn't get destructed when leaving the function. I didn't think that was an issue and couldn't recreate one, because until the previous commit we wouldn't actually add any extensions to the vector on Windows (the system I tested with). Use C++17's `std::string_view` now, which avoids the string copies `std::string` creates for itself and thus its destruction when leaving the local scope. |
August 14, 2020, 15:03 (GMT) |
Fix --debug-xr not outputting OpenXR debug prints on Windows The OpenXR debug extension was disabled on Windows as a workaround. This was an old leftover from when there was only the Windows Mixed Reality runtime on Windows. The debug extension didn't work for it and we didn't have a way to disable it just for Windows Mixed Reality. Now it seems to work though, so we remove the workaround. If specific runtimes still have trouble with the extension, we can disable it specifically for these runtimes now. |
August 14, 2020, 14:49 (GMT) |
Fix NULL pointer access in render engine reported by address sanitizer This may not have caused an actual bug. |
August 14, 2020, 14:49 (GMT) |
August 14, 2020, 14:00 (GMT) |
Merge branch 'blender-v2.90-release' |
August 14, 2020, 14:00 (GMT) |
Fix/workaround graphics issues breaking SteamVR use with Blender Windows only workaround. I'll have to investigate Linux separately. Steam's OpenGL compatibility is still new and doesn't work for us yet (neither does it for standard OpenXR examples from what I've heard and seen myself). We can work around that by falling back to our DirectX compatibility layer. Note that this DirectX compatibility still doesn't work for some systems, see T76082. Implementation note: Since the graphics binding extensions have to be enabled before we can find out which runtime is in use (e.g. SteamVR vs. Oculus, etc), we can now enable multiple graphics binding extensions but settle for a single one to use later. Once the SteamVR OpenGL backend works, we can remove this workaround again. Fixes T78267. |
August 14, 2020, 13:36 (GMT) |
Fix: BKE_reports_move moves only one report |
August 14, 2020, 13:35 (GMT) |
Cleanup: else after return |
August 14, 2020, 13:07 (GMT) |
Merge branch 'greasepencil-edit-curve' into soc-2020-greasepencil-curve |
August 14, 2020, 12:59 (GMT) |
Fix log formatting Use new line was checked incorrectly |
August 14, 2020, 11:29 (GMT) |
Merge branch 'blender-v2.90-release' |
August 14, 2020, 11:27 (GMT) |
Fix refactor report: missed flag |
August 14, 2020, 11:27 (GMT) |
Fix offset applied on top of VR landmark with no positional tracking On VR session start with positional tracking disabled, the pose would have an offset applied but it was supposed to start exactly at the landmark position. Issue is that we applied the offset to cancel out the position offset reported by the OpenXR runtime incorrectly. We only want to do that if positional tracking is enabled, because if not we don't even apply the runtime's position offset. So we'd cancel something out that wasn't there. |
August 14, 2020, 11:16 (GMT) |
BLI: add reverse iterators, iterator constructor and Vector.insert/prepend The new reverse iterators behave as the reverse iterators for contains from the standard library. Have a look at the tests to see how to use them. Using them will hopefully become easier with ranges in C++20. A Vector can now be constructed from two iterators, which is very common in the standard library. New Vector.insert methods allow adding elements in the middle of a vector. These methods should not be used often in practice, because they has a linear running time. New Vector.prepend methods allow adding elements to the beginning of a vector. These methods are O(n) as well. |
Revision 2eaf5ec by YimingWu (lanpr-under-gp, lineart-bvh, lineart-shadow, temp-lineart-contained, temp_lineart_contained) August 14, 2020, 11:10 (GMT) |
LineArt: Prevent lines showing inside text object surface, disable crease. |
August 14, 2020, 10:37 (GMT) |
Cleanup: C++ code style for Ghost-XR * Avoid deep copy of vectors (technically more than a cleanup). * Use `std::make_unique` for allocating unique pointers, rather than manual `new`. * Use `std::optional` for optional by-value return values, rather than C-style `bool` to indicate success + return-argument. * Use references rather than pointers for non-optional arguments. * Avoid manual `new`/`delete`. Use `std::unique_ptr` for local scope bound lifetime. * Use C++ `nullptr` rather than C's `NULL`. * Remove unnecessary friend declaration. These changes are generally considered good practise and move us more to a "modern C++" style. We can still go much further of course. See https://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines. |
|
|
|


Master Commits
MiikaHweb | 2003-2021