Space Shuttle Ultra development thread

Some people do not get that making add-ons take time.
 
Some people do not get that making add-ons take time.

Sorry, i dont make add-ons i dont realise it takes time, but in the next SSU version Donamy or someone can you please put in floodlights for the payload bay, it will be a real help, and you know how theres so much scenarios for final approchs how about, for example, Atlantis Final Aproach (Night). It will be quiet challenging, thats the way i like it.:beach:
 
I think they would have to get their major priorities out of the way before they can get to adding flood lights to the cargo bay. There is a scenario where you land at Edwards Air Force base at night. If you wan to use the Shuttle Fleet, just compare the that scenario file with the one you are about to make and you can probably set up a scenario like you suggested.
 
I think they would have to get their major priorities out of the way before they can get to adding flood lights to the cargo bay. There is a scenario where you land at Edwards Air Force base at night. If you wan to use the Shuttle Fleet, just compare the that scenario file with the one you are about to make and you can probably set up a scenario like you suggested.

You can land a shuttle at Edwards!!!??? Where is this scenario! I've been searching so long to land at Edwards. I'll think of myself as a John Young on STS-1.
 
I don't quite remember what add-on it was from. It was on my old folder for Orbiter. There is a scenario for the Shuttle Fleet where you are in STS-1 and you use AutoFCS to land at Edwards. I will get back to you if I find that mission. Lets lay off the chit-chat because we are getting off-topic, alright?
 
I don't quite remember what add-on it was from. It was on my old folder for Orbiter. There is a scenario for the Shuttle Fleet where you are in STS-1 and you use AutoFCS to land at Edwards. I will get back to you if I find that mission. Lets lay off the chit-chat because we are getting off-topic, alright?

Yeah, but I'm not at rest until SSU does a scenarios for STS-1 with those almost crappy MFDs.
 
Yeah, but I'm not at rest until SSU does a scenarios for STS-1 with those almost crappy MFDs.

I hope you can survive this long time without a heart attack. While STS-1 is planned already, making the old cockpit is moved backwards for a distant future.
 
Better leave it like it is. Maybe a new Orbiter version one day fixes this problem, and switching from VC to generic cockpit could become annoying for the players. After all, we might loose the last VC panel position that way, if we switch to generic cockpit...

It should be easy enough to save the last VC position and use that when switching back to the generic cockpit. Also, during docking, it might be useful to be able to switch between the docking view and the VC with a single keypress.
 
It should be easy enough to save the last VC position and use that when switching back to the generic cockpit. Also, during docking, it might be useful to be able to switch between the docking view and the VC with a single keypress.

I have not yet tried CameraMFD or a "Invented here" solution, but I think we could do even without leaving the aft station for that.

But the docking view is somewhat expected, so something should exist. Is the keybinding "C" already assigned?

EDIT: Can somebody else work on fixing the mouse events for R13L, i just discovered that I can't use meshwizard anymore, looks like the Update to VS2008 broke something.
 
Hey Y'all!
It's been a while since I've been posting in any Orbiter forum but I do have a question. How do you update the space shuttle ultra files to get the new features(smoke, srb exhaust, burnt ET, ect,ect..)?:unsure:
 
Hey Y'all!
It's been a while since I've been posting in any Orbiter forum but I do have a question. How do you update the space shuttle ultra files to get the new features(smoke, srb exhaust, burnt ET, ect,ect..)?:unsure:

The best would be waiting for the next full release.
 
EDIT: Can somebody else work on fixing the mouse events for R13L, i just discovered that I can't use meshwizard anymore, looks like the Update to VS2008 broke something.

I can't code it, but I can give you the positions, if you tell me where you need them.
 
I can't code it, but I can give you the positions, if you tell me where you need them.

The four corners coordinates of the R13L panel. I could also do with only the top left and bottom right coordinates, as it is rectangular.

The switch animations are already fixed and react properly when I work with the dialog.

No news on the bad painting of the talkbacks... it should paint on Talkback.dds according to the current code I have, but it paints on R13L.dds. I suspect I have not yet learned to use VC2008 properly.

EDIT: Enforcing a rebuild by deleting the DLL fixed it. Now the talkbacks are drawn correctly.
 
The top left is X=1.32, Y=2.29, Z=12.56

bottom right is X=1.06, Y=2.12, Z=12.26

Could you send me the working .dll ?
 
There you go, R13L fixed, the labels on the talkbacks could need fixing.

Can somebody also get me the following coordinates. Except one, you can be quite inaccurate, nobody will notice that:

- Launch position seat position of the other Mission specialist on the FD.
- On-Orbit at the right side station.
- On-Orbit at the right side aft station (must be roughly aligned with the COAS)
- On-Orbit at the left side aft station
- On-Orbit at the left side station
- On-Orbit behind the aft station (The inverse of our current MS-1 position).

I could also need the eye position below the COAS.

For the beginning, I will keep the ring structure. My preferred set-up would be making a difference between launch/Entry position and On-Orbit, with a key combination switching between both setups (automatic detection would be rather bad).
 
(automatic detection would be rather bad).
Would it? Make it dependable on OPS mode. If it detects OPS1 or OPS3 in use it will use the launch/entry positions, if it is OPS2 it will use on-orbit positions. Wouldn't that much more transparent to the user?
 
Would it? Make it dependable on OPS mode. If it detects OPS1 or OPS3 in use it will use the launch/entry positions, if it is OPS2 it will use on-orbit positions. Wouldn't that much more transparent to the user?

Well, the unseating happens after the transition to OPS2 and before the transition to OPS3, thats why I thought it would be better to use a different indication of the beginning of on-Orbit operations.
 
I'll get those positions to you ASAP !!

Also when switching to on orbit I could add some clutter such as Sony recorders and laptops and some wires maybe. Maybe use one of the laptops for the docking view through the ODS.
 
Back
Top