Did my first flight in a month after buying fs2crew voice last night. When flying from ksfo to klga and about 200nm out after calling up the main panel the sky flashed multicolor and frames dropped from my usuall 25fps steady to steady at 5. I had to abort the flight. Alt entering did not make it come back. I popped up my EVGA and my GPU was maxed at 100 the whole time. It never gets above 60 under the most dire of circumstances. This never happened before fs2crew for this aircraft and it happened as soon as I popped up the main panel. Sucks to get 5 hours into a flight and then have to abort it before the best part.I don't even know where to start to figure this out but my system does not like fs2crew NGX. I know you guys probably never encountered this in beta either, such is allways my luck.There is also another issue in where if I have scrolling text on top of my screen from the fs2crew voice I get a massive stutter, so I have to leave this feature off. No big deal but maybe this is somehow related.Also, when I looked inside the VC so I could not see outside the frames jumped back up. So this flashing multicolored cloud flash and fps drop has to do with scenery outside and the video card. My system can handle it, this is a problem and I do not think it is a coincidence, FS2crew would be the first place to look but I do not know where or how or even if I can cause the problem again.Seriously bummedMarc

Could it be use pools=0?I recently changed this from RejectThreshold=131072 and did a few flights, this being one of them. The other flights were a while ago but I do remember one of them with abnormally low frames approaching KMDW (fsdreamteam). Also had some strange graphic anomolies when panning. I have a 1gb card but still maybe this might be the cause. I changed back to using a Reject Threshold and we will see how it goes next time.Any ideas?This is the only thing I could think that could all of a sudden throttle my GPU as some new scenery came into view or maybe the FS2Crew main panel.

Hi Marc,Who knows, frankly.The NGX is FS2Crew's most popular product with a very large user base and we're not hearing about stuff like this.However, if you're making odd edits to your FSX.CFG file, you're in Test Pilot territory.Please do this:1. Delete your FSX.CFG file.2. Load FSX to rebuild it.3. Run ******* B's utility to add all his fixes to the FSX.CFG (sorry, I don't have the link handy).I'm using his edits and my FSX is rock solid.Also, you could have bad scenery installed.Many FSX issues are the result of poorly coded 3rd party scenery.

3. Run ******* B's utility to add all his fixes to the FSX.CFG (sorry, I don't have the link handy).I'm using his edits and my FSX is rock solid.

The link is http://www.venetubo.com/fsx.html

Hi,I allready did that once.But thanks though.Anybody having problems with Imaginesim KLGA?One of the last times I flew into New York I got a g3d.dll crash, the first and only time. I installed the latest FSUIPC just to be sure afterwards. 2 times having problems flying into New York and it could be this airport, who knows.I took the use pools=0 out of the cfg file, this may also be a problem as this was video card related.

Anybody having problems with Imaginesim KLGA?

YES! I have the same issue with Imaginesim KLGA for my FSX and it has nothing to do with FS2CREW! I flew MYNN-KLGA without FS2CREW and on the approach to KLGA my FPS dropped to about 5 too. After 'autolanding' (seemed the only reasonable way to try to land) I restarted my FSX and got a different aircraft and the same probably was there. I think it is the scenery problem. As far as I remember, it was the worst after dusk.P.S. please let me know if you got yours sorted. Thanks

Imagine sim it looks like it is. I also have a bleed through problem with KSJC. I will probably uninstall KLGA and KSJC and just fly into KSFO and KJFK. Too bad because I really like the characteristics of KLGA in a 737. Imaginesim support is not to help full either.

YES! I have the same issue with Imaginesim KLGA for my FSX and it has nothing to do with FS2CREW! I flew MYNN-KLGA without FS2CREW and on the approach to KLGA my FPS dropped to about 5 too. After 'autolanding' (seemed the only reasonable way to try to land) I restarted my FSX and got a different aircraft and the same probably was there. I think it is the scenery problem. As far as I remember, it was the worst after dusk.

As I've mentioned time and time again, the majority of problems people experience in FSX are related to 3rd party scenery.To rule out FS2Crew, the test is to do a flight away from your 3rd party scenery... do a flight in Africa away from all the 3rd party AI, Scenery stuff that can cause headaches.Cheers,