Search results

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?

No, unfortunately. The client connects to Orbiter through pointers and function calls, not over TCP. Would be a cool idea though. Not by any means easy to impliment....

You could also disable the graphics client.

This is correct. Orbiter 2016 introduced this feature, which allows things like docked stages and full CoM and MoI calculations with composite vessels.

What tool are you using to convert?

Is there a stack trace?

Is something in SSV passing a null pointer to a D3D9 function that then is being called eith the null pointer as an argument? surface handle, etc? The crash might not be occurring  in an SSV function, but it can still be  caused by one. These are hard ones to track down I'd recommend finding...

In my experience random crashes are caused most offen by pointers that: Have the proper checks for being null. and Aren't being set to null when an object is deleted or first created. Does it ever crash when  closing orbiter?

Having recently made some surface and elevation tiles, I wanted to add a few lessons here to this. Elevation is stored as an INT16 so the maximum number of elevation steps in any given global heightmap is 2^16 = 65536(m) It is possible, if ElevationResolution is set incorrectly, to cause...