Search results

I've checked in a fairly major update of the SSU manual. Most of the changes are related to technical details, but I've also added an Installation Instructions section.

The MDU edgekey menu issue should be fixed now. It turned out to be related to the code to load/save the VC position from the scenario file.

Checked this in.

Wow, I didn't know you had this. Do you have any of the other sections of the SODB?

I think that's just a confusing variable name. The velocity used in the ascent guidance code is the velocity relative to the center of the Earth, or Vi.

I've checked in fixed versions of the VS 2013 files.

That's a bug; the rudder should only be manually controllable if the FLT CNTLR PWR switch in on.

Is there a reason why we're doing it this way? Now that all the displays have been moved to the MDU, it seems like it would make more sense for the MDU to do everything, and just use CRTMFD to indicate when a button is pushed. Does anyone know what the mass of the ODS and airlock is? I'm...

I just tried switching from the trunk to the Centaur branch and back, and I didn't get any tree conflicts.

This has been checked in. I'm working on adding mission file entries which will hide/show the appropriate bridge rails.

I can fix ticket 49. For the moment, we can just iterate over all subsystems and add their mass to the shuttle mass. I'll also take a look at ticket 77 if I have the time.

If you zoom in on the broken displays, they start working. I've posted some screenshots on the D3D9 thread (http://www.orbiter-forum.com/showthread.php?p=491763&postcount=2962). I'm not sure what's happening here, but I think it might be related to some of the D3D9 changes. ---------- Post...

The R15 beta 2 seems to cause problems for SSU. Some of the displays only work when the camera is zoomed in; at large FOV, the original texture is shown. I've attached screenshots showing how the displays change depending on the FOV. All the affected displays use oapiBlt to copy the digits onto...

The OMS/RCS gauges on Panel O3 don't work either.

Using the RC15 beta 2, I haven't had any problems.

Is there a reason why the CentaurG meshes are missing? The code includes support for the Centaur G and the Centaur G Prime.

I can do that.

This has been checked in to SF. The D3D9 material settings had to be changed a bit; it would be nice if someone could take a look and make sure everything is okay.

Sounds good to me too.

We can comment out the code to change the ET texture at SRB sep, and re-enable it once we have working textures. GLS, can you post a list of the scenarios with pad offset problems? The shuttle should be attached to the MLP (and the MLP should be attached to the pad), so there shouldn't be any...