flashotime

I have been in contact with the developers regarding the "red artifact" issue. Have sent numerous screenshots showing the memory usage and gpu temperatures. Last weekend I re-installed widows to see if there was an issue with the OS. (getting desparate for a solution). Installed flight and ran without issue. Then I activated my live profile. CTD at the yacht. Deleted the live profile and the flight folders in appdata, and ran great again. Created a new login, and CTD at the yacht. Seems like if you delete your profile(s) and the delete the flight folders in the appdata (both the roaming and local), everything runs like it should. Noticed because of the screenshots I was doing for the developers that without the live profile, I run about 200k less in the working memory, and it does not grow. With the live profile activated, the memory seems to keep increasing in size until it crashes. Wondering if anyone else has similar experience. Do the crashes start after you login to live. Sent this to the developers, but have not heard back from them.

Thanks for the response on this issue. I have had 12 crashes that generated a report since 3/3. This does not include the times that the program just stops and exits to the desktop without generating a report. Most of the crashes are flying to the yacht (after the last re-install when I had to start over). After passing the yacht at low level, the games starts to stutter with red squares on the terrain. I can then land and when the scene goes to the movie of the plane on the water, it crashes. Sometimes the crash generates a report, but it usually does not. On the rare occasion when I can get past the yacht, it will crash in free flight. This can be with the A5 or the stearman. Doesn't matter what plane. The signs are the same. Game stutters, red squares on the terrain, and then crash. I have tried upgrading to the Catalyst ver 12 driver, and also downgrading to the ver 10 driver. Makes no difference. Ran the GPU-Z utility to see if there were any thermal spikes on my video cards, and did not exceed 70 degrees which is not much different than when I run FSX and well within spec for my cards. I added a couple of cooling fans to my case to be sure of proper cooling. Did not make any difference. Thought the thermal issue might be valid due to the shutdown after about 10 minutes into whatever activity I try. After seeing the numbers reported and taking measures to reduce the thermal load, I am not convinced that this is the issue. I will send future reports to the email you listed. This looks like an interesting game, and I would like to explore it further, and I am sure that others with the same issue feel the same.

I will add this. Have not seen any way to fix the issue. Have tried all of the recommendations in this topic, and still have the issue. Here is a typical crash report.DescriptionFaulting Application Path: C:Program Files (x86)Microsoft GamesMicrosoft FlightFlight.exeProblem signatureProblem Event Name: APPCRASHApplication Name: Flight.exeApplication Version: 1.0.0.30016Application Timestamp: 4f28a36aFault Module Name: Flight.exeFault Module Version: 1.0.0.30016Fault Module Timestamp: 4f28a36aException Code: c0000005Exception Offset: 006ef22aOS Version: 6.1.7601.2.1.0.768.3Locale ID: 1033Additional Information 1: 9e27Additional Information 2: 9e2778096e7e1e2a2e0302fe58f3eea8Additional Information 3: 9e27Additional Information 4: 9e2778096e7e1e2a2e0302fe58f3eea8Extra information about the problemBucket ID: 2860109842I5, 8MB, ATI 6770 Crossfire video.Thought I would add this because not seeing any other input. Want people to know that some of us are still having issues.