As of January 2024, runway 04L/22R is operational. The existing runway has been renamed to 04R/22L. As of today, WED won't let me make this change because there is no CIFP data for these changes. When can we usually expect this to be activated?
I am attaching a more recent ESRI image of the airport as it stands today.
Newest CIFP data as of 2025-Jan-23 is uploaded to the gateway.
This data only lists a runway 22/04. I see no reference to a 22L/044R in real world data. I have checked my real world EFB which uses Jeppesen data. It shows no 04L/22R at RPVM either.
I'm not sure where to file this as I'm not sure if this is a WED or a scenery issue.
Steam users getting lower level of detail with a large portion of the golf course wiped out. The scenery does not include these areas in its boundaries. XP Installer users reported seeing an ortho rendering of a golf course in the area, but exclusion zones aren't working where they're supposed to. This becomes a problem for scenery developers with Steam versions as they cannot reconcile issues reported by mods in the review process.
View as seen from Standalone users. Assumption is both versions have Vegetation, World Objects & Draw distance to max. Personally, I am a Steam version owner so when a mod reports seeing an issue I cannot reproduce I will have a problem fixing it. My go-to assumption was to add an exclusion zone with trees & objects but it would be difficult to verify if my changes worked. Furthermore, it appears the exclusion zone is not being honored by X-Plane because here we are.
Was able to finally resolve this issue albeit a very nuanced one. The exclusion zone was very fickle as to where it was placed. I nudged it by a few pixels and the cleanup was triggered.
ch4dwick
commented
in reference to scenery pack
105412on February 6, 2025 3:38 AM
Okay. Weird thing. I revisited this version and wondered why it wasn't working as expected. Turns out X-Plane is a little fickle when dealing with the exclusion zone. I moved the EZ by a few pixels down and added an objects exclusion. This appears to have triggered the cleanup. Just sharing this for future reference.
ch4dwick
commented
in reference to scenery pack
105949on March 8, 2025 9:53 AM
There seems to be some OSM & ESRI updates since I checked last Feb that has caused unintended incursions on the previous version. I know I said I wasn't going to post further updates until the new CIFP with the new runway was activated but should the next scenery rollout happen before the CIFP is received this will give users a troublesome experience with it. Best to just get ahead of this and fid it first.
ch4dwick
commented
in reference to scenery pack
105949on March 28, 2025 2:57 PM
I just found out that the tree & road incursions were caused by autoortho overlays even when it's not running. Removing them fixed most of the incursions except for the runway 06 area. The symptom involves xplane generating objects twice - roads, trees, houses. Disabling autoortho folders should fix this issue for now.
A follow up to
XSG-15753
Done
, Runway 04L-22R is now active on X-Plane FMS, however, scenery validation still recognizes only one runway. Normally, this would be fine, but this update introduced an issue where SIDs are now only specific to one side of the runway. Any chance we can see an update on the next few months?
Additional context: The AI ATC and the preceding flight plan filing also doesn't recognize the SIDs/STARs that use the new runway configuration so you can't file a flight plan without skipping the SID entirely and cause it to give you frequent off course warnings. In-sim FMS/FMC/Avionic don't have any issues picking up the new SIDs though.
As of January 2024, runway 04L/22R is operational. The existing runway has been renamed to 04R/22L. As of today, WED won't let me make this change because there is no CIFP data for these changes. When can we usually expect this to be activated?
I am attaching a more recent ESRI image of the airport as it stands today.
Philipp Ringler January 23, 2025 9:05 PM
Newest CIFP data as of 2025-Jan-23 is uploaded to the gateway.
This data only lists a runway 22/04. I see no reference to a 22L/044R in real world data. I have checked my real world EFB which uses Jeppesen data. It shows no 04L/22R at RPVM either.
ch4dwick February 6, 2025 11:21 AM
Guess I'll just have to wait a little longer.
ch4dwick July 11, 2025 12:33 PM
AIRAC 2507 already adds the new runway numbers. Any chance I can follow up if this is also true for gateway data?
I'm not sure where to file this as I'm not sure if this is a WED or a scenery issue.
Steam users getting lower level of detail with a large portion of the golf course wiped out. The scenery does not include these areas in its boundaries. XP Installer users reported seeing an ortho rendering of a golf course in the area, but exclusion zones aren't working where they're supposed to. This becomes a problem for scenery developers with Steam versions as they cannot reconcile issues reported by mods in the review process.
ch4dwick February 5, 2025 4:42 AM
View as seen from Standalone users. Assumption is both versions have Vegetation, World Objects & Draw distance to max. Personally, I am a Steam version owner so when a mod reports seeing an issue I cannot reproduce I will have a problem fixing it. My go-to assumption was to add an exclusion zone with trees & objects but it would be difficult to verify if my changes worked. Furthermore, it appears the exclusion zone is not being honored by X-Plane because here we are.
ch4dwick February 6, 2025 3:39 AM
Was able to finally resolve this issue albeit a very nuanced one. The exclusion zone was very fickle as to where it was placed. I nudged it by a few pixels and the cleanup was triggered.
Okay. Weird thing. I revisited this version and wondered why it wasn't working as expected. Turns out X-Plane is a little fickle when dealing with the exclusion zone. I moved the EZ by a few pixels down and added an objects exclusion. This appears to have triggered the cleanup. Just sharing this for future reference.
There seems to be some OSM & ESRI updates since I checked last Feb that has caused unintended incursions on the previous version. I know I said I wasn't going to post further updates until the new CIFP with the new runway was activated but should the next scenery rollout happen before the CIFP is received this will give users a troublesome experience with it. Best to just get ahead of this and fid it first.
I just found out that the tree & road incursions were caused by autoortho overlays even when it's not running. Removing them fixed most of the incursions except for the runway 06 area. The symptom involves xplane generating objects twice - roads, trees, houses. Disabling autoortho folders should fix this issue for now.
A follow up to
XSG-15753
Done
, Runway 04L-22R is now active on X-Plane FMS, however, scenery validation still recognizes only one runway. Normally, this would be fine, but this update introduced an issue where SIDs are now only specific to one side of the runway. Any chance we can see an update on the next few months?
ch4dwick July 20, 2025 11:54 AM
July 18 was official opening https://www.sunstar.com.ph/cebu/mactan-cebu-international-airport-opens-2nd-runway
ch4dwick July 20, 2025 1:18 PM
(not sure if this is relevant)
Additional context: The AI ATC and the preceding flight plan filing also doesn't recognize the SIDs/STARs that use the new runway configuration so you can't file a flight plan without skipping the SID entirely and cause it to give you frequent off course warnings. In-sim FMS/FMC/Avionic don't have any issues picking up the new SIDs though.
Philipp Ringler July 21, 2025 5:18 PM
please don’t make duplicate reports about the same issue.
ch4dwick July 22, 2025 9:15 AM
Okay. I wasn't sure of the process.