highways1

One question I would have is does this happen with custom AI? I had UT2 and switched to adding all of the models and flightplans myself with AI Flightplanner 2. I've not had a chance to try it yet on the 777 but previous to this I would have occasional freezes on long flights in the 7-8 hour range.

I'll throw my hat in the ring on this, had my second freeze with the 777. Happened in a similar location to the first one, in southwest Germany on the way to MUC. I didn't even touch anything, sim just froze a couple hundred miles out. I did a flight from IAD to HNL with no issues so I know my system can handle the flying length. I have FTX global and FS Global Real Weather and was flying from FSDT KORD to Aerosoft EDDM. I have the NGX and have only had a freeze once or twice after numerous flights so I don't consider that out of the ordinary.

I did a test of this at UK2000 EGLL with Orbx England and I noted about 250 mb or so more usage with the 777 than the NGX. I then disabled all of my other scenery except for a departing airport in which I used Sunsky Jet's KPHL, and the UTX features along the route as well as Orbx ENG. I rebooted the sim for each test to make sure I had all of the ram released as this can skew the results. I found that I nearly recouped the memory difference between the planes. Before, I didn't really think much of enabling all of my scenery but it's really true that you should only use what you need for that flight. It makes a sizeable difference.

Got it all set now, thanks everyone for the help. What a great plane, going to have a lot of fun with this one.

Ok thanks I'll try that.

I'm really enjoying the new 777 and have the NGX and just have a question. I was doing a flight from LAX to SFO and after takeoff the first waypoint is a vector and then you make a turn to the next waypoint which is 32 nm away. In the NGX when I get within 3 nm of the next waypoint after a vector and I can switch back to LNAV and continue as before but in the 777 it never switches to the next waypoint even when I get to 0 nm away it just stays on the vector. I looked in the tutorial but it doesn't cover this so I thought I'd post this here.

I think he's getting this and PFPX confused.

I have CYVR, Vancouver+ V3, PNW, REX, FSGRW weather, UT2 at 100% commercial AI, and am usually in the NGX. All of my sliders are too the right and I get around 15-20 FPS, with occasional dips and gains so I've been anywhere from about 13-22. I run with v1.1 and use a combo of 4096 for the buildings, 2048 for the ground, and 1024 for the shadows. I should note that I use DX10 and have no OOM issues. This setup doesn't work in DX9 so if you're using that I would back off as needed. Hopefully Steve Parson's upcoming DX10 payware app set to be released in a few weeks will spur more movement to DX10 as you can run a lot more with it.

I played around with this a little more and it is indeed the AI traffic that causes issues but I'm able to run it now, just have to endure a ~2 minute freeze when it goes to dump the last airport I was at. A little annoying but a small price to pay to fly multiple legs with high settings.

Just as an update/finding it looks like what happens is that the first leg goes fine, I sit on the ground for 45 minutes or so and then take off and when the sim goes to dump the airport and it's AI traffic it crashes. I'll have to take a look at some CFG settings but as has been said I think it's just a little too much for FSX.

I don't fly for a VA so I can't say, just probably push the sim a little too hard. I notice with FTX Global now it struggles a little more in these spots, probably related to the increased autogen. I'll do another test tonight to see if I simply freeze for 15-30 seconds which I can live with or if I crash again. I had to restart the program and I've seen errors in the past like this if it isn't the first time I've opened FSX in a session.

Thanks, that's kind of what I had thought. I wasn't in a dense area at the time but unfortunately FSX is so old that it can go at any time.

I don't use photoscenery and my REX clouds are 1024 DXT5. I'll have to test more as it might have been a fluke but even before this I've always wondered why I'd get freezes on the second leg of the session. Otherwise, everything's running well and I don't get OOM's in DX10.

I hate bringing this topic up again but I've experienced it in the past and now since getting FTX Global I'm actually getting an OOM message versus just a 1-2 minute freeze. The interesting thing was that I didn't change the view and I wasn't touching anything plus the plane was at around FL200. I admittedly run my settings hard but I'm using DX10 so for the most part I'm ok. Just wondering if there is any more to this or if it's simply an FSX limitation.

It may still be a little while longer but problem solved. Post 129: http://www.orbxsystems.com/forum/topic/62085-dx10-and-ftx-global-fix-being-worked-on/page-7#entry570658