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

Sphere Generation #1

Open
Gizmotronn opened this issue Mar 4, 2022 · 1 comment
Open

Sphere Generation #1

Gizmotronn opened this issue Mar 4, 2022 · 1 comment
Assignees

Comments

@Gizmotronn
Copy link
Member

Setting up generation for meshes & spheres for the space-level (view) of the planets in Star Sailors.

Mainly two scripts -> TerrainFace.cs and Planet.cs (to start wtih)

@Gizmotronn
Copy link
Member Author

Gizmotronn added a commit that referenced this issue Mar 4, 2022
Gizmotronn added a commit that referenced this issue Mar 20, 2022
Gizmotronn added a commit that referenced this issue Mar 20, 2022
Gizmotronn added a commit that referenced this issue Mar 23, 2022
Gizmotronn added a commit that referenced this issue Jun 22, 2022
Gizmotronn added a commit to Signal-K/client that referenced this issue Jan 24, 2023
We've got some 3d planets being rendered in javascript, these are based on the initial C# algorithms in Signal-K/starsailors#4, Signal-K/starsailors-boilerplate#1

We've got some plans to generate nfts from this: Signal-K/sytizen#18. The models here are based on the C# model, we'll have an API call setup later so that they're both equivalent to each other directly.

Next step is setting up some image exports and saving user data, providing a way for users to export the 3JS graphic to their Supabase storage row. That will be commenced later on tonight.

All the fields will be set to be callable via an API & we will compare the output of different Deepnote graphs generated from `lightkurve` to provide further adjustments to either end.
One issue is that on the frontend for the generator, some of the components aren't selectable. This is because the original example components were built for a much older version of React>Next. Since these will be callable via a custom API, and the editor will be changed to be a form, that won't be an issue.

Docs available at the central issues on signal-k org

Signal-K/marketplace#19
Signal-K/marketplace#3
Signal-K/marketplace#7
Signal-K/Silfur#26 -> These will be added to posts on the image/comment sharing part of the site (and later on Lens -> team members can refer to the roadmap) so that will be routed internally.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

1 participant