Recent content by n72.75

It's way too strong in most cases (Causes the NASSP Saturn 5 to fail to achieve a parking orbit due to how much it eats into the DV budget) It is not implemented in a way to mirrors real wind forces https://www.orbiter-forum.com/threads/atmospheric-wind-effects-do-not-feel-right.35124/post-538106

Orbiter uses TDB. I think it would be very hard to say exactly where the error is coming from other than to really go through all possible error sources and quantify them. E.g. if the error in Earth velocity is x ppm, what effect does that have on your drift error etc. Something easy to check...

I posted this in the shoutbox yesterday, but for anyone that didn't see it, this is a nice resource: https://web.archive.org/web/20220521220700/https://www.mishindiaries.com/

Thank you. I'm a little unsure on how to proceed next, and could use your input. I'm assuming this is what I'm looking for: def UpdateRotation(self, MJD=MJD0): self.MJD = MJD et = (MJD - 51544.5) * 86400 rotate = sp.pxform(self.name, "ECLIPJ2000", et) x, y, z = np.dot(rotate...

What is the best format to represent rotation in, as far as something that would get passed to the new clbkRotation function. I'm very on the fence, Quaternion vs Rotation matrix. I guess I could make overloads for both, but if cspice has a "preferred" or "native" format that we have to do less...

I'm going to add these. I will create a CELBODY3 class, so that I don't break any vtables (not that there are huge amounts of legacy celestial body addons, but still good practice). Scratch that idea, Matt. Going full-in on scope creep.

Are we able to make API calls at the substep level?

Project management is the hardest part of most projects. It probably needs a dedicated core group working on it that has more or less, daily communication over discord/irc, with clear idea of what the goal is and who's doing what.

I'm very confused. Isn't this just google earth. I also don't understand the context here...

You are probably signing up to make it if you're proposing a lot of changes :)

I think I may do this as a seperate pull request but this is a high priority on my list. The current rotation rate necessitates a lot of compromises if you want long-term accuracy. Having neutation would be really nice too.

Nice! Thank you. I will merge this into my branch and hopefully we can get it merged into Orbiter soon. I think the missing textures that I see you've added were one of the last pieces of that. Thank you.

That is not possible on a free return trajectory, at least without a huge MCC or weird trajectories that vastly extend mission times a la Aretmis I.

Searching the forums for a problem (and the solution) that someone else had is a great resource. Especially since we have almost 19 years of searchable forum archives now...

Do we have much information by way of how this was done IRL? If I understand correctly, you're looking to create something like NASSP's RTCC MFD?