Hi all,
I'm trying to convert a FS9 airport to FSX:SE. One of the clear issues early on was ground polygon flickering. This particular airport has 13 BGL files that each appear to contain a layer of the Ground Polygon.
I've converted them all and tidied up the layering through the Ground Polygon Wizard in MCX. Results are vastly improved.
There is one outstanding issue which I'm having real trouble understanding. Refer to the attached screenshot.
I just don't understand why as I get closer to the runway, the part of the runway underneath me appears to have the 'noise texture' layer disappear. You can see it in the distance, but not underneath me. I don't think there is any underlying terrain that is poking through because when I fly away, turn around and have a look at the section of runway I was hovering over, well then it's ok. But of course the runway now underneath me has had that 'noise texture' layer disappear. The issue seems to be related to distance and drawing, but I don't understand what I'm seeing and what may be the cause.
Confusing me even more is that one side of the runway displays the 'runway edge texture' layer, but the other side doesn't? How can this be when they're part of the same polygon in the same layer?
I'm looking for some help in interpreting what I'm seeing so that I can begin to try to rectify it. Any input is appreciated.
For what it's worth, I have 13 BGLs allocated to 12 separate layers (this wasn't my choice of course, just how the scenery was made). These layers range from between 8 and 52. The 'noise texture' layer is assigned to 28 and the 'runway edge texture' layer is assigned to 20.
The tire marks layer that you can see in the attached screenshot is layer 44 and as you can see, there is no problem with the visibility of that layer.
Also, I had trouble with these two BGLs when using the GP wizard first time around as it split the BGLs into separate polys, but it all wound up messed up. Second time around, I unticked the option to slice polygons and group polygons and it works much better in FSX, with of course this issue that I'm trying to describe.
I'm scratching my head with this and thank the community in advance for any help provided.
Trent
I'm trying to convert a FS9 airport to FSX:SE. One of the clear issues early on was ground polygon flickering. This particular airport has 13 BGL files that each appear to contain a layer of the Ground Polygon.
I've converted them all and tidied up the layering through the Ground Polygon Wizard in MCX. Results are vastly improved.
There is one outstanding issue which I'm having real trouble understanding. Refer to the attached screenshot.
I just don't understand why as I get closer to the runway, the part of the runway underneath me appears to have the 'noise texture' layer disappear. You can see it in the distance, but not underneath me. I don't think there is any underlying terrain that is poking through because when I fly away, turn around and have a look at the section of runway I was hovering over, well then it's ok. But of course the runway now underneath me has had that 'noise texture' layer disappear. The issue seems to be related to distance and drawing, but I don't understand what I'm seeing and what may be the cause.
Confusing me even more is that one side of the runway displays the 'runway edge texture' layer, but the other side doesn't? How can this be when they're part of the same polygon in the same layer?
I'm looking for some help in interpreting what I'm seeing so that I can begin to try to rectify it. Any input is appreciated.
For what it's worth, I have 13 BGLs allocated to 12 separate layers (this wasn't my choice of course, just how the scenery was made). These layers range from between 8 and 52. The 'noise texture' layer is assigned to 28 and the 'runway edge texture' layer is assigned to 20.
The tire marks layer that you can see in the attached screenshot is layer 44 and as you can see, there is no problem with the visibility of that layer.
Also, I had trouble with these two BGLs when using the GP wizard first time around as it split the BGLs into separate polys, but it all wound up messed up. Second time around, I unticked the option to slice polygons and group polygons and it works much better in FSX, with of course this issue that I'm trying to describe.
I'm scratching my head with this and thank the community in advance for any help provided.
Trent
