Vinny002 wrote in Wed Jul 03, 2019 11:11 pm:Let me help you clarify this, when the FG appears, the space shuttle stack exploded with the red screen appeared for a few, the SRBs is already ignited, and the SSMEs is not burning.
I meant to say my space shuttle stack falls to the horizontal position after ignition.
eatdirt wrote in Thu Jul 04, 2019 10:54 am:But I've just tried, with 2018.3.2, Shuttle downloaded and selected from the menu, as well as the airport (KTTS) and the place "South Ramp". Starting in Paused, the Shuttle is indeed at some high altitude initially. Then, unpausing, it goes down, but in my case, it just go down and stops where it should. I do not see any issues. I've tried with scenery enabled or disabled, even disabled, the Shuttle correctly goes to the right attitude in water. The only thing I've spotted is that the position on the pad is a bit weird (that's for south ramp):
In file /home/myuser/flightgear-dev/fgaddon-ng/Aircraft/SpaceShuttle/Systems/rcs_control.xml: line 766
<sum> only has one argument which makes it a no-op.
Its argument will be evaluated but <sum> will not be applied to the result.
In file /home/myuser/flightgear-dev/fgaddon-ng/Aircraft/SpaceShuttle/Systems/rcs_control.xml: line 789
<sum> only has one argument which makes it a no-op.
Its argument will be evaluated but <sum> will not be applied to the result.
In file /home/myuser/flightgear-dev/fgaddon-ng/Aircraft/SpaceShuttle/Systems/rcs_control.xml: line 812
<sum> only has one argument which makes it a no-op.
Its argument will be evaluated but <sum> will not be applied to the result.
In file /home/myuser/flightgear-dev/fgaddon-ng/Aircraft/SpaceShuttle/Systems/computations.xml: line 695
<max> only has one argument which makes it a no-op.
Its argument will be evaluated but <max> will not be applied to the result.
In file /home/myuser/flightgear-dev/fgaddon-ng/Aircraft/SpaceShuttle/Systems/computations.xml: line 728
<max> only has one argument which makes it a no-op.
Its argument will be evaluated but <max> will not be applied to the result.
In file /home/myuser/flightgear-dev/fgaddon-ng/Aircraft/SpaceShuttle/Systems/computations.xml: line 759
<max> only has one argument which makes it a no-op.
Its argument will be evaluated but <max> will not be applied to the result.
In file /home/myuser/flightgear-dev/fgaddon-ng/Aircraft/SpaceShuttle/Systems/autopilot.xml: line 3415
<product> only has one argument which makes it a no-op.
Its argument will be evaluated but <product> will not be applied to the result.
In file /home/myuser/flightgear-dev/fgaddon-ng/Aircraft/SpaceShuttle/shuttle.xml: line 3054
<product> only has one argument which makes it a no-op.
Its argument will be evaluated but <product> will not be applied to the result.
405.19 [ALRT]:input Could not find 'Effects/schemes.xml'
[...]
739.25 [ALRT]:general Failed to find a parking at airport KTTS:South_ramp
would init at 10000 feet and then drop to the pad.
plus i only have the pad... not the tower, too...
seems to be good to go so i shift to an outside view, helicopter view IIRC... hit SHIFT-I to ignite the engines and hope for a good launch... the main engines light for a few seconds and then shut off and that's the end of that attempt...
one thing i did figure out is that i need to undo all the APU settings if i want to restart the sim and try again from a cold start otherwise it loads with them still set...
the main engines light for a few seconds and then shut off and that's the end of that attempt.
Thorsten wrote in Thu Jul 04, 2019 6:09 pm:seems to be good to go so i shift to an outside view, helicopter view IIRC... hit SHIFT-I to ignite the engines and hope for a good launch... the main engines light for a few seconds and then shut off and that's the end of that attempt...
Probably the APU part was not ready..., that causes a launch abort.
Thorsten wrote in Thu Jul 04, 2019 6:09 pm:Can you post a screenshot of the APU dialog when you think it's good?
Thorsten wrote in Thu Jul 04, 2019 6:09 pm:one thing i did figure out is that i need to undo all the APU settings if i want to restart the sim and try again from a cold start otherwise it loads with them still set...
That should definitely not be true (and has never been the case for me) - APU settings are not persistent.
Now do the following (for all three switches of a group,
each controlling one APU):
(1) Switch APU controller power on — this connects the
turbines with power and activates their digital control
unit
(2) Open the fuel valves — this allows hydrazine to flow
from tanks to turbines
(3) Switch the water spray boiler controller power on —
this connects the cooling units to electrical power and
activates their digital controller
(4) Open the boiler N2 valves to allow pressurized nitro-
gen to push cooling water into them
(5) Check the talkback — it should now be grey rather
than stripe-pattern (’barberpole’), indicating that the
APU is ready to start. If the APU is not ready, check
the previous steps and verify that each switch is where
it should be
(6) Put the start switches into start/run position. Look
at the APU MEDS screen and observe how hydraulic
pressure climbs to 690 (pounds per square feet) as the
turbine reaches operating RPM.
(7) Once the turbine has reached full RPM, engage the hy-
draulic pump fully by switching main pump pressure
to ’NORM’. This puts more load onto the turbine (and
hence the turbine won’t start unless the pump is set to
low). Verify on the MEDS display that pressure now
reads around 3000.
in 5 i turned the pressure selector on which changed the PSI up to 3000...
if ((thrust1 > 400000.0) and (thrust2 > 400000.0) and (thrust3 > 400000.0) and (hyd_pressurized == 3))
Users browsing this forum: No registered users and 2 guests