Vr Tour

[johan belmans]

Hi there

a VR Tour we just finished
http://www.belly.be/Keysershoek/tour.html

[Fritzlachatte]

Where ever it is, I´ll buy the penthouse :-) 
Great!

[bluebox]

Really great !
Super curious - what was the RAM consumption for exterior 360 shots ?
Also what was the render time for those exterior shots and on what hardware specs :) ?

[mferster]

Nice work, what were the final resolutions?

[FrostKiwi]

huge respect, this is definetly the best and most complete VR tour to date, that I have seen.

Some bad stiches in the sky on most panos.

[fellazb]

Well done Johan!

[maru]

Just awesome. Makes me want to explore the whole scene, almost like an in-game experience. Is it one huge scene, or were the locations modeled as separate scenes?

The only issue seems to be the stitching, it's visible on almost every shot. Maybe you used some post processing?

[pmcf1981]

belly is great one thing what software you use to create tour ? Pano?

[johan belmans]

Hi guys,

thanks!

Here some answers:
-resolution: 13312x13312 pixels. Resolutions is way to much for VR devices, but the web app is as important as the VR app.
-Render times: differs from image to image. Mostly because we tried to reach different noise levels for exteriors vs interiors and used slaves with different specs. For the exteriors : 3% and interiors 1.7%. And for some images we used Dr over Backburner. So we ended up between 24 and 70 hours for a render.
-Hardware: We have 1x Xeon E5-2650 V4 with 128 GB Ram = CB 3060 and 2x Xeon E5-2630 V2 100GB of Ram = CB 1515
-Ram Consumption: differs again from image to image but around 70-80 GB
-Denoising: with Corona 1.4 denoising does not work on this large resolution.  Bad allocation messages, already mentioned on Mantis.

The scenes:
-Exteriors shots: the garden and all the pops are two Xref files. The interiors are all separate scenes with the garden file as an Xref.

The stitches:
damn, didn't notice them up until now. So I guess this is due to post processing.

[johan belmans]

Software: KRPano, but I am curious about what The Construct will bring us.

[johan belmans]

Hi guys,

thanks!

Here some answers:
-resolution: 13312x13312 pixels. Resolutions is way to much for VR devices, but the web app is as important as the VR app.
-Render times: differs from image to image. Mostly because we tried to reach different noise levels for exteriors vs interiors and used slaves with different specs. For the exteriors : 3% and interiors 1.7%. And for some images we used Dr over Backburner. So we ended up between 24 and 70 hours for a render.
-Hardware: We have 1x Xeon E5-2650 V4 with 128 GB Ram = CB 3060 and 2x Xeon E5-2630 V2 100GB of Ram = CB 1515
-Ram Consumption: differs again from image to image but around 70-80 GB
-Denoising: with Corona 1.4 denoising does not work on this large resolution.  Bad allocation messages, already mentioned on Mantis.

The scenes:
-Exteriors shots: the garden and all the pops are two Xref files. The interiors are all separate scenes with the garden file as an Xref.

The stitches:
damn, didn't notice them up until now. So I guess this is due to post processing.

So I guess this is due to post processing as Maru suggested

[rambambulli]

Nice belly!