

The problem seems to be tied somehow to the way textures are calculated and displayed, and it has a slight reference to the "render-to-texture" settings in the FS9 graphics options dialog as well.I encountered a big FPS loss when turning off texture rendering by either using panel_as_texture=0 or removing the checkmark for the render-to-texture option (as far as I know this option offloads the process of rending to the graphics hardware and thus results in higher framerates), so I decided to accept the gaps at the panel edges but gain FPS on the other hand.Currently I have no common solution available due to the way some panels are designed.The best would be to introduce an always visible section where the view directions (view_forward_dir etc.) are defined, and to move all panel graphics and gauges to other, subsequent sections (cannot use square brackets here, so I use ).This way, the outside view of could be oversized for those who have the display problems, whereas the panels would stay the same, eliminating the problem.As I said, some panels can be adapted this way (I'm currently at work and have no reference to a panel.cfg at the moment, but the last section in panel.cfg with the windows_size_x and y (amongst other) parameters determines size and position of don't know currently whether the windows numbering is important or the ident number is what counts here), and I'm currently trying to find out whether panels where gauges refer to a certain windows ident can be relocated so that is always newly introduced to be "before" the others come (difficult panels are DF727, RFP747, maybe the F1ATR and others, but let's see what I can do).Maybe one day I can post a success story here after some lengthy experimenting.The number of passengers is not a standard system in the sim, but something that airplane developers simulate in many different ways, either from external loaders, or with internal simulations, which might be progressive or not, there's no standard.


So, i stick with the latest Catalyst from ATI.As soon as I enable anti aliasing in the graphics driver control panel, the problem occurs.Here I need to say that the problem only occurs if I have no panel_as_texture=0 line in my fs9.cfg. So far, I used different drivers (old and new, even Omega and Detonator, and the RadLinker), but the problem doesn't go away using any other driver. That's a problem I have with many panels.I found the root cause of this is the anti aliasing setting of my graphics adapter (Radeon 9800 Pro).
