Skip to content

v0.2.0

Choose a tag to compare

View all tags
@github-actions github-actions released this 27 Oct 23:09
· 186 commits to main since this release
v0.2.0
bc9ce58

Bakes now run on the GPU, on NVIDIA and AMD cards, and are several times faster.

Download

OpenTool-v0.2.0-windows-x64.zip holds OpenTool.exe and OpenTool-cli.exe, as in 0.1.0. Unzip it and run OpenTool.exe. The only thing to install is Blender 5.2 or newer. The zip is 187.6 MB, up from 159.7 MB, because it now carries SlangPy, which runs the per-vertex pass on the GPU. THIRD_PARTY_NOTICES.md lists its parts.

Faster bakes

  • The per-vertex light, which took most of a bake's time, now runs on the GPU. Putput took 438.6 s in 0.1.0 and about 31 s on an RTX 4060 laptop GPU.
  • On the same laptop's AMD Radeon 680M, Blood Gulch, Rat Race and Putput take about 40 to 60 s. The results match the NVIDIA ones: the correlation with tool's lightmaps is the same to four digits on all three maps, and Putput's light direction differs by 0.04 degrees.
  • Blood Gulch on the RTX 4060 takes 19 s at Draft, 29 s at Normal and 67 s at High, against 24, 70 and 220 s in 0.1.0.
  • With the CPU only, Rat Race takes 181 s at the default settings and 57 s at Normal.

Device choice

  • A Device row in the app shows the GPU it found and lets you pick Auto, NVIDIA, AMD or CPU only. Auto uses a GPU with Vulkan ray queries, NVIDIA before AMD, and otherwise the CPU. NVIDIA and AMD stop the bake with a message when no such GPU is found.
  • In a settings file, device takes auto, nvidia, amd or cpu. The 0.1.0 names still load: OPTIX, CUDA and HIP mean a required NVIDIA or AMD, and ONEAPI means auto.
  • After a bake the app shows what ran on what: pages, vertex pass and denoiser. summary.json records the same under devices, plus any warnings.

Ray counts

  • With a GPU the presets use more rays: Draft 256 per texel and 1024 per vertex, Normal 1024 and 4096, High 2048 and 16384.
  • A stage that runs on the CPU uses 0.1.0's counts instead: Draft 64 and 256, Normal 256 and 1024, High 512 and 4096. The app notes this under the preset. Custom values are used as typed.
  • New settings cpu_samples and cpu_vertex_rays set the CPU counts in a settings file. Left out, they follow samples and vertex_rays.

Fixes and settings

  • Two-sided sheets, where two faces sit exactly on top of each other, no longer shadow each other. Lighting on such surfaces changes in existing levels.
  • A new seed setting (0 to 999) changes the bake's noise without changing the lighting.

Known limits

  • Windows only.
  • Tested on an NVIDIA RTX 4060 laptop GPU and an AMD Radeon 680M. Intel GPUs are untested.
  • The denoiser runs on the CPU on AMD, because Open Image Denoise's HIP device did not open on the Radeon 680M. The app shows a warning.
  • The app is not signed, so Windows SmartScreen may warn the first time. Choose More info, then Run anyway.
Assets 3
Loading