General Category > General Discussion
long pauses on departure
rbifly:
Just built a new i7 2600K based system running @ 4.5GHz. Still see the pauses on departures in the NGX. PMDG blames fsdt. fsdt blames pmdg. It would be real nice if you could work out these problems since the scenery is so nice and considering the GSX support of the NGX. :-\
virtuali:
--- Quote from: rbifly on March 20, 2012, 06:35:35 pm ---PMDG blames fsdt. fsdt blames pmdg.
--- End quote ---
I'm sorry, but we don't "blame" anyone but, based on your report:
--- Quote ---Only seems to occur with the PMDG NGX and not the MD11?
--- End quote ---
How can be explained any differently than a difference between the two airplanes, which obviously doesn't have anything to do with the scenery ? Have you reported this to PMDG ? How they explain it ?
virtuali:
In any case, I've just tried what you described as the worse situation (30 sec. pauses after departure from KLAS 7L) using the 737 NGX 800, and I couldn't see any pauses of any kind.
rbifly:
PMDG says that it is something to do with your software and security settings I think and to use at my own risk. I only get the pauses if I sit at an fsdt airport I have arrived at for a while before departing again.. The fact that it occurs on a completely new machine is interesting. running GEX,UTX,REX, UT2 PMDG 737 NGX700
virtuali:
--- Quote from: rbifly on March 20, 2012, 06:59:39 pm ---PMDG says that it is something to do with your software and security settings I think and to use at my own risk
--- End quote ---
They are wrong, and it's clear they used this explanation without knowing anything about how our software works.
In fact, since almost all objects are called by a module that is *external* to FSX (the Couatl.exe), it would be even less likely it would cause such problems to FSX, like memory consumption for example, since the memory is taken from a different set than the maximum of 4GB FSX can allocate (while, for example, their own gauges and *their* security module, being in-process .DLL, will take away from the same memory available to FSX). The Addon Manager, which runs in-process, does almost nothing right now, it's basically left just as an interface to activate the scenery.
And besides, how they explain it doesn't happen with the MD11 ? If it was our "security module", causing a conflict with their own, for example, it should happen with the MD11 too, on an FSDT scenery.
--- Quote ---The fact that it occurs on a completely new machine is interesting
--- End quote ---
What I found more interesting, instead, apart for the fact it doesn't happen with the MD11, is that nobody else posted in this thread.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version