SSU public release comments/bug reports

Status
Not open for further replies.
That texture shouldn't even be there, it's not used by SSU.
Removed it from the repository. I'm not sure how it and the texture for the S6 truss got there in the first place.

malisle: Try rebuilding the sources as I can run them without any problems. Make sure there's no failed compiles. You should end up with 13 successful builds when the solution has been built.

---------- Post added at 04:14 AM ---------- Previous post was at 03:57 AM ----------

After checking the commit history of PVarray.dds, I found that it and the S6.dds texture was associated with a check in of an S6 mesh back in 2009, probably to simulate the then upcoming STS-119 mission.

I have removed it as it can be found in the ISS A2Z add-on.
 
Whatever it was, it was related to D3D9 R10 client - I managed to pry R11 out of one of my backups and now everything works fine.
 
1) You could do only a single burn using the XXXX MNVR EXEC displays. To be specific, on the setup of the next burn, EXEC doesn't display when T-15 seconds to ignition.

2) All STS-107 scenarios except the launch scenario crash, because of missing config file. I have posted the part of orbiter.log for more details

>>> ERROR: No vessel class configuration file found for:
---------------------------------------------------------------
>>> ERROR: SpaceHAB_RDM
>>> [Vessel::OpenConfigFile | .\Vessel.cpp | 252]
---------------------------------------------------------------
>>> TERMINATING <<<
 
Last edited:
The new textures and meshes look very nice. I am a very new Orbinaut and I fear I have installed SSU incorrectly:

9qp70g3.jpg


It always looks like this, with little bits hanging off in space and the cargo bay door both open and closed. Do you suppose there's an obvious repair?
 
The new textures and meshes look very nice. I am a very new Orbinaut and I fear I have installed SSU incorrectly:


It always looks like this, with little bits hanging off in space and the cargo bay door both open and closed. Do you suppose there's an obvious repair?
This looks like you're mixing the latest checked in meshes/textures with older incompatible modules. This is a NO-GO. If you're using a specific set of pre-built modules (not built by yourself), you need to check out that specific revision ("rev") of the other stuff (configs, meshes, textures etc).
 
This looks like you're mixing the latest checked in meshes/textures with older incompatible modules. This is a NO-GO. If you're using a specific set of pre-built modules (not built by yourself), you need to check out that specific revision ("rev") of the other stuff (configs, meshes, textures etc).

OK, I think I understand how it works now. Thanks much for the reply!
 
If that doesn't - just wait for the regular release as it should be soon.
 
This looks like you're mixing the latest checked in meshes/textures with older incompatible modules. This is a NO-GO. If you're using a specific set of pre-built modules (not built by yourself), you need to check out that specific revision ("rev") of the other stuff (configs, meshes, textures etc).

OK, I tried compiling the most recent modules and was unsuccessful. That's OK. I downloaded the 1357 commit of the meshes/textures and that worked. The cargo bay textures "flash" randomly every couple seconds, but its very functional. Thanks again for your help!
 
Status
Not open for further replies.
Back
Top