I'm sure this is well known already, but I did a quick search here and couldn't really find it actually documented anywhere - maybe in a tweaking guide or some post I missed I'm sure??Anyway, I was getting as low as 10FPS in major airport areas(Chicago, SF Bay area). I did a flight into KMDW tonight and it was barely flyable. I remembered the jetway setting from installing UT2 and decided to turn that off. Wow!!! That more than doubled my FPS at KMDW. Upon departure, I don't think I went below 22FPS and it was mostly around 32 FPS. I have FPS set to unlimited in FSX and am not using any external frame rate limiter. Things now are for the most part very, very smooth with the exception of an occasional stutter here and there.Again, I bet this is well known but figure it's worth mentioning again to maybe help someone else find that last little tweak.Thanks.

I'm sure this is well known already, but I did a quick search here and couldn't really find it actually documented anywhere - maybe in a tweaking guide or some post I missed I'm sure??Anyway, I was getting as low as 10FPS in major airport areas(Chicago, SF Bay area). I did a flight into KMDW tonight and it was barely flyable. I remembered the jetway setting from installing UT2 and decided to turn that off. Wow!!! That more than doubled my FPS at KMDW. Upon departure, I don't think I went below 22FPS and it was mostly around 32 FPS. I have FPS set to unlimited in FSX and am not using any external frame rate limiter. Things now are for the most part very, very smooth with the exception of an occasional stutter here and there.Again, I bet this is well known but figure it's worth mentioning again to maybe help someone else find that last little tweak.Thanks.

Yeah, this was one of the main reasons FSX got the reputation of a poor performer. What happens is when jetways are active on AI aircraft (Which Aces in their wisdom set to the default condition), every jetway for AI aircraft within 120 miles radius of you will activate, initially severely cutting FSX performance, until they were all engaged, then it will return to normal. This took about 3 to 4 minutes, of course many people didn't wait that long before giving up. What made the situation worse was as you flew by other busy areas, those jetways would engage, periodically reducing performance. At least UT2 has the ability to suppress spawning ground aircraft, when you are above a specified altitude. Just think about sitting at KJFK where you have 4 of the busiest airports in the country within that radius, KJFK, KKGA, KEWR, and KPHL along with regional airports jetways all engaging at once. With the systems at the time of the Launch of FSX, it brought those systems to a slide show. Thankfully most of the addon traffic programs made engaging jetways an option and in the case of WOAI it wasn't a issue, since it used FS2004 models, which weren't set up that was to begin with.

This tidbit of info is always appreciated, as there will always be people new to FSX who could use the advice. One thing I don't like in UT2's Jetway setting in the UT2 GUI does not save into a persistent state. What I mean by this is, when you first click on setting to say you don't want jetways enabled and think the setting is saved, when you later reopen the app it makes it appear that the change was not saved. The change has been processed and saved in FSX correctly the first time (or at least I hope it did), but everytime I open UT2 and go to traffic options the setting reverts to jetways enabled with the checkbox checked.Anyways, aside from that little bug, I'm glad UT2 has that and many other FPS saving features to adjust AI density in accordance with the capabilities of our hardware.

One thing I don't like in UT2's Jetway setting in the UT2 GUI does not save into a persistent state. What I mean by this is, when you first click on setting to say you don't want jetways enable and think the setting is saved, when you later reopen the app it makes it appear that the change was not saved. The change has been processed and saved in FSX correctly the first time (or at least I hope it did), but everytime I open UT2 and go to traffic options the setting reverts to jetways enabled with the checkbox checked.Anyways, aside from that little bug, I'm glad UT2 has that and many other FPS saving features to adjust AI density in accordance with the capabilities of our hardware.

A.J., I think you're reading it wrong and its not a bug, unless your UT2 UI is different than mine.What you're saying is, if you want to disable the jetways you need to check the box? On my UT2 UI the setting says to check the box if you want to enable the jetways, not disable them, in which case since I leave my jetways disabled the nox is never checked. Although since I have never checked it, I cant verify if it stays checked or not when you reopen the UI, but if you want your jetways to be disabled then I wouldn't check that box if I were you.So basically if you are checking that box everytime before you fly you are turning on the jetways and not turning them off.Here's a pic of what my UI looks like. I'd be interested to know if your UI says the opposite of what mine says.

You are correct, it should be unchecked. However, I appear to have a bug on my system. I have 2.09, and the latest hotfix, but nonetheless, I seem to remember having this behavior since day one. Below is a screenshot of what I see the option default to, even if I unclick the box before reopening the app. If i unclick the box, and go to a different screen, say aircraft repaints, when I return to the options screen the box defaults to a check again. This is very annoying, and I have to wonder if it's having an impact on my frames in FSX. From what I have seen when spotting in FSX, I never see the gates connect to the AI, so that is a good thing. But I can't say for certain if they are infact disabled.I'll try asking around on the UT2 forums about this.

You are correct, it should be unchecked. However, I appear to have a bug on my system. I have 2.09, and the latest hotfix, but nonetheless, I seem to remember having this behavior since day one. Below is a screenshot of what I see the option default to, even if I unclick the box before reopening the app. If i unclick the box, and go to a different screen, say aircraft repaints, when I return to the options screen the box defaults to a check again. This is very annoying, and I have to wonder if it's having an impact on my frames in FSX. From what I have seen when spotting in FSX, I never see the gates connect to the AI, so that is a good thing. But I can't say for certain if they are infact disabled.I'll try asking around on the UT2 forums about this.

I'll have to try it and see if mine does the same.Although maybe they did it on purpose so that people are extra careful about checking the box since it can cause such a huge performance hit. I suppose in a way its good that yours keeps unchecking itself so you dont get hammered on FPS everytime to click it before you fly.It will be interesting to see what they say on the UT2 forum about it.

What I never understood was why Microsoft made the jetways move as soon as the aircraft were at the gate. Aircraft go through various states before they depart and after they arrive, one of which is pre flight. It's at this point that the jetways should move in my opinion, then they wouldn't all move at once, just prior to departure and for arrival aircraft just after taxi. That would have stopped the performance hit when flying into a new area and shouldn't have been too difficult to code.