The deprecated decodeDracoFile method should be removed and replaced with a parse method similar to other loaders. Currently decodeDracoFile does not propagate errors, and should do so. So probably a signature like:

dracoLoader.parse( arrayBuffer, /* options, maybe? */, onLoad, onError );

Issue details

While in a LibGDX environment if you press down a key and then switch to any window outside of LibGDX's scope and release that key, the LibGDX environment does not detect that release event.

Upon re-entry to the LibGDX environment, there should probably be some re-polling evaluation of the keys LibGDX thinks are pressed keys to determine if they are still pressed or not.

8th wall dialog is a good example to follow (open link on iOS 13)

https://apps.8thwall.com/8w/jini/

requestPermision has to be called in a handler triggered by a user gesture

  buttonEl.addEventlistener('click', function () {
    DeviceMotionEvent.requestPermission().then(response => {
      if (response == 'granted') {
        window.addEventListener('devicemotion', (e) => {
   

When a terrain tile fails to load you get a message like:

An error occurred in "CesiumTerrainProvider": Failed to obtain terrain tile X: 0 Y: 0 Level: 0.

This doesn't tell you what the error was/why it failed. In most cases the request has actually failed (404 etc.) and the browser will report it, but in some cases that's not the case either. The only way to see the error is to cha

Priority

Low

Issue Description

In the screenshot below, LAST MODIFIED shows Sat, 26 Oct 1985 08:15:00 GMT,which is incorrect.

Expected Results

LAST MODIFIED shows correct timestamp, so that users know when this file is modified.

Screenshots/Related files

![image](https://user-images.githubusercontent.com/25629006/52917615-75906980-32a2-11e9-8825-10885a5955d2

Expose raytracing render-path in Armory and document implementation details.

As we approach v1.0.0, we should look into versioning our docs. This is important because feature availability will depend on the version of the library being used, and this can be confusing for users if there is only one set of docs.

The two ways we could approach this are 1) keep a copy of the docs site for each old release in a subpath off of the main site 2) note next to each bit of API whi