Whitespace in VDB grid names #53802

New Issue

Thomas Volkmann · 2018-01-16T15:19:35+01:00

Thomas Volkmann commented

2018-01-16 15:19:35 +01:00

From the smoke export Wiki page:
"If high resolution is enabled, the corresponding low resolution fields are suffixed with " low"."

Can this please be changed so the whitespace gets replaced with an underscore "_low".
Having a whitespace in the vdb grids causes some confusion when inspecting the vdbs in other software (in this case Arnold).
The list of available grids reads like this:
color color low density density low heat heat old obstacles shadow texture coordinates velocity

Thanks!

From the smoke export Wiki page: "If high resolution is enabled, the corresponding low resolution fields are suffixed with " low"." Can this please be changed so the whitespace gets replaced with an underscore "_low". Having a whitespace in the vdb grids causes some confusion when inspecting the vdbs in other software (in this case Arnold). The list of available grids reads like this: color color low density density low heat heat old obstacles shadow texture coordinates velocity Thanks!

Thomas Volkmann commented

2018-01-16 15:19:35 +01:00

Added subscriber: @knekke

Philipp Oeser commented

2018-01-18 18:07:50 +01:00

Added subscribers: @kevindietrich, @lichtwerk

Kévin Dietrich was assigned by Philipp Oeser

2018-01-18 18:07:50 +01:00

Philipp Oeser commented

2018-01-18 18:07:50 +01:00

I can see this getting annoying [although I could find anything in the spec stating that those names are not allowed...]

@kevindietrich: what do you think?

I can see this getting annoying [although I could find anything in the spec stating that those names are not allowed...] @kevindietrich: what do you think?

Brecht Van Lommel commented

2018-01-26 08:12:00 +01:00

Added subscriber: @brecht

Brecht Van Lommel commented

2018-01-26 08:12:00 +01:00

@lichtwerk, I think it's reasonable to use an underscore, it does seem to be the convention for VDB files.

If we change this then the code to read VDB files should still try both "_low" and " low" though, for backwards compatibility.

If you like to fix this go ahead I think, otherwise close as not a bug.

@lichtwerk, I think it's reasonable to use an underscore, it does seem to be the convention for VDB files. If we change this then the code to read VDB files should still try both `"_low"` and `" low"` though, for backwards compatibility. If you like to fix this go ahead I think, otherwise close as not a bug.

blender-admin commented

2018-01-29 18:37:35 +01:00

This issue was referenced by 6d8a4c10b6

This issue was referenced by 6d8a4c10b65c45b2bcc2eca7779cc541af0562fb

Philipp Oeser commented

2018-01-31 20:18:54 +01:00

having trouble building with openvdb right now [/usr/bin/ld: vdb_print: hidden symbol `__cpu_model' in /usr/lib/gcc/x86_64-redhat-linux/7/libgcc.a(cpuinfo.o) is referenced by DSO]
as soon as this is out of the way, I'll have a look

having trouble building with openvdb right now [/usr/bin/ld: vdb_print: hidden symbol `__cpu_model' in /usr/lib/gcc/x86_64-redhat-linux/7/libgcc.a(cpuinfo.o) is referenced by DSO] as soon as this is out of the way, I'll have a look

Kévin Dietrich commented

2018-02-04 01:20:32 +01:00

@lichtwerk if you have trouble building OpenVDB, I can quickly make a patch for it.

Philipp Oeser commented

2018-02-04 09:56:56 +01:00

@kevindietrich : yes, please go ahead, thx!

Kévin Dietrich commented

2018-02-24 14:01:13 +01:00

Changed status from 'Open' to: 'Resolved'

Kévin Dietrich closed this issue

2018-02-24 14:01:13 +01:00

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Whitespace in VDB grid names #53802