Iβve noticed that my 3D models become corrupted or distorted when capturing video using 8thwall specifically on Chrome for Android (Galaxy S24). However, everything works correctly on iOS and the Samsung Browser on Android. It seems like handling for the Chrome patch has not been implemented yet. The issue occurs with the three.js MediaRecorder
, but A-Frame works correctly. Additionally, it only happens in Chrome.
Here is the relevant code:
javascript
XRExtras.MediaRecorder.initRecordButton(); // Adds record button
XRExtras.MediaRecorder.initMediaPreview(); // Adds media preview and share
XRExtras.MediaRecorder.setCaptureMode('fixed');
Could you please look into this issue?
Environment: android,chrome,galaxy24,three.js
video link:
[model/KakaoTalk_Video_2024-10-31-13-31-49.mp4 at main Β· HEOJUNFO/model Β· GitHub]
Hi!
Iβd be happy to look into this issue further, can you provide more details about the device, including the model number or version? In the meantime can you also test with a different version of three.js?
In this project, even after adding only the following code:
javascript
μ½λ 볡μ¬
XRExtras.MediaRecorder.initRecordButton(); // Adds record button
XRExtras.MediaRecorder.initMediaPreview(); // Adds media preview and share
XRExtras.MediaRecorder.setCaptureMode('fixed');
The same bug can be observed in the following environment:
Environment: Android, Chrome, Galaxy S24, Three.js
Which Galaxy S24? There are multiple models available.
Galaxy S24 - model name : SM-S921N
software: One UI 6.1 , Android 14, Latest patch
chrome: 130.0.6723.102
culturecon.8thwall.app/camera/
Great! Weβll look into this. Thanks!
Thank you for your prompt attention to this matter. I appreciate your assistance and look forward to hearing back from you soon. Please let me know if you need any additional information.
Hello!
Is there any progress or updated information related to the issue?
I was able to replicate the bug and have reported it to our engineering team. Iβll let you know if thereβs any updates.
Thank you for investigating the issue and reporting it to the engineering team. I appreciate your efforts and look forward to any updates you might have.
Hello.
Originally, the issue only occurred on Android Chrome, but I discovered that it has suddenly started occurring in the Samsung Browser as of today. It seems to be affected by an Android update.
Please refer to this to resolve the issue. Thank you.