Revision 7e02d33 by Mike Erwin August 19, 2016, 04:52 (GMT) |
OpenGL: don't poll for errors, rely on KHR_debug Errors are caught & reported by our GL debug callback. This gives us way more useful information than sporadic calls to glGetError. I removed almost all use of glGetError, including our own GPU_ASSERT_NO_GL_ERRORS and GPU_CHECK_ERRORS_AROUND macros. Still used in rna_Image_gl_load because it passes unvalidated input to OpenGL functions. Still used in gpu_state_print_fl_ex as an exception handling hack -- will rewrite this soon. The optimism embodied by this commit will not prevent OpenGL errors. We need to analyze what would cause GL to fail at certain points and proactively intercept these failures. Or guarantee they can't happen. |
Revision 5f7611a by Kévin Dietrich August 19, 2016, 03:22 (GMT) |
Alembic: fix crash accessing invalid objects. |
Revision bf48750 by Kévin Dietrich August 19, 2016, 02:42 (GMT) |
Fix T49111: Automatically add file path suffix for Alembic and Collada export. This aligns the behaviour of the file selection with the other exporters. The Alembic case would fail if the filepath did not have an extension set. Also set a default file name for the Alembic export operator in case the Blender file was not saved before exporting. |
Revision 4d8ac1e by Julian Eisel August 18, 2016, 23:20 (GMT) |
Cleanup: Remove redundant comment |
Revision ca5271e by Sergey Sharybin August 18, 2016, 18:47 (GMT) |
Cycles: Fix wrong allocator used for spatial builder |
Revision f4e4009 by Bastien Montagne August 18, 2016, 14:18 (GMT) |
Cleanup: some bad sizeof() usages. |
Revision 2e6d427 by Bastien Montagne August 18, 2016, 14:06 (GMT) |
Cleanup/security fix: do not use strcpy (at least in new code). This function is only really secure in a very limited amount of cases, and can especially bite you later if you change some buffer sizes... So not worth bothering with it, just always use BLI_strncpy instead. |
Revision 7b4ba65 by Bastien Montagne August 18, 2016, 13:21 (GMT) |
Cleanup for previous commit (nasty IDE replacing tads with spaces, tsst) Sorry for the noise :| |
Revision b4d36c7 by Bastien Montagne August 18, 2016, 13:18 (GMT) |
Two fixes for optional ndof & fix bplayer for that... Seriuosly, guys... Please always check that kind of changes with and without affected option, and in full build case. |
Revision 7b78532 by Bastien Montagne August 18, 2016, 12:37 (GMT) |
Freestyle: fix wrong arg order, and cleanup confusing loop (both reported by coverity). Error: `origin` and `edge` args were swapped in final `FindOccludee()` call of `ViewMapBuilder::ComputeRayCastingVisibility()` Cleanup: main for loop in `Strip::createStrip()` was really confusing (though correct), generated a false positive in coverity scan, now should be cleaner how it loops over its vprev/v/v2 triplet of consecutive items. |
Revision 26f4f7e by Bastien Montagne August 18, 2016, 12:37 (GMT) |
Final UI messages fixes (for this session...). |
Revision 8a72ec8 by Thomas Beck August 18, 2016, 09:28 (GMT) |
Fix bplayer (c) after NDOF changes from merwin |
Revision 12c3002 by Sergey Sharybin August 18, 2016, 08:36 (GMT) |
Cleanup: ifdef function which is only used from ifdef-ed code |
Revision b10d005 by Mike Erwin August 18, 2016, 04:22 (GMT) |
NDOF: compile 3D mouse code only if WITH_INPUT_NDOF When WITH_INPUT_NDOF is disabled, 3D mouse handling code is removed from: - GHOST (was mostly done, finished the job) - window manager - various editors - RNA - keymaps The input tab of user prefs does not show 3D mouse settings. Key map editor does not show NDOF mappings. DNA does not change. On my Mac the compiled binary is 42KB smaller after this change. It runs fine WITH_INPUT_NDOF on or off. |
Revision a195dd1 by Mike Erwin August 18, 2016, 04:22 (GMT) |
NDOF: suppress buttons debug log Accidentally left this in the 3D mouse code. Mac only. |
Revision f92a6b8 by Brecht Van Lommel August 18, 2016, 00:24 (GMT) |
Fix compiler warning after fix for T48913. |
Revision e8b5e66 by Brecht Van Lommel August 18, 2016, 00:24 (GMT) |
Code cleanup to use array.data() rather than &array[0] (Now without the build errors) |
Revision 7baf93c by Mai Lavelle August 17, 2016, 22:49 (GMT) |
Revert "Code cleanup to use array.data() rather than &array[0]." This reverts commit 40b367479c6fe23d6f2b6d822f2d5266485619f3. Didn't build or solve any known issue. Please don't push changes without testing them first. |
Revision 40b3674 by Brecht Van Lommel August 17, 2016, 21:54 (GMT) |
Code cleanup to use array.data() rather than &array[0]. These latter can cause MSVC debug asserts if the array is empty. With C++11 we'll be able to do this for std::vector later. This hopefully fixes an assert in the Cycles subdivision code. |
Revision c0161a1 by Brecht Van Lommel August 17, 2016, 21:16 (GMT) |
Fix T48913: cycles viewport render stuck in loop due to non-unique dupli ID. |
|
|
|


Master Commits
MiikaHweb | 2003-2021