From f0cac244397396588f42610d4b63596552078966 Mon Sep 17 00:00:00 2001
From: Marshall Quander <marshall@quander.me>
Date: Mon, 4 Jun 2018 17:43:21 -0700
Subject: [PATCH] renderer.animate -> renderer.setAnimationLoop
This was renamed in three.js r93.
---
src/hub.js | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/src/hub.js b/src/hub.js
index d31817d4c..aeb047d7a 100644
--- a/src/hub.js
+++ b/src/hub.js
@@ -222,7 +222,7 @@ const onReady = async () => {
const scene = document.querySelector("a-scene");
if (scene) {
if (scene.renderer) {
- scene.renderer.animate(null); // Stop animation loop, TODO A-Frame should do this
+ scene.renderer.setAnimationLoop(null); // Stop animation loop, TODO A-Frame should do this
}
document.body.removeChild(scene);
}
@@ -403,11 +403,11 @@ const onReady = async () => {
if (!isBotMode) {
// Stop rendering while the UI is up. We restart the render loop in enterScene.
// Wait a tick plus some margin so that the environments actually render.
- setTimeout(() => scene.renderer.animate(null), 100);
+ setTimeout(() => scene.renderer.setAnimationLoop(null), 100);
} else {
const noop = () => {};
// Replace renderer with a noop renderer to reduce bot resource usage.
- scene.renderer = { animate: noop, render: noop };
+ scene.renderer = { setAnimationLoop: noop, render: noop };
document.body.style.display = "none";
}
});
--
GitLab