# New Default Camera Behavior - Call for Feedback

**URL:** <https://community.cesium.com/t/new-default-camera-behavior-call-for-feedback/7480>\
**Category:** CesiumJS\
**Created:** [September 24, 2018, 3:52pm UTC](https://community.cesium.com/t/new-default-camera-behavior-call-for-feedback/7480 "2018-09-24T15:52:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![omar](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/omar/32/1999_2.png) [@omar](https://community.cesium.com/u/omar)\
**Post date:** [September 24, 2018, 3:52pm UTC](https://community.cesium.com/t/new-default-camera-behavior-call-for-feedback/7480/1 "2018-09-24T15:52:12Z")

</div>

Hey everyone,

Something that I’ve personally struggled with in CesiumJS in the past is losing a model while I was inspecting it. I’d accidentally click on the horizon/behind the model and I’d pan far away like in the GIF below, and then have a hard time getting back.

![camera_old.gif](https://global.discourse-cdn.com/cesium/original/1X/acd34a62431e1e138937fa0d29f5eafeb6f9ed36.gif)

We know this is something people have expressed frustration with before, so we’d love to hear your thoughts on ways to improve this! Currently, this proposed PR causes the camera to no longer pan in the direction it’s facing when below a certain height:

> <https://github.com/CesiumGS/cesium/pull/7057>

So if I accidentally click on the horizon, it just pans up/down/left/right as you can see below.

![camera_new_optimized.gif](https://global.discourse-cdn.com/cesium/original/1X/50342797fbcf40829368812cb953f00becb6d769.gif)

The catch now is to move forward you would have to zoom.

Here’s an example of the original behavior:

> **[Cesium Sandcastle](https://sandcastle.cesium.com/?src=3D%20Tiles%20BIM.html)**
>
> The Cesium Sandcastle provides an interactive environment for testing Cesium code.

And here’s that same example with the new camera:

[http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/camera-close-to-tileset/Apps/Sandcastle/?src=3D%20Tiles%20BIM.html](http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/camera-close-to-tileset/Apps/Sandcastle/?src=3D%20Tiles%20BIM.html)

Is this better or worse? It would be great to hear how this feels in your projects and applications. You can try any example on that second Sandcastle link, or try it with your own code, to see how it feels.

Here are some examples to try as well:

- Point Clouds
- [Current Camera](https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/?src=3D%20Tiles%20Point%20Cloud%20Classification.html)
- [New Camera](http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/camera-close-to-tileset/Apps/Sandcastle/?src=3D%20Tiles%20Point%20Cloud%20Classification.html)
- NYC Picking Demo
- [Current Camera](https://cesiumjs.org/Cesium/Build/Apps/Sandcastle/?src=3D%20Tiles%20Feature%20Picking.html&label=3D%20Tiles)
- [New Camera](http://cesium-dev.s3-website-us-east-1.amazonaws.com/cesium/camera-close-to-tileset/Apps/Sandcastle/?src=3D%20Tiles%20Feature%20Picking.html)  
Feel free to post your thoughts here or in the [PR](https://github.com/AnalyticalGraphicsInc/cesium/pull/7057).

---

<div class="post-metadata">

**Author:** ![omar](https://sea2.discourse-cdn.com/cesium/user_avatar/community.cesium.com/omar/32/1999_2.png) [@omar](https://community.cesium.com/u/omar)\
**Post date:** [September 24, 2018, 3:55pm UTC](https://community.cesium.com/t/new-default-camera-behavior-call-for-feedback/7480/2 "2018-09-24T15:55:23Z")

</div>

If the GIFs aren’t playing, here they are, current vs new:

[[Album] CesiumJS Camera New vs Current ![](https://i.imgur.com/Y2jSPgP.jpg?fb "CesiumJS Camera New vs Current") ](https://imgur.com/a/dczu5lE)