SSU Development Thread (2.0 to 3.0)

[SiameseCat]

Yes ([ame="http://orbithangar.com/searchid.php?ID=6389"]Space Shuttle Ultra V2.0[/ame])

 

[Donamy]

That'e the one I was talking about, it's horrible.

 

[SiameseCat]

That'e the one I was talking about, it's horrible.

What's wrong with it?

 

[Donamy]

No RMS VC, old arm and orbiter mesh, no latching of payloads, a bunch of stuff that worked before the sizing and moving of the mesh.

 

[SiameseCat]

Let me ask again: have you actually tried using this version? I just downloaded and extracted it. The RMS works. Payload latching works. I don't know what you're talking about.

 

[Donamy]

Maybe I shoould ask you something. Which scenario ? :facepalm:

---------- Post added at 02:05 AM ---------- Previous post was at 01:53 AM ----------

Was using a scenario that used the default orbiter, don't know how that got into the SSU folder.

OK, tried it again, with and orbiting scenario. Everything seems to work except for some distortion issues with the startrackers, and the fron cockpit textures are not there. I will kepp testing.

 

[SiameseCat]

Was using a scenario that used the default orbiter, don't know how that got into the SSU folder.

That explains a lot. What scenario is this? We should delete it if it's still in the SVN repository.

 

[Donamy]

If I could load this mesh into AC3D, I could fix it, but it is corrupted. :shrug:

---------- Post added at 03:00 AM ---------- Previous post was at 02:53 AM ----------

I think that scenario is a hold over from 1.25, not in the SSU 2.0 file.

 

[Wolf]

Two questions:

1) Is GPC OPS1 implemented and working in SSU 2.0 release?

2) I know you guys are currently busy with other priorities in the SSU developement but would it be possible to have in the near future a more detailed documentation?

 

[Urwumpe]

Two questions:
1) Is GPC OPS1 implemented and working in SSU 2.0 release?

Which OPS 1? There is no simple OPS1 in the Space Shuttle.

Do you mean PASS OPS G1? So the component software of it:

OPS 1011 "XXXXXX TRAJ" - partially implemented, not every feature
OPS 1041 "XXXXXX MNVR" - implemented

DISP 18 "GNC SYS SUMM 1" - partially implemented
SPEC 23 "RCS" - not implemented
SPEC 50 "HORIZ SIT" - not implemented
SPEC 51 "OVERRIDE" - not implemented
SPEC 53 "CONTROLS" - not implemented

Also OPS 0 is completely missing.

2) I know you guys are currently busy with other priorities in the SSU developement but would it be possible to have in the near future a more detailed documentation?

Is a priority task. During development, we refer to the Shuttle documentation because we don't want to deviate from it and it is really the best documentation possible, so you can be sure that the original FDF will remain to be reference.

But not everything is told by the NASA documents (especially how to use it in Orbiter) and not everything is really best described by NASA documents.

 

[STS]

Is this thread updated? I think not. Would be very helpful for new users to have it updated with the last public stable release information (2.0) and the last not stable development revission (commit?).

http://orbiter-forum.com/showthread.php?t=15598

Also, I dont know if this is very correct (asking this here), but since I use SSU to its maximum potential, if you need some kind of betatester-alphatester (for the release candidates to the stable release), I am in.

Thank you.

 

[Urwumpe]

OK, looks like some scenarios are broken.

Also, I get a crash when I use CRT MFD to display a PFD display (after the display was already rendered)

From my testing here, scenarios that fail to load:

Scenario | Log message
Launch Test| (Just CTD)
Testing Scenarios/CT-1 road test|D3D9ClientSurface::CopyRect() Failed
Testing scenarios/EDW 22 Final Approach|!!! Abnormal Program Termination !!!
Testing scenarios/EDW 22 TAEM|!!! Abnormal Program Termination !!!
Testing scenarios/MLP roll-off|**** WARNING: Mesh not found: .\Meshes\SSU\KSC_SSMEPF.msh
Testing scenarios/SLC-6 Launch test|!!! Abnormal Program Termination !!!
Testing scenarios/STS-1 T-45s|**** WARNING: Mesh not found: .\Meshes\SSU\KSC_SSMEPF.msh
Testing scenarios/STS-126 T-1m|**** WARNING: Mesh not found: .\Meshes\SSU\KSC_SSMEPF.msh

Payload Latch Test and rendezvous test are outdated.

The ".\Meshes\SSU\KSC_SSMEPF.msh" disturbs me a bit - do we have an external dependency that is undocumented? And do we really need this dependency for SSU? It is just a base mesh that is missing - why does a base mesh break our test scenarios?

 

[GLS]

Is GPC OPS1 implemented and working in SSU 2.0 release?

To complement Urwumpe's answer: currently we have the full ascent working (only in AUTO), with no aborts supported, and partial pre-launch. Hopefully we'll have some support for aborts after the mission editor is done.

Is this thread updated? I think not. Would be very helpful for new users to have it updated with the last public stable release information (2.0) and the last not stable development revission (commit?).

http://orbiter-forum.com/showthread.php?t=15598

Also, I dont know if this is very correct (asking this here), but since I use SSU to its maximum potential, if you need some kind of betatester-alphatester (for the release candidates to the stable release), I am in.

Thank you.

I'll can't edit that... anyway my changes would be:
PASS G1 software: Partially implemented
PASS G2 software: Partially implemented
PASS G3 software: Partially implemented
PASS G8 software: Partially implemented
Main Propulsion System(MPS): Partially completed, not under active development

---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------

OK, looks like the Launch Test Scenario is broken.

Also, I get a crash when I use CRT MFD to display a PFD display (after the display was already rendered)

Hmm, last time I checked it was all working.... give me 1 or 2h to get home and I'll check that

 

[DaveS]

The ".\Meshes\SSU\KSC_SSMEPF.msh" disturbs me a bit - do we have an external dependency that is undocumented? And do we really need this dependency for SSU? It is just a base mesh that is missing - why does a base mesh break our test scenarios?

Not a external dependency, just a miss by me to check in the mesh+texture. The mesh+texture has been checked into the trunk. And it is SOP for a CTD to occur when a mesh can't be loaded.

 

[SiameseCat]

OK, looks like some scenarios are broken.

Also, I get a crash when I use CRT MFD to display a PFD display (after the display was already rendered)

From my testing here, scenarios that fail to load:

Scenario | Log message
Launch Test| (Just CTD)
Testing Scenarios/CT-1 road test|D3D9ClientSurface::CopyRect() Failed
Testing scenarios/EDW 22 Final Approach|!!! Abnormal Program Termination !!!
Testing scenarios/EDW 22 TAEM|!!! Abnormal Program Termination !!!
Testing scenarios/MLP roll-off|**** WARNING: Mesh not found: .\Meshes\SSU\KSC_SSMEPF.msh
Testing scenarios/SLC-6 Launch test|!!! Abnormal Program Termination !!!
Testing scenarios/STS-1 T-45s|**** WARNING: Mesh not found: .\Meshes\SSU\KSC_SSMEPF.msh
Testing scenarios/STS-126 T-1m|**** WARNING: Mesh not found: .\Meshes\SSU\KSC_SSMEPF.msh

Payload Latch Test and rendezvous test are outdated.

The ".\Meshes\SSU\KSC_SSMEPF.msh" disturbs me a bit - do we have an external dependency that is undocumented? And do we really need this dependency for SSU? It is just a base mesh that is missing - why does a base mesh break our test scenarios?

What branch are you using? I haven't checked all the scenarios you listed, but at least some of them work for me (using either the default or Mesh-Rev1463 branches).

 

[DaveS]

Hmm, last time I checked it was all working.... give me 1 or 2h to get home and I'll check that

Same here, no issues with the PFDs. Loads great and works the same.

 

[Urwumpe]

What branch are you using? I haven't checked all the scenarios you listed, but at least some of them work for me (using either the default or Mesh-Rev1463 branches).

Trunk, compiled under VC++ 2013.

Will not work on a branch until the next release is getting finished.

 

[Urwumpe]

Found out that the SSU_Pad project only compiles in "Debug" configuration, not in release configuration. Will fix this. Please make sure that it also compiles in "Release" configuration, before you commit.

 

[DaveS]

Found out that the SSU_Pad project only compiles in "Debug" configuration, not in release configuration. Will fix this. Please make sure that it also compiles in "Release" configuration, before you commit.

Weird. Just did a successful rebuild of the entire solution in Release configuration. Using the 2010 version though, are you using another version?

 

[Urwumpe]

Weird. Just did a successful rebuild of the entire solution in Release configuration. Using the 2010 version though, are you using another version?

I use Visual Studio 2013 here. Get a strange linker error here, that I can't yet resolve, about not finding the standard hypot function.

Still, as long as such errors exist in our trunk, we can't say "Get the sources and compile them" to people who are less skilled with the VC++ !!!!!