0

I have problem with load threejs model by objectloader, i add newest ThreeJs library version to get more feature like create text, using objectloader... Here is my code:

    loadThreeJs() {
        const loader = new THREEE.ObjectLoader();

        loader.load('./assets/MVP-TW-CCTV TOWER.json', (obj) => {
            console.log(obj)
            var object3DInside = obj.children[0].children[0];
            console.log(object3DInside)
            setTimeout(() => {this.addScene(object3DInside)},1000)
        }, (xhr) => {
            console.log((xhr.loaded / xhr.total * 100) + '% loaded');
        });
    }
    addScene(obj:any)
    {
        this.viewer.impl.createOverlayScene('load-scene');
        this.viewer.impl.addOverlay('load-scene', obj );
        this.viewer.impl.invalidate(true);
    }

which THREEE is threejs library i loaded from outside. obj is scene so i get children for object3D but it always return object not an instance of THREE.Object3D. i log the result and type is object3D, it supposed to be correct but it not?

enter image description here

Paxton.Huynh
  • 172
  • 10
  • 1
    even I faced the same issue few days back https://stackoverflow.com/questions/65017846/upgrade-three-js-version-in-autodesk-forge-viewer/65023137#65023137 – Ronak Shetiya Nov 29 '20 at 15:07

1 Answers1

1

It looks like you're using another version of three.js and referencing it globally, which is not delivered by Forge Viewer itself, and it will conflict with Forge Viewer one. As Petr mentioned here (upgrade three js version in autodesk forge viewer), Forge Viewer uses self-maintained three.js r71 removed most of the built-in three.js functions.

If you want to use missing features from Forge Viewer's three.js libraries, I would advise you to use some modern development tools such as bundlers (Webpack is the most popular one). You can leverage ES6 modules and import to your app only the strictly needed dependencies. The threejs-full-es6 package lets you import Three.js features to your app independently, so in that case, we can import THREEE.ObjectLoader, and all other required dependencies will be taken care of by the package implementation.

See Forge community blog here: https://forge.autodesk.com/blog/how-add-newest-threejs-features-forge-viewer

Eason Kang
  • 6,155
  • 1
  • 7
  • 24
  • Thanks for your reply, after some effort, i still face same problem. Loader work perfectly and return exactly what i want but viewer cant regconize type of object. It still return ``object not an instance of THREE.Object3D`` – Paxton.Huynh Dec 01 '20 at 02:14
  • Could you share a non-confidential reproducible minimum, runnable code sample demonstrating the issue? It's hard for me to understand the situation without debugging. If it's not proper posted publicly, please send it to `forge[DOT]help[AT]autodesk[DOT]com` – Eason Kang Dec 01 '20 at 07:40