Feature Request - Lower VRAM usage by preprocess textures
Posted: Tue Mar 10, 2020 3:34 pm
Hey Guys,
I'm loving Octane, but I'm a bit concerns about the high Vram usage. I paint all my textures in 4k and 8K sizes. Obviously, this takes up a lot of VRAM space. To mitigate that, a lot of rendering programs are automatically preprocessing the textures down to an optimal size and using only certain tiles of the texture that contributes to the final render defined by the camera view. For example, Arnold uses the .tx file format, which allows tiling and quick resizing. Redshift also goes through a preprocessing phase per frame from the camera view to reduce the geometry and texture memory size. Modo suggests we use tiled EXR format to reduce ram usage.
After doing a quick render on similar scenes in both Octane and Redshift, I noticed that Octane is taking over 5-6 Gigabytes of Vram for geo and textures and had to use out-of-core. On Redshift, the geo and textures were reduced down to roughly 1 Gigabyte of Vram and didn't need to use out-of-core technology.
I don't write render engine, and I know that Octane is emphasizing a future of real-time playback with ray tracing, therefore preprocessing textures go against that philosophy. However, for now, I think to make Octane usable for large scenes with large PBR texture sets, it would be beneficial to provide a preprocess system to automatically scale down our texture and geometry optimally to fit into VRAM per frame and from camera view.
I apologize if I get any technical details wrong, but my general request is to reduce VRAM usage and avoid out-of-core to get optimal render times. Thank you.
I'm loving Octane, but I'm a bit concerns about the high Vram usage. I paint all my textures in 4k and 8K sizes. Obviously, this takes up a lot of VRAM space. To mitigate that, a lot of rendering programs are automatically preprocessing the textures down to an optimal size and using only certain tiles of the texture that contributes to the final render defined by the camera view. For example, Arnold uses the .tx file format, which allows tiling and quick resizing. Redshift also goes through a preprocessing phase per frame from the camera view to reduce the geometry and texture memory size. Modo suggests we use tiled EXR format to reduce ram usage.
After doing a quick render on similar scenes in both Octane and Redshift, I noticed that Octane is taking over 5-6 Gigabytes of Vram for geo and textures and had to use out-of-core. On Redshift, the geo and textures were reduced down to roughly 1 Gigabyte of Vram and didn't need to use out-of-core technology.
I don't write render engine, and I know that Octane is emphasizing a future of real-time playback with ray tracing, therefore preprocessing textures go against that philosophy. However, for now, I think to make Octane usable for large scenes with large PBR texture sets, it would be beneficial to provide a preprocess system to automatically scale down our texture and geometry optimally to fit into VRAM per frame and from camera view.
I apologize if I get any technical details wrong, but my general request is to reduce VRAM usage and avoid out-of-core to get optimal render times. Thank you.
I'm also using 4k and 8k textures a lot and even with texture compression it gets tricky on bigger scenes where photoscans (3D assets) also eat a lot of VRAM. You can optimize obviously but it would be neat to have some extra options perhaps