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

This problem should be solved next week: This is post 72 on this page: http://www.orbxsystems.com/forum/topic/62085-dx10-and-ftx-global-fix-being-worked-on/page-4

Agreed with what everyone else has said above, the scenery can be enjoyed flying commercial aircraft and it runs quite well. I initially had some OOM issues but using DX10 and dropping the resolution on the ground textures and shadows while keeping it at 4096 on the buildings has allowed me to combine all of my addons with it successfully. I highly recommend using DX10 in this area as it freed up a lot of memory room for me and improved my overall perfomance. The whole area is really awesome and CYVR is a great cherry on top.

Indeed it is a combination of things that causes the OOM's. I tried things maxed out in DX10 with all the usual combinations though with REX clouds at 1024 and I'm right at the limit upon loading the airport 9.4 nm out using the GRIZZ aproach on the NGX from SFO. The pending update which saves 200 mb should get me over the hump. Interestingly enough, last night I had a rare SmartAssembly on the descent as I was going back and forth from full-screen to windowed mode to check VAS usage. I'm using FSUIPC so it reloaded the flight right at that point which was about 60 nm out. My reloaded flight was using almost 1 gb less in VAS than the initial flight and I was able to complete the descent with no problems. I think one of the biggest problems in FSX is that it doesn't completely clear out of range scenery/aircraft so this starts to add up and can lead to OOM's in dense areas such as CYVR.

This is a great point, just have a question to add on to this. Is there a reason that FSX cannot dump VAS along the flight route. For example as a stress test I maxed out everything shadows and set the mesh to 5m as advised. At CYVR in DX10 with HD I get 3.2 to 3.4 gb with the NGX and have no issues and this rate is fairly constant. This is with REX (1024 textures), UT2 100%, Vancouver V3, and PNW. However if I fly from KSFO with these settings, I climb from an initial number of 2.2-2.3 to 3.0-3.1 at TOD and then as the airport loads I go from 3.5 to 4 gb and get an OOM. Obviously if I dial back on something I can do it and departures are no trouble I'm just trying to understand if there's anyway to improve VAS in-flight independent of settings which obviously make a difference.

I'm seeing significant improvements running in DX10 with the full compliment of UT2, NGX, PNW, Vancouver+, and REX (1024 texture clouds) however I still OOM on approach from KSFO as the airport loads at runway 26R at around 9.5 nm out. Departures and GSX activity at the airport are much improved and frames are solid (20-25 fps) in heavy rain. A couple of ideas/questions that I'm going to look into this evening. One of which is in Process Explorer I noticed that FSX.exe's priority is set to normal. If I increase it to high (1 below real-time which is dangerous to run as it uses all resources on the sim) I noticed that my memory stopped going up and stabilized around 2.9-3.0 gb with all of these addons (even 100% road traffic, I realize I should dial it down but just ignore that for this purpose). I'll be measuring the entire way to see what happens on my NGX test flight from KSFO. The other idea is something I read at the FSDT forums. Umberto meantions that as you keep on loading up addons it increases your base VAS usage. Would it make any difference if I disabled airports and/or sceneries (Manhattan X for example) that I'm not using or does that not really matter much?

I've been getting these too, once I unclick "Force HD Textures" in the add-on manager I'm fine with everything else to the right. I'm running with PNW and Vancouver V3 with the NGX and this seems to be the only way to make this combo work unless I really dial back something else. It's still pretty solid without the HD textures but I'll continue tweaking to try and make it work.

I'm running DX9 with the NGX and ORBX and I'm in the mid 20's for FPS and did a quick test with REX weather on which had heavy clouds and did not notice any issues. It was quite smooth for me and that's with all of my sliders to the right. I will say that I run my LOD at 4.5 and I suspect that maybe what's required here. I'll have to see once I add Vancouver V3. I checked my memory usage and it was around 3.2 gb using Process Explorer.

This is an interesting topic. I had to recently due a complete reinstall of Windows 7 and FSX and upon doing so it appears as though my autogen radius is reduced versus my original configuration. However, I had a few pictures saved and recreated those images with my new setup and everything looked the same so perhaps it's just me.

I think what my larger issue happened to be was that I had done an uninstall and reinstall of UT2 and had not updated the timezone files. I don't think that FS Realtime had anything to do with this and moreover it's possible I bought the program without needing it although I respect what it does. This issue was happening during DST and after DST so I think it was just forgetting to update UT2 that caused my problems.

Turns out that Joe L's solution of updating UT2's timezone file was the way to go. Thanks for everyone's help.