New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GLB does not trigger preview upload #680
Comments
@obxium : {
"image": secondFile,
"animation_url": file
} If the preview upload is not triggered app constructs JSON: {
"image": file,
} In But I think we can fix it without re-mint |
Ahh makes sense @vikiival. Thanks for the explanation. Is is possible then to use the GLB file again as the value to the poster/cover field in order to have it render in gallery view for the next ones I need to mint? |
In gallery view, what would be super heavy on objects I guess as GLB objects are quite big, it's an option to have it. |
Makes sense, so what do I need to do to have it appear on the actual object page like here: Just set the value in |
Yes this should work! |
So time to solve it, somehow? 😄 |
Closed in #791 |
Need to convince drop upload to spawn another drop upload for the second file |
Describe the bug
I minted an NFT with a GLB media file:
https://nft.kodadot.xyz/rmrk/detail/9050726-34BE282B68C3F03135-FLTS-FRACTAL_LOTUS_1-0000000000000001
The media is not present on any browser that I have access to (most contemporary browsers at latest versions). Instead it looks like this, showing only the KodaDot logo in place of the GLB.
The file in question, FLOW1.glb is approximately 38MB in size. I have used various tools, such as glTF Validator to ensure that the GLB file content is valid, and it is valid.
To Reproduce
Steps to reproduce the behavior:
Observe that the finished NFT does not correctly display the GLB model.
Expected behavior
The GLB model content should appear within the figure element for the image-preview div.
Screenshots
Desktop (please complete the following information):
Additional context
I also tried this on contemporary versions of other Desktop browsers to the same effect.
The text was updated successfully, but these errors were encountered: