Search results

What would we put in the manual? I don't see any point to this. As far as the animations are concerned, the only way to get the coordinates is the open the mesh in something like MeshWizard and see where the rotation point is. It's not something you can put in a manual.

I think all the shuttle animations (air data probes, payload bay doors, landing gear, etc.) need to be updated.

All the reference positions need to be fixed to match the new meshes.

I don't think using OrbiterSound violates the GPL any more than using Orbiter does. I don't see any reason to make OrbiterSound optional. On a totally unrelated note, is anyone able to help fix the animations to work with the new mesh?

If the payload doesn't require any interaction with the shuttle (outside of deployment with the RMS), we can do that already. We should be able to simulate most ISS missions (from the shuttle side, at least) and Hubble deployment.

I think the basic outline is good. Are we going to have multiple GPCs performing the same computations? I think this would slow down the simulation for no real benefit. My thinking is that the partition would be fairly similar to the SimpleGPCSystem class we have now, and would be responsible...

The VC should now be working for the new meshes. I'm still working on the animations and other stuff. It would be helpful if someone could make sure that all the panels are working; I think I fixed all the panels, but I might have missed one. If someone wants to tweak the position of the...

You need to enter MM 106 first (OPS 106 PRO), then move to MM 201. ---------- Post added at 09:12 AM ---------- Previous post was at 09:06 AM ---------- If you're using the STS-107 Entry Interface scenario, the entry DAP is already enabled (the GPCs are in MM 304 and both DAP PBIs are in...

For the OMS pod mission file parameter, what exactly should be specified in the mission file? Should it define the OMS pod texture or the mesh?

Where did you get these scenarios from? The SSU package only includes launch scenarios for STS-1, STS-107, STS-120 and STS-126. There aren't any scenarios for STS-26 or STS-98. I suspect you're using scenarios created for an older version of SSU, which need to be updated to work with SSU V2.0

Do you have the offsets for the other meshes (VC, RMS, etc.) to the main Orbiter mesh?

Just noticed that the DEA in the Ku-band mesh is also split into 3 different groups. Sorry to keep pestering you about these things.

As far as the code is concerned, the only difference is that both groups have to be added to animations instead of only one group. It only becomes a problem if someone is modifying the animations and forgets one of the groups. If it can be fixed easily, it's probably better to merge the groups...

The new mesh works for me too. ---------- Post added at 07:18 PM ---------- Previous post was at 04:18 PM ---------- The Ku_band_DA mesh also has 2 groups named Gimbal_lock_structure and 2 groups named Dish_receiver_supports. Again, this can be handled in code easily if you don't want to...

I can't open the Orbiter mesh in MeshWizard; I get "Run-time error 9: Subscript out of range". For some reason, MeshWizard doesn't seem to like the FUSELAGE and LOX_UMBILICAL_PANEL groups; I'm not sure if this is a problem with MeshWizard or with the new mesh. ---------- Post added at 11:42 AM...

This might be a scenario issue; the shuttle tends to roll when the scenario starts (this is due to an Orbitersim initialization problem). CSS is enabled when the scenario starts, so that's not a problem. ---------- Post added at 11:16 AM ---------- Previous post was at 11:14 AM ----------...

If everything is done, it might be a good idea to check the meshes in so we can work on updating the code to handle the new meshes.

I've uploaded the release to sourceforge, and created a link from Orbithangar to the sourceforge download page.

I've created a tag for the latest revision (rev. 1533), which will be released once the Orbithangar issues are sorted out. In the meantime, we can continue development as before.

Space Shuttle Ultra is an atttempt to create a realistic simulation of the space shuttle. Please read the included SSU Readme First.txt file for installation instructions are required addons. This public alpha release was created from Rev. 1534 of the Space Shuttle Ultra code.