Flight Question Soyuz TMA new issue

[n122vu]

Lately when I attempt the Soyuz to ISS mission from Clive Bradbury's tutorial, I am unable to control the TMA after reaching orbit. I press J twice as Mustard indicates is necessary in order to have 100% fuel (Soyuz Launchers manual), but when I engage main engines, I have no thrust, even after I switch to the Ural and press K to open the solar array. In addition, if I accelerate time, the TMA seems to "fall away" from the Ural as an invisible craft, and switching to the Ural reveals 0% fuel.

I don't remember encountering this in the past when I would attempt to use this vehicle, only since I started trying to fly this tutorial. Am I doing something incorrectly, or is there an issue with my Soyuz installation?

Thanks for any advice.

Regards,
n122vu

 

[n122vu]

FYI, I tried this on a separate installation of Orbiter and get the same result. Pressing J makes the Ural availalbe as a selectable vessel but with 0% fuel, while the SoyuzTMA has 100% fuel but no thrust, even after extending the solar array on Ural.

Starting to get frustrated here. Can anyone help?

**EDIT** Pressing J a second time with either SoyuzTMA or Ural selected does not seem to change the situation. Still no fuel on one and 100% fuel on the other but no thrust, even though I have main engine sounds...

 

[n122vu]

Anyone?

 

[Fireproof]

how did you triple post?

 

[n122vu]

how did you triple post?

All three posts on different days? Only way I can think of it would let me.

 

[MajorTom]

Man, I really don't know...

I use Soyuz TMA a lot, and never had this problem. I'm not even sure that the TMAJ dummy spacecraft is necessary...I just load up SoyuzTMA on top of my multistage2 launcher and all is well, no fuel problems. Perhaps you should make sure you've got the newest version of multistage2 and spacecraft3?? I'd visit Vinka's site if not sure.

Meanwhile, a workaround: You could simply edit [double-click] your (current state).scn scenario and change the prplevel , aka propellant level, from 0.0 to 1.0, then re-run Orbiter, loading your current state...that should fix your fuel problem. (And if you're having trouble getting to the ISS using Clive's tutorial you could also use this trick to cheat and get more fuel )

Make sure you are changing the prplevel of the ship that uses the module soyuztma, and not "soyuz" or "soyuztmai" which would be other things such as your launch vehicle.

MT

 

[n122vu]

Man, I really don't know...

I use Soyuz TMA a lot, and never had this problem. I'm not even sure that the TMAJ dummy spacecraft is necessary...I just load up SoyuzTMA on top of my multistage2 launcher and all is well, no fuel problems. Perhaps you should make sure you've got the newest version of multistage2 and spacecraft3?? I'd visit Vinka's site if not sure.

Meanwhile, a workaround: You could simply edit [double-click] your (current state).scn scenario and change the prplevel , aka propellant level, from 0.0 to 1.0, then re-run Orbiter, loading your current state...that should fix your fuel problem. (And if you're having trouble getting to the ISS using Clive's tutorial you could also use this trick to cheat and get more fuel )

Make sure you are changing the prplevel of the ship that uses the module soyuztma, and not "soyuz" or "soyuztmai" which would be other things such as your launch vehicle.

MT

Thanks for the reply. I'll check out my spacecraft3 & multistage dll's. It is possible they were overwritten with older versions when installing another addon.

I'll use the workaround in the meantime to continue the tutorial. Had thought about doing that but the analyst in me wanted to figure out what the heck I was doing wrong.

Thanks again,
n122vu

 

[Albinon]

I came across the fuel loss situation in SoyuzTMA. After looking at the code from Dave Henderson, I noticed a timing problem that happens at separation. Dave uses a lot of old orbiter calls in his code. He sets up his old-style clbk functions in his header file and references back to his CVEL code in his .cpp. This seems to lose a step in timing sometimes. This is fixed in MajorTom's beta TMA project.