Menu
▾
▴
flightgear-bugs — FlightGear Bug Tracker
You can subscribe to this list here.
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(87) |
Aug
(322) |
Sep
(222) |
Oct
(158) |
Nov
(189) |
Dec
(381) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(462) |
Feb
(287) |
Mar
(253) |
Apr
(192) |
May
(140) |
Jun
(151) |
Jul
(199) |
Aug
(141) |
Sep
(162) |
Oct
(62) |
Nov
(335) |
Dec
(284) |
| 2013 |
Jan
(203) |
Feb
(330) |
Mar
(247) |
Apr
(59) |
May
(118) |
Jun
(165) |
Jul
(96) |
Aug
(65) |
Sep
(112) |
Oct
(364) |
Nov
(162) |
Dec
(82) |
| 2014 |
Jan
(257) |
Feb
(279) |
Mar
(200) |
Apr
(130) |
May
(128) |
Jun
(85) |
Jul
(81) |
Aug
(161) |
Sep
(76) |
Oct
(106) |
Nov
(79) |
Dec
(117) |
| 2015 |
Jan
(84) |
Feb
(73) |
Mar
(60) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
| 2017 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Washington S. <was...@gm...> - 2018-01-25 00:20:39
|
After MESA upgrade some lights are not being rendered right. It's a MESA issue or is a upgrade that need be patched in FlightGear? Before MESA upgrade -> https://imgur.com/gallery/CzAQO After MESA upgrade -> https://imgur.com/gallery/NdEmu OS: Arch Linux Rolling Release FlightGear: 2017.3.1-1 MESA before: 17.2.6-1 MESA after: 17.3.0-2 -- Atenciosamente, Washington F. Santos OpenPGP Public Key <http://pgp.mit.edu/pks/lookup?op=get&search=0xC6D3C10AA4B48AD1> |
|
From: Adam J. <ada...@ya...> - 2017-07-18 19:46:11
|
<div>I would email the developers-list instead, it is updated daily, this one; very rarely, and I mean very rarely</div><div>Have a great day!</div><div><br /></div><div><br /></div><div>18.07.2017, 16:01, "Pui Lau" <pyl...@ho...>:</div><blockquote type="cite"> <div dir="ltr"> <div id="divtagdefaultwrappere76c1a16b30fd17657df2a5b8511e54a" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr"> <p><span style="font-family:Calibri,Helvetica,sans-serif,serif,EmojiFont;">Dear Sir or Madam</span><br /> </p> <div style="color:rgb(0,0,0);"> <div> <div id="divtagdefaultwrappere76c1a16b30fd17657df2a5b8511e54a" dir="ltr" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"> <p style="font-family:Calibri,Helvetica,sans-serif,serif,EmojiFont;font-size:16px;"> <br /> </p> <p style="font-family:Calibri,Helvetica,sans-serif,serif,EmojiFont;font-size:16px;"> I am Pui Lau and currently modeling SpitfireVb over Simulink model. However, when I launched FlightGear, the wing of the spitfire was bent up. I tried different commands that on the common command session. What should I do so that the wing is able to expand. </p> <p style="font-family:Calibri,Helvetica,sans-serif,serif,EmojiFont;font-size:16px;"> <br /> </p> <p style="font-family:Calibri,Helvetica,sans-serif,serif,EmojiFont;font-size:16px;"> The following attachment is the photo of the spitfireVb.</p> <p style="font-family:Calibri,Helvetica,sans-serif,serif,EmojiFont;font-size:16px;"> <br /> </p> <p style="font-family:Calibri,Helvetica,sans-serif,serif,EmojiFont;font-size:16px;"> Regards,</p> <p style="font-family:Calibri,Helvetica,sans-serif,serif,EmojiFont;font-size:16px;"> Pui Lau</p> <br /> <p></p> </div> </div> </div> </div> </div> ,<p>------------------------------------------------------------------------------<br />Check out the vibrant tech community on one of the world's most<br />engaging tech sites, Slashdot.org! <a href="http://sdm.link/slashdot">http://sdm.link/slashdot</a><br /></p>,<p>_______________________________________________<br />Flightgear-bugs mailing list<br /><a href="mailto:Fli...@li...">Fli...@li...</a><br /><a href="https://lists.sourceforge.net/lists/listinfo/flightgear-bugs">https://lists.sourceforge.net/lists/listinfo/flightgear-bugs</a><br /></p></blockquote> |
|
From: Pui L. <pyl...@ho...> - 2017-07-17 13:48:02
|
Dear Sir or Madam I am Pui Lau and currently modeling SpitfireVb over Simulink model. However, when I launched FlightGear, the wing of the spitfire was bent up. I tried different commands that on the common command session. What should I do so that the wing is able to expand. The following attachment is the photo of the spitfireVb. Regards, Pui Lau |
|
From: sidi l. <sid...@gm...> - 2017-05-18 17:37:56
|
As the image shows, the anti aliasing and the vegetation seems to be broken. MacOS Sierra 10.12.5, 2017.2 latest nighty version. https://ibb.co/epR90k |
|
From: ion s. <io...@ya...> - 2017-01-27 23:46:02
|
Continually testing 2017-devel, built and installed latest commit today, and heli BO 105 does not start up, autostart or any in way at all in 2017. Personally, Im working around it, Im not bothered, but I thought Id honor the existence of this mailling list, publicly posting on a forum felt a little ridiculous. On my 2016.4.4 install, aircraft behaves nominally. Have a great day! |
|
From: Adam J. <ada...@ya...> - 2017-01-18 01:53:54
|
<div>2017-version demonstrates a notable decrease in FPS with the F15C-aircraft.</div><div> </div><div>The only bug noted.</div> |
|
From: Adam S. <ada...@ou...> - 2015-11-03 20:45:19
|
Hi To begin with, I am MIG29pilot on the forum. I am not sure if this is the right mailing list to post this on, but it said bugs, so: I tried to get into the forum just now and all I got was this: General Error SQL ERROR [ mysql4 ] Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (111) [2002] An sql error occurred while fetching this page. Please contact an administrator if this problem persists. Is anyone else getting this and what can be done? Thanks Sent from Mail for Windows 10 |
|
From: <fli...@go...> - 2015-03-16 22:08:37
|
Comment #4 on issue 1673 by bcoco...@gmail.com: P-51D wants 'system' instead of 'autopilot' https://code.google.com/p/flightgear-bugs/issues/detail?id=1673 [Tested p51d rev 428] Line 579 of p51d-jsbsim.xml the tag <autopilot file="Systems/autothrottle"/> is calling the file Systems/autothrottle.xml which contains <system> (should be <autopilot>) AFAICS FlightGear source code has not been changed and JSBSim is rightfully reporting an error : the p51d XML files are inconsistent. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-16 20:49:01
|
Status: New Owner: ---- New issue 1708 by pwadedot...@gmail.com: Terrain across parts of KSKF https://code.google.com/p/flightgear-bugs/issues/detail?id=1708 *What steps will reproduce the problem?* try to land or takeoff KSKF *What is the expected output? What do you see instead?* Expect full length of runways paved. Terrain overlays parts of airport. *Any output in the console (black window)?* n/a *What FlightGear version are you using (when using GIT version, please mention date)?* 3.4.0 *What operating system and graphics card?* Ubuntu 14.04.2 LTS, Trusty Tahr *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-15 19:18:52
|
Status: New Owner: ---- New issue 1707 by flpyb2...@yahoo.com.br: WEBSITE 10x10 scenery wrong links!!! https://code.google.com/p/flightgear-bugs/issues/detail?id=1707 *What steps will reproduce the problem?* 1.Open the main website in Potuguese and go to scenery download area V2.12 2.point cursor on some blocks on map, like Souh-East Brasil scenery, that represents São Paulo, Santos, and Rio de Janeiro. *What is the expected output? What do you see instead?* It would be redirected to file w050s30 but it is linked with w080n00. User will download wrong area. Compare it to link below: 2.10 http://www.flightgear.org/legacy-Downloads/scenery-v2.12.html You can see, they are different. Thanks from Brasil! Felipe Yoshino -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-15 14:50:55
|
Status: New Owner: ---- New issue 1706 by v...@iveze.nl: 3.4 mp aircraft invisible by angle https://code.google.com/p/flightgear-bugs/issues/detail?id=1706 At some view angles mp aircraft disappear. The "correct" angle to disappear seems to differ per aircraft. *What steps will reproduce the problem?* 1. Watch the aircraft model or from the cockpit 2. Pan left right and maybe up down a bit 3. *What is the expected output? What do you see instead?* The aircraft not disappearing *Any output in the console (black window)?* No, not in the log either *What FlightGear version are you using (when using GIT version, please mention date)?* 3.4.0 *What operating system and graphics card?* Win 8.1 gtx670mx *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* You can see it on this ATC film. Near the touchdown zone the camera is at the "correct" angle to have the planes disappear. Watch these landings from minute 18.30 and 23.15. http://www.emmerich-j.de/EDDF/Films/20150307fri2033-34.ogv -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-15 13:18:08
|
Comment #3 on issue 1673 by gijsrooy: P-51D wants 'system' instead of 'autopilot' https://code.google.com/p/flightgear-bugs/issues/detail?id=1673 Bertrand, it seems to be broken again with current Git. Now it's expecting 'autopilot' instead of 'system'. Did someone revert the JSBSim change? -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-15 11:01:26
|
Comment #2 on issue 1703 by richard....@gmail.com: Route Manager: Crash in routePath.cxx when changing departure airport after completed flight https://code.google.com/p/flightgear-bugs/issues/detail?id=1703 There is a workaround for this: Clear the departure and destination airports by going into the text box and deleting the characters. Then enter the departure airport and runway. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-14 14:34:31
|
Comment #13 on issue 214 by legoboyv...@gmail.com: C-172 missing transponder, battery and avionics switch https://code.google.com/p/flightgear-bugs/issues/detail?id=214 The C172-detailed has a transponder and more! It also has texture updates. Please see the github repository at https://github.com/Juanvvc/c172p-detailed. I reccommend adding this to the Project, as part of the base aircraft (as a seperate aircraft) Regards, Legoboyvdlp -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-13 19:49:26
|
Status: New Owner: ---- New issue 1705 by clrc...@gmail.com: 3.4, 3.4.1 windows does not seem stable in VISTA https://code.google.com/p/flightgear-bugs/issues/detail?id=1705 *What steps will reproduce the problem?* 1. Start flightgear any plane any airport 2. fly, sometimes during initial taxi 3. sometimes with background tasks running, sometimes FG all alone the simulator suddenly is not responding and has to be forced shut down *What is the expected output? What do you see instead?* Stable, runable, responsive simulator *Any output in the console (black window)?* none and none no matter the debug levl *What FlightGear version are you using (when using GIT version, please mention date)?* 3.4, 3.4.1 *What operating system and graphics card?* Windows Vista 32bit ATI Radeonx300 *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* I've been testing this for weeks, sending in the few reports when the are generated, posted many times in the forum about things I thought were happening, have tried many planes, many airports, all settings off, and in different combinations. It's not the set up of the simulator but something even deeper. The simulator is not behaving correctly, after several installs/re-installs. Most recently I went from 3.4.1 back to 3.4 and still have the issue. Next I will try 3.2 and then I'll go back to 2.12.1 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-13 19:39:07
|
Comment #2 on issue 1700 by clrc...@gmail.com: FG "Fails to Find ICAO.groundnet.xml files for (Airport)" https://code.google.com/p/flightgear-bugs/issues/detail?id=1700 after the problem resurfaced he tried deleting his airports.txt file and got his groundnets back yet again. Ray -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-13 18:45:28
|
Status: New Owner: ---- New issue 1704 by tomicmih...@gmail.com: Wrong cloud base height https://code.google.com/p/flightgear-bugs/issues/detail?id=1704 *What steps will reproduce the problem?* 1.Paste this METAR:LYBE 131800Z 26008KT 3500 -RA BR OVC003 04/04 Q1019 TEMPO OVC002 2.Take off and you will notice that the cloud base is much higher. 3. *What is the expected output? What do you see instead?* I expect the cloud base to be at 300 ft but it is much higher at approximately 1400 ft. *Any output in the console (black window)?* *What FlightGear version are you using (when using GIT version, please mention date)?* Flightgear 3.4.1 *What operating system and graphics card?* Windows 8.1. Nvidia GTX650. *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-13 11:53:50
|
Comment #1 on issue 1703 by richard....@gmail.com: Route Manager: Crash in routePath.cxx when changing departure airport after completed flight https://code.google.com/p/flightgear-bugs/issues/detail?id=1703 This is easily reproducible: 1. Start with the UFO at EGKK 2. Open the Route Manager 3. Enter EGKK as the departure airport 4. Enter EGFF as the destination airport 5. Activate the route 6. Clear the route (imagine you arrived at EGFF and want a departure route) 7. Enter EGFF as the departure airport 8. Select runway 30 as the departure runway Segmentation fault with backtrace as above. It doesn't seem to be specific to these airports. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-13 10:10:49
|
Status: New Owner: ---- New issue 1703 by richard....@gmail.com: Route Manager: Crash in routePath.cxx when changing departure airport after completed flight https://code.google.com/p/flightgear-bugs/issues/detail?id=1703 *What steps will reproduce the problem?* I don't know that this will reliably reproduce the problem, because I've done this before and it's been OK, but this is what I did: 1. Fly a route with the route manager 2. On arrival, clear the route (Clear List) 3. Change the departure airport to current airport to start new route 4. Select the departure runway Specifically, this was after arrival at Cardiff (EGFF) runway 30 and changing the departure airport to Cardiff (EGFF) runway 30 to start a new route. *What is the expected output? What do you see instead?* Flightgear crashes. *Any output in the console (black window)?* See below for backtrace. *What FlightGear version are you using (when using GIT version, please mention date)?* Git next, updated 12 Mar 2015 *What operating system and graphics card?* Ubuntu 14.04.2, NVIDIA GeForce GTX 770 with NVIDIA driver 331.113 *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* Program received signal SIGSEGV, Segmentation fault. 0x0000000000930093 in computeLegCourse (radiusM=1473.7747730309509, previous=..., this=0xe03d2d0) at /home/richard/Flightgear/flightgear/src/Navaids/routePath.cxx:247 247 if (wpt->type() == "hold") { (gdb) bt #0 0x0000000000930093 in computeLegCourse (radiusM=1473.7747730309509, previous=..., this=0xe03d2d0) at /home/richard/Flightgear/flightgear/src/Navaids/routePath.cxx:247 #1 RoutePath::commonInit (this=this@entry=0x7fffffffc830) at /home/richard/Flightgear/flightgear/src/Navaids/routePath.cxx:904 #2 0x0000000000931336 in RoutePath::RoutePath (this=0x7fffffffc830, fp=0xec99bc0) at /home/richard/Flightgear/flightgear/src/Navaids/routePath.cxx:862 #3 0x0000000000940139 in flightgear::FlightPlan::rebuildLegData ( this=this@entry=0xec99bc0) at /home/richard/Flightgear/flightgear/src/Navaids/FlightPlan.cxx:1207 #4 0x0000000000941bcc in unlockDelegate (this=0xec99bc0) at /home/richard/Flightgear/flightgear/src/Navaids/FlightPlan.cxx:1265 #5 flightgear::FlightPlan::setDeparture (this=0xec99bc0, rwy=0xe59b2e0) at /home/richard/Flightgear/flightgear/src/Navaids/FlightPlan.cxx:463 #6 0x000000000072e053 in FGRouteMgr::setDepartureRunway (this=0x197bc60, aIdent=0x144ba550 "30") at /home/richard/Flightgear/flightgear/src/Autopilot/route_mgr.cxx:823 #7 0x000000000073473f in SGRawValueMethods<FGRouteMgr, char const*>::setValue (this=<optimised out>, value=<optimised out>) at /home/richard/Flightgear/install/include/simgear/props/props.hxx:562 #8 0x00007ffff6ece152 in SGPropertyNode::set_string (this=0x18bc140, val=0x144ba550 "30") at /home/richard/Flightgear/simgear/simgear/props/props.cxx:502 #9 0x00007ffff6eca9cd in SGPropertyNode::setStringValue ( this=this@entry=0x18bc140, value=0x144ba550 "30") at /home/richard/Flightgear/simgear/simgear/props/props.cxx:1553 #10 0x00000000007a4a69 in copy_from_pui (node=<optimised out>, object=0x125b8a58) at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:647 #11 FGPUIDialog::applyValues (this=this@entry=0xdf0aab0, objectName=...) at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:750 #12 0x000000000062ccff in do_dialog_apply (arg=0x125666d0) at /home/richard/Flightgear/flightgear/src/Main/fg_commands.cxx:1000 #13 0x00007ffff6ee333b in SGBinding::innerFire (this=0x12566860) at /home/richard/Flightgear/simgear/simgear/structure/SGBinding.cxx:92 #14 0x00007ffff6ee4059 in SGBinding::fire (this=<optimised out>) at /home/richard/Flightgear/simgear/simgear/structure/SGBinding.cxx:79 #15 0x00000000007a4787 in action_callback (object=<optimised out>) at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:563 ---Type <return> to continue, or q <return> to quit--- #16 0x00000000007a7a7b in invokeCallback (this=0x125b8a58) at /usr/include/plib/pu.h:681 #17 setCurrentItem (item=<optimised out>, this=<optimised out>) at /usr/include/plib/puAux.h:256 #18 fgComboBox::update (this=0x125b8a40) at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:1571 #19 0x00000000007a4eec in FGPUIDialog::updateValues ( this=this@entry=0xdf0aab0, objectName=...) at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:734 #20 0x000000000062ce1f in do_dialog_update (arg=0x11782370) at /home/richard/Flightgear/flightgear/src/Main/fg_commands.cxx:962 #21 0x00007ffff6f0ba5e in SGCommandMgr::execute (this=this@entry=0x13904f0, name=..., arg=arg@entry=0x11782370) at /home/richard/Flightgear/simgear/simgear/structure/commands.cxx:89 #22 0x0000000000a461c0 in f_fgcommand (c=<optimised out>, me=..., argc=<optimised out>, args=<optimised out>) at /home/richard/Flightgear/flightgear/src/Scripting/NasalSys.cxx:467 #23 0x00007ffff6e929b9 in setupFuncall (ctx=ctx@entry=0xd2ddeb0, nargs=2, named=named@entry=0, mcall=0) at /home/richard/Flightgear/simgear/simgear/nasal/code.c:321 #24 0x00007ffff6e9453b in run (ctx=ctx@entry=0xd2ddeb0) at /home/richard/Flightgear/simgear/simgear/nasal/code.c:724 #25 0x00007ffff6e970d0 in naCall (ctx=ctx@entry=0xd2ddeb0, func=..., argc=argc@entry=0, args=0x0, obj=..., locals=...) at /home/richard/Flightgear/simgear/simgear/nasal/code.c:912 #26 0x00007ffff6e97370 in naCallMethodCtx (ctx=0xd2ddeb0, code=..., self=..., argc=0, args=<optimised out>, locals=...) at /home/richard/Flightgear/simgear/simgear/nasal/code.c:983 #27 0x0000000000a45999 in callMethodWithContext (locals=..., args=0x0, argc=0, self=..., code=..., ctx=0xd2ddeb0, this=<optimised out>) at /home/richard/Flightgear/flightgear/src/Scripting/NasalSys.cxx:263 #28 callWithContext (locals=..., args=0x0, argc=0, code=..., ctx=0xd2ddeb0, this=0xa0e8f90) at /home/richard/Flightgear/flightgear/src/Scripting/NasalSys.cxx:246 #29 FGNasalSys::handleCommand (this=this@entry=0xa0e8f90, moduleName=moduleName@entry=0x12e90480 "__dlg:route-manager", fileName=<optimised out>, src=src@entry=0x12e903d0 "updateRunways();", arg=arg@entry=0x12e902f0) at /home/richard/Flightgear/flightgear/src/Scripting/NasalSys.cxx:1222 #30 0x0000000000a4325a in FGNasalSys::handleCommand (this=0xa0e8f90, ---Type <return> to continue, or q <return> to quit--- arg=0x12e902f0) at /home/richard/Flightgear/flightgear/src/Scripting/NasalSys.cxx:1235 #31 0x00007ffff6ee333b in SGBinding::innerFire (this=0x12e90510) at /home/richard/Flightgear/simgear/simgear/structure/SGBinding.cxx:92 #32 0x00007ffff6ee4059 in SGBinding::fire (this=<optimised out>) at /home/richard/Flightgear/simgear/simgear/structure/SGBinding.cxx:79 #33 0x00000000007a4787 in action_callback (object=<optimised out>) at /home/richard/Flightgear/flightgear/src/GUI/FGPUIDialog.cxx:563 #34 0x00007ffff4bb8bf3 in puInput::checkKey(int, int) () from /usr/lib/libplibpu.so.1 #35 0x00007ffff4bb7e55 in puGroup::checkKey(int, int) () from /usr/lib/libplibpu.so.1 #36 0x00007ffff4bb4eaf in puKeyboard(int, int) () from /usr/lib/libplibpu.so.1 #37 0x00000000007ecbcf in FGKeyboardInput::keyHandler (key=9, keymod=0, mousex=240, mousey=283) at /home/richard/Flightgear/flightgear/src/Input/FGKeyboardInput.cxx:252 #38 0x0000000000bc3298 in flightgear::FGEventHandler::handle (this=0x14f0950, ea=..., us=...) at /home/richard/Flightgear/flightgear/src/Viewer/FGEventHandler.cxx:220 #39 0x00007ffff6238737 in osgViewer::Viewer::eventTraversal() () from /usr/lib/libosgViewer.so.99 #40 0x00007ffff6239ed9 in osgViewer::ViewerBase::frame(double) () from /usr/lib/libosgViewer.so.99 #41 0x0000000000bc906a in fgOSMainLoop () at /home/richard/Flightgear/flightgear/src/Viewer/fg_os_osgviewer.cxx:335 #42 0x00000000006539af in fgMainInit (argc=20, argv=0x7fffffffde08) at /home/richard/Flightgear/flightgear/src/Main/main.cxx:509 #43 0x0000000000620546 in main (argc=20, argv=0x7fffffffde08) at /home/richard/Flightgear/flightgear/src/Main/bootstrap.cxx:234 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-13 02:57:22
|
Comment #1 on issue 1700 by trennor....@gmail.com: FG "Fails to Find ICAO.groundnet.xml files for (Airport)" https://code.google.com/p/flightgear-bugs/issues/detail?id=1700 ADDENDUM: Some one suggested deleting the navdata_x.x_cache in .fgfs, and I did so. Parking positions now work. Might be something to try. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-12 17:06:41
|
Comment #2 on issue 1701 by emptyYet...@gmail.com: Environment temperature could depend also on METAR https://code.google.com/p/flightgear-bugs/issues/detail?id=1701 Actually I did some more patient testing. It does seem to be semi-implemented, the issues is just that it can take very long to reach that temperature, and that its only the startup METAR that decide the temp, any further metar updates will be ignored it seems (for a couple of minutes at least): If I start up at Thule with M21 in METAR, the temperature starts to decrease with about 1 degC per 5 seconds, down from 15degC. So takes a couple of minutes to reach the temperature. After it has reached -10degC and still descending, I relocate to KNUQ and get a 14 degC in METAR, however the temperature keeps decreasing towards -21degC. After some further minutes, it slowly starts to go towards the correct temperature, this time even slower, about 50 seconds for each degreeC. So there is 2 bugs: 1 - It starts with wrong temperature and only very slowly goes towards the correct one. 2 - Updating metar wont update the temperature until after a while, and this time even 10 times slower than the initial very slow rate. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-12 16:13:44
|
Comment #1 on issue 1701 by emptyYet...@gmail.com: Environment temperature could depend also on METAR https://code.google.com/p/flightgear-bugs/issues/detail?id=1701 Forum thread about this: http://forum.flightgear.org/viewtopic.php?f=69&t=25625 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-12 16:08:20
|
Status: New Owner: ---- New issue 1702 by emptyYet...@gmail.com: Properties aren't passed correctly to the shaders after a reset https://code.google.com/p/flightgear-bugs/issues/detail?id=1702 *What steps will reproduce the problem?* 1. Load up plane with ALS landing light and turn it on 2. Reset the sim 3. Notice the light now stays on, whether or not its enabled. *What is the expected output? What do you see instead?* All shaders do not get updated properly after a reset. *Any output in the console (black window)?* No. *What FlightGear version are you using (when using GIT version, please mention date)?* 3.3, 3.4 and 3.5 *What operating system and graphics card?* Same bug on several different win7 systems. *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* Comment from Thorsten in http://forum.flightgear.org/viewtopic.php?f=47&t=24226&p=232346#p232346: "It seems properties aren't passed correctly to the shaders after a reset, probably the uniform factory code isn't reset proof. I'm getting the same behaviour for the ground haze or the air pollution, which are just frozen to whatever value they were before a reset." -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-12 15:57:33
|
Status: New Owner: ---- Labels: Type-FeatureRequest New issue 1701 by emptyYet...@gmail.com: Environment temperature could depend also on METAR https://code.google.com/p/flightgear-bugs/issues/detail?id=1701 Describe the feature you would like to see implemented. Be as precise as possible and include additional information (eg. links to certain websites). Please limit the request to reasonably small and simple features. Fundamental changes need to be discussed on the mailing list. At the moment /environment/temperature-degc does not seem to depend on METAR. For example a METAR code of M21/M25 should give an temperature of -21 degrees centigrade at an airfield. This would be very useful for those airplanes that has cabin temperature control, and Thorsten's new frost on glass effect. Also for icing of wings, and fuel etc. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
|
From: <fli...@go...> - 2015-03-12 13:10:03
|
Comment #21 on issue 1470 by cook.com...@gmail.com: Hang on startup at "loading scenery" https://code.google.com/p/flightgear-bugs/issues/detail?id=1470 I haven't seen this problem since a hard drive crash caused me to reinstall everything. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings |
1 message has been excluded from this view by a project administrator.
