Also still unsolved: missing Runway numbers.

the German traffic patterns are implemented using platzrunden.txt, and we're having trouble getting that updated all the time with correct and complete information. 

The traffic pattern information mentioned in QuickInfo->Airfield Info is NOT part of platzrunden.txt and is already in our maintenance cycle for a few years, but includes only traffic pattern direction and altitude, not the entire exact pattern. Also its not suited for multiple traffic patterns for different aircraft types. 

These conflicting sources for german traffic circuits are a PITA at the moment, so one of the upcoming internal projects is to get rid of this platzrunden.txt entirely and add a design tool to EV4 that we can use internally so we can append linefeatures like traffic circuits, arrival and departure procedures, CTR transit routes etc as part of our daily aerodata maintenance work.  

@infosavannah-blog-de what exactly do you ,mean? AFIK all runways have runway idents ? 

yes, the RWY numbers are there, but you have to zoom in very far to make them appear.

In my opinion, the traffic pattern, the TPaltitude and the RWY designators should appear simultaneously at a zoom level that is considered suitable for approaching an airfield.  Normally you call 5 min out, and that is the time you need this info displayed.

Runway Idents and traffic pattern altitude text take a certain screenspace to be readable. To have TPaltitude, Runway ident and traffic pattern kick in at exactly the same camera would mean the rendering of the traffic pattern would have to be delayed until zoomed in at the same level where runway idents get displayed. Personally I find that too late, I still find it interesting to know if an airfield has a left- or righthand pattern, even when zoomed out at levels where runway Idents are not doable anymore, for example this screenshot : 

But as always we're open for different opinions .....