In PBRT-v4, the "Option" keyword was introduced to set miscellaneous options. Typically, I have been able to treat all rendering options as parameter lists, but this particular one seems to break that pattern.
As far as I have been able to tell from the PBRT-v4 source code (pbrt/parser.cpp:877), it is only valid to set these sequentially, i.e.:
However, given that PBRT-v4 is still under active development, perhaps it would make sense to also support treating the options themselves as a parameter list? I.e., allowing something like this:
Not sure that this would help in any specific regard, but it would at least allow treating the file format in a more unified way.
Also, is there any example files out there that actually use these options? I couldn't find any among the PBRT-v4 example scenes (https://github.com/mmp/pbrt-v4-scenes).
In PBRT-v4, the "Option" keyword was introduced to set miscellaneous options. Typically, I have been able to treat all rendering options as parameter lists, but this particular one seems to break that pattern.
As far as I have been able to tell from the PBRT-v4 source code (
pbrt/parser.cpp:877), it is only valid to set these sequentially, i.e.:However, given that PBRT-v4 is still under active development, perhaps it would make sense to also support treating the options themselves as a parameter list? I.e., allowing something like this:
Not sure that this would help in any specific regard, but it would at least allow treating the file format in a more unified way.
Also, is there any example files out there that actually use these options? I couldn't find any among the PBRT-v4 example scenes (https://github.com/mmp/pbrt-v4-scenes).