Necolatis wrote in Fri Aug 25, 2017 7:15 pm:If you fly in MP, try sure to switch off MP sounds, they have tendency to crash FG sadly.
The Crash also happens with Singleplayer, With everyplane, with every setting
Necolatis wrote in Fri Aug 25, 2017 7:15 pm:If you fly in MP, try sure to switch off MP sounds, they have tendency to crash FG sadly.
Alant wrote in Fri Aug 25, 2017 7:50 pm:The log also has this, just before the exit was requested:-
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:flaps overspeed!
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:103.6064711699826
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:break
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_scene_commands.cxx:76:Program exit requested.
I do not know what the "bend" refers to.
Is it all related to the flap overspeed message?
Does the computer have a graphics processor (GPU), and is this being used?
Alan
FGAddon/Aircraft/F-86/Sounds/F-86-sounds.xml: <path>Aircraft/Hunter/Sounds/click.wav</path>
FGAddon/Aircraft/F-86/Sounds/F-86-sounds.xml: <path>Aircraft/Hunter/Sounds/click.wav</path>
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:flaps overspeed!
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:103.6064711699826
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:break
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_scene_commands.cxx:76:Program exit requested.
Bulldog 1 wrote in Fri Aug 25, 2017 8:30 pm:Necolatis wrote in Fri Aug 25, 2017 7:15 pm:If you fly in MP, try sure to switch off MP sounds, they have tendency to crash FG sadly.
The Crash also happens with Singleplayer, With everyplane, with every setting
Bulldog 1 wrote in Fri Aug 25, 2017 9:26 pm:I have ben fliyng for a long time and nothing happens
wkitty42 wrote in Fri Aug 25, 2017 9:04 pm:i note that the log indicates...
- the craft is the F-86
- the F-86 needs some love
- unknown volume type (default to "lin")
- dependency on the Hunter craft for a click sound
- Code: Select all
FGAddon/Aircraft/F-86/Sounds/F-86-sounds.xml: <path>Aircraft/Hunter/Sounds/click.wav</path>
FGAddon/Aircraft/F-86/Sounds/F-86-sounds.xml: <path>Aircraft/Hunter/Sounds/click.wav</path>- missing local previews
- AI traffic is apparently enabled
- and it looks like there was some damage(?) to the craft while flying (flaps) but maybe not
- Code: Select all
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:flaps overspeed!
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:103.6064711699826
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:break
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
nasal:5:G:\Jenkins\workspace\Windows-release\flightgear\src\Scripting\NasalSys.cxx:449:bend
input:3:G:\Jenkins\workspace\Windows-release\flightgear\src\Main\fg_scene_commands.cxx:76:Program exit requested.- before the exit was requested...
i took her up for a quick spin... squirrelly li'l thing! i landed very smoothly but at 200+ kts... ran out of runway burning up the brakes but not too awful badly i was trying to work out the trim to let her fly level without gaining altitude with the stick in neutral position... she kept leaning left so i was also hunting for that trim on my joystick... i might try it again and maybe this time i'll fly it from the cockpit instead of from the helicopter view (which was a first for me!)
remember, too, that flightgear is a simulator... not a game
wkitty42 wrote in Sat Aug 26, 2017 1:11 am:that's what he's talking about... you should not have to restart the machine just because you get a crash report...
however, i will ask, have you checked that your memory is all in good shape and not faulty? if not, go grab a boot disk with memtest86+ on it and run it... leave it to run for several full loops... it has a lot of tests that it runs and you cannot do anything else on the machine... if you have bad ram, it should find it... it may take hours and hours to run but it is better to be sure you have good ram than to keep limping along crashing all the time...
Users browsing this forum: No registered users and 7 guests