TheShuttleExperience
Well-known member
Are there plans to make every switch in the flight deck work (even if they do not have a function)?
Project Space Shuttle Vessel
- Thread starter GLS
- Start date
GLS
Well-known member
Hmm... not really. There are some that are "working", but they do nothing but waste time during loading and saving. IMO it is a better investment of time to implement the subsystem and/or the GPC software that uses the switches, and implement them only in that process, thus making them (fully) operational.
The v2 update (still a bit in the future) will have the OMS/RCS stuff on panels O7 and O8 working, and that will already be a good chunk of the flight deck.
Tiny_Bob
Addon Developer
is there a higher quality version of the SLF and EDW available somewhere? EDW is also part way underwater.
GLS
Well-known member
Hi there!
There are no changes in SSV to the surface textures in those areas: KSC is the regular (hi-res) terrain, and EDW is from Antelope Valley addon.... what surface elevation resolution are you using? (Launchpad > Options > Planetary effect > Max. resolution level)
Did you install the Orbiter hi-res terrain for Earth, and the Antelope Valley addon? There should be links for those in the Downloads section of the forum. Those make Orbiter much more realistic.
Tiny_Bob
Addon Developer
i should have the high res textures and the antelope valley add on, but maybe orbiter is being weird since i have only one copy of textures. i use the "PlanetTexDir =" line in the orbiter config, since i have 3 installs of orbiter and dont want to have 3 copies of the textures haha.
Max resolution level is set to 19, so that shouldnt be a problem. im betting its some other addon that changed the surface tiles, so a reinstall of my SSV orbiter install might fix it.
EDW is a little wet still
GLS
Well-known member
Does any of the other installations, with the PlanetTexDir change, show the terrain as it should?
Tiny_Bob
Addon Developer
ok in the install where the textures are stored, its very much not right, but the OpenOrbiter install i have works and looks just fine.
GLS
Well-known member
I'm not sure the PlanetTexDir change is a good solution to avoid having several replicas of the large files in the Textures folder...
I have several Orbiter installs, but the hi-res stuff (mostly the Archive folders) is in a separate folder, and I created symbolic links in each installation to point to that folder. This way only the "basic" textures are replicated, and the big files are shared. There should be a thread with instructions for this somewhere in the forum.
I have several Orbiter installs, but the hi-res stuff (mostly the Archive folders) is in a separate folder, and I created symbolic links in each installation to point to that folder. This way only the "basic" textures are replicated, and the big files are shared. There should be a thread with instructions for this somewhere in the forum.
Tiny_Bob
Addon Developer
ill do some research on that and see where i get
Tiny_Bob
Addon Developer
jealous of yall that can get the various payload mods to work, these missions look amazing. Id love to make some of my own "natively" SSV compatible payload, but IDK if @GLS has stuff planned down the pipeline. i know enough about mesh making and cfgs i think to make basic non-animated payloads, but things like the sunshades IDK
GLS
Well-known member
I'm not making payloads* for the shuttle, but only the "NASA parts": upper stages, support structures, etc. So anyone can make the payloads that were launched or, more interestingly, the ones that weren't launched, or even invent new payloads.
Off the top of my head: there was a larger version of COBE that was going to be launched from the shuttle in Vandenberg, and the Spitzer telescope and Mars Observer were originally also shuttle payloads. There are also the military sats: I added the SPDS, so AFP-731 can now be launched (good luck knowing how it looked), there is also the DSCS pair from 51-J, and there is always the capability to make a KH-11 retrieval mission.
So there are dozens of payloads that can already be launched from SSV. The required work is mostly modelling and mission planning, as SSV has no shuttle-payload electrical or communications interface to complicate the payload. BTW, discrete commands can be sent to a payload from the upper stages, as explained in the manual. If there is "payload making information" missing in the manual, let me know.
Looking forward, I can say there is a high chance that we are going to have the PAMs "soon", as in before v2.0, and if I'm lucky even an improved IUS. I might even loose my mind and improve the Centaur in the process. But then, all this might require major changes that break compatibility, and so it could have to wait for v2.0... I don't yet.
*) as a separate project, I have the 3 flown probes (Galileo, Magellan and Ulysses) mostly done, for several years now, but SSV (and now Orbiter) is sucking up all of my free time. That and some Orbiter limitations mean that it is not progressing as fast as it should, but eventually it will get done.
GLS
Well-known member
And the never flown PAM-A.Yes, yes, PAM-D's would be goodso that those PAM entries in editor's combo boxes are not greyed out anymore...
Tiny_Bob
Addon Developer
GLS
Well-known member
From what I know, the PAM-A did not have sunshields
Tiny_Bob
Addon Developer
GLS
Well-known member
Yes, that is part of the cradle.
