Cant get VDBs to load: KtoA Could not get bounds for file

ethan.crossno
Contributor
Contributor

Cant get VDBs to load: KtoA Could not get bounds for file

ethan.crossno
Contributor
Contributor

I've tried loading multiple VDBs with the ArnoldOpenVDBVolume but I get the same error every time. "[KtoA] Could not get bounds for file: <filename>". I am correctly populating the grids parameter with the density grid. The same VDBs load correctly inside MtoA, just not in KtoA for some reason. I'm including an example file with a small vdb for testing on your end.

 

ethancrossno_2-1710523969512.pngethancrossno_3-1710524012761.png

 

 

 

Katana Version: 6.0v1

KtoA Version: 4.2.2.0

Arnold Version: 7.2.2.0

OS: Windows

0 Likes
Reply
637 Views
4 Replies
Replies (4)

Stephen.Blair
Community Manager
Community Manager

Works for me. But Katana doesn't like paths with spaces in them. I get a Katana "VolumeBounds" message and no bounding box in the viewport with a vdb that's in a "/Katana vdb issue" folder. But it still renders.

And if I put the vdb in a path with no spaces, there's no warnings or other messages.

ktoa_volume.jpg



// Stephen Blair
// Arnold Renderer Support
0 Likes

ethan.crossno
Contributor
Contributor

Thanks! Good to know. I can confirm the paths to our VDBs don't have spaces. Here is an example of the path: O:/projects/PROJECT/production/sequences/wcge/shots/wcge_0100/fx/work/BG_Smoke/v001/BG_Smoke.0247.vdb

 

But I still get no viewport location, and an error message on the SceneGraph about not getting the bounds. 

ethancrossno_0-1711478137337.png

 

0 Likes

Stephen.Blair
Community Manager
Community Manager

A quick scan of the release notes didn't show anything specific to this type of problem, but I would try with a newer version. Arnold 7.2.2 is from awhile ago (8 bug fix releases and 3 feature releases ago).



// Stephen Blair
// Arnold Renderer Support
0 Likes

ethan.crossno
Contributor
Contributor

Sure thing! We launched a version of Katana 7.0v2 with KtoA 4.2.5.3 which uses Arnold 7.2.5.3 and we are still seeing the same issue.

 

 

ethancrossno_1-1711488074016.png

 

0 Likes