Support STS-127 Launch scenarios for 7/15/09

Check my scenario. I don't have the Jem:jem. It's still not working for me. Any help?

I tried your scenario and it works for me. Definitely:
1. Post your orbiter.log after it crashes.
2. Start with only JEM_BUS, as Donamy said above. If that works,
add in vessels, one at a time, according to what is attached/docked to what,
and see where it goes south.
 
at risk of seeming too succinct and too eureka-ish I will post this again. If no other reason because it just works.... IT WORKS... so do your install like this and be rid of issues with shuttle fleet... If you want any other vessels on orbiter make a separate installation for those and keep this magnificent STS environment pristine and isolated. Enhancements can be made but only with great care not to replace .msh, .ini and .cfg files. So forgiveme, but here it is again.
 

Attachments

  • definitive install sequence.jpg
    definitive install sequence.jpg
    139.1 KB · Views: 7
at risk of seeming too succinct and too eureka-ish I will post this again. If no other reason because it just works.... IT WORKS... so do your install like this and be rid of issues with shuttle fleet... If you want any other vessels on orbiter make a separate installation for those and keep this magnificent STS environment pristine and isolated. Enhancements can be made but only with great care not to replace .msh, .ini and .cfg files. So forgiveme, but here it is again.

Following STS-127 I will be issuing newer versions of the Expansion pack which will include the STS-125 and STS-127, so be warned that this will be out of date then. The individual packages for 125 & 127 will be removed from Orbithangar when the newer version expansion pack is released, and I will probably incorporate the Shuttle Fleet service pack into a new full shuttle fleet package at that time.

Dave

p.s., I've noticed lately that when helping others correct their problems, more often than not they haven't followed the directions I've provided. And, I'm assuming that when they correct their difficulties, they rarely come back and post that the problem is solved.
 
When you change those we will have a round at it again and we'll figure it out again. It is definetly worth it.

But Something that might help could be to direct users to ignore all documents included on the addons required... ...INSTEAD to follow and trust "The Official STS Fleet Installation" manual... And publish the latest version with each new update.
Then with updates that require meshes or textures make us DL the whole section with every update... For .ini, ,.cfg and .scn we can handle the small DL.

I ran into problems when I read all the docs on every addon and tried to configure each to work on all of the scenarios provided with said addon... With strange results (STS-127 updt revealed those)
Then, with a serious tudh to the head, I realized that those scenarios were not part of the fleet world and I, really, had no use for.
Eh... 2 cents.
But please dont be discouraged.
This Shuttle Fleet and SSU ( with all its own issues ) and NASSPmake this Orbiter sim be a very serious thing.
Thank you again.
 
STS-128 is just about ready for release. :P
 
Back
Top