Project Ultimate Project ISS for Orbiter

[The Aviator]

In our early project we were using the Quest from Mustard site, but now I think we will model another Quest module. Do you think you can work on the existing Quest for now and then modify the new one with the work you did on the older one?

 

[Woo482]

yes I will start to do It in a few days when you get a mesh all I need to do is change the name of the mesh we are using

 

[Orbinaut Pete]

Hi all,

Firstly, i am thrilled that this project is starting to get underway, and that so many developers have deicided to help with the project.


However, before everyone goes racing ahead developing things, what I want to do first is to develop a proper plan of what needs to be done, and who will do it, so that people do not waste time developing things that have already been done/are already been worked on/are not needed.


The key to a successful project is what i call the three C's, dont forget them:

Co-operation: Everyone must co-operate with each other and not work against each other

Collaboration: Everyone must collaborate with each other and not hold anything back

Commitment: Everyone must commit to this project and do the best job possible.


Me and The Aviator have assumed the roles of Project Managers, This is because, 1, we cannot bring much else to the project, and 2, because we will be the only ones with enough time to do it, as we will not be doing much else. We will be fair and are open to suggestions/ideas/comments, but the final decisions will rest with us.


I have devised a skill level system to determine who will be best suited to do which task. Please could all developers respond with what level you think you are:

1= No real skills with Orbiter and little knowledge of spaceflight.

2= Limited skills with Orbiter .scn's and .cfg' files only. OK/Good knowledge of spaceflight.

3= Good skills with Orbiter .tex and .msh files, good knowledge of spaceflight and spaceflight systems

4= C++ skills and above. Good skills in all areas of Orbiter and excellent knowledge of spaceflight systems.

5= Higher math capability. Excellent knowledge and skills with Orbiter and excellent knowlegde of science of spaceflight systems.

Me and The Aviator are level 2.

Once everybody has responded with their level, the next step wil be to compile a full list of all tasks that need to be done, then give each task a required skill level. Then we can deicide who will do what, and development can begin. I want to create different "departments" i.e., a Modules department, an Animations department, a VC department etc. All departments must CO-OPERATE WITH EACH OTHER!!!!
Once plan is complete, I will start a new thread titled "Project ISS Ultimate for Orbiter" All development news will be posted there.

So far, developers I know to be involved are:

RussH
Unussapiens
Thorton
Donamy
Woo482
Josh B (helping RussH with code)
______________________________________________________________
Idea:

This will require people with skills outside of Orbiter:

I want to create an open source website for the project, for information, and so that people can help us if needed. Eventually we will release via the site. I want to create a logo and a colour scheme for the project. Anyone with skills in webdesign, or anyone who can offer hosting, post below. I want to create a "Publicity" department to handle this sort of thing.
______________________________________________________________

I cant stress enough the importance of planning and of co-operation. Without it, the project will not succeed.


Finally, Thorton, are you sure that Node 3 will be on the side of Unity? Im pretty sure it will be underneath - see: http://www.nasa.gov/mission_pages/station/structure/ISS_Assembly_Art.html

 

[Russ_H]

I am committed to this project and I think with the leadership that The Aviator and Orbinaut Pete have shown will help us complete this project.

I think setting goals for the project is a good idea we need to set scope and then not add new systems or ideas to the plan. We can keep track of all new Ideas and then when we plan the next set of goals we can use the new ideas.

I have ok C++ skills and can code dll's that run clean in orbiter. I am a new programmer so I have a lot to learn.

My modeling and uv-mapping skills are close to professional.
I am not that good at texturing but I can do it.

Russ

 

[Thorton]

level 3, good modeling and texturing skills

Finally, Thorton, are you sure that Node 3 will be on the side of Unity? Im pretty sure it will be underneath - see: http://www.nasa.gov/mission_pages/st...embly_Art.html

This is obsolete images, it was decided move Node 3, because of problems with MLM, which can't be copmplete in time (end of 2010).

About planning, I suppose we should start from first module (Zarja)& ISS configuration and then move consistently, from one module (confuguration) toanother.

 

[Kyle]

This is great that the Orbiter community can come together and build a great addon! I was on the SSM2007 community and they don't do anything. Also, if you need someone to work the Scenario folder, I'm your guy.

 

[The Aviator]

About planning, I suppose we should start from first module (Zarja)& ISS configuration and then move consistently, from one module (confuguration) toanother.

This was my idea. So, for now, you are alone in the modules exteriors department. So you can manage things as you want. Then, when you finish with them, we can pass them to the interiors and VC department to make the interiors, then pass it to animations department. It could be a base idea, but for now everyone can keep on working what he is doing. Just start make something, then we can organize us better.
Keep on working guys... I think we are on the right way!


-----Posted Added-----


And Thorton, can you please tell us what are the modules you have ready?

 

[unussapiens]

Yeah, I have a mesh for Quest. It's currently untextured, but I should be able to fix that within a couple of weeks (Maybe even by next weekend). I'll also try to get a VC (textures for that are easy).

 

[The Aviator]

Unussapiens, are you using pictures of the real module as a base for making mesh and textures?

 

[Donamy]

Donamy told me in a pm that he has some VC stuff build for the Iss and that we could use this for our project.

Donamy can you give us an inventory of what you have?

Thanks
Russ

Russ,

Everything I have, has been released in my ISS experience and STS-123 and STS-124 payloads addons.

Destiny with VC
Kibo with VC and RMS
SSRMS
DEXTRE with palets
CETA carts
MBS
Harmony no VC
Columbus no VC
posable EVA astronauts
and more ...

 

[Thorton]

And Thorton, can you please tell us what are the modules you have ready?

Almost all of them. Zarya is almost ready, i need change location of docking target only.

Donamy, could i use some of your textures from sts-122 addon?


-----Posted Added-----


Also I suppose it would be better if somebody, whowill make interior of modules send me interior mesh and textures then i could merge it in one model then send to animation department.

 

[unussapiens]

Skills:

I can model well, and can get great textures if I can get good photos. I can make basic textures from scratch, but they won't be as good.

I am a proficient programmer in python and I plan on transitioning to C++ soon, so I will be able to help.

I am quite proficient mathematically and can learn new concepts quickly. I have a basic understanding of the spacecraft systems and plan to learn a lot more about them.

I am currently attempting to make my Quest mesh useable. atm it's just a basic mesh and config file, but you'll be able to use it for making scenarios, even it does look like c**p.

 

[Thorton]

unussapiens, i have Quest mesh, can you make interior and send it to me, i'll combine them, send to Russ H and he make dll.

 

[markl316]

I'm a 2. I can play orbiter very well, use scenario editor (I'm very creative) and I can do simple config files.
I'm very good at working with other people too. :beach:

 

[unussapiens]

Thorton: It's probably easiest if you send me what you have so I can make sure the VC will fit properly. Which program do you use for modelling? I can probably open it, but I'd like to know anyway. Email me at [email protected].

 

[Donamy]

Donamy, could i use some of your textures from sts-122 addon?

Sure, use whatever you need.

 

[unussapiens]

Some documents that may be useful: http://www.nasa.gov/mission_pages/station/news/ISS_Reference_Guide.html

 

[The Aviator]

Hi all, ISS Team!
As I can see, we have several people working on Quest module. I think it could be a good idea to make this as first complete module and see the results...
I think that the better way is to complete the exteriors model first, then make interiors and finally animations. While doing this work, woo482 will work on making the module UMMU compatible, to allow EVA from Quest. I think the most important thing is to make it close to the real one as possible. So we can use NASA pictures and documents as a base to work. Ok people, I think we have liftoff!

 

[Master of Blades]

This sounds intresting... By your standards, I'm a level 2, capable of creating scenario files (without using the scenario editor if so is required), can do most things in Orbiter. I am also able to create webpages, graphical designs for mentioned webpages etc

 

[Russ_H]

work plan

I think it could be a good idea to make this as first complete module and see the results...

AS soon as the model mesh is done send it to me. I do not need the vc to start working. The model mesh and vc are loaded each with code and only rendered when used.

The model will then go to the vc person to be used to make the vc.
after the vc is done I can add it.

Note: all parts must be named I do not use numbsrs in the code I use names. With c++ a header file is made using the mesh file and each named part is given a number. The program for a module knows the group number for that mesh by it's name. so we would name a panel of switches some thing like this.

c1= column 1 r1 = row 1
Switch_c1_r1 or actual name the switch for what it does. switch_deploy_hatch_001.

ok now the reason for this is when we make a mesh file and just use the numbers if we go back and work on the model the numbers may change. By using names when the numbers change the names stay the same. This way if we need to fix something on the mesh we can and not have to redo work. This is a real fast way to work and we do not have to have a completed mesh to start coding.

While doing this work, woo482 will work on making the module UMMU compatible

I do not want to take work away from woo482 but I can code the mmu stuff in the main dll and make it work with a vc or 2d panel.

If woo482 would like I can set up an svn server so he can work on the c++ code with me. If he can do the ummu stuff he can work in the c++ code and set up the same numbers. Also there is so much more he can do in the code if he understands the numbers like I think he does.

woo482 this would be hard to start with but if you can set up a ummu I know you can work in the code with me. Its the same numbers and I would show you where to put them.

Russ


-----Posted Added-----

Skills:
I am a proficient programmer in python and I plan on transitioning to C++ soon, so I will be able to help.

I am quite proficient mathematically and can learn new concepts quickly. I have a basic understanding of the spacecraft systems and plan to learn a lot more about them.

Nick It would also be a good idea if you could work in our code with us.
you will be a better programmer then me when you get started.

An svn server is free and it is a way we can all work on the code at the same time. it also backs up our work as we go.

Russ


-----Posted Added-----


We can also have sound where we want. We will need a good sound guy to make all the wav files.

Russ


-----Posted Added-----
Work update

I just received the quest mesh from Thorton and it's nice model of high quality.

Thank you for your hard work on this model.

I should have a working dll within a day or 2 for this