Hi everyone.
I hope that someone in the community can confirm and/or point me to a fix for the following issue. I just installed a new ATI Video card in my PC, and when I run Orbiter with FSAA turned on the HUD graphics dissapear leaving only the MFDs and the autopilot buttons drawn at the bottom of the screen. This phenomenon only occurs when in normal cockpit mode and not the 3d cockpit mode. Likewise, the simulation information block in the upper right hand corner of the screen also dissapears. When I switch to any of the external views, on the other hand, the simulation information block re-appears.
Does anyone have any ideas on what might be going on? My thought is that the FSAA algorithm utilized by ATI might be interpreting the HUD graphics data incorrectly as the edge of an object to perform anti-aliasing on and the lines are being averaged out (for lack of a better term) before being finally drawn on the screen. ATI Catalyst Control Center allows for several different FSAA modes such as box, small tent, large tent, and edge detect. I have experimented with each of these settings along with the overall number of AA passes (i.e. 2x,4x,6x etc.) but all of them show the same behavior with respect to the HUD graphics in Orbiter.
Is there some configuration setting in Orbiter that would work-around this graphical issue?
My previous video card had an Nvidia GPU on it and it did not show this same quirk when running with any of the user defined FSAA modes.
I would appreciate any feedback that anyone has on my problem.
Thanks for your time.
I hope that someone in the community can confirm and/or point me to a fix for the following issue. I just installed a new ATI Video card in my PC, and when I run Orbiter with FSAA turned on the HUD graphics dissapear leaving only the MFDs and the autopilot buttons drawn at the bottom of the screen. This phenomenon only occurs when in normal cockpit mode and not the 3d cockpit mode. Likewise, the simulation information block in the upper right hand corner of the screen also dissapears. When I switch to any of the external views, on the other hand, the simulation information block re-appears.
Does anyone have any ideas on what might be going on? My thought is that the FSAA algorithm utilized by ATI might be interpreting the HUD graphics data incorrectly as the edge of an object to perform anti-aliasing on and the lines are being averaged out (for lack of a better term) before being finally drawn on the screen. ATI Catalyst Control Center allows for several different FSAA modes such as box, small tent, large tent, and edge detect. I have experimented with each of these settings along with the overall number of AA passes (i.e. 2x,4x,6x etc.) but all of them show the same behavior with respect to the HUD graphics in Orbiter.
Is there some configuration setting in Orbiter that would work-around this graphical issue?
My previous video card had an Nvidia GPU on it and it did not show this same quirk when running with any of the user defined FSAA modes.
I would appreciate any feedback that anyone has on my problem.
Thanks for your time.