SSU Development thread (4.0 to 5.0) [DEVELOPMENT HALTED DUE TIME REQUIREMENTS!]

[GLS]

So what is needed, exactly ?

Well, I'm separating them "by hand", i.e. text editor and some visual help from Blender, but I can only do so much. Panels like C2 or F2-F8 were made in such fashion that my approach doesn't work (or would take days/weeks).
I'm finishing a last panels I can do (probably won't finish today), and the rest is left to the graphics department. After that, the next step is to create a branch so that the vc size can be corrected (easier to do with separate panels).
Also, with separate panels custom versions can be made, like the overhead panels on Columbia...

... and in 15 years or so we could also do the MCDS cockpit. :lol:

 

[Donamy]

Sounds easy enough.

 

[GLS]

Sounds easy enough.

You didn't spend the afternoon re-ordering 134 circuit breakers... :lol:

 

[Donamy]

I think I made them in the first place. :rofl:

 

[DaveS]

Well, I'm separating them "by hand", i.e. text editor and some visual help from Blender, but I can only do so much. Panels like C2 or F2-F8 were made in such fashion that my approach doesn't work (or would take days/weeks).
I'm finishing a last panels I can do (probably won't finish today), and the rest is left to the graphics department. After that, the next step is to create a branch so that the vc size can be corrected (easier to do with separate panels).
Also, with separate panels custom versions can be made, like the overhead panels on Columbia...

... and in 15 years or so we could also do the MCDS cockpit. :lol:

Currently we're missing alot of the aft panels. This should be a complete list of the missing panels:

• R14
• R15
• R16
• R17
• R18
• L13
• L14
• L15
• L16
• L17
• A11
• A12
• A13
• A14
• A15
• A16
• A17

So, we're missing more less half the actual flight deck.

 

[Donamy]

So the other half is all set and working ?

 

[GLS]

Well.... :uhh:
Those missing panels are full of CBs, which we still don't use (but I have created a control for them), so I'd say they are low priority. I'd say add them as needed.

 

[Donamy]

Agreed. What else ?

 

[GLS]

Agreed. What else ?

I remember DaveS posted an image of panel F6 I think, so he has worked on those forward panels... not sure what's the status on his end.
I think I'm on the last panel I can do. I could also do A1U, A1L, A1R, O14, O15 and O16 if someone would separate the guards in there. Another one is R11, which we have a one panel, but is made of 2 parts (R11U and R11L). It probably makes some sense to separate it but, again, that's too much for my tools.

I'm wondering if it wouldn't be better to leave the forward panels alone for now, create the branch and work "new" ones already with the correct size. Not sure how much itch this would cause Urwumpe, as it would mean keeping the panel code (in the trunk) as is for a while.

 

[DaveS]

I remember DaveS posted an image of panel F6 I think, so he has worked on those forward panels... not sure what's the status on his end.

All done really. I would however like some new and more accurate switch guards as well as new clear switch covers for the drag chute and landing gear PBIs. Here's two photos that shows some of the various switches used on the flight deck, including the switch guards:

https://www.dropbox.com/s/ippynflm9gym9y0/switch_guards600.jpg?dl=0
https://www.dropbox.com/s/ztm7cdgrtbm98p0/switches_600.jpg?dl=0

 

[Donamy]

All done really. I would however like some new and more accurate switch guards as well as new clear switch covers for the drag chute and landing gear PBIs.

And how many thousand do you wish to change ?

 

[Urwumpe]

And how many thousand do you wish to change ?

Should be a few dozen, maybe even less than 50... not sure if this makes it better in your eyes than a few thousand. :shrug:

I also think, better looking switch guards are not making the switches behave better. Even a Story Musgrave mesh could be better for realism (And its easier to implement, since there is no hair to animate)

 

[GLS]

My complaint about the switches, levers, CBs, guards, etc, is that there are several "versions" of them. As I went thru the panels I'm saw that the switches on panel A use X points, and the ones on panel B use Y points. Not to mention the textures. Creating one version of each of them (mesh and texture), and then updating each panel would be a good idea to standardize things.

 

[Urwumpe]

About the cryo-indicators on the overhead panel, would it be possible for you to make them vibrate during launch or reentry?

 

[GLS]

About the cryo-indicators on the overhead panel, would it be possible for you to make them vibrate during launch or reentry?

Yes I'd say it's possible to have the mechanical meters wobble. I thought about doing that for their "normal operation" when the value changes by a big amount, when changing the value source for example, and maybe have the needle overshoot and oscillate a bit... but I was doing something else at the time and decided to not do it. As for vibrations during ascent and reentry, we would have to somehow define what exactly are those parts, and how much vibration there is at any moment to then decide on how much wobble there would be... not something at the top of my priority list ATM.

 

[DaveS]

My complaint about the switches, levers, CBs, guards, etc, is that there are several "versions" of them. As I went thru the panels I'm saw that the switches on panel A use X points, and the ones on panel B use Y points. Not to mention the textures. Creating one version of each of them (mesh and texture), and then updating each panel would be a good idea to standardize things.

This what I have done for the new F6 panel. All the switches are clones of each other and share the same texture. This what it is for the moment: https://www.dropbox.com/s/2g68056xa12cqb2/Panel_common.jpg?dl=0

Not much but it will grow once more switches/CBs are using it.

 

[Urwumpe]

Would be a funny feature request. "Macro Mesh files", allowing to define a switch once and then just put copies of the switch everywhere by referring to the macro...

 

[GLS]

Would be a funny feature request. "Macro Mesh files", allowing to define a switch once and then just put copies of the switch everywhere by referring to the macro...

Yeah, that's a good ideia, but I think you might be programming a bit too much... :lol:

 

[Urwumpe]

Yeah, that's a good ideia, but I think you might be programming a bit too much... :lol:

Well, that is why I said funny. It makes no sense, since a good CAD tool can do the same better.

 

[DaveS]

Here's a nice 360° panorama of Discovery's flight deck in very high resolution: http://www.gigapan.com/gigapans/102753