Hypersim, Photorealistic Synthetic Dataset for Indoor Scene Understanding
github.com
github.com
That paper also mentions something that has still not found its way into an Apple product: they posed 3D models of hands and then degraded them to appear as depth maps, with jagged edges, artifacts, and occlusions.
GPUs are a superior computer for raytracing calculations. But...
CPUs have the software advantage: decades of engineering effort have been poured into CPU-renderers. While we're at the point where GPU-rendering is starting to become a thing, it will inevitably take decades of engineering to recreate all of those features on the GPU.
One important GPU specific problem is the shortage of RAM: CPUs always have more RAM available (even if that CPU-RAM is much much slower). Teaming up the CPU + GPU to handle the RAM problem for large scenes is going to take significant effort. The general ideas are known in research papers and whatever, but not really ported to the actual tools yet. Disney's Moana dataset is known to take ~100GBs of geometry data / textures / animations. But there's no GPU on the planet that can hold all that data. So you'd have to make a CPU+GPU team to take on that problem.
However it might lack some features or flexibility compared to V-Ray.
The other thing to consider is the evermotion dataset might contain a lot of V-Ray Materials and Layers that might be CPU only. At one point Chaosgroup had a list of all the difference between CPU/GPU, but it appears they either solved all of them and/or took the page down.
I think the Chaos Group documentation you're thinking of is here: https://docs.chaosgroup.com/display/VMAX/V-Ray+GPU+Supported...
Indeed, at least according to this documentation, some of the render elements we are relying on to generate the Hypersim dataset are unsupported on the GPU.
CPU is universal and has more RAM. Optimizing very sophisticated ray tracing for GPU with tiny amount of VRAM could be very tricky. It is easier to do dirty code on CPU, and wait for couple of weeks.
Apple also had spare CPU cycles. This stuff could run overnight in background.
Windows 10 has "curl" support out of the box since update 1803.
Huh, TIL.
(At first I thought that maybe Microsoft had just done something like
Set-Alias -Name curl -Value Invoke-WebRequest
but no, it’s the real deal[0].)[0]: https://devblogs.microsoft.com/commandline/windows10v1803/
Windows does not have unzip but I think you can uncompress files from the Windows command line via a detour to powershell: powershell "expand-archive file.zip -d <path/to/destination...>"
I just checked, this works fine here.