2 ms·
Because not everyone doing 3D graphics is implementing AAA rendering engines on RTX cards. The ANARI effort was born exactly because the visualisation industry
by pjmlp 1y ago
Because not everyone doing 3D graphics is implementing AAA rendering engines on RTX cards.
The ANARI effort was born exactly because the visualisation industry refusal to adopt Vulkan as is.
- flohofwoe 1y agoLooking at the ANARI spec and SDK it looks pretty much like a typical C API to me, implementing an old-school scene-graph system. What am I missing - e.g. what makes it specifically well suited for non-C languages? :) If anything it looks more like an admission by Khronos that Vulkan wasn't such a great idea (but a 3D API that's based on scene graphs isn't either, so I'm not sure what's so great about ANARI tbh).
- pjmlp 1y agoPython is part of ANARI value proposal, and the standard takes this into account. https://github.com/KhronosGroup/ANARI-SDK/tree/next_release/examples/python https://github.com/KhronosGroup/ANARI-SDK/tree/next_release/...
- fulafel 1y agoAt first blush it looks like it supports writing C in Python more than going along the grain of the managed nature: status_handle = ffi.new_handle(anari_status) #something needs to keep this handle alive (from https://github.com/KhronosGroup/ANARI-SDK/blob/next_release/examples/python/anari_tutorial.py#L48 https://github.com/KhronosGroup/ANARI-SDK/blob/next_release/...)