71cdb55953
After spending way too much time looking into the image handle code because I assumed the issue is some interaction between OSL code using a texture and the image system that's in SVM mode (which never happened before the custom camera) with printf debuggine because OptiX doesn't work in debug builds, it turns out the issue was something else entirely: C++ iterator bullshit. Specifically, when we remove an entry from services->textures, this invalidates the iterator, so the code restarts from the beginning. However, the for-loop still increments the iterator *before* checking the termination criterion. If we remove the only element of the map, we: - Set it = map.begin(), which equals map.end() since it's empty now - Increment it at the end of the loop iteration - Compare it == map.end(), which is wrong now since we're past the end No idea how this didn't blow up sooner, none of this seems camera-specific?? Anyways, the fix is simple - only increment if we didn't restart. Pull Request: https://projects.blender.org/blender/blender/pulls/141580
Blender
Blender is the free and open source 3D creation suite. It supports the entirety of the 3D pipeline—modeling, rigging, animation, simulation, rendering, compositing, motion tracking and video editing.
Project Pages
Development
License
Blender as a whole is licensed under the GNU General Public License, Version 3. Individual files may have a different but compatible license.
See blender.org/about/license for details.