Doorway and Knobs update, general cleanup/standardization, still much more to do.
I feel like this should be handled in KX_Scene::NewRemoveObject(), but then I don't think we'll properly handle physics. So, this approach is probably fine.
Good catch, LGTM (both changes)
Add deprecated messages.
It would be nice to get @campbellbarton's thoughts on the error handling (the user-friendliness of the error message and consistency with other error reporting). If we don't get a review from Campbell in a reasonable time (a week?) then I think this is still okay to commit.
Thanks for the report, fixed now.
Closed by commit rBc641a5563fa0.
Nobody with OS X can't reproduce this?
Closed by commit rB1d0f1a1ec9c0.
There's also some refresh issues, but that's for T43818 to solve.
It stop working exactly as the object dimensions become bigger than 100, I'll remove that arbitrary limit.
I think that a feature like this would be better than making two or more renderlayers and compositing just because two render layers mean two different renders in a row, which means more time. I don't know how blender works under the hood, I imagined that with material override there's some "switch material" at the end for every object, so I thought that it would be easy to just mark some objects to be excluded from this switch.