eatdirt wrote in Wed Jan 08, 2020 10:41 pm:@wkitty, I've just managed to destroy the Shuttle at ignition by pulling my joystick back and holding it locked there BUT before starting fgfs on the command line. That must be an initialization issue!
eatdirt wrote in Wed Jan 08, 2020 10:41 pm:If I pull the joystick well after starting fgfs, but before pressiong SHITF+I, nothing happens, as it should. Could you test if you get the same symptoms, I am able to reproduce it at 100%.
eatdirt wrote in Wed Jan 08, 2020 10:41 pm:Nothing in the console, up to this (which may be the consequence of the explosion)
yeah, that is fine because as soon as i move the stick (or click a button IIRC) it settles down and everything works as expected/desired...
eatdirt wrote in Thu Jan 09, 2020 3:33 pm:Yes, I understand that. But what I meant is that, even with a perfectly fine and trimmed joystick, could someone also test that we can actually destroy the Shuttle at ignition time by doing:
1) Take your joystick and pull it (maximal elevon deflection) and hold it there
2) Start flightgear (and Shuttle-launch scenario) while still holding the josytick!!! (crucial)
3) With your remaining free hand, switch on APU, boilers, high pressure hydraulics, and then press SHIFT+I
=> Shuttle explodes at ignition because it tries to fly horizontally, as ordered by the joystick.
fgfs[21709]: segfault at 93a4d2 ip 00007f875b82f9ba sp 00007f8749a12ad8 error 7 in libSimGearCore.so.2019.2.0[7f875b775000+152000]
I can verify that this destroys the Shuttle - I have a CH Fighterstick that has trim wheels that apply to the actual controls rather than usual trim, so all I have to do is set the elevator trim wheel to maximum up & start the shuttle -> boom!
Thread 146 "fgfs" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f2258b7b700 (LWP 18179)]
0x00007f23341e29ba in naObj (type=type@entry=2,
o=0xa61961 <FGAIFlightPlan::createClimb(FGAIAircraft*, bool, FGAirport*, FGAirport*, double, double, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)+1>)
at /usr/src/debug/simgear-2019.2.0-9.mga7.x86_64/simgear/nasal/misc.c:33
33 o->type = type;
Actually, let's narrow down the pathway a bit.
PS Yes, the conclusion is that the survival rate is currently 0!
Thorsten wrote in Sat Jan 11, 2020 1:47 pm:Actually, let's narrow down the pathway a bit.
From my observations, whatever is commanded by the joystick at the point the 'hydraulic pressure select' is enabled is locked in & you can't change it with the joystick after that
Users browsing this forum: No registered users and 0 guests