Carlos Cabada

Having same problem here. > Example: > > ``` > > import * as THREE from "./node_modules/three/build/three.module.js"; > import { Interaction } from "./node_modules/three.interaction/build/three.interaction.module.js"; > > ``` > > Produces...

Wow, has this been resolved? I don't want to run to this issue.

I'm also interested in this.

Has anyone figured out something yet? Or it's literally impossible at the moment? I'm looking forward to use for the following pipeline: 1. Create a scene with Three.JS 2. Export...

> > It works great on desktop and non-iOS devices. > > What desktop? MacOS+Chrome (Obvs AR not being used) Talking about ``, which forces USDZ for iOS devices.

Did you manage to fix this? I'm encountering this bug right now.

This has been solved in the latest version of the library, just confirmed it. @Alexander-Trinh @derekchan916

I'm trying to run this on Jeston Nano but I get stuck on this: ``` out_boxes, out_scores, out_classes = self.sess.run( [self.boxes, self.scores, self.classes], feed_dict={ self.yolo_model.input: image_data, self.input_image_shape: [image.size[1], image.size[0]], K.learning_phase():...

After leaving it for a while, it displays the following message: ``` kthreadd: page allocation stalls for 10004ms, order:2, mode:0x27080c0(GFP_KERNAL_ACCOUNT|__GFP_ZERO|__GFP_NOTRACK) kthreadd invoked oom-killer: gfp_mask=0x27080c0(GFP_KERNEL_ACCOUNT|__GFP_ZERO|__GFP_NOTRACK), nodemask=0, order=2, oom_score_adj=0 Out of memory:...

Memory is hitting the limit, just verified it with `tegrastats` I'm adding a **swapfile** to help the the memory, will let you know if that fixed it.