When taxing to runway 07R via L Y Y1 M29 you will see that the taxi sign is showing that you are close to runway 07L. This should be 07R. And i think this is the case on every taxiway to 07R, it shows the wrong info.
Oh, thanks for the heads-up! It is quite possible that this may have slipped my quality control, I will doublecheck and correct if necessary!
Cheers, Jan
Should be fixed now with new version of EDDF in XP12.
phjjjjj
commented
in reference to scenery pack
65906on February 17, 2019 4:08 PM
Satellite imagery indicates that there is no runway numbering on "runway 36". I believe that technically, there exists no runway 36 in EDDF and runway 18 is used for takeoff exclusively.
Guys, you don´t have to work on the Scenery Gateway version of EDDF. It will never show in the simulator, because the Aerosoft custom hybrid airport is suppressing it.
I will take care of all changes at EDDF and also doublecheck the ILS components.
Only I (on account of Laminar) can alter EDDF, so just report the problems and I will fix them...
Holding points M19, M25, M29, R11, R15, R17 (and possibly some more I missed) show 07L instead of 07R.
X-plane 11.51r1 (not 100% sure about scenery pack id).
Hallo i am using an aerosoft scenry of EDDF and notice that the fps coming near to the runway 07C so that my sim probably crashs. I desable a lot of my plugings to check if the issue appears again. After many tries whatever i do my fps are always droping. I come to you today to ask for a way to find a solution for this problem.
gercarst
commented
in reference to scenery pack
97940on August 26, 2023 6:51 PM
Hello Julian, could the recommended version (92577) be revised?
I downloaded the recommended version and only added the breakaway pushback areas.
The 2 mentioned taxiway problems are already in the recommended version.
1.) The Flow definition is wrong. According to local procedures the main traffic shall be 25/18 where a tailwind component of 5kn is acceptable on rwys 25 AND a tailwind component of even 15kn for rwy 18.
More tailwind component of 15kn on rwy 18 results in closure of rwy 18. This scenery accepts tailwind component of 35kn for rwy 18, wich is obviously too much.
2.) The designator for Lufthansa Cargo is NOT "dlh" but "gec" and therefore the LH-Cargo Hub is not filled correctly
See both changes I suggest in the apt.dat that is enclosed
Regards Ron
"Just for your information - posting these kind of bug reports will basically never get the airport fixed. You will have to do it yourself using the free WED program and the Scenery Gateway. You can hope someone else will do it, but you may have to wait a long time or possibly forever.
Laminar Research does not fix airports, only the volunteer airport artist community (= normal users) do."
So feel free to dive in scenery development and fix these issues!
There is no way to set a tailwind limit in Xplane. There is also no “GEC” livery in XPlane (yet), so setting has no effect. In fact often Lufthansa passenger aircraft park on those ramps, too.
I admit its not easy to fully understand the various possibilities of creating a wind-rule on such complex airports like EDDF, where a parallel rwy system(25/07) is colliding with a widely different departure rwy(18) in terms of heading.
The current version of EDDF in global airports produces the following warning in the world-editor: [quote]
EDDF: Wind Rules in flow 'Standard SouthWest Flow' allow Runway 18 to be used with up to 34 kts tailwind component @ 35 kts winds (warning only)
EDDF: Wind Rules in flow 'Standard Northeast Flow' allow Runway 18 to be used with up to 35 kts tailwind component @ 35 kts winds (warning only) [unquote]
So far so bad. No pilot on earth would take a 4000m rwy with a wide body plane at a tailwind component of 35kts as a takeoff rwy.
In my bug report I had enclosed a modified apt.dat with necessary changes in the wind-rules/rwy usage to avoid those ridiculous ATIS messages regarding "runway in use".
When opening this modified apt.dat in WED it says now [quote]
EDDF: Wind Rules in flow 'SouthWest Flow' allow Runway 18 to be used with up to 15 kts tailwind component @ 35 kts winds (warning only)
EDDF: Wind Rules in flow 'Northeast Flow' allow Runway 18 to be used with up to 15 kts tailwind component @ 35 kts winds (warning only) [unquote]
Thats what we want. A maximum of 15kts tailwind component for 18, as stated in the official Jeppesen docs. If tailwind component exceeds 15kts, then 18 is closed. At the same time maximum crosswinds of 35kts remain unchanged for 25/07
Thus your statement "There is no way to set a tailwind limit in Xplane" is wrong. Its just a matter of using the wind rules in the right way.
2.)
no “GEC” livery in XPlane (yet)? It has no effect to put in the correct airline designator? Excuse me!
See the following screenshot using x-plane 12 with the add-on "Traffic Global" in EDDF at the LH-Cargo hub, as its supposed to be
Sorry, you don´t understand enough about these things and I don´t have the time to explain it further. Suffice it to say, you are wrong.
You can use the apt.dat in your own version though with no problem, the official EDDF wont use it.
You must be logged in to participate in the discussion
When taxing to runway 07R via L Y Y1 M29 you will see that the taxi sign is showing that you are close to runway 07L. This should be 07R. And i think this is the case on every taxiway to 07R, it shows the wrong info.
Jan Vogel October 18, 2018 5:31 PM
Oh, thanks for the heads-up! It is quite possible that this may have slipped my quality control, I will doublecheck and correct if necessary!
Cheers, Jan
Jan Vogel March 5, 2021 4:10 PM
I will fix this when I overhaul the hybrid (Aerosoft) version of this airport. Will work on the Gateway version at the same time.
Jan Vogel September 25, 2022 5:38 PM
Should be fixed now with new version of EDDF in XP12.
Satellite imagery indicates that there is no runway numbering on "runway 36". I believe that technically, there exists no runway 36 in EDDF and runway 18 is used for takeoff exclusively.
Guys, you don´t have to work on the Scenery Gateway version of EDDF. It will never show in the simulator, because the Aerosoft custom hybrid airport is suppressing it.
I will take care of all changes at EDDF and also doublecheck the ILS components.
Only I (on account of Laminar) can alter EDDF, so just report the problems and I will fix them...
Jan
Holding points M19, M25, M29, R11, R15, R17 (and possibly some more I missed) show 07L instead of 07R.
X-plane 11.51r1 (not 100% sure about scenery pack id).
Jan Vogel January 26, 2021 8:19 AM
Thanks for the report, I will take a look!
Hallo i am using an aerosoft scenry of EDDF and notice that the fps coming near to the runway 07C so that my sim probably crashs. I desable a lot of my plugings to check if the issue appears again. After many tries whatever i do my fps are always droping. I come to you today to ask for a way to find a solution for this problem.
I am using a
Peronekiko October 27, 2021 6:02 PM
i am using a GTX 1070 Graphic card
Jan Vogel October 29, 2021 11:44 AM
You problem can not be solved by Laminar Research.
As this is marked as recommended...is it ment to be used with xp11 already? I get missing library files when i try to load it.
Error message: additional library requiered
"0:00:38.387 E/SCN: Unable to locate object: lib/airport/ground/terrain_FX/taxi_sign_base/light/3.6m/3.6m.obj"
Jan Vogel September 18, 2022 2:37 PM
Lol, are you serious?
N8033 Fox September 20, 2022 6:14 PM
It works great on XP12
third party components request
Hello Julian, could the recommended version (92577) be revised? I downloaded the recommended version and only added the breakaway pushback areas. The 2 mentioned taxiway problems are already in the recommended version.
-Rwy 18. Taxiway/runway join issue(s).
-Rwy 25R. Taxiways should not overlap runway shoulders except near taxiway/runway intersections.
-Assets (forests/objects/facades/roads/draped polygons/exclusions/AI networks/other) have been placed outside airport boundary.
1.) The Flow definition is wrong. According to local procedures the main traffic shall be 25/18 where a tailwind component of 5kn is acceptable on rwys 25 AND a tailwind component of even 15kn for rwy 18.
More tailwind component of 15kn on rwy 18 results in closure of rwy 18. This scenery accepts tailwind component of 35kn for rwy 18, wich is obviously too much.
2.) The designator for Lufthansa Cargo is NOT "dlh" but "gec" and therefore the LH-Cargo Hub is not filled correctly
See both changes I suggest in the apt.dat that is enclosed
Regards Ron
Stefan Frank February 9, 2024 2:49 PM
hi ronB1950,
quoting Jan Vogel:
"Just for your information - posting these kind of bug reports will basically never get the airport fixed. You will have to do it yourself using the free WED program and the Scenery Gateway. You can hope someone else will do it, but you may have to wait a long time or possibly forever.
Laminar Research does not fix airports, only the volunteer airport artist community (= normal users) do."
So feel free to dive in scenery development and fix these issues!
BR, Stefan
Jan Vogel February 10, 2024 5:24 PM
There is no way to set a tailwind limit in Xplane. There is also no “GEC” livery in XPlane (yet), so setting has no effect. In fact often Lufthansa passenger aircraft park on those ramps, too.
ronB1950 February 12, 2024 9:21 PM
@Jan Vogel
1.)
I admit its not easy to fully understand the various possibilities of creating a wind-rule on such complex airports like EDDF, where a parallel rwy system(25/07) is colliding with a widely different departure rwy(18) in terms of heading.
The current version of EDDF in global airports produces the following warning in the world-editor:
[quote]
EDDF: Wind Rules in flow 'Standard SouthWest Flow' allow Runway 18 to be used with up to 34 kts tailwind component @ 35 kts winds (warning only)
EDDF: Wind Rules in flow 'Standard Northeast Flow' allow Runway 18 to be used with up to 35 kts tailwind component @ 35 kts winds (warning only)
[unquote]
So far so bad. No pilot on earth would take a 4000m rwy with a wide body plane at a tailwind component of 35kts as a takeoff rwy.
In my bug report I had enclosed a modified apt.dat with necessary changes in the wind-rules/rwy usage to avoid those ridiculous ATIS messages regarding "runway in use".
When opening this modified apt.dat in WED it says now
[quote]
EDDF: Wind Rules in flow 'SouthWest Flow' allow Runway 18 to be used with up to 15 kts tailwind component @ 35 kts winds (warning only)
EDDF: Wind Rules in flow 'Northeast Flow' allow Runway 18 to be used with up to 15 kts tailwind component @ 35 kts winds (warning only)
[unquote]
Thats what we want. A maximum of 15kts tailwind component for 18, as stated in the official Jeppesen docs. If tailwind component exceeds 15kts, then 18 is closed. At the same time maximum crosswinds of 35kts remain unchanged for 25/07
Thus your statement "There is no way to set a tailwind limit in Xplane" is wrong. Its just a matter of using the wind rules in the right way.
2.)
no “GEC” livery in XPlane (yet)? It has no effect to put in the correct airline designator? Excuse me!
See the following screenshot using x-plane 12 with the add-on "Traffic Global" in EDDF at the LH-Cargo hub, as its supposed to be
https://postimg.cc/H8nf5crs
Jan Vogel February 15, 2024 5:32 PM
Sorry, you don´t understand enough about these things and I don´t have the time to explain it further. Suffice it to say, you are wrong.
You can use the apt.dat in your own version though with no problem, the official EDDF wont use it.