General Category > General Discussion
long pauses on departure
rbifly:
Unfortunately this problem seems to still be present. I recently reinstalled FSX and all my add ons and I still have the issue. I will still get the long pause on departure from KLAS or KDFW at abut 1000 feet still over the airport. I do think it is related to UT2 and wonder what I can do to solve this. The thing that is unique is that the problem will not present itself at first, but only after sitting at an airport for an extended period of time. I think the UT2 traffic activity builds to a level so that there is some conflict. Is there something you can suggest to troubleshoot this? Simconnect? graphics? page file?
virtuali:
If the problem happens only after a while, it's unlikely a conflict between the scenery and UT2, and the pause is caused by UT2 alone, since basically all the scenery objects are created immediately as soon as you enter the scenery area, which in case of KDFW is fairly large at 16 nm, once all objects are created, there's almost zero Simconnect activity on our part, even the active Docking systems and the special custom runway lights don't use Simconnect, except for querying the AI positions but, it's the same if the AI were default and, since you said that by removing UT2 the problem goes away, it means the scenery itself is not causing any problems with AI.
What happens if you simply lower the AI density in UT2 ?
rbifly:
I just did a flight from KLAX to KLAS... No problems on that leg. After arriving at the gate, I toggled UT2 off. Just before takeoff from KLAS, I toggled UT2 back on. Still had the 30 second pause. Yesterday I tried toggling UT2 off before takeoff and still got a pause at KDFW. Not sure what the mechanism is, but it requires a period of time before it presents itself. Will try at a reduced UT2 setting, but I think I will still have an issue.
Next repeated the above with the UT2 sliders reduced from 70% to 30%. No change... same 30 second pause departing LAS
Finally disabled UT2 again by way of the xml... flew LAX to LAS with no issues. Sat in LAS for about an hour then on departure had a 15 second pause at the same location... Now wondering if it is really UT2 at fault? Any ideas?
virtuali:
Before, you said this after removing UT2:
--- Quote ---Interesting though that the pause were only about a 1 second now
--- End quote ---
Now you are back to 15 seconds pause ?
If it happens only after some time, maybe it's simply the whole combination of your installed addons in FSX that have requested too much memory, and Windows has decided to reclaim it.
Memory might become fragmented after some time, you might try an utility like this:
http://www.pcwintech.com/cleanmem
Try to run a memory defrag just before takeoff, and see if it makes any difference.
rbifly:
No change... I stayed on the ground in KLAS longer and experienced a 30 second delay on departure.
I will add that when I'm experiencing this if I exit FSX it will take a long time before I am able to click the exit confirmation button. A clue?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version