Space Shuttle Ultra 1.25 Revision B development

[SiameseCat]

If I remember, I'll post the compiled binaries on the sourceforge page in a few days (once we're certain there aren't any problems from the changes Urwumpe and I have been making). If you have Visual Studio, compiling SSU should just involve opening the project, selecting Release mode and clicking 'Build Solution'.

 

[Urwumpe]

Still the wiki is not a bad idea, but one alone can't enter the data. Compilation is pretty simple for us. Also the lua extension should be documented there then. And we could keep track of which features are already done and which need further work.

 

[DaveS]

Still the wiki is not a bad idea, but one alone can't enter the data. Compilation is pretty simple for us. Also the lua extension should be documented there then. And we could keep track of which features are already done and which need further work.

Can anyone in the project start the wiki on SF or does it require a project admin?

 

[Urwumpe]

Can anyone in the project start the wiki on SF or does it require a project admin?

AFAIR, just a single project admin needs to create a ticket so we get a MediaWiki provided, but entering the data is what takes effort.

 

[orb]

AFAIR, just a single project admin needs to create a ticket so we get a MediaWiki provided, but entering the data is what takes effort.

I think that after changes to SF one and half years ago members additionally need permissions granted by a project admin to edit the MediaWiki. Before those changes, anyone (not even a project member) could edit it, but last time I tried to edit a wiki page in a project where I'm a developer (though not active lately), I couldn't, because I had no appropriate permissions (but still I could commit SVN and upload releases).

 

[DaveS]

AFAIR, just a single project admin needs to create a ticket so we get a MediaWiki provided, but entering the data is what takes effort.

Maybe we could take one section each? I could tackle the KSC section and later when we support it, VAFB.

 

[Urwumpe]

I think that after changes to SF one and half years ago members additionally need permissions granted by a project admin to edit the MediaWiki. Before those changes, anyone (not even a project member) could edit it, but last time I tried to edit a wiki page in a project where I'm a developer (though not active lately), I couldn't, because I had no appropriate permissions (but still I could commit SVN and upload releases).

Yes, that is usual there.

Maybe we could take one section each? I could tackle the KSC section and later when we support it, VAFB.

OK, I could then maybe document those subsystems that I implement, like the MDMs and the Ku Band Antenna.

Who wants to document LibUltra?

---------- Post added at 11:32 AM ---------- Previous post was at 11:04 AM ----------

You can find the wiki here:

https://sourceforge.net/apps/mediawiki/shuttleultra/index.php?title=Main_Page

Who wants to get editing privileges?

 

[DaveS]

You can find the wiki here:

https://sourceforge.net/apps/mediawiki/shuttleultra/index.php?title=Main_Page

Who wants to get editing privileges?

Except me?

 

[Urwumpe]

Except me?

Not yet sure if we need even to grant privileges there, looks like a normal mediawiki from here.

Something different: Anybody artistic volunteering for providing a good looking homepage for our sourceforge project?

 

[orb]

Not yet sure if we need even to grant privileges there, looks like a normal mediawiki from here.

I was wrong with user privileges being set for MediaWiki. I just checked it on a project where I'm a member. It depends on group assignment of the user:

The action you have requested is limited to users in one of the groups: editor, admin.

 

[Urwumpe]

Can somebody also look at separating the middeck panels for getting the vectors collected?

---------- Post added at 02:48 PM ---------- Previous post was at 02:10 PM ----------

Does somebody know how many AC motors each MCA controls? I currently look at how to structure it properly, if I know a maximum number of motors, I can limit in how many paths I need to split the internal AC bus.

Currently, I need for each AC motor two hybrid relays (deploy/stow), and a single contactor for providing AC power to the MCA (controlled for example by PL BAY MECH PWR SYS 1 & 2).

---------- Post added at 05:03 PM ---------- Previous post was at 02:48 PM ----------

BTW: Does somebody know how to program a nice small explosion effect? :lol:

Quote from the Operational limits on performing the DA gimbal wiggle test with a stowed DA: "Possible safety hazard. The DA gimbal motors are not explosion proof."

 

[Urwumpe]

Donamy: Can you make the signal strength meter appear a bit curved, like the pressure meters on the forward overhead panels?

http://images.jsc.nasa.gov/lucenewe...page=true&photoId=STS046-03-021&hitsperpage=5

I could then use the same code for it.

 

[Donamy]

I'll see what I can do

 

[DaveS]

Donamy: Can you make the signal strength meter appear a bit curved, like the pressure meters on the forward overhead panels?

http://images.jsc.nasa.gov/lucenewe...page=true&photoId=STS046-03-021&hitsperpage=5

I could then use the same code for it.

I guess the same request goes for the RMS speed indicator on A8U as it is of the same design. BTW, anyone know which font is used on the Standard Switch Panels that hold payload specific switches and tb's?

 

[Urwumpe]

I guess the same request goes for the RMS speed indicator on A8U as it is of the same design. BTW, anyone know which font is used on the Standard Switch Panels that hold payload specific switches and tb's?

Good question. I have only the font standards for flight data files, I would suggest it is a standard font for aerospace projects. Maybe Helvetica.

 

[SiameseCat]

One other issue I've seen is that, when the Orbiter shutdown method is set to 'De-allocate memory and display launchpad dialog', Orbiter doesn't shutdown, but just displays 'Please wait while Orbiter is closing down the simulation session'. This only occurs in scenarios with SSU. I suspect this has something to do with the Lua code, because this problem only appeared recently.

 

[Donamy]

Is it a problem ?

 

[DaveS]

I'm just thinking here. Any one of you up to working on a generic "ASE-module" that would allow somone to easily make a ASE that could be integrated into SSU? The layout would resemble Spacecraft3.dll but instead of handling just about any spacecraft, it would only deal with ASEs.

Panels/systems could be handled like in Radu094's only Systems and Panels SDK, if any of you remember that one. Here's a link to a version (1.7) on Orbit Hangar: [ame="http://www.orbithangar.com/searchid.php?ID=1898"]SPSDK 1.7[/ame]

 

[Urwumpe]

You mean Airborne Support Equipment?

Can be done, but I think we would get ahead faster by just using a standard framework for producing such DLLs.

 

[DaveS]

You mean Airborne Support Equipment?

Yes.

Can be done, but I think we would get ahead faster by just using a standard framework for producing such DLLs.

I was just suggesting a layout example. I think by going this route we'll have an easier time making the ASEs. And you guys can concentrate on the more important shuttle systems.