Help test the new shadows feature in Cesium

CesiumJS
1

Hi all,

As overwhelmingly requested, Sean and Dan have been working for months on what we believe is one of the most robust shadow implementations out there.

This is coming to Cesium soon and we need your help testing it!

Check out the Shadows Sandcastle example and please provide any feedback in #3856.

Thanks,

Patrick

terrain.jpg
terrain.jpg900×446 134 KB

buildings.jpg

2

That looks awesome guys!

It did crash on my system (OS X, Chrome 50) when changing to wood tower, then selecting everest. The error:

An error occurred while rendering. Rendering has stopped.
undefined
DeveloperError: This object was destroyed, i.e., destroy() was called.
Error
    at new DeveloperError (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Core/DeveloperError.js:44:19)
    at VertexArray.throwOnDestroyed (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Core/destroyObject.js:45:19)
    at continueDraw (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Renderer/Context.js:927:12)
    at Context.draw (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Renderer/Context.js:966:9)
    at DrawCommand.execute (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Renderer/DrawCommand.js:480:17)
    at executeCommand (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Scene/Scene.js:1432:21)
    at executeShadowMapCastCommands (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Scene/Scene.js:1851:21)
    at executeCommandsInViewport (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Scene/Scene.js:2022:13)
    at updateAndExecuteCommands (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Scene/Scene.js:1912:17)
    at render (http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/shadows/Source/Scene/Scene.js:2327:9)

3

Thanks for testing! I also have OS X and Chrome 50, and was not able to reproduce the exception after trying a few times. Perhaps it is timing related. Are you able to reproduce it consistently?

Thanks again!

Patrick

4

That issue was introduced during some refactoring for the tests and was fixed here: https://github.com/AnalyticalGraphicsInc/cesium/pull/3969

Best,

Dan