Adobe's OpenPBR BSDF headers packaged for R under Apache-2.0. The pinned implementation targets the OpenPBR 1.1.1 model. The upstream shader remains header-only. A small registered native interface exercises its BSDF and reports the supported model version:
openpbr::openpbr_version()
# [1] "1.1.1"
This is the material model version; packageVersion("openpbr") reports the R
package version. Package versions use x.y.z-n, with x.y.z taken from upstream:
the current version is 1.1.1-0, where 0 is the packaging revision. Increment
that suffix for packaging changes that retain the same upstream version.
The function checks an index-matched diffuse evaluation against
the expected Lambertian response. Renderers supply geometry, lighting, and
transport; this package does not provide an R shader constructor.
Install glmheaders first, then openpbr. A consuming package should declare both:
LinkingTo: openpbr (>= 1.1.1-0), glmheaders (>= 1.0.1-1)
The C++ entry point requires GLM to be included first:
#include <glm/glm.hpp>
#include <openpbr/openpbr.h>
R supplies the include paths when installing the consumer. No custom linker
flags or linkage to this package's verification DLL are needed. To isolate the upstream API, include
GLM first, then include openpbr/openpbr.h inside a namespace. Configuration
macros must be set before including OpenPBR. Upstream settings remain unchanged.
Keep R's standard -DNDEBUG compilation flag to disable upstream assertions
that could otherwise terminate the R process. Custom build systems must also
define NDEBUG.
For standalone tools, locate headers with
system.file("include", package = "openpbr") and the corresponding glmheaders
directory. Code compiled during tests or examples should also declare its header
dependencies in Suggests, as LinkingTo is an installation-time dependency.
The pinned upstream revision and copyright attributions are recorded in
COPYRIGHTS. API documentation is available in the
upstream repository.
Compile-and-run tests use R's native interface to exercise the installed
headers, BSDF evaluation, sampling, and embedded lookup tables.
Download the latest successful main source build. Open that page and use its Download the R source tarball link. The filename and release notes identify the package version, branch, full commit SHA, and build run; the notes also include the tarball's SHA-256 checksum. These are development source packages, not CRAN releases or compiled binaries.
Build R source package
runs R CMD build for every branch push, pull requests targeting main, and
manual runs. Every successful run has a downloadable Actions artifact retained
for 30 days. Successful main-branch pushes and manual runs also publish durable
release assets. Pull requests and other branches cannot replace main's download.
The release page selects a new download only after the uploaded tarball has been downloaded again and its checksum verified. Older runs cannot replace a newer main build, and previous assets remain available at their original URLs. Use the linked package asset rather than GitHub's autogenerated source archives.