Skip to content
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

[BUG] HTML export does not correctly keep viewport #358

Open
pablovela5620 opened this issue Dec 21, 2024 · 5 comments
Open

[BUG] HTML export does not correctly keep viewport #358

pablovela5620 opened this issue Dec 21, 2024 · 5 comments

Comments

@pablovela5620
Copy link

Here's a video showing what I mean.

supersplat-regression-2024-12-21_11.14.12.mp4

Here is the original splat + HTML viewer files

https://huggingface.co/datasets/pablovela5620/supersplat-regression/blob/main/splat-viewer.html

@slimbuck
Copy link
Member

I've noticed that the browser sometimes caches old versions of the html file. Can you please try clearing the browser cache and then loading the html again?

@pablovela5620
Copy link
Author

I cleared browser data using

Click the three vertical dots (⋮) in the top-right corner.
Navigate to More Tools > Clear browsing data.
In the Time range dropdown, select All time.
Check Cached images and files.
Click Clear data.

and I'm still getting the same results

@pablovela5620
Copy link
Author

I've tried both on my linux machine, and on my MacBook. Exporting on either current viewport or 1st camera results in the broken view above

@slimbuck
Copy link
Member

Oh damn I know what the issue is. (Sorry just got a chance to look).

We set the camera's front and back clipping plane to cover the whole scene's extents and in this case it means the front clipping plane is too large.

You can edit the .html file and set line 203 and 204 something like:

this.entity.camera.farClip = 100;
this.entity.camera.nearClip = 0.01;

Sorry about this, it's actually come up once before and I just forgot to submit a fix.

@pablovela5620
Copy link
Author

Looks like that fixed it! Ill leave this issue for now until there's a more permanent fix

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants