While working on some texturing, I decided to give the baking setup a try, and ran into an unexpected error: the baker is trying to allocate Optix to run its tracer. This is failing because I don't have an nVidia GPU, but the tracer configured in the Bake Geometry Textures node is Embree, which even though it probably doesn't support my AMD GPU, does support my AMD CPU.
Either way though the baker shouldn't be trying to use the Optix tracer when I've selected the Embree tracer, and the Baker doesn't even have Optix listed as an option, which is appropriate in this case.
Thanks!
Bake Geometry Textures bug?
194 3 2-
- WinterLightDP
- Member
- 21 posts
- Joined: March 2022
- Online
-
- tamte
- Member
- 9334 posts
- Joined: July 2007
- Offline
WinterLightDP
, and the Baker doesn't even have Optix listed as an option, which is appropriate in this case.
so you see that menu only with a single option which is embree?
if that's the case the parameter may still default to value saying 'optix' just showing the first menu entry as it couldn't find it's current value in the menu
You may need to specifically pick that from the menu again just so that it changes the value
you can also confirm the value by RMB/Edit String on the Tracer parameter
that's a pretty common drawback of dynamic menus if this is one of them, but that's just a guess
Edited by tamte - Nov. 4, 2025 20:14:13
Tomas Slancik
CG Supervisor
Framestore, NY
CG Supervisor
Framestore, NY
-
- AslakKS
- Member
- 284 posts
- Joined: Feb. 2016
- Offline
-
- WinterLightDP
- Member
- 21 posts
- Joined: March 2022
- Online
I haven't yet updated to .13, but I did discover that after setting the cage setting to use the input bounding box, the Optix error (eventually) disappeared. I guess it wasn't immediate because some other node was cooking.
http://WinterLightStudios.ca [winterlightstudios.ca]
-
- Quick Links



