Update the Cesium and Babylon engines / Make Babylon work on unsaved …

…changes

* Updated Cesium engine to 1.34 and leveraged the new [`basepath`](CesiumGS/cesium#5320) option in `Cesium.Model.fromGltf`.
* Updated Babylon.js engine to get a [tangent fix](BabylonJS/Babylon.js#2222).
* Babylon (like Cesium) now defaults to previewing the content in the tab as opposed to the content saved in the file, the same way it's done in this [Babylon Plaground Example](https://www.babylonjs-playground.com/#1AbIIF#7).

Resolves Issue AnalyticalGraphicsInc#15

> **Work in Progress**
> - Active preview for Babylon is not currently working for some reason.  More investgiation needs to happen.

CHANGELOG.md

@@ -1,5 +1,11 @@
 # Change Log
 
+### 2.0.2 - UNRELEASED
+
+* Updated Cesium engine to 1.34 and leveraged the new [`basepath`](https://github.com/AnalyticalGraphicsInc/cesium/issues/5320) option in `Cesium.Model.fromGltf`.
+* Updated Babylon.js engine to get a [tangent fix](https://github.com/BabylonJS/Babylon.js/pull/2222).
+* Babylon (like Cesium) now defaults to previewing the content in the tab as opposed to the content saved in the file.
+
 ### 2.0.1 - 2017-06-01
 
 * Update Babylon engine to fix glTF 1.0 support.

README.md

@@ -37,8 +37,8 @@ This works for arrays as well, for example the list of enabled render states.  H
 
 Press <kbd>ALT</kbd> + <kbd>G</kbd> on your glTF file, or look for the command `Preview 3D Model` in VSCode's list of commands (<kbd>CTRL</kbd> + <kbd>SHIFT</kbd> + <kbd>P</kbd>) and use that.
 
-The Babylon.js and Three.js engines will preview the saved model as opposed to
-the current content in your open VS Code tab.  The Cesium engine will first try
+The Three.js engines will preview the saved model as opposed to
+the current content in your open VS Code tab.  The Babylon and Cesium engines will first try
 to preview what is currently in your tab, and only if that fails will it fall
 back on displaying the version of the model saved on disk.