Moderator Julian reports "Road network incursion on runway 03/21" but I don't see any roads. I am not an expert, all I did was change the beacon type. If the layout is broken how did this get in here in the first place?
The only other submission was the default scenery and most likely it did not have an exclusion zone. It is good practice to include them in every pack you create to make sure autogen elements (trees, roads, etc) do not show up in unwanted places.
Thank you Jennifer. I am just learning. I will elevate my object detail level and add the needed exclusion zone(s) as needed. Thanks for taking the time to help me.
I maxed out "number of objects" and "number of roads". This is XP10.51. I can't see any road incursions. I apologize for beating this to death, but I really want to get the beacon fix into the system.. Here are screen shots of the airport and the corresponding render settings (attached)
The issue may lie in the X-Plane version. Moderators and the X-Plane team are only considering things against X-Plane 11 which has newer, recut scenery so the road patterns may be different.
Again, it is generally always good practice to include exclusion zones if you've already gone through the trouble of creating scenery. Make sure you set them to exclude everything (it might default to nothing or only one thing, so it may appear they aren't doing anything either).
Trying to fix the scenery for runway number changes per the bug report. See my comment, the gateway is refusing my upload for the runway numbers. Apparently the "CIFP" data (whatever that is) is out of date. I will upload when this is fixed.
This is incorrect. The runway numbers have changed due to the magnetic variation having changed. Please see the attached which clearly shows the runways are perfectly aligned with the satellite imagery which Wed-O-Maker applied. I was not involved in setting the coordinates of the overlays.
The runway numbers shouldn't pose a problem - even if they are outdated, X-Plane can guess the right runway as long as it is in the right location. This seems to be the case here, so the runway number being outdated has actually no adverse effect in X-Plane. You will be able to submit the new runway numbers when we update the runway data server-side (first cycle of 2019 probably).
My issue is not being able to upload to the scenery gateway to correct the original problem
XSG-6616
Done
. The upload process reports a server-side validation error and prohibits it. It seems I need to wait for 2019-1 cycle then?
Oy, that sneaky magvar drift..... I tried to change them but apparently they are not updated in CIFP data? I get a validation error when trying to upload:
"Error: could not find runway(s) 03 12 21 30 required by CIFP data at airport KBAM"
What should I do? The airport is stagedready for upload and has no local validation errors for the gateway target.
You must be logged in to participate in the discussion
KBAM - The airport beacon is a military type showing two whites and a green. This is a civilian airport, so the beacon should show white-green
Bob Denny July 3, 2017 1:42 PM
Changed the beacon type from Military to Airport. Flash pattern is now correct white-green.
Bob Denny July 16, 2017 12:22 PM
Moderator Julian reports "Road network incursion on runway 03/21" but I don't see any roads. I am not an expert, all I did was change the beacon type. If the layout is broken how did this get in here in the first place?
Jennifer Roberts July 17, 2017 8:32 AM
The only other submission was the default scenery and most likely it did not have an exclusion zone. It is good practice to include them in every pack you create to make sure autogen elements (trees, roads, etc) do not show up in unwanted places.
Bob Denny July 17, 2017 2:43 PM
Thank you Jennifer. I am just learning. I will elevate my object detail level and add the needed exclusion zone(s) as needed. Thanks for taking the time to help me.
Bob Denny July 21, 2017 8:18 AM
I maxed out "number of objects" and "number of roads". This is XP10.51. I can't see any road incursions. I apologize for beating this to death, but I really want to get the beacon fix into the system.. Here are screen shots of the airport and the corresponding render settings (attached)
Bob Denny July 21, 2017 8:20 AM
Hmm.. the attachments didn't work. Here are dropbox links:
https://dl.dropboxusercontent.com/u/8209159/KBAM-1.jpg
https://dl.dropboxusercontent.com/u/8209159/KBAM-2.jpg
Jennifer Roberts July 21, 2017 8:41 AM
The issue may lie in the X-Plane version. Moderators and the X-Plane team are only considering things against X-Plane 11 which has newer, recut scenery so the road patterns may be different.
Again, it is generally always good practice to include exclusion zones if you've already gone through the trouble of creating scenery.
Make sure you set them to exclude everything (it might default to nothing or only one thing, so it may appear they aren't doing anything either).
Trying to fix the scenery for runway number changes per the bug report. See my comment, the gateway is refusing my upload for the runway numbers. Apparently the "CIFP" data (whatever that is) is out of date. I will upload when this is fixed.
Philipp Ringler December 14, 2018 5:41 PM
CIFP data for this runway is correct.
The scenery is wrong, the runway needs to be moved in order to be correct.
Bob Denny December 17, 2018 4:54 PM
This is incorrect. The runway numbers have changed due to the magnetic variation having changed. Please see the attached which clearly shows the runways are perfectly aligned with the satellite imagery which Wed-O-Maker applied. I was not involved in setting the coordinates of the overlays.
Philipp Ringler December 17, 2018 8:21 PM
The runway numbers shouldn't pose a problem - even if they are outdated, X-Plane can guess the right runway as long as it is in the right location. This seems to be the case here, so the runway number being outdated has actually no adverse effect in X-Plane. You will be able to submit the new runway numbers when we update the runway data server-side (first cycle of 2019 probably).
Bob Denny December 17, 2018 8:58 PM
My issue is not being able to upload to the scenery gateway to correct the original problem
Philipp Ringler December 17, 2018 9:02 PM
I pushed a manual change for you. Try in a few minutes.
Bob Denny February 4, 2020 11:57 PM
A belated thanks for this. I sort of lost interest in scenery development for a while.
Jan Vogel February 28, 2021 11:18 AM
Airport has been updated recently, this report can be closed.
Oy, that sneaky magvar drift..... I tried to change them but apparently they are not updated in CIFP data? I get a validation error when trying to upload:
"Error: could not find runway(s) 03 12 21 30 required by CIFP data at airport KBAM"
What should I do? The airport is stagedready for upload and has no local validation errors for the gateway target.