Johnbc

Thanks for the reply. Website now working again.

Since yesterday I'm unable to access the website (Pilot2atc) either via Google Chrome or Microsoft Edge. It says the site is unsafe and comes up with the following error - NET::ERR_CERT_COMMON_NAME_INVALID Not sure if this is just my computer or more widespread.

Just an observation on the website - I found the text on the tutorials page very difficult to read. To a lesser extent some of the text on the Purchase page is also difficult to read.

Just tried to download an older AMD driver (actually tried 12.4, 12.8 and 12.10). Firstly the Catalyst Control wouldn't work - however with Radeon Pro working, I just continued. However then I found that FSX wouldn't load - fatal error message - an unhandled win 32 exception occurred in FSX.exe (3844). There do appear to be too many problems to overcome for those with AMD Graphics Cards - it's looking like a return to DX9 for me.

Wulf, thanks for that advice I'll see if it helps and report back. With me, the screen freezes and I'm unable to access the minimize or the delete x but thanks for the comment.

After flying with DX10 and then exiting to FSX Menu Screen - I find the screen has been corrupted ie the top left corner has an overlay in the top left corner and most of the bottom third of the menu screen is missing (except the fly now button). If I click on any of the buttons there is no response. If I try to exit via the red cross in the top right, there is no response. I have to go to Task Manager to exit FSX. This problem only occurs when using DX10. I've got an AMD Graphics card - Radeon 9 series 280x, 3gb. Has anyone got any idea how to solve this problem?

After flying with DX10 and then exiting to FSX Menu Screen - I find the screen has been corrupted ie the top left corner has an overlay in the top left corner and most of the bottom third of the menu screen is missing (except the fly now button). If I click on any of the buttons there is no response. If I try to exit via the red cross in the top right, there is no response. I have to go to Task Manager to exit FSX. This problem only occurs when using DX10. I've got an AMD Graphics card - Radeon 9 series 280x, 3gb. Has anyone got any idea how to solve this problem?

When I exit the flight and it returns to the FSX Menu Screen, the screen has been corrupted ie the top left hand corner has an overlay from somewhere with buttons saying yes or no. Also the bottom third of the menu screen is absent except for the fly now button. I have tried clicking on this and settings etc but there is no response. The only solution is to delete it via Task Manager. The AMD graphics card is - Radeon 9 series 280x with 3gb. I have installed the latest driver 14.501. I tried to find and install 12.4 but without success. I've reported this issue to AMD (if they can get it right with version 12 why can't they replicate this in the latest version). Anyway thanks for all your help Steve. I will try posting it in the discussion forum.

I enabled the missing texture fix. I just have the one monitor. Escape doesn't work. The FSX Menu Screen is corrupted and after a while I get the message - Microsoft Flight Simulator has stopped working. A problem caused the program to stop working correctly ......... When I revert back to DX9 there is no problem, it works fine.

Thank you for the useful information - I didn't realise that AMD Graphics Cards are such a problem with DX10. However I have altered AA to 8x and I now have the water setting to High x1. I tried it flying for well over an hour without any problems. When I exit the flight I can't access the FSX Menu, I need to use Task Manager to close FSX.

I read good reviews about dx10 ie slightly improved graphics, possibly better fps and more stable than dx9. I bought DX10 Scenery Fixer and carefully followed the instructions for setting up with AMD Catalyst Control. However I find that I'm unable to fly more than 20 minutes without the scenery breaking up ie large triangles, flashing large areas of the screen etc (previously I've noticed this prior to an 'out of memory' error). I have reverted back to DX9 and flown the same route but with no problems at all. I have experienced very few memory problems with DX9. I assume that I must be doing something wrong as I can't find any other similar complaints. Can anyone point me in the right direction to eradicate this problem? All the best, Johnbc