Hi,
first - please don't believe everything you can read on the web, better always do your own tests! So far I 've read that FB-post Thomas Sharpless only tested external sites like roundme.com or 360cities.net and e.g. not the krpano MAKE VTOUR outputs (especially the VR-OPT one).
What he called 'shimmer' is actually
aliasing and is only related to the ratio of the pano-image-size and the output-size. When the pano-image-resolution is too high compared to the output-rendering-resolution this can cause aliasing, but that depends also on the image-content itself (e.g. high-contrast edges).
And there are many possibilities to to 'tune' this - the first one would be using a image-size that matches the output-resolution, e.g. for current VR-headset a cube-size of ~1500px matches the screen-resolution in a good way (the VR-OPT droplet automatically generates such images for VR-usage).
The next one would be using image-sizes that allow mipmapping (e.g. cube-sides with 2048px or 4096px).
Additionally also the
oversampling setting can be increased, then the output will be rendered at a higher resolution and then downscaled. This cost performance of course (depending of the power of your GPU) but therefore it also reduces aliasing-effects and make the image more overall-clear.
Best regards,
Klaus