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: <fli...@go...> - 2015-03-11 03:33:27
|
Status: New Owner: ---- New 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 Over a week ago, my groundnet.xml files worked just fine. When I launched FG through my launcher with a parking position designated, my aircraft spawned where I wanted it. NOW I get a message in my terminal: "Failed to find a parking at airport ICAO Parking pos." I end up spawning on default rwy. Why? I changed NOTHING in my FG; except what changes were done through terrasync. What's happened? When is somebody going to fix this very basic feature? FlightGear version: 3.2.0-1 SimGear version: 3.2.0 PLIB version: 185 -- 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-11 03:20:21
|
Comment #18 on issue 178 by clrc...@gmail.com: Reinit/reposition with speed > 0 may cause NaN issues and crash (YASIM propeller planes) https://code.google.com/p/flightgear-bugs/issues/detail?id=178 Even better solution that works without needing a reworking of YASIM. Consider leaving the IAS entry blank. I have had great success with this tactic restarting any of the turbo props with an in-air start. I only enter the LAT, LON, and Heading in the case of turbo props and I only include IAS on jets. -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-10 21:37:40
|
Comment #2 on issue 1694 by gilberto...@gmail.com: floating houses around LFEY https://code.google.com/p/flightgear-bugs/issues/detail?id=1694 Thanks, you are right about it. I had downloaded the new scenery 2.0 for this region, but its directory was not on the first one on my FG_SCENERY, and the one above it had the scenery 1.0 version of this island, hence why it was being loaded. Sorry about that. -- 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-10 06:32:48
|
Comment #1 on issue 1568 by clrc...@gmail.com: segfault at start when I choose KSFO airport https://code.google.com/p/flightgear-bugs/issues/detail?id=1568 before I upgraded to 3.4.1 I installed 3.2 and had this very issue at KSFO trying to load the C172p. What i did to solve it, I happened to have FG version 2.12.1 on another machine, and I pointed 3.2 to the default scenery of 2.12.1 and the sim loaded. I subsequently installed the Scenery-v2.12, the version of scenery for FG version 2.12, the entire world, for me to use FG 3.2/3.4.1 and I've not had any issues like those reported by people using the Scenery 2.0. I am waiting to hear that the known issues are fixed in 2.0, before I turn on the terrasync to get it all. -- 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-10 06:18:12
|
Comment #1 on issue 1679 by clrc...@gmail.com: Callsigns should be secured https://code.google.com/p/flightgear-bugs/issues/detail?id=1679 This, of course, is a very well known issue going way back to the earliest days of Multiplayer. In the 1.9.1 days I brought this issue up to the forum in the rogue pilots at KSFO thread, which eventually became a very heated issue -- the one side claiming freedom to be molested ( you could be attacked in the streets of the world at any time), the other freedom from molestation ( no gaming server in the world comes without registration). The ignore pilots in the pilots list feature was a direct result. It works great. After the fact. As we know, this feature is backwards. By the time you need it, the offense is already occurred. But then, how is one to know who to ignore? :-) And if an offender can just change names, and even to names of respected pilots, and I'm told there is a new feature that would ignore a pilot for an entire upgrade cycle... then we eventually end up doing individually something worse than what registration would accomplish. Potentially ignoring the good people that typically use the ignored name. The above original poster only mentioned a couple of the things that were going on that day at KSFO -- the language and the name 'stealing' ( for want of a word ) but the real issue was how that offender was able to knock some of the pilots out of the multiplayer, and then block them using their typical callsign, until the blocked figured out to change their callsigns. This has to do with the constant calls from the offender to load material into your sim thru the multiplayer. I wish I had kept the crash log from that day. In it there were enough calls to load the Eurofighter that my machine was eventually overloaded and my sim crashed. This is how he gets you out. Then he sees you have gone, and takes the name of someone popped out of sim. And then you don't know that you've been spoofed until you see in the mpmap that you're name is already taken. Names can't be "owned" currently, and I see the logic of that. A pilot might be Atlas Virtual Airlines AVA0001, and also American Virtual Airlines AVA0001. Seven characters is a poor limit. Maybe it's enforced by some internal issue I am not aware of. Of course, the best advice given to me by the "okay to be molested side" was "Go fly somewhere else" and I have done so to great enjoyment. In that scenario the ignore feature is a waste of menu space. Best used for ATC's trying to ignore people at the controlled airport not being controlled. The biggest problem I see with registering names is that in-sim pilot lifespans are sporatic at best. Having a register means that even people that never fly can register a poplular nick/callsign, and that's not very productive either. It's a tough issue, and after years of using flightgear, I have to admit that the free-to-molest side has won me on the points of the issue so far. 1 go fly somewhere else plenty of controlled airspace and a great huge beautiful FG world to explore. 2 don't restrict names it doesn't allow for the recycle of names ( how many Mavrick's have there been hehe ) 3 if people don't come on and push systems, like this guy loading so much material he can pop you out, then how can we code to stop such abuse. I would have fought for this feature many moons ago, but It's not a good idea to me any more. --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-10 05:27:08
|
Comment #1 on issue 1698 by clrc...@gmail.com: Start/pushback tutorial Fuel Pumps (B777-300) https://code.google.com/p/flightgear-bugs/issues/detail?id=1698 I ran into this as well. The trick is to add some fuel to the empty center tank. Turn on the only tanks not already on in the panel, the center tank switches ( the lowest ones in the diagram ) and the tutorial continues. I believe that the circle being offset all over all the tutorials may be related to the designers screen resolution versus the resolution some of us are using. I was using 1024X768 and I see exactly like what is in the picture above, the circle basically centered "north" of what it is supposed to be highlighting. I could be wrong about the resolution thing -- it's just a theory. -- 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-09 12:49:46
|
Comment #4 on issue 1699 by billytou...@gmail.com: Aircraft Ratings Submission System in "Download Aircraft" webpage https://code.google.com/p/flightgear-bugs/issues/detail?id=1699 I have read that Torsten, thanks. The thing is though that the current system isn't working good enough either, in my opinion. I proposed the user ratings as an alternative rating, not as a direct replacement of the official rating. It will only help developers quickly locate innacurate ratings and acquire many ratings for unrated aircraft. This will never ever going to be done through the official process. It is way easier and a thousand times more effecient to do it the way Clement proposed. This would generate hundreds of feedback/ratings submitions for each plane. -- 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-09 11:00:16
|
Comment #3 on issue 1699 by cumuluni...@gmail.com: Aircraft Ratings Submission System in "Download Aircraft" webpage https://code.google.com/p/flightgear-bugs/issues/detail?id=1699 Please read http://wiki.flightgear.org/Aircraft_rating_system#Who_rates_an_aircraft.3F and search the devel mailing list. There were good reasons why we did not implement a rating based on user voting. Torsten -- 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-09 10:47:57
|
Comment #2 on issue 1699 by billytou...@gmail.com: Aircraft Ratings Submission System in "Download Aircraft" webpage https://code.google.com/p/flightgear-bugs/issues/detail?id=1699 Well the thing is I am not a programmer and so I can't code :( I would be willing to help in any other way I can though. Just tell me what we would need to do in order to see this rating system implemented and point me to the right direction as to what do I need to read first. Thanks :) -- 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-09 10:38:28
|
Updates: Status: NeedInfo Comment #1 on issue 1699 by clement....@gmail.com: Aircraft Ratings Submission System in "Download Aircraft" webpage https://code.google.com/p/flightgear-bugs/issues/detail?id=1699 About 3) I have the following in my mind: Inside FlightGear we can create a very simple "Submit rate" dialog where the user can set the rating for his humble opinion then press the "Submit" button. This submission should be managed by a simple web script who record this rating then the aircraft download page would show the average of these 'user-ratings'. My proposition is not so different than yours except that I would make it possible to submit the rate from FlightGear (avoiding to ask our user to open their web browser) I think that could give us much more submission. Are you willing to work on some of these point ? I can help you in case you are lost at some part, but I won't handle that alone for sure ;) -- 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-08 17:44:33
|
Status: New Owner: ---- Labels: Type-FeatureRequest New issue 1699 by billytou...@gmail.com: Aircraft Ratings Submission System in "Download Aircraft" webpage https://code.google.com/p/flightgear-bugs/issues/detail?id=1699 As the FGDATA is now free of aircrafts (great decision IMO), we got to focus on creating a better "Aircraft Download" webpage with more functionality. Here are some ideas for consideration: 1.) Allow registered users thump up/down aircrafts and allow "sort by rating". 2.) Keep download stats to allow "short by downloads" 3.) Allow registered users to easily submit a different rating than the one the author set for Cockpit, FDM, Model and Systems. We may then show an average of these ratings as an alternative, or automatically perform re-evaluation of the shown data if a certain number of user ratings deviate greatly from what the author set. This will help us: a.) quickly rate all the unrated aircrafts, b.) raise the ratings of the underated models (strict/perfectionist authors) and c.) lower the rating of planes that have been over-rated. -- 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-08 16:24:20
|
Updates: Status: Expired Labels: Scenery Comment #1 on issue 1694 by gijsrooy: floating houses around LFEY https://code.google.com/p/flightgear-bugs/issues/detail?id=1694 Looks like you have the old scenery. Try using TerraSync for the latest and greatest, see http://wiki.flightgear.org/TerraSync -- 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-08 15:01:11
|
Status: New Owner: ---- New issue 1698 by Deanpove...@gmail.com: Start/pushback tutorial Fuel Pumps (B777-300) https://code.google.com/p/flightgear-bugs/issues/detail?id=1698 *What steps will reproduce the problem?* 1. When in the tutorial once all fuel pumps are on (6) nothing happens it continually prompts to turn them on 2. The pink circle is not next to pumps 3. *What FlightGear version are you using (when using GIT version, please mention date)?* The version is 3.4 *What operating system and graphics card?* MAC OSX YOSEMITE 10.10.2 Attachments: Screen Shot 2015-03-08 at 15.00.16.png 1.5 MB -- 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-08 13:40:52
|
Updates: Status: WontFix Comment #2 on issue 1591 by gijsrooy: Restore defaults sets invalid paths https://code.google.com/p/flightgear-bugs/issues/detail?id=1591 FGRun will be gone with the next release of FlightGear, in favour of a built-in launcher. Therefore, I'm closing this issue to prevent anyone from spending a lot of time on fixing things in FGRun. -- 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-08 13:39:52
|
Updates: Status: WontFix Comment #7 on issue 1529 by gijsrooy: Aircraft Center airplanes don't appear in FGRun https://code.google.com/p/flightgear-bugs/issues/detail?id=1529 FGRun will be gone with the next release of FlightGear, in favour of a built-in launcher that's built to work with the aircraft center. Therefore, I'm closing this issue to prevent anyone from spending a lot of time on fixing things in FGRun. -- 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-08 13:38:52
|
Updates: Status: Expired Comment #4 on issue 1295 by gijsrooy: Integrated GUI launcher https://code.google.com/p/flightgear-bugs/issues/detail?id=1295 We now have a built-in Qt launcher that's shipped by default on Mac and will be used on other OS in the coming release. FGRun will be gone by then, therefore I'm closing this issue. -- 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-08 13:37:51
|
Updates: Status: WontFix Comment #7 on issue 1003 by gijsrooy: FGRUN 1.7.0 forgets parkpos https://code.google.com/p/flightgear-bugs/issues/detail?id=1003 FGRun will be gone with the next release of FlightGear, in favour of a built-in launcher. Therefore, I'm closing this issue to prevent anyone from spending a lot of time on fixing things in FGRun. -- 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-08 13:36:52
|
Updates: Status: WontFix Comment #3 on issue 911 by gijsrooy: Sorting options for airplanes in FGRun https://code.google.com/p/flightgear-bugs/issues/detail?id=911 FGRun will be gone with the next release of FlightGear, in favour of a built-in launcher. Therefore, I'm closing this issue to prevent anyone from spending a lot of time on fixing things in FGRun. -- 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-08 13:35:51
|
Updates: Status: WontFix Comment #3 on issue 1348 by gijsrooy: Fgrun holds unnecessary memory while fgfs runs https://code.google.com/p/flightgear-bugs/issues/detail?id=1348 FGRun will be gone with the next release of FlightGear, in favour of a built-in launcher. Therefore, I'm closing this issue to prevent anyone from spending a lot of time on fixing things in FGRun. -- 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-08 05:52:23
|
Status: New Owner: ---- New issue 1697 by shredde...@comcast.net: "flightgear has stopped working" https://code.google.com/p/flightgear-bugs/issues/detail?id=1697 *What steps will reproduce the problem?* 1.trying to click run on the flightgear 3.4 launch screen 2. 3. *What is the expected output? What do you see instead?* i expect to load the simulation, i see a windown pop up saying lfightgear has stopped working *Any output in the console (black window)?* *What FlightGear version are you using (when using GIT version, please mention date)?* 3.4 *What operating system and graphics card?* windows 7-64 bit. ati radeon 6370 *Please provide any additional information below or as attachment (Avoid expiring external links, such as to imageshack/pastebin/...).* i have uninstalled and re installed multiple times. for some reason i have two models of each aircraft even with new installs. also i used to install in 32 bit on my system cause it worked better, now i didnt see that option Attachments: 9aaa00b6-4c51-4f33-91dd-9b0acd634537.zip 9.0 KB -- 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-07 00:57:01
|
Comment #5 on issue 1695 by gilberto...@gmail.com: rain only in half of the screen on certain view position https://code.google.com/p/flightgear-bugs/issues/detail?id=1695 Oh, I see I missed Issue 596, I am so sorry. -- 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-07 00:55:36
|
Comment #4 on issue 1695 by gilberto...@gmail.com: rain only in half of the screen on certain view position https://code.google.com/p/flightgear-bugs/issues/detail?id=1695 If this is something new or not I have no clue, but I did look for all older issues containing the word "rain" before posting here and I could not find anything about having half of the screen raining and half not. Could you please show me which issue did I duplicate here? -- 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-07 00:53:32
|
Comment #19 on issue 596 by NasalMusician: No precipitation with certain airplanes at certain view angles https://code.google.com/p/flightgear-bugs/issues/detail?id=596 Issue 1695 has been merged into this issue. -- 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-07 00:52:31
|
Updates: Status: Duplicate Mergedinto: 596 Comment #3 on issue 1695 by NasalMusician: rain only in half of the screen on certain view position https://code.google.com/p/flightgear-bugs/issues/detail?id=1695 Nothing new, and please don't make duplicate bug reports. -- 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-06 22:37:40
|
Comment #1 on issue 1687 by lannycha...@gmail.com: 3.4 HUD has no numbers https://code.google.com/p/flightgear-bugs/issues/detail?id=1687 More info: my new iMac has a much better graphics card, an NVIDIA GeForce GTX 775M 2048 MB, with which the HUD numbers appear normally. -- 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.