cant autostart

by **KLM** » Sat May 07, 2011 7:24 pm

hello folks,

first of all i will introduce myself

im mike im 16 years old and i come from holland and im new to the game.
i had some question about flying in game.
can someon explain me what to do when on the runway.
how to start the plane?
how to take off.
I click autostart alot of times but the screens wont turn on

(i use a keyboard and mouse)

thanks in advance for all your helpful reactions

by **Johan G** » Sat May 07, 2011 7:46 pm

Hello and Welcome Mike!

It would be much easier to help you if we knew what aircraft you're "sitting in", and what version of FlightGear you're using.

As you mention screens that wont turn on I can only assume that you're not trying to start the default Cessna, but rather an airliner.

by **KLM** » Sat May 07, 2011 7:59 pm

thanks

well i have no idea wich flightgear it is.
but if you have info about how i can let a 747 fly that welcome to.
i dont know how to accelerate.

by **Johan G** » Sat May 07, 2011 8:29 pm

Which 747 version? 747-100, 747-200, or 747-400, or maybe some other version?

They differ to some degree in start-up procedure.

(I have no personal experience with them, but I'm reading from the FlightGear Wiki.)

by **Gijs** » Sat May 07, 2011 8:51 pm

Welkom Mike!

Nieuwe Nederlanders zijn altijd welkom

As author of the 747-400 I am supposed to be able to tell you how to start it. But it depends on the version you're using. Latest versions can be downloaded from this link (more recent than the download at FlightGear.org). It is important that you download the package that fits your FlightGear version, else it won't work. All those should have a 747-400 > Autostart menu option (in FlightGear). Clicking that will start the engines, turn the lights on etc. Before takeoff you'll need to perform some other actions thoug, which are explained at our wiki. You can make it as realistic/complicated as you want

If the autostart menu doesn't work, we'll have to hunt for the problem. But, as we cannot get into your computer (luckily not!!), you're the one that should provide us with as much info as you can. FlightGear version (if you downloaded it from flightgear.org, you'll probably have the latest stable: 2.0.0), operating system (Windows/Mac/Linux) etc.

Cheers and enjoy!
Gijs

PS: Graag even aan hoofdletters en punten denken. Leest een stuk makkelijker, zeker op een forum met mensen van over de hele wereld.

by **KLM** » Sat May 07, 2011 9:03 pm

Hoi gijs ,

Bedankt voor je warm welkom.

Ik heb de laatste versie (2.0) en speel het op windows vista.
Ik heb een probleem met de boeing 777-200 ER.
Als ik hem wil autostarten doet die niks en blijven de schermpjes zwart staan.
Ik hoop dat je me goed kan informeren.
Ik wil later ook piloot worden.Denk jij dat dit spel mij kan voorbereiden op mijn opleiding?

Betreft interpunctie:mijn shift knop drukt heel stroef (sorry voor het ongemak)

by **Gijs** » Sat May 07, 2011 9:08 pm

I'll send you a PM (prive bericht), so our non-Dutch reading forumites won't have to crack the code

by **kneedragon** » Wed May 25, 2011 7:28 am

Hi all. 1st post.

I did have FGFS running fairly well in Ubuntu10.10. Had problems going to 11.04 and ended up wiping the drive - fresh install. Now I find that many of the aircraft that have 'autostart' don't start. About the only one that does work is the A10. I saw the conversation above and decided to try the 747-400. It doesn't start either.

By default, FGFS installs in a directory that has ownership - root. To enable adding more aircraft, I have taken ownership with sudo of the
/usr/share/games/FlightGear/Aircraft
directory. This enable me to move the unzipped aircraft into it. Other than that, I haven't changed anything. The FGFS version is 2.0.0. The terminal output reads like this. I would welcome any suggestions.

Code: Select all: mike@mike-System-Product-Name:~$ fgfs --aircraft=747-400 FGMultiplayMgr - No receiver port, Multiplayermode disabled Nasal runtime error: props.setAttribute() with invalid attribute at /usr/share/games/FlightGear/Nasal/props.nas, line 25 called from: /usr/share/games/FlightGear/Nasal/gui.nas, line 137 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/string.nas, line 225 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202 called from: /usr/share/games/FlightGear/Nasal/io.nas, line 210 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/string.nas, line 225 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202 called from: /usr/share/games/FlightGear/Nasal/multiplayer.nas, line 378 called from: /usr/share/games/FlightGear/Nasal/multiplayer.nas, line 446 Initializing Doors Initializing Liveries Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/string.nas, line 225 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202 called from: /usr/share/games/FlightGear/Nasal/gui.nas, line 376 called from: /usr/share/games/FlightGear/Nasal/aircraft.nas, line 519 called from: /usr/share/games/FlightGear/Aircraft/747-400/Nasal/liveries.nas, line 4 loading scenario 'nimitz_demo' creating 3D noise texture... ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started DONE Electrical System ... ok mike@mike-System-Product-Name:~$

by **polly** » Thu May 26, 2011 12:22 pm

If the Nasal errors are contributing to the autostart script failing, I posted a solution some while ago but, in case it was wrong, nobody has commented with the real solution. For me, those nasal error messages are associated with
multiplayer messages not working; there's been discussion on -devel ( concerning stuttering and local weather ) that
suggests nasal modules are not always executed in the right sequence.
My fix is to rebuild with optimization disabled, I just confirmed with yesterday's git the problem remains: if I build
with optimization enabled then I get no multiplayer chat and with optimization disabled then the nasal error messages go away and chat works OK. I use this command line for the build:

Code: Select all: CFLAGS="-march=i686 -ggdb -O0" CPPFLAGS="-march=i686 -ggdb -O0"

I don't know about the audio error messages, Fedora 14 with pulseaudio as installed works OK for me without an error messages.
viewtopic.php?f=27&t=11416

by **AndersG** » Thu May 26, 2011 4:57 pm

polly wrote in Thu May 26, 2011 12:22 pm:My fix is to rebuild with optimization disabled, I just confirmed with yesterday's git the problem remains: if I build
with optimization enabled then I get no multiplayer chat and with optimization disabled then the nasal error messages go away and chat works OK. I use this command line for the build:
Code: Select all
CFLAGS="-march=i686 -ggdb -O0" CPPFLAGS="-march=i686 -ggdb -O0"

Interesting. I build with "-g -O2 -march=core2 -mfpmath=sse" and for me MP chat works fine (I have a Q9400 Core2 quad CPU).
Is i686 the appropriate architecture for your hardware? Have you tried -march=native?
I use gcc version 4.5.3 (Debian 4.5.3-1).

There may well be some broken code that breaks with (some) optimization - the trouble is finding it.

/Anders

by **polly** » Thu May 26, 2011 8:06 pm

Anders,
It was some months ago you advised me to fix those nasal error messages when I reported the multiplayer chat problem. I tried _everything_ including regressing my system to ext3 from ext4 in case it was a 'delayed write' problem ( the nasal bug seemed to shift around ) .
Eventually I tried a debug script which was some years old. That script had -march i386 due to some problem we had ( 4 ?? ) years back with simgear. Today I determined it's only the -O0 that is important for this Nasal error / multiplayer problem on my system. ( Home brew Dual core X2-245 with 4Gby, fgfs threading tried both on and off )

In summary, yesterday's git clone fgdata, simgear, flightgear; configure and make .. the nasal errors appear, the plane pops up on mpmap but no mplayer messages are received.

Same source tree, make clean; ./configure CFLAGS="-O0" CPPFLAGS="-O0" make for both simgear and flightgear: ... no Nasal errors at startup and multiplayer messages are OK.
( I noticed the make process had two minds about the optimization level :

g++ -DHAVE_CONFIG_H -I. -I../../src/Include -I../../src -O0 -I/usr/local/include -g -O2 -Wall -D_REENTRANT -MT MIDG_main.o -MD -MP -MF .deps/MIDG_main.Tpo -c -o MIDG_main.o MIDG_main.cxx
.. etc ..

but after that build there are no Nasal error messages and MP Chat is OK. I now know it takes more than printf's to debug nasal but if you can advise how, I can rebuild with optimization and try to look at things. Meanwhile I'll try your settings. Mine:

<xxxx=yyyy>/comm<=>uname -a
Linux yyyy 2.6.35.12-90.fc14.i686 #1 SMP Fri Apr 22 16:14:44 UTC 2011 i686 i686 i386 GNU/Linux

<xxxx=yyyy>/comm<=>gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/i686-redhat-linux/4.5.1/lto-wrapper
Target: i686-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-bootstrap --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-gnu-unique-object --enable-linker-build-id --enable-languages=c,c++,objc,obj-c++,java,fortran,ada,lto --enable-plugin --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-1.5.0.0/jre --enable-libgcj-multifile --enable-java-maintainer-mode --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --disable-libjava-multilib --with-ppl --with-cloog --with-tune=generic --with-arch=i686 --build=i686-redhat-linux
Thread model: posix
gcc version 4.5.1 20100924 (Red Hat 4.5.1-4) (GCC)

KLM, Sorry if I'm muddling your thread but Anders' advice was on the mark for me: fixing unrelated Nasal error messages solved a Nasal execution problem. If memory serves, my Nasal problems started just after I installed Fedora14, previously Fe13.

by **kneedragon** » Fri May 27, 2011 3:11 am

Would a multi_player_chat problem stop the auto start from working?

In my previous ubuntu 10.10 install, most of these aircraft worked. Now, in ubuntu 11.04, the autostart is broken. What's changed?

Humbly and respectfully, if the solution to the problem is to learn git, to learn GCC, learn nasal, to learn to compile and link and build major projects myself, just to start the engines, ...

[edit] My 737-300 spawns with the systems powered up and the engines already running, so I can use that one. It shows much the same error messages as the ones which don't work.

Code: Select all: mike@mike-System-Product-Name:~$ fgfs --show-aircraft Available aircraft: 737-300 Boeing 737-300 // spawns with systems running. 747-400 Boeing 747-400 // spawns cold - no autostart 747-400-fo Boeing 747-400 (First Officer) 777-200ER Boeing 777-200ER // spawns cold - no autostart A-10 Fairchild A-10 (YASim FDM) // spawn cold - does start A6M2 A6M2 Zero A6M2-jsbsim A6M2 Zero (JSBSim) CitationX Cessna Citation-X // spawns cold - no autostart. This is the one I really want working. Dragonfly Moyes Dragonfly SenecaII PA34-200T Seneca II (alias for SenecaII-jsbsim) SenecaII-jsbsim PA34-200T Seneca II (obsolete, use SenecaII [without -jsbsim]) SenecaII-panelonly PA34-200T Seneca II (no 3d model, 2d panel only) ZLT-NT Zeppelin NT07 airship ZLT-NT-copilot Zeppelin NT07 multiplayer copilot b1900d Beechcraft B1900D // spawns cold - no autostart bo105 Eurocopter Bo105 // spawns cold - no autostart c172p Cessna 172P Skyhawk (1981 model) c172p-2dpanel Cessna 172P Skyhawk (1981 model), 2D panel c172p-panel-only Panel only for IFR-training (Cessna 172P) c182rg Cessna 182RG // invisible dhc2F de Havilland Beaver - Floats dhc2W de Havilland Beaver - Wheels f-14b Grumman F-14B // spawns switched on and running. f-14b-bs F-14b multiplayer back-seater j3cub Piper J3 Cub (J3C-65, 1946 model) mibs FG video assistant sopwithCamel Sopwith Camel 1F.1 (uiuc) sopwithCamel-YASim Sopwith Camel 1F.1 (YASim) sopwithCamel-v1-nl-uiuc Sopwith Camel starship Beechcraft Starship I // spawns switched on and running. ufo UFO from the 'White Project' of the UNESCO mike@mike-System-Product-Name:~$ fgfs --aircraft=737-300 Failed to load file: "Aircraft/737-300/Models/Flightdeck/Instruments/STBY/alt.xml" FGPropertyManager::GetNode() No node found for /sim/model/pushback/ki FGMultiplayMgr - No receiver port, Multiplayermode disabled Nasal runtime error: props.setAttribute() with invalid attribute at /usr/share/games/FlightGear/Nasal/props.nas, line 25 called from: /usr/share/games/FlightGear/Nasal/gui.nas, line 137 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/string.nas, line 225 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202 called from: /usr/share/games/FlightGear/Nasal/io.nas, line 210 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/string.nas, line 225 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202 called from: /usr/share/games/FlightGear/Nasal/multiplayer.nas, line 378 called from: /usr/share/games/FlightGear/Nasal/multiplayer.nas, line 446 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/string.nas, line 225 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 235 called from: /usr/share/games/FlightGear/Nasal/string.nas, line 202 called from: /usr/share/games/FlightGear/Nasal/gui.nas, line 376 called from: /usr/share/games/FlightGear/Nasal/aircraft.nas, line 519 called from: /usr/share/games/FlightGear/Aircraft/737-300/Nasal/liveries.nas, line 2 loading scenario 'nimitz_demo' creating 3D noise texture... DONE ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.center_lfe ALSA lib pcm.c:2212:(snd_pcm_open_noupdate) Unknown PCM cards.pcm.side bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) bt_audio_service_open: connect() failed: Connection refused (111) ALSA lib pcm_dmix.c:957:(snd_pcm_dmix_open) The dmix plugin supports only playback stream ALSA lib pcm_dmix.c:1018:(snd_pcm_dmix_open) unable to open slave Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started Scaling image '/usr/share/games/FlightGear/Aircraft/737-300/Models/fans.png' from (255,255) to (256,256) Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: bad/missing argument to subvec() at /usr/share/games/FlightGear/Nasal/screen.nas, line 161 called from: /usr/share/games/FlightGear/Nasal/screen.nas, line 115 Nasal runtime error: No such member: list at /usr/share/games/FlightGear/Nasal/view.nas, line 367 called from: /usr/share/games/FlightGear/Nasal/view.nas, line 336 called from: /usr/share/games/FlightGear/Nasal/globals.nas, line 100 Nasal runtime error: No such member: list at /usr/share/games/FlightGear/Nasal/view.nas, line 357 called from: /usr/share/games/FlightGear/Nasal/view.nas, line 345 called from: /usr/share/games/FlightGear/Nasal/view.nas, line 337 called from: /usr/share/games/FlightGear/Nasal/view.nas, line 233 called from: /usr/share/games/FlightGear/Nasal/view.nas, line 207 called from: /usr/share/games/FlightGear/Nasal/globals.nas, line 100 AL lib: ALc.c:1420: alcDestroyContext(): deleting 1 Source(s) AL lib: ALc.c:1818: alcCloseDevice(): deleting 1 Buffer(s) mike@mike-System-Product-Name:~$ fgfs --aircraft=737-300

by **ThorstenB** » Fri May 27, 2011 8:17 am

For your info, we also have an entry in our bug tracker for this issue - always good to keep this updated when there is any new information, otherwise we're spending time to investigate/debug outdated issues:
http://code.google.com/p/flightgear-bugs/issues/detail?id=314

I had already tried to locate the issue for a while, but unfortunately I was unable to reproduce it on my system. Might also depend on compiler version. I guess we do have some unsafe code in there, which only breaks with specific compiler versions / settings.

Those who can reproduce it: it would be very, very helpful if you could help in narrowing down the issue a bit more. If you are sure, that a specific compiler options (i.e. "-g -O0") doesn't produce the issue, but using another option (ie. "-g -O2") shows problems, then try to locate the specific source file which is affected by this settings using incremental builds with different options.

Start with compiling simgear and flightgear with different settings ("good" options for simgear, "bad" options for flightgear) - this already proves whether the issue is in simgear or flightgear.
Once we know if it's in fg or sg, we can do incremental recompiles within the respective project. You can pick some specific source directories below flightgear/src/... or /simgear/simgear/... and run "make clean" in the subdirectories.
Then go back to the main level and run ' make CXXFLAGS="-g -O2" ' (or -O0) which triggers a rebuild only affecting the cleaned directories. This way, we should be able to locate the actual directory containing the broken source. We can even continue by removing specific object files (i.e. "multiplaymgr.o") in these directories to locate the very source file. Will need a few iterations to locate the file - but it'd be worth it.

I'd also be interested in someone who could provide me with a "broken" fgfs binary eventually. But before that's of any value to me, we'd need to narrow down the issue some more.

by **kneedragon** » Fri May 27, 2011 9:49 am

Thank you ThorstenB, much appreciated.

The binaries are from the FG website. I didn't compile them. I installed FG from the Canonical "Ubuntu Software Centre" app, and that's about as much as I know about them. I know they're version 2.0.0. You might be able to find out from Canonical where they get those binaries from. I suspect they're the same ones linked to on the homepage at http://flightgear.org/Downloads/binary.shtml

If this Ubuntu install is like the last one, I'd have to go find and install and configure GCC anyway. By default, Canonical either leave it out or disable it - like the root account.

If it would help, I could go into a directory and ls -Verbose and provide all the attributes and so forth of what's in there.... ?

by **ThorstenB** » Fri May 27, 2011 6:08 pm

kneedragon wrote in Fri May 27, 2011 9:49 am:If it would help, I could go into a directory and ls -Verbose and provide all the attributes and so forth of what's in there.... ?

Hmm, thanks, but no, unfortunately it wouldn't help. In order to investigate, I'd still need someone who could help with narrowing down the issue through incremental recompiles/tests as described above. And preferably use the current GIT version for tests.

It's interesting though that the same issue already affected the 2.0.0 release, right? I wasn't aware yet. So it's not related to any of our recent changes.

Board index ‹ FlightGear ‹ Support ‹ Flying

cant autostart

cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Re: cant autostart

Who is online