Landing rwy 27
Re: Landing rwy 27
Just landed at KBOS on 27 when it appeared I hit something just above the runway on flare. Does the attached file fix the problem?
Re: Landing rwy 27
I am still having this issue with RWY 27 at BOS. When I cross over the threshold for RWY 27, the runway markings go blurry until I have touched down. I tried adding the file on the previous page to my FT/BOS scenery. And I have my mesh set to 5. Any updates on this?
Re: Landing rwy 27
I have fixed my issue on this topic with the installed file and tweaking all of the settings listed in the FlyTampa BOS documentation.jammen737 wrote: ↑Thu Apr 16, 2020 9:31 pm I am still having this issue with RWY 27 at BOS. When I cross over the threshold for RWY 27, the runway markings go blurry until I have touched down. I tried adding the file on the previous page to my FT/BOS scenery. And I have my mesh set to 5. Any updates on this?
Re: Landing rwy 27
This issue is a FSX/P3D common issue from a long time ago with elevated thresholds adjacent to water (like KBOS, SBRJ...) or thresholds higher than the contiguos terrain (like SBKP rwy15).
I've been evaluating this issue with some brazilian developers and I found that:
1. it uses to happen mostly if you come from another airport, not if you take off from the specific airport to just fly a visual pattern and land again
2. it is related to the hightest mesh resolutions, as it tends to not take place if you reduce resolution to a higher algarism (moving slider to the left)
3. it is related to the speed with which the simulator loads terrain mesh ahead of you while flying, as in the events in which I noted the simulator still loading and shaping the threshold lithograph during short final, the issue occurred, which means its cause was the fact of the simulator had haven't enough time to load mesh data and draw the terrain under threshold on time before you cross the stripes
From time to time I still see this issue in some places.
As you use higher mesh resolution (slider to the right), the simulator needs more time to draw the terrain (the simulator increase resolution of terrain mesh around you as you get closer to the terrain element). The mountain far away on the horizon is loaded initially with low resolution and becomes better shaped as you come closer to it. The same occurs with thresholds higher than what is around (water or low ground).
If you (unrealisticly) pause your simulator for some seconds on the very short final and then continue to land, probably it will not occur anymore. In the other hand, if you start simming at KBOS rwy 09, take off eastbound and make a 180º on initial climb to land immediatly on 27, it will not take place, as the terrain all around the airport is already fully loaded since the beggining.
I'm still looking for a realistic solution to use my desired 1m mesh resolution everywhere with no problems like this. The negative point in reducing mesh resolution to 5m, 10m and so on is that sometimes you fly somewhere that requires higher resolutions (like LPMA) and the worst thing is to remember to increase mesh resolution only when about to touchdown in those places.
I've been evaluating this issue with some brazilian developers and I found that:
1. it uses to happen mostly if you come from another airport, not if you take off from the specific airport to just fly a visual pattern and land again
2. it is related to the hightest mesh resolutions, as it tends to not take place if you reduce resolution to a higher algarism (moving slider to the left)
3. it is related to the speed with which the simulator loads terrain mesh ahead of you while flying, as in the events in which I noted the simulator still loading and shaping the threshold lithograph during short final, the issue occurred, which means its cause was the fact of the simulator had haven't enough time to load mesh data and draw the terrain under threshold on time before you cross the stripes
From time to time I still see this issue in some places.
As you use higher mesh resolution (slider to the right), the simulator needs more time to draw the terrain (the simulator increase resolution of terrain mesh around you as you get closer to the terrain element). The mountain far away on the horizon is loaded initially with low resolution and becomes better shaped as you come closer to it. The same occurs with thresholds higher than what is around (water or low ground).
If you (unrealisticly) pause your simulator for some seconds on the very short final and then continue to land, probably it will not occur anymore. In the other hand, if you start simming at KBOS rwy 09, take off eastbound and make a 180º on initial climb to land immediatly on 27, it will not take place, as the terrain all around the airport is already fully loaded since the beggining.
I'm still looking for a realistic solution to use my desired 1m mesh resolution everywhere with no problems like this. The negative point in reducing mesh resolution to 5m, 10m and so on is that sometimes you fly somewhere that requires higher resolutions (like LPMA) and the worst thing is to remember to increase mesh resolution only when about to touchdown in those places.
Re: Landing rwy 27
george[flytampa] wrote: ↑Thu Jun 21, 2018 8:44 pm The attached file should fix the dodgy aircraft collision when transitioning over the 27 coastline.
Copy it into 'your Prepar3d'\FlyTampa\Boston\scenery
Thank you very much , this solved my problem after 3 days of aggravation , good thing I came across this post.
Good job