@SpaceRanger

Final tweaks. Ready to ship now.

Changelog

• tweaks and updates (668bf78)
• section info and general styling (4d03cc2)
• fixed naming issue (703ca92)
• fix deploying failed cause of fsevents (fe68974)

Added detailing to the Site. My escapades are now details on there. Ready to ship, but I Just need to do one more thing.

Added Nav Icons thant remain when Nav is collapsed(AI did most of this). Now I can actually begin filling in info.

Changelog

• added nav icons (9afecd8)

Changelog

• added video background (5b61f31)

Site now uses Video Background from different anime. Spent atleast 2 hours sourcing for, and editing videos.

TCH

Changelog

• collapsible navbar (5a5e017)

I have been able to acheive a collapsible Navbar. Crazy how much I have forgotten basic things lol. Always happens.

Changelog

• collapsible navbar (5a5e017)

I have been able to acheive a collapsible Navbar. Crazy how much I have forgotten basic things lol. Always happens.

Changelog

• configured 2 way channel websocket broadcast. can now receive info from the frontend (2500f28)

Yeah. That’s all.
“THAT’S ALL YOU DID FOR 2 HOURS 🙆‍♀️”.
Yeah. Keep judging. Until you try to code in RUST 😑🙂

Changelog

• configured 2 way channel websocket broadcast. can now receive info from the frontend (2500f28)

Yeah. That’s all.
“THAT’S ALL YOU DID FOR 2 HOURS 🙆‍♀️”.
Yeah. Keep judging. Until you try to code in RUST 😑🙂

Changelog

• Made the in App world go 60* faster than the normal time. (be91922)

Basically, 1 Normal second is 60 seconds in app. 1 Normal hour is 60 hours in app

Changelog

• Trajectory calculation Now uses universal timestamp (c842228)

Okay, Because Celestrak tracks and updates satellite data at different times, The data from the API doesn’t actually reflect the current coordinates of the satellites, especially when compared to one another. While the specific orbits were accurate, The timing was completely random, and so, if 2 satellites were recorded in the same position, 6 hours apart, My simulation will start them in the same coordinate. This is obviously dangerously inaccurate.
Fix: I removed the simulated “timestep” entirely, and Built the whole thing to Check current time, Check time the satellite’s data was recorded, and Simulate Orbit/Calculate trajectory and coordinates based on that.

Problem with that is, without the timestep, My previous calculation for How fast this thing can run in relation to real word time will be totally wrong. I’ll fix that next.

Changelog

• Improve error handling for satellite and debris data fetching; adjust time step for simulation (7e7c487)

Coming back to this after legit leaving it for One month 😭. Anyway, I fixed error handling for Cases where the user is not able to ping the Celestrak servers to get the data needed. Now It just falls back to the Cache. I also reduced the amount of time That goes by in app, to perfectly mirror the real world.

A few different things have bugged me since last I Devlogged.
For one, i’m not tntirely sure how to go on. What i need, to remove, and all.
Secondly, everything is so Unorganized rn. So many debris and satellites Just swimming around in Orbit against a static Earth And everything doesn’t even scale properly.
Lastly, I’ve tried to focus a bit more on Orging My own YSWS.
Thank goodness stardance was extended(Expected, but thank goodness still).

Changelog

• Made the in App world go 60* faster than the normal time. (be91922)

Basically, 1 Normal second is 60 seconds in app. 1 Normal hour is 60 hours in app

Changelog

• Trajectory calculation Now uses universal timestamp (c842228)

Okay, Because Celestrak tracks and updates satellite data at different times, The data from the API doesn’t actually reflect the current coordinates of the satellites, especially when compared to one another. While the specific orbits were accurate, The timing was completely random, and so, if 2 satellites were recorded in the same position, 6 hours apart, My simulation will start them in the same coordinate. This is obviously dangerously inaccurate.
Fix: I removed the simulated “timestep” entirely, and Built the whole thing to Check current time, Check time the satellite’s data was recorded, and Simulate Orbit/Calculate trajectory and coordinates based on that.

Problem with that is, without the timestep, My previous calculation for How fast this thing can run in relation to real word time will be totally wrong. I’ll fix that next.

Changelog

• Improve error handling for satellite and debris data fetching; adjust time step for simulation (7e7c487)

Coming back to this after legit leaving it for One month 😭. Anyway, I fixed error handling for Cases where the user is not able to ping the Celestrak servers to get the data needed. Now It just falls back to the Cache. I also reduced the amount of time That goes by in app, to perfectly mirror the real world.

A few different things have bugged me since last I Devlogged.
For one, i’m not tntirely sure how to go on. What i need, to remove, and all.
Secondly, everything is so Unorganized rn. So many debris and satellites Just swimming around in Orbit against a static Earth And everything doesn’t even scale properly.
Lastly, I’ve tried to focus a bit more on Orging My own YSWS.
Thank goodness stardance was extended(Expected, but thank goodness still).

Changelog

• tweaks and updates (7fc4786)
• Ported satellite data from backend, and introduced satellite component in frontend. (b6b8e5d)

Meh. Frontend change. Not much.

Changelog

• tweaks and updates (7fc4786)
• Ported satellite data from backend, and introduced satellite component in frontend. (b6b8e5d)

Meh. Frontend change. Not much.

Changelog

• Updated program to include, and handle both satellite and debris Cache Data from Celestrak (1665273)

Basically, Now I have 2 files of both Debris data and Satellite Data