Flying SenecaII at night

[kuifje09]

How do I fly the senecaII at night, its all dark, not button to get some light in the cockpit.

Maybe I missed some button or setting, but with no light or lit buttons and knobs and dials, no fun in flying at night.

Then I tried to change some ac-files, but could not find all parts, i.e. the big tumble knobs left. and a lot more.
Also it is not nice to have parts highlithed when not nesseccary.
So I tried install blender to see if that could help me find the buttons... but no ac3d import.
The latest imp/exp addon does not work. So I am totally stuck.

Can somebody tell if and where to start to make some light in the darkness.

Maybe the original developer can do it quickly. ??? would be nice to have the buttons and dials lit-up automaticaly when darkness falls... then no knob has to be added to turn-on the light. But then what if you get in a thunderstorm...

[Torsten]

Hi,

if everything else fails, read the manual
http://wiki.flightgear.org/Seneca_II_Panel_Reference

#38 might help.

Torsten

[kuifje09]

Silly I missed that. 22 and 38, 22 does not work, but 38 does....

Thanks Torsten.

[kuifje09]

Alright, then comes up the next question. How can I have the white rings on the knobs and the two push buttons also have lit up.

In other words.. Why does this " <dimming>instrumentation/comm[1]/dimming-norm</dimming> "
in the KR165 ( general instruments ) not listen to the dimm command.. in fact a make-red command....

I can change it in the propertytree, but then it becomes low- to high- light-white .
( I added a material line to kr165.ac ... so only the buttons changed )

While the xml says it should listen to

Code: Select all

 <dimming>instrumentation/comm[1]/dimming-norm</dimming>

edit: I hope I am clear enough with this cryptic description

[kuifje09]

Okay, changed to the radios. of the c172... Got it working now.
Reformed the dimmer section of the SenecaII.

Only one thing I cannot find. The switches / labels of 43 HSI gyro control
What file would I have to look in?

[Torsten]

The Seneca's HSI is a KI525a and the relevant files are in SenecaII/Models/kcs55.

Torsten

[kuifje09]

Ah , I have found it, changed things to my needs. Also made quick fix to set the heading indicator.
Click on the compas will set the headingindicator to the compass setting as would be the case pushing the toggle switches.
But it takes so long....

I still have one problem, the plane keeps craching now and then,, but usual after flying a time, then changing the radiosetting with the change-frequency on the radio ( middle white ) . It just happened again.

One thing is showing up : "Nasal runtime error: container index not scalar
at __dlg:radios, line 5"

Any idea where to look for ?

Also to catch the panic, compiled FG with the -g option in download_and_compile, but still get this :

Program terminated with signal 11, Segmentation fault.
#0 0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0x0896424d in ?? ()
#2 0x00000018 in ?? ()
#3 0x13f604a8 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

EDIT : regenerating now with : -DCMAKE_BUILD_TYPE=Debug

[Hooray]

to get a proper backtrace for SG/FG related crashes, you would want to use this: http://wiki.flightgear.org/Building_usi ... bug_Builds
Note that this is a configuration-time setting that may be cached, so better re-run cmake for SG/FG

[kuifje09]

Build with the debug option went fine, the exe is much larger now, now hope for a crash...

So far no crash, and no error messages about the radio dialog.

Very strange, what a recompile for debug can do ?

I am afraid I need to come back to this.. will fly some time with the debug-enabled-FG

[kuifje09]

As I expected.. Here is a gdb printout:

Code: Select all

Core was generated by `/home/flight/FG/install/fgfs/bin/fgfs --fg-root=/home/flight/FG/install/fgfs/fg'.
Program terminated with signal 11, Segmentation fault.
#0  0x08bd8372 in naiHash_newsym ()
(gdb) bt
#0  0x08bd8372 in naiHash_newsym ()
#1  0x08bcfbf9 in setupArgs.isra.3 ()
#2  0x08bd37f9 in naCall ()
#3  0x08bd3b91 in naCallMethodCtx ()
#4  0x08bd3c8c in naCallMethod ()
#5  0x086658d1 in callMethod (locals=..., self=..., code=..., args=0x0, argc=0,
    this=<optimized out>) at /home/flight/FG/fgfs/flightgear/src/Scripting/NasalSys.cxx:247
#6  call (locals=..., args=0x0, argc=0, code=..., this=0xf692028)
    at /home/flight/FG/fgfs/flightgear/src/Scripting/NasalSys.cxx:235
#7  FGNasalSys::handleCommand (this=0xf692028, moduleName=0xae98ef8 "__js0",
    fileName=0x154241dc "/input/joysticks/js/button[7]/binding",
    src=0xaf20978 "controls.adjPropeller(-0.25)", arg=0xae98df0)
    at /home/flight/FG/fgfs/flightgear/src/Scripting/NasalSys.cxx:1152
#8  0x08660e53 in FGNasalSys::handleCommand (this=0xf692028, arg=0xae98df0)
    at /home/flight/FG/fgfs/flightgear/src/Scripting/NasalSys.cxx:1164
#9  0x082799a8 in do_nasal (arg=0xae98df0)
    at /home/flight/FG/fgfs/flightgear/src/Main/fg_commands.cxx:183
#10 0x08c09093 in SGBinding::innerFire() const ()
#11 0x084385d6 in FGButton::update (this=0x10d37f48, modifiers=0, pressed=true, x=-1, y=-1)
    at /home/flight/FG/fgfs/flightgear/src/Input/FGButton.cxx:65
#12 0x0844897e in FGJoystickInput::updateJoystick (this=0xae7b470, index=0, joy=0xae7b48c,
    dt=0.016666666666666666)
    at /home/flight/FG/fgfs/flightgear/src/Input/FGJoystickInput.cxx:360
#13 0x08448acb in FGJoystickInput::update (this=0xae7b470, dt=0.016666666666666666)
    at /home/flight/FG/fgfs/flightgear/src/Input/FGJoystickInput.cxx:370
#14 0x08c32039 in SGSubsystemGroup::Member::update(double) ()
#15 0x08c322db in SGSubsystemGroup::update(double) ()
#16 0x08c32039 in SGSubsystemGroup::Member::update(double) ()
#17 0x08c322db in SGSubsystemGroup::update(double) ()
#18 0x08c31e82 in SGSubsystemMgr::update(double) ()
#19 0x0829f3ea in fgMainLoop () at /home/flight/FG/fgfs/flightgear/src/Main/main.cxx:108
#20 0x087a52d9 in fgOSMainLoop ()
    at /home/flight/FG/fgfs/flightgear/src/Viewer/fg_os_osgviewer.cxx:333
#21 0x0829ff97 in fgMainInit (argc=15, argv=0xbff7c144)
    at /home/flight/FG/fgfs/flightgear/src/Main/main.cxx:493
#22 0x08251ce6 in main (argc=<error reading variable: Cannot access memory at address 0x0>,
    argv=<error reading variable: Cannot access memory at address 0x4>)
    at /home/flight/FG/fgfs/flightgear/src/Main/bootstrap.cxx:278


b.t.w. the radio-dialog error also is back...

[Philosopher]

Can you also compile simgear as debug for us? it looks like the same as issue #1397 and it would be nice to see what pointer it crashes on.

It sounds like removing your joystick should keep the crashing away, but then you can't fly .

[Hooray]

yeah, handleCommand() will always re-parse and re-compile the binding: https://gitorious.org/fg/flightgear/sou ... .cxx#L1134
I'd add a SG_LOG() statement to see if it always crashes inside the conditional, i.e. around: https://gitorious.org/fg/flightgear/sou ... .cxx#L1146

And if that's the case, let's check the context/hash handling there

[kuifje09]

Okay, I rebuilded the Simgear as debug libs, but now I have 2 versions of each file :
libSimGearCore.a
libSimGearCored.a
libSimGearScene.a
libSimGearScened.a

Whould I rename , or recompile FG with an option to tell there is a Simgear-debug version also ?

Edit: If I am the only one with this kind of "bug" it might possibly because I have a not full standard flightgear ?
I made some changes for the mouse handler in nasal and took another radio-set in the senecaII
Not the general version but the version of the C172P .
The first want be an issue, but the radio's could be? but this bug seems to be at joystick handler ?
My changes may not be misleading...

[Philosopher]

Hi Kuifje,

I submitted a fix, so it will (probably) appear tomorrow in Git. No need for debugging anymore . Thanks for your help, I hope it works for you.