the fix is now pushed
Thorsten wrote in Sun Mar 21, 2021 8:28 am:Theoretically (I haven't tried) it should be possible to do a one-time channel in JSBSim
<channel name="reset-damage" execute="systems/flyt/damage-reset">
<fcs_function name="systems/flyt/tied/damage-reset">
<function>
<v>0</v>
</function>
<output>systems/flyt/damage-reset</output>
</fcs_function>
<fcs_function name="systems/flyt/tied/damage-reset-flaps-main-damage-rate-manuv">
<function>
<v>0</v>
</function>
<output>systems/flyt/flaps-main-damage-rate-manuv</output>
</fcs_function>
<fcs_function name="systems/flyt/tied/damage-reset-flaps-main-damage-rate">
<function>
<v>0</v>
</function>
<output>systems/flyt/flaps-main-damage-rate</output>
</fcs_function>
</channel>
if (SpaceShuttle.pdrs_auto_seq_manager.sequence_slot_array[0] > 0)
<rms-auto-sequences>
<section-defined type="bool">true</section-defined>
<num-sequences type="int">1</num-sequences>
<sequence>
<num-points type="int">4</num-points>
<point>
<x type="double">12.0</x>
<y type="double">2.0</y>
<z type="double">0.0</z>
<pitch type="double">0.0</pitch>
<yaw type="double">0.0</yaw>
<roll type="double">0.0</roll>
<delay type="double">0.0</delay>
</point>
<point n="1">
<x type="double">10.0</x>
<y type="double">2.0</y>
<z type="double">0.0</z>
<pitch type="double">0.0</pitch>
<yaw type="double">0.0</yaw>
<roll type="double">0.0</roll>
<delay type="double">0.0</delay>
</point>
<point n="2">
<x type="double">10.0</x>
<y type="double">2.0</y>
<z type="double">0.0</z>
<pitch type="double">3.0</pitch>
<yaw type="double">0.0</yaw>
<roll type="double">0.0</roll>
<delay type="double">0.0</delay>
</point>
<point n="3">
<x type="double">13.0</x>
<y type="double">1.0</y>
<z type="double">0.0</z>
<pitch type="double">0.0</pitch>
<yaw type="double">0.0</yaw>
<roll type="double">0.0</roll>
<delay type="double">0.0</delay>
</point>
</sequence>
</rms-auto-sequences>
@Thorsten: I had a crash when I tried to use an automatic sequence for the RMS through spec 94
I had a small error with RCS valve state when resuming
The most probable scenario for that one is a user-side input error. Item 13 expects you to do a slot assignment, if you do
ITEM 13 EXEC
the most probabe cause is that you saved with the previous code state that had less parameters and resumed with the new state that has more
setprop("/fdm/jsbsim/systems/rcs-hardware/helium-right-rcs-valve-A-status", helium_right_rcs_A);
<valve-helium-left-rcs-A type="double">1</valve-helium-left-rcs-A>
<valve-helium-left-rcs-B type="double">1</valve-helium-left-rcs-B>
right missing
<valve-tank-left-rcs-12 type="double">1</valve-tank-left-rcs-12>
<valve-tank-left-rcs-345A type="double">1</valve-tank-left-rcs-345A>
var helium_right_rcs_A = getprop("/fdm/jsbsim/systems/rcs-hardware/helium-right-rcs-valve-A-status");
var helium_right_rcs_B = getprop("/fdm/jsbsim/systems/rcs-hardware/helium-right-rcs-valve-B-status");
setprop("/save/valve-helium-left-rcs-A", helium_left_rcs_A);
setprop("/save/valve-helium-left-rcs-B", helium_left_rcs_B);
var tank_left_rcs_12 = getprop("/fdm/jsbsim/systems/rcs-hardware/tank-left-rcs-valve-12-status");
var tank_left_rcs_345A = getprop("/fdm/jsbsim/systems/rcs-hardware/tank-left-rcs-valve-345A-status");
var tank_left_rcs_345B = getprop("/fdm/jsbsim/systems/rcs-hardware/tank-left-rcs-valve-345B-status");
It seems they are no written during save state at line 439 in save.nas
Contingency BLUE is broken for me - I've tested two times the scenario of 2 engines failing during stage 1
Contingency BLUE is broken for me
abort is declared - and the Shuttle detonates.
Item 4 depressed and explosion. No idea about that.
I had it two times in a row - unfortunately
Users browsing this forum: No registered users and 0 guests