Fly Controller Widget Behaves Differently in Chrome then in Edge-And other questions

[bkaplan1]

The running of an Experience Builder 3D scene with a Fly Controller performs problematically different in Edge and Chrome.   I'm using "Plan Routes"  The initial view using Edge is what would be expected as shown below with the start pin.  But Chrome behaves badly.

When I run it in Chrome, the start point is not the start point of the path but zoomed into ground level.  

I tried working around this issue in Chrome by adding a point to the route and set it for 0 seconds and 0 degrees rotation.  But it zooms to an off center location shown here in Chrome.  The last screen shot is in Edge

What is road path for this widget.  It would be nice to have:

* For points to specify an elevation 

* For "Plan routes", more control on the nodes of the route.  I don't understand how the turning performs and if the turns at nodes can be customized.

* When changing the "Plan routes" elevation, the starting and ending point angle is such that one doesn't get a good perspective of the ground.  One can combine points here but with the Points stuck on the ground, the combination of point and path is not ideal.  

* When setting a message action to extent changes, provide an option to set the scale.

* Add extent indicators such that when one is flying through a scene, an extent indicator on a map inset moves with the fly through.

Lastly, I can find only a single Esri video on the Fly Controller Widget.  Is it covered in other videos.  It would be nice to have a tutorial for each widget and for the tutorial to cover what it can do and also the limitations.

Thanks.

[Shen_Zhang]

Hi @bkaplan1 

Thank you for all the feedback. I couldn't reproduce your issue regarding Chrome though. Would it be possible for you to provide me with a sample app or a recording showing the bug? 

For the questions and suggestions you posted beneath:

• When turning at the nodes of a path, you can choose either a smoothed path (following a smoothed path calculated based on path length & fly time) or a real path (a sharp turn). You can try set the fly time longer or density the nodes at the turnings if you want it to be smoother.
• "When changing the "Plan routes" elevation, the starting and ending point angle is such that one doesn't get a good perspective of the ground" - I assume you find this while trying out with your walkaround with the bug? Adding an altitude setting to the point should be able to solve this.

As for the rest, I think those are good points and we'll see how we can make more improvements. Also, thank you for mentioning the documentation and tutorials. Please feel free to reach out to the Esri support team to raise a ticket for the features that are important to you.