SSU V1.25 Release

[Orbinaut Pete]

I have suffered a serious setback today. Windows refused to boot up so I was forced to revert back to the factory image. Which means that I have lost everything related to SSU, especially the new LC-39 elements.

I don't know if it will be restarted(again!). Right now I don't feel like totally recreating three very complex elements(hardstand and general scenery, FSS, MLP and RSS)

Did you back them up anywhere?

Is there no way at all to retrieve them from your HDD?

 

[DaveS]

Did you back them up anywhere?

Unfortunately not.

Is there no way at all to retrieve them from your HDD?

Don't think so as a re-format is part of the restore sequence.

 

[Urwumpe]

I think it would become smarter to have all development files (including the files for the mesh editors) on the version control. This way such hardware problems can't cause much damage.

I'll take a look if I have some Inkscape graphic files committed, so these don't get lost. Any ideas on how to format the documentation for SSU 1.25?

 

[Donamy]

I'm for that.

 

[Orbinaut Pete]

DaveS:

If you have re-formatted your HDD, then I doubt this will work. But if you want to check to see if anything is recoverable, I use this.

It's free, legal, and easy to use.
www.recuva.com

 

[DaveS]

DaveS:

If you have re-formatted your HDD, then I doubt this will work. But if you want to check to see if anything is recoverable, I use this.

It's free, legal, and easy to use.
www.recuva.com

Thanks for the tip but no joy. The files are lost forever.

 

[Orbinaut Pete]

The files are lost forever.

That's impossible - they must have gone somewhere!:rofl:

Just think - where did you leave them last?
Try looking under the bed - stuff always turns up there!!!:rofl::rofl:

 

[DaveS]

Now back in SSU development shape with everything reinstalled. Will most likely start FSS work tomorrow.

It's going to be a looooooooong road back to where things was.

Best case estimate: A month or so
Realistic case estimate: 2 months or more

 

[Donamy]

That's a real bummer Dave, we'll just have to add that stuff next release.

 

[Urwumpe]

Now back in SSU development shape with everything reinstalled. Will most likely start FSS work tomorrow.

It's going to be a looooooooong road back to where things was.

Best case estimate: A month or so
Realistic case estimate: 2 months or more

Well, we have the meshes now in the SVN, can you maybe make a simplified model of the FSS/RSS, which we could use in some distance, for improving the performance?

This way, we can release with the existing FSS/RSS stuff and can overwrite them later.

 

[DaveS]

Seems like we have a bug in the code after examining a scenario file:

  "PYROS Bp" Switch PYROS Bp: exception thrown

Doesn't cause any CTDs or anything, just that message in the scenario file.

 

[Urwumpe]

Seems like we have a bug in the code after examining a scenario file:

  "PYROS Bp" Switch PYROS Bp: exception thrown

Doesn't cause any CTDs or anything, just that message in the scenario file.

Shouldn't cause a CTD, because the exception got intercepted before it got thrown up through the whole module, but the question is, which kind of uncaught exception it is and which error caused it. I will investigate, the error message bears my handwriting.

 

[Orbinaut Pete]

Guys,

Just a quick question:

As it is now possible to control the SRMS with the RCS controls on the Numpad, does this mean that it will also be possible to control the SRMS with a joystick??

Thanks.

 

[Donamy]

Yes you can.

 

[SiameseCat]

Seems like we have a bug in the code after examining a scenario file:

  "PYROS Bp" Switch PYROS Bp: exception thrown

Doesn't cause any CTDs or anything, just that message in the scenario file.

Shouldn't cause a CTD, because the exception got intercepted before it got thrown up through the whole module, but the question is, which kind of uncaught exception it is and which error caused it. I will investigate, the error message bears my handwriting.

Checked in code that should fix this. IIRC, I added this error message when DaveS was having problems with CTDs.

The exception is being thrown by the BasicSwitch class; the problem (I think) is that usCurrentPosition, which stores the switch position, is not initialized in the constructor, but is used to retrieve the label for the current position.

 

[Donamy]

Were you able to work on the RCS-RMS switch ?

 

[SiameseCat]

Haven't done that yet. Any preferences for the key combination?

 

[Donamy]

Would numlock work ? That way, the light would be an indicator.

 

[DaveS]

Haven't done that yet. Any preferences for the key combination?

How about Ctrl-Numpad Divide? Translation: Enable RMS control only when Orbiter's RCS control's are in the OFF mode?

 

[Urwumpe]

How about Ctrl-Numpad Divide? Translation: Enable RMS control only when Orbiter's RCS control's are in the OFF mode?

Could then be handled over the RCSMode callbacks.