TransX won't save plans

[newps17]

Hello everyone

I am a relative newcomer to the orbiter world and I apologize to the members here if what I have to ask is redundant or already answered. I tried to search the forum and find the answer but I couldn't figure it out.

So, here goes:

I have been using the Capt. CryBaby tutorial to get to Mars. Everything works out just great until I want to save and return to my plan. I followed his exact steps and did exactly as I was told. Whenever I save a flight though, my plan (I just spent hours on getting the Cl. App down as low as I can get it) is not there anymore. Does TransX save the plans or am I missing something critical? Or do you have to stay in the same "session" of Orbiter while doing flights to the planets, etc?

I have been wanting to learn how to do some interplanetary flights and I figured this tutorial is a good way to go and start learning. This is getting frustrating (which is no surprise, it is rocket science!) and I'm eager to be a student of spaceflight.

Any help is much appreciated!

Thanks!!!

 

[Piper]

As long as the TransX MFD is running when you save you should be fine. Are you switching your TransX MFD to something else when you save?

 

[newps17]

No, I'll be in Orbiter then exit to the Orbiter Launchpad and save the current scenario. I'll load the scenario I just saved and TransX will be wiped of the plan. Do you have to load the plan once in TransX? Oh, and TransX is still on the same MFD.

 

[Napes Weaver]

Wow, that is strange...you shouldn't be having this problem newps17. I'm not familiar with the tutorial you mention and I'm doubtful that these suggestions will be of any help, but here goes: First, I'm a little confused about the way you talk about saving your current scenario. (You probably already know) This happens automatically every time you exit and return to the Orbiter launch pad. The way I use TransX is to write down the MJD for departure, return to the launch pad, exit orbiter and open the current scenario with notepad. I then replace the current MJD with the one I've written down. When you do this you should be able to see within the text of the scenario file that the TransX MFD is open and also the changes to it's settings that you have made. At this point simply close the scenario and choose yes to "save current changes" or, if you choose to rename it, take care to save it as a .scn file and not as "name.scn.txt", which is easy to accidentally do. When you restart Orbiter choose current scenario, or whatever you've named it to. Invariably, you will still have to do some fine tunning to your closest approach, but you won't be starting from scratch.
Just as a note (again, I'm not familiar with the tutorial you mentioned) it took me a while to realize two things in particular (I'm not sure why). One: it really helps to run the sim at *10 when adjusting this MFD. Everything just goes much quicker. Two: once you are on your way, you can make small corrections in your course without the manoeuvre mode by simply using your translational thrusters and watching the result in the closest approach field of the TransX MFD.
Hopefully something in this reply will help. Your problem is a real mind teaser. Good luck

 

[agentgonzo]

That's very strange. Can you post the contents of the saved scenario file and I'll take a look at it. I presume that you are using the latest version (though I've not heard of any problems saving with any versions)

 

[fromscrap]

exactly the same problem and one more...

That's very strange. Can you post the contents of the saved scenario file and I'll take a look at it. I presume that you are using the latest version (though I've not heard of any problems saving with any versions)

I used the same tutorial and got the same problem as newps17, but not for the first time... so I don't think there's something wrong especially with the tutorial. I saved my fine tuned HTO (ctrl+s) with two TransX-MFDs open (stages 1:2, 2:2) and this was the only TransX-related contents of my scn file:

BEGIN_MFD Left
TYPE User
MODE TransX
END_MFD

BEGIN_MFD Right
TYPE User
MODE TransX
END_MFD

I guess this is not enough to tell orbiter something about the MFDs' status.

And here's my 2nd TransX problem which might be solved easier. At a certain distance away from earth on the way to mars with
a Cl. App of 20.0K the former stage 1:2 disappeared and stage 2:2 became 1:1, as described in the tutorial. Now, as soon as that happened, the Cl. App changed to 3.5G!

I'd be grateful if someone would possibly post his/her ideas to explain what went wrong.

Cheers,
Chris

(Third problem is that I still don't really know how to handle this forum's editor ;-)).

 

[flying coffin]

I've seen this behavior before. In my case, if the vessel had a space in the name, like "AV020 Centaur", transx would fail to save the plan. If the vessel
was renamed to AV020Centaur, then transx would work fine.

-Chris

 

[fromscrap]

Chris,

thanks for your quick reply.
I flew the DG4, called GL-01 in the scn file - without blanks. But maybe there's some hidden information in that file so here's a complete copy from notepad.
Since I don't know yet how to put it in a frame this is rather long. Sorry.

BEGIN_DESC
Orbiter saved state at T = 1879
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 60247.4017349222
END_ENVIRONMENT

BEGIN_FOCUS
Ship GL-01
END_FOCUS

BEGIN_CAMERA
TARGET GL-01
MODE Cockpit
FOV 90.00
END_CAMERA

BEGIN_HUD
TYPE Orbit
REF AUTO
END_HUD

BEGIN_MFD Left
TYPE User
MODE TransX
END_MFD

BEGIN_MFD Right
TYPE User
MODE TransX
END_MFD

BEGIN_PANEL
END_PANEL


BEGIN_SHIPS
ISSrojectAlpha_ISS
STATUS Orbiting Earth
RPOS -2880920.26 -5665270.71 2191067.14
RVEL -6798.442 3591.091 357.000
AROT 64.89 -16.40 -50.63
VROT 0.03 0.01 0.11
PRPLEVEL 0:1.000
IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
NAVFREQ 0 0
XPDR 466
END
Mir
STATUS Orbiting Earth
RPOS 4709408.81 320625.00 4693998.31
RVEL -5458.760 301.861 5478.415
AROT -29.92 70.18 47.07
IDS 0:540 100 1:542 100 2:544 100
XPDR 482
END
Luna-OB1:Wheel
STATUS Orbiting Moon
RPOS -2182306.95 504831.93 1635.71
RVEL -333.309 -1441.619 -1.961
AROT -0.01 -0.03 32.23
VROT 0.00 0.00 10.00
IDS 0:560 100 1:564 100
XPDR 494
END
GL-01eltaGliderIV
STATUS Orbiting Earth
RPOS -3363763.33 -524162.34 -5633199.01
RVEL 6688.900 -386.053 -3958.330
AROT -173.17 68.45 -88.70
PRPLEVEL 0:0.915 1:0.942 2:0.983
IDS 0:45 100
NAVFREQ 94 524
XPDR 0
;-------------------------- Skin parameters must contain directory name of skin (without space)
MeshSkin spacetech
;-------------------------- Cargo payload must contain name of config file or "none".(see doc)
CargoPayload none
NOSECONE 0 0.00
GEAR 0 0.00
AllDoorsState 0 0.00 0 0.00 0 0.00 0 0.00 0 0.00 0 0.00 0 0 0.00
But1Cockpit 0 0 0 2 2 2 0 2 2 2 2 2 2 2 2 1 1 2 1 1 1 5
But2Cockpit 0 0 0 0 0 0 0 0 2 2 2 2 2 0 1 1 0 0 1 1 0 0
TransEffect 0
LifeBut1State 0 2 1 0 0 2 2 2 2 2 2 2 2 0 3
LevelBatt 100.0002
Emergency_power 10000.0000
VoltageStartBus 0.0000
VoltageGen1 96.2820
VoltageGen2 96.2819
VoltageGenBus 96.0000
O2tankALevel 99.9844
N2tankALevel 100.0000
O2tankBLevel 100.0000
N2tankBLevel 100.0000
CabinO2Level 21.3979
CabinCO2Level 600.0000
CabinTempLevel 21.2000
CabinPressure 14.7000
CabinMoistLevel 36.0000
CabinDustLevel 0.0001
CabinO2Setting 21.4000
CabinTempSetting 21.2000
CabinPressSetting 14.7000
AntennaTarget no_target
O2ConsumptionSetting 6
FuelConsumptionSetting 3
MainenginePower 1
;------------------Crew parameters UMMUCREW Function-Name-Age-CardiacPulse-WeightKg (fonction of Pilot must be: Capt)
NoOneOnBoard 0
NoPilotOnBoard 0
UMMUCREW Capt-Mr_Captain-37-66-78
FailGearFailure 0
FailGearCollapse 0
FailLeftMainEngine 0
FailRightMainEngine 0
FailHoverEngine 0
FailRcs 0
FailSurfaceControl 0
FailComputer 0
FailComputerBlueScreen 0
FailAutopilot 0
FailExtRadiator 0
FailAirbrake 0
FailNoseCone 0
FailCanopy 0
FailAntenna 0
FailLeftTurbo 0
FailRightTurbo 0
FailCargoDoor 0
SpacesuitTimer 0
END
END_SHIPS

BEGIN_ExtMFD
END

There are abundant ships in this file, even one with a smiley. ;-)
I forgot the weirdest thing: sometimes the TransX MFDs are in their appropriate state when an scn is reloaded but most of the time they are not. It's quite erratic.

Chris


-----Post Added-----


...just a few hours later without any changes except that at this time stage 2:2 had turned to 1:1 (shown in both TransX MFDs) as usual and MJD had been changed by me so i didn't have to sit in DG4 for a year to wait for the launch window. You can see from the TransX section that it will work, and it does.
Puzzling.
Forgot to mention it: this is TransX 3.13.

BEGIN_DESC
Orbiter saved state at T = 644717
END_DESC

BEGIN_ENVIRONMENT
System Sol
Date MJD 60595.2579726586
END_ENVIRONMENT

BEGIN_FOCUS
Ship GL-01
END_FOCUS

BEGIN_CAMERA
TARGET GL-01
MODE Cockpit
FOV 90.00
END_CAMERA

BEGIN_HUD
TYPE Orbit
REF AUTO
END_HUD

BEGIN_MFD Left
TYPE User
MODE TransX
Ship GL-01
FNumber 1
Int 2
Orbit True
Vector 140472793618 -2976129.17629 50646379493.7
Vector -11345.6097103 -1.01986254835 31248.1673418
Double 1.32712439955e+020
Double 60595.2579725
Handle Sun
Handle Earth
Handle Mars
Select Target
0 Mars
Autoplan
0 0
Plan type
0 2
Plan
0 0
Plan
0 0
Plan
0 0
Select Minor
0 None
Manoeuvre mode
0 0
Base Orbit
0 0
Prograde vel.
0 0
Man. date
0 60595.2579725
Outward vel.
0 0
Ch. plane vel.
0 0
Intercept with
0 0
Orbits to Icept
0 0
Graph projection
0 0
Scale to view
0 0
Advanced
0 0
Prograde vel.
5 3350.46953112
Eject date
5 60588.9277885
Outward vel.
0 0
Ch. plane vel.
5 0.1421
Finvars
Finish BaseFunction
END_MFD

BEGIN_MFD Right
TYPE User
MODE TransX
END_MFD

BEGIN_PANEL
END_PANEL


BEGIN_SHIPS
ISSrojectAlpha_ISS
STATUS Orbiting Earth
RPOS 6584233.23 -124571.72 -1297566.50
RVEL 268.214 -7425.892 2053.372
AROT -132.04 17.70 82.54
VROT 0.05 0.03 -0.10
PRPLEVEL 0:1.000
IDS 0:588 100 1:586 100 2:584 100 3:582 100 4:580 100
NAVFREQ 0 0
XPDR 466
END
Mir
STATUS Orbiting Earth
RPOS -3045168.02 345411.19 5926082.80
RVEL -6874.527 -261.800 -3508.668
AROT -29.92 70.18 47.07
IDS 0:540 100 1:542 100 2:544 100
XPDR 482
END
Luna-OB1:Wheel
STATUS Orbiting Moon
RPOS 502820.10 2183489.73 4558.87
RVEL -1441.517 331.619 2.400
AROT -0.01 -0.03 60.60
VROT 0.00 0.00 10.00
IDS 0:560 100 1:564 100
XPDR 494
END
GL-01eltaGliderIV
STATUS Orbiting Sun
RPOS 140472793436.93 -2976129.19 50646379993.68
RVEL -11345.610 -1.020 31248.167
AROT -0.02 80.03 -0.02
PRPLEVEL 0:0.881 1:0.930 2:0.983
IDS 0:45 100
NAVFREQ 94 524
XPDR 0
;-------------------------- Skin parameters must contain directory name of skin (without space)
MeshSkin spacetech
;-------------------------- Cargo payload must contain name of config file or "none".(see doc)
CargoPayload none
NOSECONE 0 0.00
GEAR 0 0.00
AllDoorsState 0 0.00 0 0.00 0 0.00 0 0.00 0 0.00 0 0.00 0 0 0.00
But1Cockpit 0 0 0 2 2 2 0 2 2 2 2 2 2 2 2 1 1 2 1 1 1 5
But2Cockpit 0 0 0 0 0 0 0 0 2 2 2 2 2 0 98 1 0 0 1 1 0 0
TransEffect 0
LifeBut1State 0 2 1 0 0 2 2 2 2 2 2 2 2 0 3
LevelBatt 100.0002
Emergency_power 10000.0000
VoltageStartBus 0.0000
VoltageGen1 96.2820
VoltageGen2 96.2819
VoltageGenBus 96.0000
O2tankALevel 99.8011
N2tankALevel 99.9950
O2tankBLevel 100.0000
N2tankBLevel 100.0000
CabinO2Level 21.3979
CabinCO2Level 600.0000
CabinTempLevel 21.2000
CabinPressure 14.7000
CabinMoistLevel 36.0000
CabinDustLevel 0.0001
CabinO2Setting 21.4000
CabinTempSetting 21.2000
CabinPressSetting 14.7000
AntennaTarget no_target
O2ConsumptionSetting 6
FuelConsumptionSetting 3
MainenginePower 1
;------------------Crew parameters UMMUCREW Function-Name-Age-CardiacPulse-WeightKg (fonction of Pilot must be: Capt)
NoOneOnBoard 0
NoPilotOnBoard 0
UMMUCREW Capt-Mr_Captain-37-66-78
FailGearFailure 0
FailGearCollapse 0
FailLeftMainEngine 0
FailRightMainEngine 0
FailHoverEngine 0
FailRcs 0
FailSurfaceControl 0
FailComputer 0
FailComputerBlueScreen 0
FailAutopilot 0
FailExtRadiator 0
FailAirbrake 0
FailNoseCone 0
FailCanopy 0
FailAntenna 0
FailLeftTurbo 0
FailRightTurbo 0
FailCargoDoor 0
SpacesuitTimer 0
END
END_SHIPS

BEGIN_ExtMFD
END

 

[flying coffin]

The way to post the .scn file is wrap the code tag around it.
You can do that with the # icon above when you post.

I'm not sure if your ISS name might have something to do with it or
that character combination triggers a smiley.

 

[cr1]

[offtopic]
Of course, since the

:P

inside

ISS:ProjectAlpha_ISS (right after the first three letters)

triggers the smiley, like this: ISSrojectAlpha_ISS
[/offtopic]

 

[fromscrap]

now... two different transx scn files saved within a minute

first, thanks to the flying coffin - i'll use the #-icon next time, and cr1: there's a parser
in the forum software that exchanges text for smilies, i know. don't like that.

yesterday i paused orbiter (ctrl+p) and saved the current state (ctrl+s) as i usually do.
but then i wasn't sure if i really saved it, so i pressed ctrl+s once again.
definitely no other buttons pressed.
the outcome was two scn files with one of them containing all the transx information
while the other had none. i could see this even before i opened the scns with notepad
from the different file sizes displayed by windows (xp).
the time stamp for both files was the same: 23:34, that's central european time.

i might add that most of the saved scns of this session were correct and that i'll cling
to transx anyway. heading to and arriving at mars is quite an easy job with this mfd.
maybe one day i'll understand the mystery of transx slingshots, too.
by now there are too many questions left to accomplish that task.

chris

 

[Cpt CryBaby]

Sorry in so late on this. Did you ensure there are no spaces in ship names? Have a look at this link from the checklist. I think lots of people just skip over it.

http://www.stillmixtup.com/orbiter/ShipNameSpace.html

This may or may not be the issue. Worth checking out.

sorry so late to reply.