General Category > General Discussion
Strange Pauses at Dreamteam Airports?
virtuali:
--- Quote from: rhodges on January 08, 2011, 12:54:04 am ---Am I overlooking a Dreamteam specific uninstall function somewhere?
--- End quote ---
All our products come with a proper Windows installer. This means, like any Windows program that has a proper installer, the one and only way to do an Uninstall is through the Windows Control Panel, in the Add/Remove programs section, which is the place were all Windows program with an Installer put their Uninstall procedures.
--- Quote ---Also, do you have any idea why the later setup, and the manger not seeing SP2?
--- End quote ---
The one and only reasons why BOTH our installer and the Addon Manager report you don't have the SP2 installed is, very simply, because you don't have the SP2 (or Acceleration Pack) installed. There's just no other way.
Maybe your real problem is you have a faulty SP2 installation, with some mixed up files coming from RTM.
Both the installers and the Addon Manager check the file version of the FSX.EXE file. You can check this yourself, by right-clicking on it, and select "Properties"->"Details". The FSX.EXE from SP2 should be 10.0.61472, the Acceleration is 10.0.61637. If your FSX.EXE version is not any of these two, it means SP2 is not installed, or your FSX install is corrupted somehow
rhodges:
Success!
1. Checked my fsx.cfg version: 10.0.614720
2. For good measure, downloaded a new fsx_sp2_ENUSP2 from the Microsoft download center.
3. Installed the new SP2. The fsx.cfg version is again 10.0.614720.
4. Uninstalled all Dreamteam files with the control panel add/remove provisions. Some were not removed from either the FSX library and/or fsdreamteam folder. Deleted these.
5. Downloaded the latest stand alone setup_addonmanagerx.exe file along with the latest LSZH, LSGG, KFLL, KJFK, KLAS, and KORD DT airports. While I was at it, went ahead and downloaded Lihue-hilo, Dallas Fort Worth, and Honolulu Intl. for a future purchase as soon as I am sure everything is stable now. Discovered that all except KLAS were newer versions than those I had installed. I guess I need to make a version check on my FS9 DT airports as well, but everything still looks good there.
6. Installed the newly downloaded DT files. As I did, the installation created new dll.xml and EXE.xml files. The original dll.xml file was the one that I discovered and mentioned earlier that seemed to be causing the pauses in aircraft movement.
All six airports are now returned to their full fantastic glory again, and there is no sign of the aircraft movement pauses which created this scenario.
Uberto, I know I peeved you a bit with my ignorance, but thank you so much for hanging in there with me and your kind help.
Respectfully:
RTH
virtuali:
--- Quote from: rhodges on January 08, 2011, 05:25:39 pm ---As I did, the installation created new dll.xml and EXE.xml files. The original dll.xml file was the one that I discovered and mentioned earlier that seemed to be causing the pauses in aircraft movement.
--- End quote ---
It wasn't the XML files by themselves, but another addon you had installed which required a module either in the DLL.XML or in the EXE.XML, which created the problem.
--- Quote ---All six airports are now returned to their full fantastic glory again, and there is no sign of the aircraft movement pauses which created this scenario.
--- End quote ---
I was quite sure of that. Now, it would be probably interesting to know why someone in another forum had to say "this is a common problem with FSDT sceneries", which clearly wasn't...
rhodges:
Well, I may have spoken too soon.
School may or may not still be out on this problem.
I just made the following discoveries when I tried to select third party aircraft. I don't know whether this would have been all or not, but I tried several (i.e. Capt.Sim 757, LDS 767, Aeroworx King Air, PMDG 1900, and a generic third party bird or two. Some came up with partial panels, others shutdown FSX.
1. First indication during startup was that I got an error message stating that FSUIPC nor Wideclient were not being linked to work.
2. When I selected the LDS 767, it stated that it needed to be reinstalled.
3. Looked in the ADDON provisions at top of the FSX display. All that were listed were Couati-Powered Products and Addon Manager. Quickgoto, FSUIPC, PMDG, and Leveld Simulations which also should have been listed had been removed.
4. Reinstalled the latest version of FSUIPC. (4.60a best I remember).
5. Some birds that previously shutdown FSX now worked (i.e. PMDG 1900). Others still shutdown FSX (i.e. Aeroworx King Air) and I no longer got the FSUIPC or Wideclient errors.
6. Being that new DT installations had replaced my DLL.XML file, to see what would happen I put the DLL.XML file that I had when all of this started back in my FSX folder. All aircraft in question are back working and the addon listings were replaced. I fully expected the pauses which motivated this thread to start with to be back, but to my surprise aircraft movement at DT KJFK was smooth, textures were still normal and SO FAR I see no other problems with anything else.
Uberto, relative to "another addon....created the problem" You may be 100% correct, but it seems to me that somebody is being outnumbered here. My DT update, in particular the DLL.XML file caused untold problems with countless other third party items. Obviously there is a conflict here but I have no idea who the culprit is.
Neither do I have any idea whether this "is a common problem" or not, however, ironically there is a more recent post totally unrelated to mine in the FSX forum at AvSim with the topic: "Freezing every 4 seconds at cloud 9 Bergen". Am I mistaken, or isn't cloud 9 at least a distant cousin to Dreamteam?
Hopefully all problems are solved now but time will tell.
On the plus side to everything, (I hope), the first thing I did this morning was to purchase the three airports I did not have, KDFW, PHLI, and PHNL.
Respectfully:
RTH
virtuali:
--- Quote ---I just made the following discoveries when I tried to select third party aircraft. I don't know whether this would have been all or not, but I tried several (i.e. Capt.Sim 757, LDS 767, Aeroworx King Air, PMDG 1900, and a generic third party bird or two. Some came up with partial panels, others shutdown FSX.
--- End quote ---
That's to be expected. Since you started with a fresh DLL.XML, all other 3rd party modules that were installed there were disabled so, any product requiring any of those modules wouldn't work anymore.
--- Quote from: rhodges on January 10, 2011, 12:58:11 pm ---6. Being that new DT installations had replaced my DLL.XML file
--- End quote ---
No, they don't replace anything, they only ADD the Addon Manager section, if is not there.
There's ONLY one case in which your DLL.XML is replaced: when, due to having edited it by hand or because *another* installer from another product has corrupted it, our installer will check this and will ASK you if you want to replace your corrupted DLL/EXE.XML with a fresh one.
This check is made BEFORE touching the XML files, and is made by asking to the standard MS XML validation library if the XML file is correct. If it's not, you'll see a diagnostic message during the installation telling which line contains the error and you are given the option to start with a fresh file, but our installer will never, ever, replace the XML file on its own, nor will ever corrupt them, because it's also using the standard MS XML parser to process them so, it's not possible the XML files would become corrupted by our installers, which simply reacts to corruption that was created elsewhere (either by another product, or by hand-edited the files, perhaps with the wrong text editor)
--- Quote ---to see what would happen I put the DLL.XML file that I had when all of this started back in my FSX folder. All aircraft in question are back working and the addon listings were replaced. I fully expected the pauses which motivated this thread to start with to be back, but to my surprise aircraft movement at DT KJFK was smooth, textures were still normal and SO FAR I see no other problems with anything else.
--- End quote ---
This just proves the pauses weren't caused by our sceneries, since you now don't have any pauses...you said you *updated* FSUIPC with the most current version: this is just an example of something that might have fixed your issue, since the XML file is the same, but it's now activating an updated module. Same might have happened with other modules you had, which you might have upgraded while reinstalling them. Our installers always get the module directly from the internet so, you always get the latest version.
--- Quote ---My DT update, in particular the DLL.XML file caused untold problems with countless other third party items
--- End quote ---
Sorry, no. I confirm that our installers will never replace an XML file, except in case when the XML files was *already* corrupted before running our installer. This is the one and only time the XML files are created from scratch, and there's also a clear warning about this during the installation.
--- Quote ---however, ironically there is a more recent post totally unrelated to mine in the FSX forum at AvSim with the topic: "Freezing every 4 seconds at cloud 9 Bergen". Am I mistaken, or isn't cloud 9 at least a distant cousin to Dreamteam?
--- End quote ---
That's not obviously a fair example, since that post just appeared now, and was started by the same user (anakletor) that started the *same* thread here, and the fact you have also started the same thread on avsim, doesn't make it a "known" FSDT/C9 problem, just because there are only 2 users who posted about it in the last two days with one (you), saying the pauses are now gone, and there was also an user there who replied he never had the problem to begin with:
http://forum.avsim.net/topic/323214-strange-pause-at-kjfk/page__view__findpost__p__1905867
user ubersu said:
--- Quote ---"Interesting problem... I have all FSDT airports for both FSX and FS9 and have never seen this happen - it's the first I've ever heard of it."
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version