- This topic has 7 replies, 3 voices, and was last updated 3 weeks, 6 days ago by
.
-
I tried moving the mixerPlane to position z: 6, but I noticed that when the camera’s z coordinate is in the range of (0, 6), I cannot interact with the HTML content. However, outside this range, everything works fine. I also attempted to move the mixerPlane along the X or Y coordinates, and I encountered similar issues.I recorded a video; could you please take a look and advise me on how to properly move the mixerPlane to z: 6 while ensuring it functions correctly?
https://drive.google.com/file/d/1OYZJTymHluqReG76bhAa5LCjk9LQG8kE/view
Replace the last segment of the htmlmixer.js code with the following to run the test:
app.renderCallbacks.push(function(delta, now) { mixerPlane.object3d.position.z = 6; mixerPlane.object3d.rotation.x = 45; mixerContext.update(delta, now); });No access. You could prepare your link a little better before posting it…
take a look and advise me on how to properly move the mixerPlane to z: 6 while ensuring it functions correctly?
Puzzles and JS coding. Fast and expensive.
If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.
Try to access it from another googl user:
You need to share the files so that it can be accessible to other users:
set a couple of limitations to prevent this issue
Puzzles and JS coding. Fast and expensive.
If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.
Actually, my scenario is in first-person perspective, and there is a computer at the position where z is 6, with the computer screen simulated using mixerPlane. The issue I’m facing prevents my camera from interacting with the HTML elements within the mixerPlane when the camera is positioned between z = 0 and z = 6. However, moving the camera to the negative z-axis or beyond z = 6 allows for interactions.
I have also encountered this issue in some Three.js demos
- You must be logged in to reply to this topic.