Interactive Training
-
Ok thank you for answers
-
-
hmmm as I just noticed those are renamed as for their extension.
they used to be .txt and now they are .run
Did anything else changed? Should we expect any change with the U1?
-
.run and .txt have always been there and are different
-
@Red:
.run and .txt have always been there and are different
there are no txt files now and there where no run files previously. I’m talking about public staff.
-
the fact that there are no txt file in 4.33 TRN and there was no .run files in the 4.32 TRN don’t mean something changed.
As I said, both .txt and .run are valid means for scripting a TE.
The difference is not new (or public vs dev) but simply the fact that a .TXT script must be initialized by the user (by clicking the enable training script checkbox) while the .run script is transparent for the user and will always be ran at TRN initialisationIn 4.32 trn, the user could decide to use the scripted par or not, while in 4.33 he can’t.
that’s because of the text of the training manual that expect the user to have a certain situation active in the training scenario but which in fact could be different from one pilot to another pilot due to the saved item in the pilot.ini file.
so to maintain synchronisation between the training scenario and the text, .run files have been used rather than .txt files.the second difference is that the 4.32 TRN had text instruction displayed in 3D from the .Txt file whereas the 4.33 TRN have the instructions in the training manual, explained in much better detail than a few lines of text displayed as subtitles as you fly.
hence the need for the user to be able to enable or disable that.
but in 4.33 the script is mandatory and therefore can’t be user selectableHope that clears it
-
Thanx RedDog the fact that no reference existed for those was a bit confusing.
So run forces the code to ignore pilot ini file. Right?
Hmmm good one. -
no, the .run doesn’t force to discard the pilot ini file
The .run opposed to the .txt doesn’t display the “enable training script” checkbox so the script is run always at TE start regardless if the users wants it or notThe pilot.ini is read and may default some avionic variable to specific value
Let’s say for example: UHF preset 15 saved in the pilot.ini => Te starting in air will have the UFC radio preset 15 active (although I as a TRN designer don’t know what preset 15 is for user Arty?)
At TE start the TE will initialized with the pilot.ini file, setting UHF to preset 15 The .run will script the TE so 292.3 is entered in COM 1 right after mission start, during a short pause - so when the Text says Kunsan tower is set in your UHF radio, it’s what the user sees in his pit, regardless of his pilot.ini fileSame scrips were used to default in the air with a fuel load which is not full (landing TRN, flameout, AAR trn etc etc) and many other things
Another interesting difference about .txt and .run is that .txt works only with TRN missions, but .run works with .TRN and .TAC
-
Hello,
I dig this topic out because I want to deal with training scripts. To figure out how to do that, I created a very simple TE and renamed it to “.trn”.
From an existing trainings-TE I took the “.run” and renamed accordingly. For the sake of simplicity the script should only activate “FREEZE”,
write a few lines and switch off “FREEZE” again.//Delay for freeze WAIT 1 //Start sim in paused mode SimCommand SimMotionFreeze //Text layout setup SetColor 0xffffffff SetTextBoxed 2 SetFont 3 SetTextOrientation 0 SetFlash 0 //Some text SetCursor -0.98 0.08 Print 2 "Welcome to the BMS Landing training mission" MoveCursor 0 -0.08 WaitPrint 3 "Please wait until your cockpit is set up." MoveCursor 0 -0.08 Print 4 "Initial setup finished. You have the aircraft." //resumes mission SimCommand SimMotionFreeze
Unfortunately, the TE remains in FREEZE mode. Did I forget something?
Regards
Maddoc
-
I have built a training mission that unfortunately cannot be started (I attached the files).
Could someone test why “Take Off” doesn’t work? It works as a .tac, but not as a .trn.
There is also a problem in multiplayer. The script starts only at the host.
Aren’t the training missions capable of multiplayer?Regards
MadDoc
-
I have built a training mission that unfortunately cannot be started (I attached the files).
Could someone test why “Take Off” doesn’t work? It works as a .tac, but not as a .trn.
There is also a problem in multiplayer. The script starts only at the host.
Aren’t the training missions capable of multiplayer?Regards
MadDoc
Tested it as single player. When loaded the clock is stop. In order to takeoff only thing I needed to do was start the clock.
Might load it up to a server and test it MP as well
-
Aaaaarg, the clock won’t start after klicking on Take Off… Nice feature…
Unfortunately it doesn’t work with a server. For some reason I can’t join.