Reply 40 of 60, by BMSliger
Are you saying that as long as AA and/or AF are not enabled in the OpenGL tab of the Display Properties/Advanced window, then on your machine the CAT 3.1 drivers work with Glidos without crashing when you exit a mission? If so, I would be interested in knowing your machine and OS specs (I saw the specs in your sig but it doesn't specify your OS) since I cannot get the CAT 3.1 drivers to work for me even with no AA or AF and 16bit desktop. I am using WinXP Pro with SP1. When I complete a mission or hit the escape key with the CAT 3.1 drivers loaded, I always crash when my desktop is set to 16bit. and my screen always hard locks before displaying the menu that allows you to exit the mission when my desktop is set to 32bit. This hard lock can only be fixed by a reboot of my machine.
In reference to AA and AF in RB3D - as far as I know, 16bit OpenGL in the CAT 3.1 drivers do not work with these options enabled. At least for me in IL-2, when I enable AA and AF in 16bit OpenGL, I do not see the results. If I enable AA and AF in 16bit D3D mode, I do see the changes. I believe that 16bit AA and AF only work in D3D. Since Glidos only translates Glide calls to OpenGL calls and not D3D calls, how can AA and AF work in RB3D with the CAT 3.1 drivers and Glidos?
Thanks for your help.