| A | B | C | D | E | F | G | H | I | |
|---|---|---|---|---|---|---|---|---|---|
1 | Scenery Editor Feedback Status | ||||||||
2 | Timestamp | Reported by | Manual reference | Issue Type | Description of issue | Is there any other information you would like to provide? | Status | Version | Feedback |
3 | 11/8/2021 21:48:27 | brennanhackard | 8.1.1 | Spelling mistake | The word "Hangars" is spelled "Hangers" in the section for hangars on the editing checklist. | Approved | 21.7.0.2 | N/A | |
4 | 11/18/2021 11:10:07 | Jet_Airways_995 | 1A.3.2 | Spelling mistake | The eighth main bullet point states "Adding [customs] towers should be avoided", spelling in brackets may be more appropriate as [custom] towers. | Approved | 21.7.0.3 | N/A | |
5 | 11/18/2021 11:39:40 | Jet_Airways_995 | 5.1.1 | Spelling mistake | Step 3 under "Creating Pavements" in 5.1.1 states that "once three [of] more are placed", words in brackets may be more suitable as three [or] more | Approved | 21.7.0.3 | N/A | |
6 | 11/23/2021 3:53:01 | MajorTom | 4.1 Satellite imagery | Content | There is a lot more to know about using SAS with a good result in IF. A description is here: https://community.infiniteflight.com/t/tips-and-how-tos-real-world-airfield-information-research-satellite-imagery-parallel-facades-extrusion/608259/3 Feel free to use completely or partially if you like. | Approved | 21.8.0.1 | N/A | |
7 | 11/23/2021 3:58:52 | MajorTom | 7.4 technical locations | Content | The location of LOC antennas could be found in official documents for non FAA airports. There are antennas that are not placed where the roughly estimate in the document says. A better way are entering the coordinates in IF. | This also effects runway placement and adjustment of satellite images. A explanation is found here: https://community.infiniteflight.com/t/tips-and-how-tos-real-world-airfield-information-research-satellite-imagery-parallel-facades-extrusion/608259/7 In my opinion editing should start with placing the runways correct by coordinates to make sure that there will be no issues with a misplaced airport now and in future. | Approved | 21.8.0.1 | N/A |
8 | 11/26/2021 10:34:31 | Jan | 7.1 & 7.2 | Content | More information about view points and their placement would be useful. Also, when more than one view point has been added, which one is selected for ATC view? | Not at this time. | Approved | 22.1.0.1 | Only one can be selected currently, this may change in future updates but all towers should have a view point added. Thanks, RAH. |
9 | 12/2/2021 13:33:48 | Jan | 5.10 | Content | Please add information about "Set as apron" button | Not at this time | Approved | 22.2.0.1 | N/A |
10 | 12/23/2021 15:43:06 | Zuhair.Mazhar | 3.2.2 | Content | Addition of A220-300 in the appropriate aircraft category | Approved | 22.1.0.2 | N/A | |
11 | 12/23/2021 15:44:17 | Zuhair.Mazhar | 1.20 | Content | Addition of OSM to list of abbreviations | Approved | 22.1.0.2 | N/A | |
12 | 12/25/2021 10:34:51 | Chris_Hoss | 1A.1.4 | Formatting issue | The last question in the Q and A (How do I report issues) needs to have a space the spread it out from the other questions | Approved | N/A | Q and A's removed for the time being. Thanks, RAH. | |
13 | 12/30/2021 3:20:11 | Adam_S | 3.2.2 | Spelling mistake | Aircraft listed in category C - "A318/319/320/32" /32 should have a 1 at the end, indicating the A321. | Approved | 22.1.0.1 | N/A | |
14 | 3/12/2022 14:14:39 | Siddhansh | 8.4 and 11.1 | Content | - The section with the facades could use some guidance on how to correctly use facades. Some elaboration on the theory behind how facades are applied and how they can be manipulated by adding/removing/moving nodes to help new editors better understand the working of the system. - The original dimensions (width and height that define how they are mapped on faces ) for the root images in the facades can be included so that editors can refer to it while using the facades to avoid stretched/compressed textures. | Negative. | Rejected | N/A | Thank you for the feedback, as the guide and editor has been updated since these were suggested, they are no longer applicable. Please report further if that is not the case. Thanks, RAH. |
15 | 3/12/2022 14:23:36 | Siddhansh | 11.10 | Content | The hangars and terminals section mentions that nodes should be added to large buildings to avoid clipping/rendering issues, however this issue was fixed in 22.1 and hence adding nodes might not be required. | No. | Rejected | N/A | Thank you for the feedback, as the guide and editor has been updated since these were suggested, they are no longer applicable. Please report further if that is not the case. Thanks, RAH. |
16 | 3/12/2022 14:26:27 | Siddhansh | 8.30 | Content | The pro-tip at the very end of the page mentions that buildings with height less than 1m aren't allowed. I'm not 100% sure, but I believe with 22.1, roof buildings with height lesser than 1m (but more than 0.1m) render perfectly without any glitch. | Rejected | N/A | Thank you for the feedback, as the guide and editor has been updated since these were suggested, they are no longer applicable. Please report further if that is not the case. Thanks, RAH. | |
17 | 6/28/2022 5:06:09 | ECoops123 | 5.10 | Content | The "Do's and Don'ts" of editing is not easily visible to all editors viewing through the document meaning the section could be a standard table, and not a drop-down list. "Use as few pieces of pavement as possible" should be a highlighted section of information as many editors have missed this and have had to redo their airports. | - | Under Review | N/A | This is under review, I am hoping we will have a fix for all the tables that will then allow us to utilize this for the "do's and dont's" section. Thanks, RAH. |
18 | 7/5/2022 7:35:06 | Jan | 6.20 | Content | Information about curved lines connecting two taxiways. When, for example taxiway A crosses taxiway C, always use the name of lower ranked taxiway for the curved lines connecting A and C.. Usually the higher letter/number. C in this case. | Approved | 23.1.1 | N/A | |
19 | 7/5/2022 7:54:59 | Jan | ? | Content | Information about the need for a database update. The following items will only be updated after a database update: - map - start locations - airport elevation - boundary - tower view - runways - ILS - ... | Approved | 23.1.1 | N/A | |
20 | 7/5/2022 7:57:26 | Jan | ? | Content | Information about a workaround for elevation or boundary issues. Temporarily setting the airport elevation to a higher value so the terrain isn't covering any objects anymore, edit them the right way and returning elevation to its original value when done. | Rejected | N/A | We would prefer not to recommend this hack but Editors are of course free to use this method if they are confident. Thanks, RAH. | |
21 | 7/5/2022 8:24:15 | Jan | 9.50 | Content | In order to prevent issues with objects sticking out, the distance between two nodes of a model line can not be smaller than the length of the object used. | Approved | 23.1.1 | N/A | |
22 | 7/5/2022 8:37:20 | Jan | ? | Content | Information about how to add or edit runways, including Tom's way of using coordinates to place windsocks to get the runway ends exactly right. | Under Review | |||
23 | 7/5/2022 8:40:23 | Jan | ? | Content | Information about which approach lights to select for each runway end. So the differences between the options and how to select the one that comes closest to the real life situation. | https://community.infiniteflight.com/t/tips-and-how-tos-real-world-airfield-information-research-satellite-imagery-parallel-facades-extrusion/608259/18 | Under Review | ||
24 | 7/5/2022 9:04:03 | Jan | ? | Other | Search isn't working very well. Often there are no results for things that are mentioned in the manual several times. | Approved | N/A | Known issue, hopefully will have this fixed soon. Thanks, RAH. | |
25 | 7/13/2022 3:02:51 | XY_MAGIC | 3.1.2 | Content | The first link (Scenery Editor Category) in Step 3 directs you to the scenery editing category. It should direct you to the scenery editing:editors category tho. | Approved | 22.8.1 | N/A | |
26 | 7/25/2022 12:09:01 | Jan? | ? | Content | This adds to my earlier report about adding information about how to add or edit runways. In this case it's about adding information about the runway shoulders. That the width is fixed and can't be changed and that adding pavement along the runway to recreate the shoulders is also an option. | Under Review | |||
27 | 8/2/2022 9:29:07 | Jan | ? | Content | Another addition to information about the runway properties. When the runway width is smaller than 15, the numbers won't be shown. | Under Review | |||
28 | 9/1/2022 5:39:49 | Jan | 4.20 | Content | The manual now says this about Quality: "Select 100% - if the file needs to be smaller, consider using a lower zoom level such as z20 instead of z21." After a lot of testing it turns out that using a setting of 50% image quality gives a virtually identical result as when 100% is used. Yet the file size when using 100% image quality is almost 8 times larger. A zip file created with 100% image quality and a size of 450Mb, would give the exact same amount of detail as a file created with 50% image quality that is only 70Mb and is way easier to share. More information is in a pinned message in #sas in Discord. | Approved | 23.1.1 | N/A | |
29 | 10/17/2022 5:35:18 | XY_MAGIC | 5.10 | Other | The icons that indicate if something should be done or not are missing in the Do's and Don'ts section. (All other Do's and Don'ts sections have ✅ and ❌ in front of them) | Approved | 22.8.1 | N/A | |
30 | 11/8/2022 12:12:20 | XY_MAGIC | 11.1.3 | Content | In the sentence “No more than 2 peer reviews can be given per airport[…]“ it still says that 2 PRs are allowed however this was changed to only 1 recently. | Approved | 22.8.1 | N/A | |
31 | 1/29/2023 19:20:07 | AviationFlyer | 3.3.2 | Content | "If changing the airport boundary, a navigation database update will be required before the new boundary is reflected in-app. Therefore Editors must not add any new buildings/objects in the new airport boundary until this has been updated" - This is clearly not followed because there are so many times this rule would waste unnecessary time (and reviewers are not very strict about this rule). Therefore, a suggestion to make it more clear is to change the must not too should not. | Approved | 23.1.1 | N/A | |
32 | 4/3/2023 11:53:27 | Mathurin_Garcier | 8.2.2 | Content | The table with hangar sizes should include the C-130’s dimensions, useful for military airfields. If needed I measured that 17 meters is the minimum required height for a hangar. | Yes, it could be done for the C-17 aswell | Approved | 23.2.1 | N/A |
33 | 6/29/2023 10:56:02 | Major Tom | 6.10 | Content | in the do and do not table, at the point "do not add Xs to taxiways" add " , or runways" | It is quite irritating that this form has the IFATC logo on top | Approved | 24.1.1 | N/A |
34 | 3/16/2024 14:53:06 | brunocr98 | 1A.4.3 | Content | I want a note to be added explaining that reviewers are only limited to review and provide feedback on airports, and not to perform any changes themselves. This is in response to an event raised by an editor via DM, in which he complained about a reviewer making some changes to his airport, before posting the feedback. The editor affirms that the reviewer changed some lines and uploaded the changes as a draft, without his consent. I don't mind if reviewers make changes to airports, as long as they're small and aren't worth of sending them back to the review cycle. Notable/significant issues must always be addressed by the editor. The note should reference the sentence that says: "Review editing quality via the "Official Review" process." | Refer to the link for the context of my report: https://community.infiniteflight.com/t/kbgr-bangor-international-airport/781395/22?u=brunocr98 | Under Review | ||
35 | |||||||||
36 | |||||||||
37 | |||||||||
38 | |||||||||
39 | |||||||||
40 | |||||||||
41 | |||||||||
42 | |||||||||
43 | |||||||||
44 | |||||||||
45 | |||||||||
46 | |||||||||
47 | |||||||||
48 | |||||||||
49 | |||||||||
50 | |||||||||
51 | |||||||||
52 | |||||||||
53 | |||||||||
54 | |||||||||
55 | |||||||||
56 | |||||||||
57 | |||||||||
58 | |||||||||
59 | |||||||||
60 | |||||||||
61 | |||||||||
62 | |||||||||
63 | |||||||||
64 | |||||||||
65 | |||||||||
66 | |||||||||
67 | |||||||||
68 | |||||||||
69 | |||||||||
70 | |||||||||
71 | |||||||||
72 | |||||||||
73 | |||||||||
74 | |||||||||
75 | |||||||||
76 | |||||||||
77 | |||||||||
78 | |||||||||
79 | |||||||||
80 | |||||||||
81 | |||||||||
82 | |||||||||
83 | |||||||||
84 | |||||||||
85 | |||||||||
86 | |||||||||
87 | |||||||||
88 | |||||||||
89 | |||||||||
90 | |||||||||
91 | |||||||||
92 | |||||||||
93 | |||||||||
94 | |||||||||
95 | |||||||||
96 | |||||||||
97 | |||||||||
98 | |||||||||
99 | |||||||||
100 | |||||||||