Performance difference between 106 and latest?

Questions
1

Hello,

I have a project https://quakeviz.app that runs on these npm packages…

    "three": "0.106.2",
    "three-orbitcontrols": "^2.102.2",
    "three-shaders": "1.0.16",

I am making this project repo public on my github as a little front end project to show React.js, Three.js, Server Side Rendering of Three.js Objects, and some basic Node.js and FlatDB work.

It works but on some peoples computers they have some performance issues when using the orbit controls just a little laggy is all. Do the latest packages offer any overall generalized performance improvements?

2

It’s odd that orbit controls should cause any performance issues. If you measure the framerate (e.g. with stats.js) does it change when OrbitControls is being used? You might need to measure why the scene is slow to get an answer on this, but usually three.js itself is not the bottleneck so much as the number of draw calls, or scene- or device-specific issues.

Aside, we recommend using OrbitControls (and any other part of three.js itself) directly from the three package, like:

import * as THREE from 'three';
import { OrbitControls } from 'three/examples/jsm/controls/OrbitControls.js';

That tends to avoid certain version mismatch issues, but might not affect performance directly.

1 Like
3

Hey Don,

Yeah that’s a good call… I hadn’t taken a look to see what was deep in the three package. I will definitely check that out at some point.

So far it’s a refactor from

to

1 Like