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

KCL: Look straight ahead on startup #4657

Open
wants to merge 15 commits into
base: main
Choose a base branch
from

Conversation

adamchalmers
Copy link
Collaborator

The engine used to look straight ahead when it started. Recently it changed to an isometric viewpoint. While this looks nice, the frontend team needs time to adjust tests which assumed the old viewpoint.

So, temporarily ensure the old view is set at the start.

The engine used to look straight ahead when it started. Recently it
changed to an isometric viewpoint. While this looks nice, the frontend
team needs time to adjust tests which assumed the old viewpoint.

So, temporarily ensure the old view is set at the start.
Copy link

qa-wolf bot commented Dec 4, 2024

QA Wolf here! As you write new code it's important that your test coverage is keeping up.
Click here to request test coverage for this PR!

Copy link

vercel bot commented Dec 4, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
modeling-app ✅ Ready (Inspect) Visit Preview Dec 4, 2024 8:55pm

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure why, but the gizmo still seems to be picking up the new initial vantage from the engine. Maybe this will only need a small fix

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

But I don't think it should block personally?

@adamchalmers
Copy link
Collaborator Author

This PR is now managed by Frank

@pierremtb
Copy link
Collaborator

Do we still need this?

@pierremtb
Copy link
Collaborator

@nadr0 I think we can close that in favour of #5532 right?

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

Successfully merging this pull request may close these issues.

3 participants