FSDreamTeam forum
Products Support => JFK for FSX/P3D => Topic started by: Razgriz on September 24, 2008, 02:20:36 am
-
As soon as the trial starts I get a fatal error CTD. I just downloaded the new 2510 version of the Addon manager.
-
As soon as the trial starts I get a fatal error CTD. I just downloaded the new 2510 version of the Addon manager.
Checked again, it's all fine here.
As I've told you in a PM, you downloaded basically at the same moment when we were updating it, it might be that you just got a corrupted file, if you were exactly in the middle of a transfer. Try it again.
-
Yes that's after you PMed me and I downloaded a new file.
-
Yes that's after you PMed me and I downloaded a new file.
I can only confirm the current version that is online is fine. Nobody else reported the crash so far.
Try to uninstall it entirely, reply "Yes" to the question about removing the Addon Manager, then reinstall.
-
virtuali,
I have the same issues and others ...
If I download and install the *new* (at or after Sept. 24th) KJFK will it also include the missing textures/PAPI/ParkMe/YouControl fixes that were posted at the top of this forum as well?
Thanks.
-
If I download and install the *new* (at or after Sept. 24th) KJFK will it also include the missing textures/PAPI/ParkMe/YouControl fixes that were posted at the top of this forum as well?
Yes, the installer downloaded after Sept. 24th includes all fixes released on the forum already.
-
If I download and install the *new* (at or after Sept. 24th) KJFK will it also include the missing textures/PAPI/ParkMe/YouControl fixes that were posted at the top of this forum as well?
Yes, the installer downloaded after Sept. 24th includes all fixes released on the forum already.
I uninstalled the original version + addon-manager completely restarted and checked everything. Then re-downloaded and installed post Sept. 24th version; all appears fine but still get CTD's.
Any suggestions? ???
-
I uninstalled the original version + addon-manager completely restarted and checked everything. Then re-downloaded and installed post Sept. 24th version; all appears fine but still get CTD's.
When it happens, exactly ? As soon as FSX starts ? After a while ? At JFK only ?
-
I uninstalled the original version + addon-manager completely restarted and checked everything. Then re-downloaded and installed post Sept. 24th version; all appears fine but still get CTD's.
When it happens, exactly ? As soon as FSX starts ? After a while ? At JFK only ?
It seems to happen at the KJFK airport while in the flight arbiterarely; either while taxiing/TOF/LND etc.; but NOT on loading of flight or within the menu options. It also happens if I exit the Sim from the flight directly, but not from the startup flight menu, which will close the sim without incident. When I reverted the setup back to the condition pre-KJFK eveything behaved correctly with no issues. I also reduced AI sliders and AutoGen to make sure it wasn't a system resource issue. I have a feeling it is related to SimConnect and a possible conflict of your snake and my ITRA's ActivePanel-NAVSTACK drivers but I have no way of knowing for sure. And sometimes the ParkMe menu options just won't work for some reasons. Any other suggestions? ???
-
And sometimes the ParkMe menu options just won't work for some reasons. Any other suggestions? ???
To check if it's related to the Couatl module, you can disable it in your EXE.XML (located at %APPDATA%\Microsoft\FSX), just set the <Disabled> tag to True.
If you still have a crash, at least you would know it's not that module.
-
And sometimes the ParkMe menu options just won't work for some reasons. Any other suggestions? ???
To check if it's related to the Couatl module, you can disable it in your EXE.XML (located at %APPDATA%\Microsoft\FSX), just set the <Disabled> tag to True.
If you still have a crash, at least you would know it's not that module.
OK! I'll try that.
PS: Attached is an example of what happens.
1. Snake version (1.0.0.118).
2. Crash in the FS.
3. Snake remains in MEM even if shutdown is normally executed from FS startup menu.
[attachment deleted by admin]
-
Virtualli,
I tried removing the Snake and then the add-on manager to verify if it was either of those but the FS still CTD if I exited from the Flight directly; So, I thought it was something else within the game. I uninstalled KJFK entirely and the CTD went away. Then I re-installed it and the CTD came back even if the snake and AM are disabled in the dll.xml/exe.xml files. Strange Huh! :o
Moreover, in the game itself, What happened is a CTD would occur after I landed and used FS ATC to obtain a parking (Gate) spot, then taxied to it, and just as I was to make the turn to the spot a CTD would occur. When I removed the snake and Addon manager from usage as you suggested this would go away but not the CTD from the above paragraph.
I've attached a bundle of files in a .Zip from the CTD reporting debug feature; perhaps this can help ???
Any other suggestions? ???
[attachment deleted by admin]
-
I tried removing the Snake and then the add-on manager to verify if it was either of those but the FS still CTD if I exited from the Flight directly; So, I thought it was something else within the game. I uninstalled KJFK entirely and the CTD went away. Then I re-installed it and the CTD came back even if the snake and AM are disabled in the dll.xml/exe.xml files.
From your description, it seems that the CTD is not caused by the Addon Manager or Couatl. BUT, Couatl itself is not able to close down if FSX doesn't close cleanly. Which is something we might be able to fix, but it certainly wouldn't fix your issue entirely, except for not having to manually close it down from the Task Manager anymore (in case FSX crashes)
So, it might look like as if the *scenery* itself is causing the crash, rather than the two executable modules.
However, as we have seen in other cases as well, more than the scenery, it might be something that appears only when the scenery is installed, even if it's not part of the scenery per se. For example, by installing JFK, the very presence of its AFCAD file might attract a much bigger quantity (and different models too) of AI, comparing to the default. And, one of them might have a problem which causes the crash.
The only thing that's sure, following your report, is that neither the Addon Manager or the Couatl module are causing the crash, because you are having it even with both disabled.
-
I tried removing the Snake and then the add-on manager to verify if it was either of those but the FS still CTD if I exited from the Flight directly; So, I thought it was something else within the game. I uninstalled KJFK entirely and the CTD went away. Then I re-installed it and the CTD came back even if the snake and AM are disabled in the dll.xml/exe.xml files.
From your description, it seems that the CTD is not caused by the Addon Manager or Couatl. BUT, Couatl itself is not able to close down if FSX doesn't close cleanly. Which is something we might be able to fix, but it certainly wouldn't fix your issue entirely, except for not having to manually close it down from the Task Manager anymore (in case FSX crashes)
So, it might look like as if the *scenery* itself is causing the crash, rather than the two executable modules.
However, as we have seen in other cases as well, more than the scenery, it might be something that appears only when the scenery is installed, even if it's not part of the scenery per se. For example, by installing JFK, the very presence of its AFCAD file might attract a much bigger quantity (and different models too) of AI, comparing to the default. And, one of them might have a problem which causes the crash.
The only thing that's sure, following your report, is that neither the Addon Manager or the Couatl module are causing the crash, because you are having it even with both disabled.
I would say this is true for most (99%) of the CTD's. I'm using MTX v5.1b for Traffic and will set the AI sliders to "0" for all just to be sure. The funny thing is that some times everything works great ParkMe, YouControl, and scenery all together with everything nicely. But the CTD from the exit FS directly out of the Flight occurs 100% of the time when KJFK is installed. And CTD from FS ATC taxi to Gate is also 100% of the time - perhaps its an AFCAD issue but I must admit I'm confused with the difference in parking spot labeling in the scenery and the AFCAD and ParkMe. I'm sure that you'll put a listing in a manual soon so there is no more confusion; Please! :D
What else do you need? Any other suggestions? ???
-
Virtualli,
The CTD occurs regularly at FS ATC's/AFCAD gate H314 and the snake has it's issues too (see attached).
I also noticed that a CTD occurs after 15mins into the game ... Is this a Addon-Manager Trial timer Issue?
My product is bought and paid for... :'( I did have the trial versions of Cloud9's Bergan X, Xcity Rome, and Aerosoft's Florence X which I've just uninstalled to see if that resolves this. I do own the Cloud9's Orlando X scenery should I uninstall this as well?
Any thing else you need or suggest? ???
[attachment deleted by admin]
-
The CTD occurs regularly at FS ATC's/AFCAD gate H314 and the snake has it's issues too (see attached).
I'm sorry, but this simply doens't happen. Please be more specific. What does it mean "CTD occurs regularly at gate H314" ? It always crashes when you simply move there with the goto Airport menu ? It crashes when you are directed there by the ATC ? It crashes when you manually taxi there ? It crashes when you are standing there doing nothing, after a while ?
Because, I've just checked, moving to that gate result in no crash at all on my machine. Tried many times.
also noticed that a CTD occurs after 15mins into the game ... Is this a Addon-Manager Trial timer Issue?
Of course not, first because there's nothing that happens at 15 minutes, and not, because otherwise we would have plenty of reports of users in Trial, which are many thousands, that would complain they have a CTD after 15 minutes.
Please, don't keep assuming the crash is *caused* by the Addon Manager. YOU said yourself that you have the crash even with BOTH Addon Manager AND Couatl DISABLED. So, once and forever, assuming that what you said before is true (CTD even with both program disabled), the CTD clearly doesn't have anything to do with the Addon Manger or Coautl. The fact that you see a message stating Couatl has crashed, doens't mean anything: the same "thing" that is making your FSX crashing, is probably causing Couatl to be crashing as well.
We are probably able to fix the fact that Couatl remains loaded after FSX crashed. But that it's just a minor issue, it would only save you to have it manually terminated after a crash, which shouldn't happen in the first place. In this case, Couatl is not the *cause* of a crash, is the *victim*...Even fixing Couatl by making it able to quit even when FSX terminates abruptly,will not stop the crash from happening.
Any thing else you need or suggest? ???
I've already listed suggestions. Since, as you said yourself, disabling both the Addon Manager and Couatl doesn't fix the crashes, this clearly exclude these two.
As I've said already, the fact that uninstalling JFK solves the issue, might be also related to something that *comes* at JFK, like an AI. I'm assuming you ARE using the current JFK installer (24th Sept.) because that one includes a fix for two missing textures we posted in the forum that, if missing *might* cause a crash.
I'm sorry, but the only way to be sure a problem exists in a software, is being able to reproduce it.
-
The CTD occurs regularly at FS ATC's/AFCAD gate H314 and the snake has it's issues too (see attached).
The crash message for Couatl reads "Couatl engine launcher has stopped working". This means that you don't have the latest Couatl.exe available, because from version 1.0.0.116 it would display "Couatl™ Scripting Engine for FSX has stopped working". Could you please check the version number of Couatl.exe?
Thanks in advance,
Ganesh
-
The CTD occurs regularly at FS ATC's/AFCAD gate H314 and the snake has it's issues too (see attached).
The crash message for Couatl reads "Couatl engine launcher has stopped working". This means that you don't have the latest Couatl.exe available, because from version 1.0.0.116 it would display "Couatl™ Scripting Engine for FSX has stopped working". Could you please check the version number of Couatl.exe?
Thanks in advance,
Ganesh
Mr. Ganesh,
Yes, it is v1.0.0.118.
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2471;image)
-
Yes, it is v1.0.0.118.
Since you posted two different screenshots at two different times, the fact that you see build 118 on the screenshot were you had the Simconnect diagnostic mode turned on, doesn't necessarily mean you had 118 on the screenshot were you reported it crashing.
However, we have a new build online that should be able to quit even when FSX is exiting abrubtly. If you run JFK installer again, it will get the new one.
However, it's unlikely this will fix your crash problem, since (as you said in your message) you had the crash even with both the Addon Manger and the Couatl module disabled from startup.
-
First, On the ground at KJFK after Landing, I call up ATC for a "Taxi to Gate", get instructions and begin a progressive taxi, and while taxiing to the gate assigned (eg. H314 or Hotel 314) the CTD occurs (on taxiway KK in this instance).
This explanation is still not very helpful:
Do you mean that, each time you get cleared to THAT specific gate, you get a crash while taxiign or the H314 gate was just an example, and you might get it on any gate ?
Second, when I'm at the gate (eg. 31), get ATC clearance to depart and Taxi, begin my taxi and while taxiing for take off (different Taxiiways depending on the wind direction/runway assignment); I get a CTD. It take me roughly 15 min to do this and thus I noticed the pattern
No, there's maybe a pattern, but perhaps is entirely different from what you are thinking. It looks to be related to ATC in some way. Can you confirm it happens only if you get clearance. OR, it just happens (I already asked you this in the previous message), if you just stay there doing nothing, after 15 minutes ?
[3. Lastly, I did install the fixes to the original and then uninstalled everything, restarted the PC, and downloaded the post Sept. 24th setup as you had instructed before; do I need to re-apply the other fixes?
No, as stated many times already, the current installer includes all fixes posted in the forum for the scenery and, since it automatically gets crucial files (dll and exe) from the net when starting, these are always guaranteed to be the last version.
-
Virtualli,
OK; I've just downloaded the newest version and uninstalled the OLD and made sure that there are NO file(s)/folder(s) remaining in the FS directary. I'll restart and install the lastest version and get back to you with a complete test and clearer answers.
-
Virtualli/FSDT Staff,
The new version(s) work much better; Bravo! :D It resolved the CTD for the 15min.'s/Cloud9/Aerosoft Addon-Manager trialware products CTD issues and the snake is behaving correctly. But there are still a couple of minor issues I'm having and I want to be sure that its NOT KJFK; so I'll post later - Now you guy go and get some coffee on me; you've earned it. ;)
-
Virtualli,
Wish I had good new; unfortunately not :'( :(
Try this proceedure with 3 different aircraft (FS Default Cessna 172/ Epic Dynasty LT v1.5/ AlphaSim F-5) to be sure it was NOT aircraft mdl/gauge related. Also, disable all modules (including FSUIPC / InCabin Browser, AI SDK, AI Carriers, except ADDON MANAGER and Snake) to be sure no conflicts with the game.
Weather: Realtime; Time: (Dusk) 18:45EST; Date: Sat OCT 4th'08.
1. Obtained ATIS, and IFR release and Taxi instructions, from FS ATC, from spot (PARKING 7 -- RAMP CARGO) via taxiways SB, S, B, E, C, ZA to Runway 22R.
2. At runway got Hold Short instructions, then Position and Hold.
3. When in position, ATC cleared for TOF and I acknowledged.
4. Began TOF roll and CTD. (approx. 15-17 min.'s passed from time of step 1 and CTD).
This process is consistant. I disabled all AI at KJFK and removed MTX5.1b KJFK AFCAD so there wouldn't be any conflicts. There is something in the scenery that is causing this ... :-\
Any suggestions? ???
[attachment deleted by admin]
-
This process is consistant. I disabled all AI at KJFK and removed MTX5.1b KJFK AFCAD so there wouldn't be any conflicts. There is something in the scenery that is causing this ...
I think to have asked you TWICE already, yet you haven't done this test:
Do you still have a crash if you are simply standing on a parking place, DOING NOTHING ? Don't call the ATC, don't do ANY-THING. Just wait for 15, 17 or whatever time you want.
Can't you undertand that, if I've asked you (twice) to do this test, it's because it WAS important, to understand if it's linked to the ATC or not, so it might be, for example, an AFCAD problem ?
-
This process is consistant. I disabled all AI at KJFK and removed MTX5.1b KJFK AFCAD so there wouldn't be any conflicts. There is something in the scenery that is causing this ...
I think to have asked you TWICE already, yet you haven't done this test:
Do you still have a crash if you are simply standing on a parking place, DOING NOTHING ? Don't call the ATC, don't do ANY-THING. Just wait for 15, 17 or whatever time you want.
Can't you undertand that, if I've asked you (twice) to do this test, it's because it WAS important, to understand if it's linked to the ATC or not, so it might be, for example, an AFCAD problem ?
Sorry for not answering that question directly or more quickly; Yes! Once or twice when I was simply parked at the spot, and another time while I was on a taxiway, and yet another time when flying (I paused the game to answer and talk on the phone) and YES it CTD'ed. I'll try more tests to be more sure.
This CTD and the "Exit FS directly out of flight CTD" are the only ones left, to my knowledge. And they do go away when KJFK is Uninstalled. :-\ don't ask me why!
-
And they do go away when KJFK is Uninstalled.
Can you please confirm that, as you said previously, that if you just DISABLE both the Addon Manager and Couatl from their XML files, the crash still happens ? This is also very important to know: I need to be absolutely sure that the 2 modules aren't the problems, and it's something in the scenery.
Keep in mind that I'm still unable to reproduce it...you are the only one reporting a crash with this specific pattern.
-
And they do go away when KJFK is Uninstalled.
Can you please confirm that, as you said previously, that if you just DISABLE both the Addon Manager and Couatl from their XML files, the crash still happens ? This is also very important to know: I need to be absolutely sure that the 2 modules aren't the problems, and it's something in the scenery.
Keep in mind that I'm still unable to reproduce it...you are the only one reporting a crash with this specific pattern.
Yes, the Crash still happens if I DISABLE both the Addon Manager and Couatl from their XML files. Also, it happens only when ATC is used at KJFK at/around 15 min.'s or so into the game/flight (wheather parked at one spot or taxiing on a taxiway/runway it doesn't seem to matter). I also doesn't matter if AI or other modules are enabled or disabled; Even if FSUIPC or other modules like InCabin Browser etc. are enabled or not, it crashes in either case. I checked the Disk using ScanDisk for corruptions and NOTHING wrong there. The CTD does occur at other airports as well but ONLY if KJFK is installed. Does this answer all the questions? Please let me know - Thank you.
-
Yes, the Crash still happens if I DISABLE both the Addon Manager and Couatl from their XML files.
Ok, at least we can exclude the modules.
The CTD does occur at other airports as well but ONLY if KJFK is installed.
This is even stranger. Even airports very far from JFK ?
However, try with the attached AFCAD, I found a problem in one of the taxiway nodes, it might change something.
[attachment deleted by admin]
-
Yes, the Crash still happens if I DISABLE both the Addon Manager and Couatl from their XML files.
Ok, at least we can exclude the modules..
I'm not fully convinced of that because of FSUIPC's interaction with several Joystick AXIS' and its AutoSave feature; I'm also wondering about InCabin Browser module. But I think I've illiminated the ITRA's Active-Panel NAVSTACK's SimConnect interactions possibilities with your snake - The only thing is everything in FS loads slower now. :-[
The CTD does occur at other airports as well but ONLY if KJFK is installed.
This is even stranger. Even airports very far from JFK ?
YES; KEDW or KORD are what I tried.
However, try with the attached AFCAD, I found a problem in one of the taxiway nodes, it might change something.
OK Thank you - I'll try again and let you know.
PS: I even updated my NVIDIA Graphic drivers just to be sure but that had nothing to do with it.
-
I'm not fully convinced of that because of FSUIPC's interaction with several Joystick AXIS' and its AutoSave feature;
I was meant to say "at least we can exclude OUR modules". We don't use, we don't require and we shouldn't be affected by the presence/absence of FSUIPC. But of course, it might be interesting to try disabling that one as well.
I'm also wondering about InCabin Browser module. But I think I've illiminated the ITRA's Active-Panel NAVSTACK's SimConnect interactions possibilities with your snake - The only thing is everything in FS loads slower now. :-
In your case, I'd start with disabling all the modules in the XML files, then testing one by one, adding one module at time.
-
Virtuali,
I'm not fully convinced of that because of FSUIPC's interaction with several Joystick AXIS' and its AutoSave feature;
I was meant to say "at least we can exclude OUR modules". We don't use, we don't require and we shouldn't be affected by the presence/absence of FSUIPC. But of course, it might be interesting to try disabling that one as well.
========================
Yes, I'll be doing that later today to be sure. But, I think your AFACD resolution of the three different name/types to the "PARKING 0" spots near the JetBlue Hanger may have resolved the CTD AFCAD issue; I still have more testing to do there just to be sure but NO CTD's so far from just standing there or Taxiing around there thus far; Bravo!
I'm also wondering about InCabin Browser module. But I think I've illiminated the ITRA's Active-Panel NAVSTACK's SimConnect interactions possibilities with your snake - The only thing is everything in FS loads slower now. :-
In your case, I'd start with disabling all the modules in the XML files, then testing one by one, adding one module at time.
================
I'll try them one by one together with your modules to see what might be conflicting (ie. Coult/AddonManager + FSUIPC ONLY and Coult/AddonManager + AICarrier ONLY, etc.). Thanks for all the suggestions; I think we are around 90% closer to resolving this and I appreciate your help and patience.
Gratci!
-
Virtuali/FSDT Staff,
I got some good news and some, OK not so good news, but the good news first ...
NO more AFCAD/Coult/Addon Manager related CTD's so far ... Gratci/Gratzier to all the FSDT Team! ;D
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2593;image)
See Attached: KJFK_AI_1.jpg
However...
Many of the CTD Issues are related to 4 different issues that when combined cause these problems:-
1. VISTA 64-bit Swap file size allocation being too large above the recommended size (when used on a RAID JBOD setup).
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2597;image)
See Attached: ERROR_KJFK_CTD.jpg
2. Nvidia newest driver (v178.13) issues.
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2595;image)
See Attached: ERROR_KJFK_CTD2.jpg
3. InCabin Brower v1.1 for FSX .xml configuration file bugs.
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2599;image)
See Attached: ERROR_KJFK_CTD4.jpg
So, its not directly related to KJFK project but, the impact of the scenery on the system was larger then expected. And all the above go away when KJFK is Uninstalled; thus I've mentioned them here.
The "not so good" news are ...
1. Missing Taxiway/Runway Numbers for 22R on the left side.
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2601;image)
See Attached: ERROR_KJFK_SIGNS.jpg
2. AI ground vehicle traffic seem to run through the KJFK bridges.
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2603;image)
See Attached: ERROR_KJFK_AI_Traffic.jpg
3. Need a map of the Terminal(s)/Parking Spot(s) for use with ParkMe.
FSDT, this is an outstanding project/product; I hope these minor fixes/updates won't burden you too much but they will be greatly appreciated. :D
Gratzie!
[attachment deleted by admin]
-
Hi,
for problem n.2, try to place KJFK on first position of scenery library, or on top of UTE.
Regards.
Alessandro.
-
Hi,
for problem n.2, try to place KJFK on first position of scenery library, or on top of UTE.
Regards.
Alessandro.
Mr. Alessandro,
I believed I moved it from that spot just to solve a scenery priority issue for another addon but, I will try that and get back to you about it. Thank you and I'll wait for the next fix/patch!
-
Alessandro/Virtuali & Ganesh/Kappa,
1. Alessandro; the answer to above default AI Vehicle traffic issue was resolved by your suggestion; Grazie! ;)
2. Virtuali/Ganesh,
I found a problem with the Coult installation in KJFK v1.0/Coult v1.0.0.120 which caused the CTD's:
With version .118 and before the installation use to modify the EXE.xml file to add its following statements correctly. But it did not handle the issues of EOF truncation very well; I think you all resolved this in version .120 by simply replacing the existing EXE.xml with a new one; Is this correct so far?
Why I say this is, because I'm using an add-on application (which most people have called AICarriers v.2 Release 2 (http://library.avsim.net/sendfile.php?Location=AVSIM&Proto=ftp&DLID=112008)) combined with Coult v.118 (or earlier) corrupted the exe.xml and caused CTD's (see attached for more: BAD_EXE.XML). The developer of AICArriers did not list the statements correctly in his installation of exe.xml file (see attached: exe.xml_Before_KJFK.xml); so really he's to blame.
eg.
COULT v1.0.0.120 Corrupted the original EXE.xml file:
But where your installation of KJFK is at fault is in that it doesn't recognize statements within an existing exe.xml file and merely just replaces the existing one with its own; I'm sure that you'll agree from a programming stand point that this is a disaster. Normally, if its missing it shouldn't be an issue or cause a CTD. However, in this apps case it loads some trust features into FSX via the FSX.CFG file and some how that triggers the CTD because its statements are now missing from the EXE.xml file as the result of the KJFK v1.0 Installation. (see attached: FSX.cfg)
eg. AICarriers statements the cause CTD (FSX.cfg) with Coult v1.0.0.120 installation[Trusted]
C:\Program Files (x86)\AICarriers\aicarriers.exe.wcechncizenkhoiqkwocqulotbtzathhwekzqzuc=1
For the Coult, You'll have to resolve that for the next update or there will be even more issues with other addons. I re-installed AICarriers and it gave the necessary statements but NOT inserted according to MS' standards. (see attached for more: GOOD_EXE.XML)
I then manually modified the EXE.xml to improve on its convention and make it correct to MS' requirements in syntax order and ASCII character truncations etc. (see attached for more: Better_EXE.XML)
This issue is now resolved; However, there is still one last CTD that occurs; the "Exit the Sim from the Flight CTD" which I believe is still related to KJFK but I'm NOT sure what the cause is yet; maybe you can suggest something?
I've ATTACHED the AICarriers (FREEWARE) [AICarriers Release 2.zip] (http://library.avsim.net/sendfile.php?Location=AVSIM&Proto=ftp&DLID=112008) along with my examples of the .xml files [exe_xml_&_FSX_CFG_files.zip] (http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2784) for you all to do your own tests.
Thank you for your time and attention; And Good Luck! :)
==========================================
3. PS: Kappa, Can you resolve this? Grazie! :D
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2601;image)
-
With version .118 and before the installation use to modify the EXE.xml file to add its following statements correctly. But it did not handle the issues of EOF truncation very well; I think you all resolved this in version .120 by simply replacing the existing EXE.xml with a new one; Is this correct so far?
No. The installer hasn't changed the slightest bit. It is exactly the same code that is used to deal with DLL.XML, which has been used since Zurich has been released, it's just the file affected is EXE.XML, but the actual code is the same. So, there are absolutely no difference between the two versions.
The developer of AICArriers did not list the statements correctly in his installation of exe.xml file (see attached: exe.xml_Before_KJFK.xml); so really he's to blame.
That file is NOT corrupted! It simply have everything on a single line, which is STILL legal XML! In fact, *because* XML is *designed* to exchange data between different OS which might use different ways of indicating End-Of-Line, XML standard dictates that EOL characters are NOT required. That's why there are opening/closing tags in the first place!
However, writing back the XML file in a non-Dos standard, might confuse OTHER installers (NOT OURS!!) that, in these case, might create a *real* mess, because they parse the XML *assuming* it have CRLF linebreaks at each line, and THAN corrupting it, this time for real. So, it's not a good idea in any case.
But where your installation of KJFK is at fault is in that it doesn't recognize statements within an existing exe.xml file and merely just replaces the existing one with its own
That's not what it does. Our installer creates a new EXE.XML file ONLY if it doesn't find one on the hard drive, which is the default on a new FSX instalation. If an EXE.XML is already there, it obviously add its section to it.
HOWEVER, even if the EXE.XML created by AiCarriers wasn't really "corrupted" (if you open it in IE, is still legal XML and so is for FSX), they did a *different* type of "corruption". In our installer, we had some code to DEFEND ourselves against a slightly different kind of apparent corruption: those caused by Wilco installers, which instead convert the file from Dos to Unix line-endings. Still a legal file, but not very smart because, many of other installers were confused by this.
So, in order to fix the Wilco gotcha, we had some code that detected the Wilco-style "corruption" that is DIFFERENT from the AI-Carriers-style "corruption", which doesn't use Unix EOL chars, it simply doesn't use ANY EOL char at all..(I'm using the term corruption in quotes, to mean that is not really a corruption, but it's just a change of standard which might confuse other installers)
THIS code only took care of the "Wilco corruption" because we never heard of the other kind until now so, IN THIS CASE (and ONLY in this case), if an XML file was found with a *different* kind of "corruption" other than Wilco's, we assumed it was really corrupted, and replaced with a new one.
In ALL other cases (including after installing a Wilco product), when the XML is correct and hasn't suffered from any kind of messing with EOL indicators, we DON'T replace it, we just add our section.
So, the issue is not that our installer "replaces the EXE.XML with its own", it's just that it wasn't programmed to deal with ALL different kind of "corruptions", but just the Wilco one.
I think to have found a solution, by including a proper XML validator in the installer, that is able to deal with all cases, and by writing back the file in DOS format, it should "fix" any XML, even when it was "corrupted" by other installers.
This issue is now resolved; However, there is still one last CTD that occurs; the "Exit the Sim from the Flight CTD" which I believe is still related to KJFK but I'm NOT sure what the cause is yet; maybe you can suggest something?
I'm sorry, but I'm still not able to reproduce this. Nobody else is reporting it so far, so I must conclude it's nothing related to the scenery.
-
Thank you, Virtuali!
I appreciate your explaining your installer to me; Now at least we know that "AICarriers" can cause another EXE.xml issue with your installer(s) that you can create/add a validator for. That should bring down the bug reports; I hope! ;)
Regarding the "Exit the Sim from the Flight CTD" issue, I still don't know what causes it... But If I uncheck KJFK from the Scenery Library list and or Uninstall it all together; this CTD goes away. I did as Alessandro suggested, and moved it up/down in priority in FS' Scenery menu to see if that makes a difference; but, sadly NO! :'( :( It does resolve the AI vehicle issue though, when its done as he suggested. Finally, I'll still trouble shoot this and see what I can fix or report to you; Thank you for trying on your end.
PS: Can "we" get a Scenery fix for the Signs? ... that might be the issue causing the "Exit the Sim from the Flight CTD" issue or an AFCAD issue with some of the ILS' which might not have been noticed till recently. I'll check back on all this with you; as I start to feel better and get back to my normal routine. - "Head Cold" is only 80% cured! :P :-[ :'(
-
Regarding the "Exit the Sim from the Flight CTD" issue, I still don't know what causes it... But If I uncheck KJFK from the Scenery Library list and or Uninstall it all together; this CTD goes away.
Try to rename the file called LC_2817.bgl to LC_2817.back on JFK scenery folder and test the scenery.
Regards.
Alessandro.
-
Regarding the "Exit the Sim from the Flight CTD" issue, I still don't know what causes it... But If I uncheck KJFK from the Scenery Library list and or Uninstall it all together; this CTD goes away.
Try to rename the file called LC_2817.bgl to LC_2817.back on JFK scenery folder and test the scenery.
Regards.
Alessandro.
Mr. Alessandro,
Does this file deal with Signs or something else entirely? OK, I'll try and let you know...
-
Alessandro/Staff,
1. I did as you said; I'm NOT sure what is suppose to happen but the CTD's still there. The only thing that did happen differently is that FSX's Scenery builder took more time reloading the scenery.
(See attached: KJFK_ERROR_.jpg & KJFK_ERROR_CTD.jpg)
2. I have this issue with the Flickering Trees in KJFK FSX as well: HERE (http://www.fsdreamteam.com/forum/index.php?topic=1115.msg9174#msg9174)
I know you guys want to be done with this and move on the KLAS but, please, lets resolve this... Grazie!
[attachment deleted by admin]
-
(See attached: KJFK_ERROR_.jpg & KJFK_ERROR_CTD.jpg)
I'm sorry, but I can't see any error or problem in your screenshots. You are running the Simconnect diagnostics in Verbose mode, it simply showing normal operations there, no errors I can see from your screenshot.
2. I have this issue with the Flickering Trees in KJFK FSX as well: HERE (http://www.fsdreamteam.com/forum/index.php?topic=1115.msg9174#msg9174)
I've already posted a screenshot there that clearly shows there's no flickering. So, it must be something else.
I know you guys want to be done with this and move on the KLAS but, please, lets resolve this... Grazie!
As we said, many times already, the only chance to be able to fix something, is to be able to reproduce your crash. Since we can't, we can only make guesses, but at this point I'm quite sure your crash is not related to the scenery, even if it DOES goes away the scenery. It's probably that "something else" that is conflicting with the scenery, and it might probably be solved either by removing the scenery OR by removing that "something else".
Are you able to test the scenery on a brand new FSX installation with nothing else except FSX SP1 and FSX SP2 ?
-
Virtuali,
RE: Flickering Trees
OK; I see the YouTube site shows that the videos: "This video is not yet processed." - Its a problem with FRAPS 64bit .avi encoding and they haven't fixed that with the new version, I'm guessing. Could you please wait for that? It will show you exactly what is happening and its, most likely, video driver related but, I'm not sure because it only happens with KJFK trees and NOT with the surrounding (DEFAULT FSX) trees.
RE: CTD
I agree with your assessment; I have honestly run out of options. I've tried removing all the modules and their Apps from the exe.xml/dll.xml files as you suggested. I don't know what else to do to FSX to get it to co-orporate and reveil the "troublemaker." Any other suggestions? I do have a VISTA 32 Labtop which I've use for things like this - I could install FSX - SP1 - Acceleration and do a test. But it would most likely NOT show the same results, since it doesn't have all the addons/hardware that I have on the my Flight Sim system.
Also, the SimConnect Verbose output to screen is a consequence on the installation of my ITRA's ActivePanel-NAVSTACK II latest driver which uses SimConnect; previous ones didn't. If you know how to turn the dare thing off, please let me know. It honestly bugs me. I've asked ITRA and am still waiting for a responce (4-5 months later). ::)
PS: Flight Sim System uses Vista-64 SP1 with FSX, SP1 and Acceleration installed.
Anything else? ???
-
But it would most likely NOT show the same results, since it doesn't have all the addons/hardware that I have on the my Flight Sim system.
But at least you would know it's not caused by the scenery.
Also, the SimConnect Verbose output to screen is a consequence on the installation of my ITRA's ActivePanel-NAVSTACK II latest driver which uses SimConnect; previous ones didn't. If you know how to turn the dare thing off, please let me know.
delete the Simconnect.ini file you have in your Documents\Flight Simulator folder
-
But it would most likely NOT show the same results, since it doesn't have all the addons/hardware that I have on the my Flight Sim system.
But at least you would know it's not caused by the scenery.
Also, the SimConnect Verbose output to screen is a consequence on the installation of my ITRA's ActivePanel-NAVSTACK II latest driver which uses SimConnect; previous ones didn't. If you know how to turn the dare thing off, please let me know.
delete the Simconnect.ini file you have in your Documents\Flight Simulator folder
Thank you; I'll do both and get back to you. Grazie! :D
-
Virtuali,
1. RE: SimConnect.ini
I removed the file from the folder as you suggested and the output screen went away. I, also, edit it and excluded the statements because I wanted to limit any possibility of future CTD's as the result of missing files when function call are made etc. (I'm not sure that it would happen but, just want to be sure). However, the "EXIT the Sim from Flight CTD" is still there, so this is obviously NOT the cause of the problem, but at least I'm rid of that annoying output console screen. Grazie! - You're doing tech support for ITRA as well now. :D ;D
Here is what I did ...
eg.
ORIGINAL:
[SimConnect]
level=verbose
console=1
;RedirectStdOutToConsole=1
;OutputDebugString=1
;file=c:\simconnect%03u.log
;file_next_index=0
;file_max_index=9
MODIFIED:
[SimConnect]
;level=verbose
;console=1
;RedirectStdOutToConsole=1
;OutputDebugString=1
;file=c:\simconnect%03u.log
;file_next_index=0
;file_max_index=9
2. RE: The Flickering trees at KJFK Video's
YouTube has still NOT processed those uploaded videos. So, I compressed them in 7Zip and uploaded it here; Flicker Tree at KJFK (Zip filesize: 99.6MB+ ) (http://x-plane.org/home/JamesChams/TREES.zip); Please download it and see the trouble we are having. I've also included a short clip of the surrounding default FSX trees which DON'T have this issue. Maybe it is something you can fix at some point. Finally, let me know when you've downloaded it so that I can removed it from the offsite website; shared space reasons. Grazie!
3. CTD / Install FSX/KFJK on another system to test ...
I'm currently working to install it on a couple of other machines. I'm still recovering from my head cold so my energy is not fully there yet; But I'll let you know this for sure. I did do as Alessandro suggested, by renaming the file called LC_2817.bgl to LC_2817.back on JFK scenery folder to test the scenery but, like I mentioned before, all that did was cause the scenery loader to take longer to load KJFK the first couple of times; there is NO difference with the "EXIT the Sim from Flight CTD", which is still there. :( :'( :-\
4. KJFK Taxiway signs
The issue here is NOT that many signs are two sided or not, the issue is that in some cases there is NO picture on either side of the sign or FSDT is NOT using aviation convention for sign placement. This results in us, customers, NOT to be able to use a sign as intended.
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2799;image)(see attached: KJFK_ERROR_SIGNS.jpg) (http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2798;image)
Please Help!
[attachment deleted by admin]
-
Maybe it is something you can fix at some point. Finally, let me know when you've downloaded it so that I can removed it from the offsite website; shared space reasons.
I don't need to see the video, the screenshots posted are perfectly clear with regards to what is happening. However, the screenshots I've posted, show the problem doesn't happen here. As I said, many times already, in order to have a chance to fix a problem, we must be able to reproduce it, otherwise we are simply shooting in the dark, like you CTD problem, which I'm sure will go away on a clean system.
I'm starting to have a theory that it might be dependent on system load. You guys are simply overloading your system with too much stuff and too high settings, that the graphic engine can't keep it up anymore.
Can you try to lowering ALL your settings A LOT (but still be able to see at least the trees), and check if the problem happens as well ? Put everything down, AI, scenery size, try to at least double the fps, if you can.
The issue here is NOT that many signs are two sided or not, the issue is that in some cases there is NO picture on either side of the sign
That's an entirely different issue. I was replying to an user that specifically mentioned taxisigns not being double-sided: there was no mention of having found taxisigns with no textures whatsoever on either side...
Please, instead of posting screenshots, try to use simple descriptions like, "at taxi K, interesecting with taxi X", or just type coordinates.
-
Virtuali,
OK I will do as you suggest and get back to you ...
Please look at the videos; It's NOT a scenery setting issue, as I get that on the brand new installation on the LAPTOP as well; it only has a basic build-in video card with shared VRAM and FSX default graphic settings, NO ADD-ON at all except your KJFK. (NO AI, NO FSUIPC, NO UTX, nothing but FSX SP1, (SP2)Acceleration).
The missing taxiways signs are all over the place; that is why I mentioned them here and NOT on the other post; I agree, their not the same issue.
Thanks! :D
-
Please look at the videos; It's NOT a scenery setting issue, as I get that on the brand new installation on the LAPTOP as well; it only has a basic build-in video card with shared VRAM and FSX default graphic settings, NO ADD-ON at all except your KJFK. (NO AI, NO FSUIPC, NO UTX, nothing but FSX SP1, (SP2)Acceleration).
As I've said already, I don't need to see the video. The screenshots clearly shows the problem which, as I've said, doesn't happen here.
Also, regardless of the fact you say it's NOT a scenery settings or something that might be related to other addons, I've said an entirely different thing, and I kindly ask you to TRY IT, please. If I'm asking something, it's becuse there IS a resons, which might lead to a solution even if I can't reproduce it here.
So, PLEASE, can you try LOWERING ALL YOUR FSX SETTINGS, so low that your fps will double or even better, basically turn down everything, just leave the Scenery Density to a minimum setting that will at least show the affected trees. Everything else, put it down. I need to check a theory, if you don't even try, it's worthless continuing.
The missing taxiways signs are all over the place; that is why I mentioned them here and NOT on the other post; I agree, their not the same issue.
You are now talking of a 3rd ENTIRELY different issue again. In your previous message, I had the impression you were referring to taxiway signs with no indications on either side. Now, you are saying "missing" taxiway signs ? That's very different. Please, clarify. And, as I've said already, give me at least some place to look because, after a random check, taxi signs here looks just fine.
-
Virtuali,
OK, give me a little time. I'm sick and am suppose to be in bed recovering but, bordom is getting to me much more :D ;
Don't worry, I will do as you ask and get back to you. I want this resolved as much as I'm sure you do as well. ;D
8)
-
Virtuali,
1. I just noticed today that FSDT has updated KJFK's Coult v1.0.0.140 with Keymapping (BRAVO! & Grazie! ;D) and Addon Manager X 2.5.1.1 (and only you all know what else). This means, that I've just spent the time reinstalling; I'll let you know if still see all the above bugs present there or NOT.
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2819;image)
2. PS: I'm buying XPOI; but when I try to download it on the site it says "Coming Soon!" so, I'll wait. But, I just bought your/Aersoft's FlorenceX for FSX. ;) It's an amazing scenery package; Grazie! :D
Please read the Right bottom corner of this pic. Grazie!
(http://www.fsdreamteam.com/forum/index.php?action=dlattach;topic=1049.0;attach=2817;image)
[attachment deleted by admin]
-
Virtuali/Ganesh,
OK; I did as you asked with the following results.
3 similar systems: (They have these in common)
OS: VISTA (32/64-bit), 2 or 4GB RAM, 8800GTX WCE; FSX-SP1-Acceleration/SP2
1. KJFK v1.0 (FSX) with Add-On manager v2.5.1.1 /Coult v1.0.0.140 installation corrupts existing data in EXE.xml. (I tried this several times with AICarriers content and *rubbish* statements that I included for the test).
2. RESET Display settings to default, shutdown and saved settings in FSX and RESTARTED; "EXIT the Flight CTD" still there on ALL THREE SYSTEMS when KJFK is installed ONLY; NO other Add-ons at all (including SDK's - Object Placement Tool, Traffic Toolbox & Visual Effects Tool).
3. FPS: 11-14 at KJFK with Default C172.
4. TAXIWAY Signs are missing in many places BUT NOT the same locations on each seperate INSTALLATION. :o ???
I don't know what else to tell you; Any other suggestions? ???
-
1. KJFK v1.0 (FSX) with Add-On manager v2.5.1.1 /Coult v1.0.0.140 installation corrupts existing data in EXE.xml. (I tried this several times with AICarriers content and *rubbish* statements that I included for the test).
Doesn't happen here.
It's not very clear from this message, if you noticed the corruption before, after or regardless, the installation of AI Carriers. In all cases, the current installer should be able to fix any corruption created but other installers, and it certainly DO NOT corrupts the file itself. It NEVER DID, BTW, it's just the previous version wasn't able to FIX the corruption created by AI Carriers, only the one created by Wilco installers, this one should be able to fix the AI Carriers-created corruption, but our installer NEVER, EVER, corrupted an XML!!
2. RESET Display settings to default, shutdown and saved settings in FSX and RESTARTED; "EXIT the Flight CTD" still there on ALL THREE SYSTEMS when KJFK is installed ONLY; NO other Add-ons at all (including SDK's - Object Placement Tool, Traffic Toolbox & Visual Effects Tool).
Doesn't happen here. By doing this test, you only verified is not caused by *another* addon, but still might be created by something else, otherwise everyone should have it.
3. FPS: 11-14 at KJFK with Default C172.
22-25 fps with C172 here. I'm using a 8800GTX with Vista 32 as well.
4. TAXIWAY Signs are missing in many places BUT NOT the same locations on each seperate INSTALLATION.
Can't simply happen. Either you have the same taxiway signs always wrong, OR they are alwyas right. They simply can't change depending on the system. Unless there's a video driver problem, that is affecting the drawing of textures.
I'm still convinced you are using SETTINGS TOO HIGH. That's why you have low fps, that's why you have your system struggling to draw textures, that's why you probably have CTD, because your video driver is probably bugged when overloaded, and probably this is also the reason why you see flickering trees.
I don't know what else to tell you; Any other suggestions? ???
I'm exhausted all the available suggestions for you. It's just that you are still the only one right now reporting this problem, in the way you are describing it (CTD on exit, for example, or XML file corruption, nobody reported so far, except you)
-
Quote from: JamesChams on Today at 08:21:44 PM
1. KJFK v1.0 (FSX) with Add-On manager v2.5.1.1 /Coult v1.0.0.140 installation corrupts existing data in EXE.xml. (I tried this several times with AICarriers content and *rubbish* statements that I included for the test).
Doesn't happen here.
It's not very clear from this message, if you noticed the corruption before, after or regardless, the installation of AI Carriers. In all cases, the current installer should be able to fix any corruption created but other installers, and it certainly DO NOT corrupts the file itself. It NEVER DID, BTW, it's just the previous version wasn't able to FIX the corruption created by AI Carriers, only the one created by Wilco installers, this one should be able to fix the AI Carriers-created corruption, but our installer NEVER, EVER, corrupted an XML!!
The exe.dll, by default, if NO add-ons are installed, it installs correctly. If add-on exist in the file prior to installing KJFK, the entire content of that file is trashed and ONLY the coult items are added/replaced; So, I'm guessing that the installation either see's the file as corrupt and replaces it or it replaces it by default. So, I tested my theory, and If I custom create a file or use the installation file of the AICarriers, they both get trashed for KJFK's Coult. Does this explain what is happening?
Quote
2. RESET Display settings to default, shutdown and saved settings in FSX and RESTARTED; "EXIT the Flight CTD" still there on ALL THREE SYSTEMS when KJFK is installed ONLY; NO other Add-ons at all (including SDK's - Object Placement Tool, Traffic Toolbox & Visual Effects Tool).
Doesn't happen here. By doing this test, you only verified is not caused by *another* addon, but still might be created by something else, otherwise everyone should have it.
Could be; But I though it was a RAID HDD issue because I was getting this after the CTD in some instances. So I did a SCANDISK and DEFRAG on the affected system. And replaced the entire DRIVE with another one just to be sure, and updated the MB/RAID drivers to nForce v20.08 which was recently released. The "EXIT the Flight CTD" still remains if I exit the Sim from KJFK but NOT at other airports, like KORD, LSZH. This is why I think something is the matter with the KJFK FSX files; But, only you could verify that.
Quote
3. FPS: 11-14 at KJFK with Default C172.
22-25 fps with C172 here. I'm using a 8800GTX with Vista 32 as well.
With my current setting I get 40+ FPS with the Flight Sim system and around 20-30FPS with the other two systems in FSX with default airports or some payware like your Florence X package. But, I get an average of 11-14FPS when I use the KJFK in each of these systems. NO Overclocking is being done on the Video Cards, CPU, or Motherboard (MB). I know you CAN'T replicate this but it is happening and other are posting visual problems too, with I now believe might be related to a combination of NVidia's graphic card new/old drivers and VISTA's OS updates (as of OCT 15th). Can you post Pics of your FSX Display settings and I will use those exact settings an see if they are the same, OK?
Quote
4. TAXIWAY Signs are missing in many places BUT NOT the same locations on each seperate INSTALLATION.
Can't simply happen. Either you have the same taxiway signs always wrong, OR they are alwyas right. They simply can't change depending on the system. Unless there's a video driver problem, that is affecting the drawing of textures.
I'm still convinced you are using SETTINGS TOO HIGH. That's why you have low fps, that's why you have your system struggling to draw textures, that's why you probably have CTD, because your video driver is probably bugged when overloaded, and probably this is also the reason why you see flickering trees.
I'm NOT making this up; as I stated earlier, there is NO over pressuring on any of the graphic cards or other system components. But that is what I'm seeing; I'll have to do more tests to give you a better explaination - It might be as you say a Video Card issue.
Quote
I don't know what else to tell you; Any other suggestions?
I'm exhausted all the available suggestions for you. It's just that you are still the only one right now reporting this problem, in the way you are describing it (CTD on exit, for example, or XML file corruption, nobody reported so far, except you)
OK! Can you just give me your FSX settings and I will mirror them on each system and let you know.
Grazie!
-
OK! Can you just give me your FSX settings and I will mirror them on each system and let you know.
I'm out of office today, I'll get back to you on Monday.
-
Virtuali,
Thank you! I'll wait for it.
-
The exe.dll, by default, if NO add-ons are installed, it installs correctly. If add-on exist in the file prior to installing KJFK, the entire content of that file is trashed and ONLY the coult items are added/replaced
Doesn't happen here.
It happens ONLY if the EXE.XML is REALLY corrupted. Meaning, not "corrupted" like after Wilco or even AI Carriers, because these files were STILL (as I've already explained) legal XML files, just with different standard for EOL characters.
The file will be trashed ONLY, and ONLY, if the XML was ALREADY corrupted "beyond repair", meaning, not a legal XML file anymore, usually because it was hand-edited trying to "fix it", usually with open tags, etc.
So, I'm guessing that the installation either see's the file as corrupt and replaces it or it replaces it by default. So, I tested my theory, and If I custom create a file or use the installation file of the AICarriers, they both get trashed for KJFK's Coult. Does this explain what is happening?
That's exactly what I've said, this can only mean your XML file was ALREADY corrupted (REALLY corrupted, not "Wilco-corrupted" or "AI-carriers" corrupted! ), BEFORE installing JFK, it WAS NOT corrupted BY JFK!
So I did a SCANDISK and DEFRAG on the affected system. And replaced the entire DRIVE with another one just to be sure, and updated the MB/RAID drivers to nForce v20.08 which was recently released.
That would only tell you that your file system is not trashed. There are thousands other ways why you might have crashes, without being the file systems's fault.
But, only you could verify that.
We already verified everything. The very fact you are still the only one reporting THIS behaviour, is enough proof that the CTD is not related to the scenery itself, otherwise we would have the forum flooded with such reports by now.
Can you post Pics of your FSX Display settings and I will use those exact settings an see if they are the same, OK?
There's no need, of course, to post "pics". FSX has a feature to save/load settings...
I'm NOT making this up; as I stated earlier, there is NO over pressuring on any of the graphic cards or other system components. But that is what I'm seeing; I'll have to do more tests to give you a better explaination - It might be as you say a Video Card issue.
None is telling you you are "making this up"... I only said that if you see a taxiway sign missing on a system and a DIFFERENT one missing on another, it's clear that it can't be "in" the scenery, it must be just a random problem of drawing textures, that might have affected any texture. If it was inherent to the scenery, you should have seen always the SAME textures missing on all systems.
-
Virtuali,
I believe that the NVIDIA GeForce 8800 drivers are not able to handle the awesome scenery of KJFK. I believe that is a major cause of the CTD and that is the relationship to it. As to wheather or NOT the scenery is *causing* the CTD, I cannot know; only assume.
Other people are have issues, wheather or not they have the same issues or reported them, I cannot comment about. I'm only interested in resolving the issues that I am having which I believe is related to the scenery and the installation. You asked me to test this on multiple systems and use lower/default settings and I did; I used 3 systems to compare on; the flight system that I was originaly having the problem on, a Sony labtop and another system this is comparable to the flight system I have; I found similar results in the above mentioned EOF truncation of the dll.xml file and the CTD triggered by the "Exit directly from the Flight." I did as you asked.
Could you please send me pics of your Display settings in FSX and I will match them exactly in my settings and see if this is truely an independant issue or part of the KJFK package - for the purpose of helping you help me resolve this and for all other users as well. Is this too much to ask right now? I return to work tomorrow but I will endevor to report back to you as soon as I am able.
Thank you very much.
-
I believe that the NVIDIA GeForce 8800 drivers are not able to handle the awesome scenery of KJFK
Mine certainly are.
I believe that is a major cause of the CTD and that is the relationship to it.
It's probably more complex than simply stating "nvidia driver's can't handle JFK". It's probably due to a specific setting, that might be or not default, that might be or not default in any release of the drivers, that might be or not caused by a driver "tweaker", etc.
Other people are have issues, wheather or not they have the same issues or reported them, I cannot comment about.
I can, of course. Other people HAD issues, these were ALL fixed already, both with downloadable files posted in the forum, and they are all included in the installer. There are no problems open, except yours. And, nobody ever reported a "CTD when exiting", like you are.
I found similar results in the above mentioned EOF truncation of the dll.xml file
You are probably meaning the EXE.XML file, not the DLL.XML file...
However, I think to have found what's happening, in this case. And, it's again caused by AICarrier's. Its installer writes an incomplete XML, without the header ( <?xml version etc... , the sample EXE.XML in the FSX SDK of course has the header). Such file is considered corrupted by our installer, which replaces it with a new one.
I've already updated the installer to defend itself even with this kind of error so, it will add the header to the exe.xml, if there's none.
and the CTD triggered by the "Exit directly from the Flight."
There's nothing more that I can say, except I can't reproduce it.
Could you please send me pics of your Display settings in FSX and I will match them exactly in my settings
As I've said, there's no need to post pictures, because FSX has a settings Load/save feature.
-
Virtuali,
- Could you please send me pics of your Display settings in FSX and I will match them exactly in my settings
As I've said, there's no need to post pictures, because FSX has a settings Load/save feature.
Can you send me *your* FSX Display settings ".cfg" file and I'll load that?
Thank you for "fixing" your installer to handle the above mentioned and lets stop debating about "who's right"; I don't care; I just want to fix this.
Grazie! :D
-
Can you send me *your* FSX Display settings ".cfg" file and I'll load that?
Here's the settings. Load the .CFG using the "Load settings" feature, and copy the Addon Manager tweaks because they aren't saved in the .CFG settings. Many are default, anyway.
I'm using nVidia 177.98 drivers, everything at default, except Antialiasing at 8x and Anisotropic filtering at 16x
[attachment deleted by admin]
-
Grazie!
... I will try and let you know! :D
-
Virtuali,
OK; This is a REPORT of the existing installation of KJFK v1.0/XPOI v1.0.6 on VISTA 64-bit. I'm ONLY trying to resolve this for myself and other users in your installer which, is why I'm posting this.
1. REINSTALLED KJFK for FSX again today 10:07PM EST (10/19/2008) after RE-DOWNLOADING the installer.
I. EXE.XML file before the KJFK re-installation performed above. I left the previous installation of KJFK
just to see how this will/should work (ie. I just re installed over the old setup).
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>AICarriers</Name><Path>C:\Program Files (x86)\AICarriers\aicarriers.exe</Path>
<CommandLine>-nogui</CommandLine>
</Launch.Addon>
</SimBase.Document>
II. EXE.XML after above KJFK installation performed.
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
</SimBase.Document>
YOU CAN SEE THAT THE STATEMENTS FOR AI CARRIERS ARE MISSING IN THE NEW EXE.DLL FILE. Can you fix your next version of the installer to check/correct for this?
2. So, I manually re-added the AICarrier Statements into the EXE.XML again and tried this test again with the new XPOI v1.0.6 installation today at 10:27PM EST (10/19/2008).
I. EXE.XML file before the XPOI installation performed above after I re-inserted AICarriers statements
manually using Notepad and saving the file.
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
<Launch.Addon>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Name>AICarriers</Name><Path>C:\Program Files (x86)\AICarriers\aicarriers.exe</Path>
<CommandLine>-nogui</CommandLine>
</Launch.Addon>
</SimBase.Document>
II. EXE.XML after above XPOI installation performed.
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="Launch" version="1,0">
<Descr>Launch</Descr>
<Filename>exe.xml</Filename>
<Disabled>False</Disabled>
<Launch.ManualLoad>False</Launch.ManualLoad>
<Launch.Addon>
<Name>Couatl</Name>
<Disabled>False</Disabled>
<ManualLoad>False</ManualLoad>
<Path>fsdreamteam\couatl\couatl.exe</Path>
</Launch.Addon>
</SimBase.Document>
SO, THIS IS DEFINITIVE EVIDENCE that this happens consistently; Now does it happen to your installation of AICarriers or other statement? Can you fix your installers to resolve this in the next version(s) of XPOI as well as KJFK?
I've now had to resolve this each time by manually adding the AICarrier statements back into the file and saving it ... :'( :(
3. Next, You are using an OLDER (177.98) Nvidia Graphic Driver; this is the latest version for 32-bit driver (below) and I'm using the 64-bit version so, there might be differences. ??? Would you be willing to test KJFK with this 32-bit version on your systems to see if you have the same results with the MISSING TAXIWAY SIGNS and "Exit FSX from the Flight CTD" ?
GeForce Release 178 WHQL
Version: 178.24
Release Date: October 15, 2008
Operating System: Windows Vista 32-bit
Language: U.S. English
File Size: 85 MB
Nvidia Driver: http://www.nvidia.com/object/winvista_x86_178.24_whql.html (http://www.nvidia.com/object/winvista_x86_178.24_whql.html)
4. I'll test the Display setting configurations, you've provided, with the new file you've given me, and see if I get everything working again with the "Missing Taxiway Signs" and "EXIT FS from the Flight CTD". But this is all I have to report at this time.
Finally, Please lets not debate these issues anymore; This is just my report; maybe no one else has this but, I get it on all 3 systems; so, to me, this is a FACT. Would you kindly re-check your systems, if time permits?
Thank you for your time and attention.
-
YOU CAN SEE THAT THE STATEMENTS FOR AI CARRIERS ARE MISSING IN THE NEW EXE.DLL FILE. Can you fix your next version of the installer to check/correct for this?
Sorry, but this is not what happened.
I've tested it with the EXE.XML files YOU sent me some days ago and, the EXE.XML created by AICarriers, the one that YOU named "EXE.XML before JFK", didn't included the XML header! The first line that specifies the version and the encoding.
THIS, and ONLY THIS was the problem and, of course, wasn't caused by our installer. If the XML HAD a correct header, it WORKED with AICarriers installer as well
SO, THIS IS DEFINITIVE EVIDENCE that this happens consistently; Now does it happen to your installation of AICarriers or other statement? Can you fix your installers to resolve this in the next version(s) of XPOI as well as KJFK?
No, it's not the "definitive evidence", because it didn't happened here. NOT with the files as you posted NOW (which have an header, unless you manuall fix it yourself before posting it). What DID happen, exactly as I've said before and in all previous messages, is that, if the XML was ALREADY WRONG ( = missing the header, in this case), it was considered to be corrupted and replaced with a new one.
So, as usual, the installer has now been improved AGAIN to cover ANOTHER case of ANOTHER product which creates a wrong XML file. Our installer is becoming more and more a "fixer" for other product's fault because NOW, is able to:
1) Fix the Unix-style EOL created by Wilco
2) Fix the missing EOL created by AICarriers
3) Fix the XML with a missing XML header
I think we might consider selling the installer as a stand-alone product, considering all the fixing it's now able to do, to repear damaged XML files...
BOTH installers, for JFK and XPOI are NOW "fixed", since this morning, being now able to repeair even this new kind of already existing corruptions.
3. Next, You are using an OLDER (177.98) Nvidia Graphic Driver; this is the latest version for 32-bit driver (below) and I'm using the 64-bit version so, there might be differences. ???
It might older, but it works.
Would you be willing to test KJFK with this 32-bit version on your systems to see if you have the same results with the MISSING TAXIWAY SIGNS and "Exit FSX from the Flight CTD" ?
Yes, but I'm sure it will work, because I upgraded all the WHQL drivers that were released during the 5 months JFK was in developement and, of course, never had such behaviour. Kappa, which made all the textures, use Vista 64 and GTX8800, he doesn't have it either...
Finally, Please lets not debate these issues anymore; This is just my report; maybe no one else has this but, I get it on all 3 systems; so, to me, this is a FACT.
I'm sorry, but as long as I can't reproduce it, the only way I have to understand if there's a problem in the scenery, is to see if anyone else has reported it. And, nobody else has, and THIS is a fact as well, which is of course more statistically relevant, because we had something like 30.000 downloads of JFK so far...
-
YOU CAN SEE THAT THE STATEMENTS FOR AI CARRIERS ARE MISSING...
So, as usual, the installer has now been improved AGAIN to cover ANOTHER case of ANOTHER product which creates a wrong XML file. Our installer is becoming more and more a "fixer" for other product's fault because NOW, is able to:
1) Fix the Unix-style EOL created by Wilco
2) Fix the missing EOL created by AICarriers
3) Fix the XML with a missing XML header
I think we might consider selling the installer as a stand-alone product, considering all the fixing it's now able to do, to repear damaged XML files...
BOTH installers, for JFK and XPOI are NOW "fixed", since this morning, being now able to repeair even this new kind of already existing corruptions.
Grazie Virtuali/Staff! ;D That's why you're the best ... :D That's why I've bought all your products; and many of the one's you've done for other developers too; and will continue to do so. :)
Would you be willing to test KJFK with this 32-bit version on your systems to see if you have the same results with the MISSING TAXIWAY SIGNS and "Exit FSX from the Flight CTD" ?
Yes, but I'm sure it will work, because I upgraded all the WHQL drivers that were released during the 5 months JFK was in developement and, of course, never had such behaviour. Kappa, which made all the textures, use Vista 64 and GTX8800, he doesn't have it either...
I'm still testing this but all I can say right now is that both your settings and mine work; There is an overheating issue that I discovered with my watercooled 8800GTX's which I must remedy first; this is most likely the cause of the CTD's when at KJFK because that scenery taxes the hardware a little. But the issue with the taxiway signs is something else which I don't know all the answers for; I'll get back to you with that.
All the best with all the sceneries/utilities/add-on's your coming out with. :D 8)
-
BOTH installers, for JFK and XPOI are NOW "fixed", since this morning, being now able to repeair even this new kind of already existing corruptions.
Virtuali,
Did you/staff upload this new installer to the download links? (Because I redownloaded and installed them yesterday and they are still the *original files* with the same original problem).
If you can find the time ... ;)
Grazie!
PS: Just bought XPOI today and like it. ;D
-
I confirm both XPOI and JFK installers that are online now, are able to fix the missing XML header bug caused by AICarriers, tried and tested, with the XML files you sent me.
-
I confirm both XPOI and JFK installers that are online now, are able to fix the missing XML header bug caused by AICarriers, tried and tested, with the XML files you sent me.
OK; Thank you. I'll redownload and give you confirmation. ;)
Also, I did notice something you mentioned before; If I load a flight and leave the sim alone with the aircraft on a parking spot (Windowed Mode) and unattended it does CTD; What might cause that? ???
I, also, do have a liquid cooling issue as I've added a few items to the system which are draining power and overheating the system and causing lockup's; I'll resolve this on my own; but the CTD for KJFK's "EXIT the flight from the Sim" is all that remains and the above mentioned CTD. :-\ :'(
If you can suggest something; I would appreciate it.
Grazie!
-
Also, I did notice something you mentioned before; If I load a flight and leave the sim alone with the aircraft on a parking spot (Windowed Mode) and unattended it does CTD; What might cause that? ???
Doesn't happen here. And doesn't happen to anyone else.
I, also, do have a liquid cooling issue as I've added a few items to the system which are draining power and overheating the system and causing lockup's; I'll resolve this on my own; but the CTD for KJFK's "EXIT the flight from the Sim" is all that remains and the above mentioned CTD.
As I've said, many times already, it doesn't happen here, and nobody reported it so far except you. The fact that you are saying you have hardware issues, might lead to believe (I was sure of this already, but this only confirms it), it's nothing related to JFK scenery, except that the scenery is simply quite complex and might put some extra stress on a system that, if already has some issues like overheating to begin with, it might cause crashes. Of course, that shouldn't happen on a normal system and, in fact, it doesn't happen.
-
I would fully except that, except for the fact, that it happens on the other two that I've got which DON'T have water cooling systems or overheating issues; So there is something else which is still escaping me. :-\
And yes I know you can't reproduce it ... let's not debate that anymore. ;)
If you can do/say something to help, it would be much appreciated. :)
Grazie!
-
Virtuali,
OK; I just downloaded and re-tried KJFK v1.0 installer and got the same result as mentioned earlier with the installer overwriting the previous EXE.XML file >:( ; You might want to try again with these files. ::)
Attached:
[attachment deleted by admin]
-
I just downloaded and re-tried KJFK v1.0 installer and got the same result as mentioned earlier with the installer overwriting the previous EXE.XML file >:( ; You might want to try again with these files.
First, the files you sent me now are NOT the same files you sent me earlier. They are clearly hand modified, because I don't think the AI Carriers installer now uses newlines on each line *except* the one with the <Path> statement, look the line here:
<Name>AICarriers</Name><Path>C:\Program Files (x86)\AICarriers\aicarriers.exe</Path>
There are two tags (<Name> and <Path>) on the same line, which is different from the file you sent me a couple of days ago, that didn't had ANY newline, on any line.
Are you trying to manually modify the XML in all possibly foul ways, in order to trick our installer on purpose ????
HOWEVER, I've just check the current JFK installer I have, which is 138.645.024 bytes long and dated Oct. 20th, which is exactly the same version is online now, and it DOES'T do what you are saying, by running it over your EXE.ORG_XML renamed to EXE.XML first, results in a perfectly good XML, with AICarriers in, no "overwriting" and it even fixed the missing newline between <Name> and <Path> you put in there...
-
Are you trying to manually modify the XML in all possibly foul ways, in order to trick our installer on purpose ????
NO; What I did after installing the KJFK/XPOI, I manually had to input the AICarriers text and it was at that time that I used the same format you had just for my ability to read it and ensure that the module would load in FSX for me. Now, when I went to reinstall; It was *MY* modified file and so didn't work. I wasn't trying to trick your installer; but at least you know now that If a user had done this, as I did, he/she too would have *LOST* the AICarriers statements; I'm glad I backed it up. ;)
HOWEVER, I've just check the current JFK installer I have, which is 138.645.024 bytes long and dated Oct. 20th, which is exactly the same version is online now, and it DOES'T do what you are saying, by running it over your EXE.ORG_XML renamed to EXE.XML first, results in a perfectly good XML, with AICarriers in, no "overwriting" and it even fixed the missing newline between <Name> and <Path> you put in there...
Grazie!
I guess I'll try it again; You will also have to do this to XPOI's installer because it does the same thing too. ;)
-
but at least you know now that If a user had done this, as I did, he/she too would have *LOST* the AICarriers statements;
No, because, as I've said, the installer is able to deal even with that gotcha in the file.
I guess I'll try it again; You will also have to do this to XPOI's installer because it does the same thing too.
It does not. Tried with that one as well, and tried even by re-downloading from the website, just to be sure the correct version was up.
-
Virtuali,
OK; Great - I want these Installers to be the one's I use and back up to DVD for future re-installs ...
I might have to do that if my FSX is unrecoverable from these nasty CTD's. :(
Thanks a bunch. :D
-
but at least you know now that If a user had done this, as I did, he/she too would have *LOST* the AICarriers statements;
No, because, as I've said, the installer is able to deal even with that gotcha in the file.
I guess I'll try it again; You will also have to do this to XPOI's installer because it does the same thing too.
It does not. Tried with that one as well, and tried even by re-downloading from the website, just to be sure the correct version was up.
Virtuali,
I hate to use your own words but ''It doesn't happen here!'' :-\
1. I tried re-downloading/re-installing KJFK/XPOI 5 times just to make sure that I didn't miss the correct upload by you and NONE of the installers are able to resolve the above problem HERE.
2. Got the water cooling issue worked out but still CTD form KJFK ONLY on all 3 machines -
1. LABTOP: VISTA 32 with FSX Acceleration (NOTHING ELSE) + KJFK.
2. MINI-TOWER: VISTA 64 with FSX SP2 (NOTHING ELSE) + KJFK.
3. FLIGHT SYSTEM: VISTA 64 with FSX Acceleration (EVERYTHING ELSE) + KJFK. (ONLY SYSTEM with WATER COOLING)
ALL CTD with KJFK installed on "Exit the Sim from flight" and CTD at random (some in Flt. some just parked on the ground, with me doing nothing), HERE.
I guess nothing can be done? ??? ::)
-
1. I tried re-downloading/re-installing KJFK/XPOI 5 times just to make sure that I didn't miss the correct upload by you and NONE of the installers are able to resolve the above problem HERE.
I'm sorry, but I've already tested and confirmed it twice: with the files YOU sent, both the first ones and the more recent ones, the EXE.XML is correctly handeld, both by JFK and by XPOI. You must have the wrong installer. Or you must have ANOTHER "customly corrupted" XML file (like the other time), that you haven't sent me yet.
ALL CTD with KJFK installed on "Exit the Sim from flight" and CTD at random (some in Flt. some just parked on the ground, with me doing nothing), HERE.
I'm sorry, but I don't want to repeat myself again: as long as you are the only one reporting it (and you are) and as long I can't reproduce it, there's nothing to do, and it's probably nothing you related to the scenery. If it WAS, we should have at least some other reports.
-
Virtuali,
The CTD's are caused by ADDON MANAGER v2.5.1.1
1. It is somehow triggered when KJFK scenery is active in FSX's scenery library.
2. It, also, causes CTD's when I made purchases for FlorenceX and, today, when I purchased Cloud9's XCity Rome - and used the SAVE the .reg file(s) for each of these products.
INSTALLERS:
Also, redownloaded the KJFK/XPOI/ADM today and same results with the EXE/DLL.xml file(s). They are exactly the same files I gave/posted for you. Your installer defends by erasing the original file and just replacing it with its own.
Yes, it happens here, and I'm the only reporting it; That is all!
-
The CTD's are caused by ADDON MANAGER v2.5.1.1
They aren't. If they were, you would have seen a message coming from Windows about "bglmanx has a problem...", etc.
1. It is somehow triggered when KJFK scenery is active in FSX's scenery library.
That's even more proof that they are NOT created by the Addon Manager becuase that one is always running, not just when a scenery is active on the library.
2. It, also, causes CTD's when I made purchases for FlorenceX and, today, when I purchased Cloud9's XCity Rome - and used the SAVE the .reg file(s) for each of these products.
Nobody reported this as well (look at Cloud9 forum for proof). But please, don't start a support thread about Cloud9 here.
BUT, since you have a problem with saving and (see below about the EXE.XML) PERHAPS you have permissions messed up on your drive.
Also, redownloaded the KJFK/XPOI/ADM today and same results with the EXE/DLL.xml file(s). They are exactly the same files I gave/posted for you
Works perfectly with the files you sent me.
Your installer defends by erasing the original file and just replacing it with its own.
It doesn't. Checked many times already. The new installer doesn't even try to fix the files by itself anymore. To fix the errors created by other installers, it now uses an official W3C validator, which is 100% sure to be working.
I'm the only reporting it
Yes, you are.
-
Virtuali,
I see with these continual response from you, that there is no solution in the making ... Am I to believe that you are stating that this is all in my head? Or all in 3 of my computers *heads*?
Its NOT a permissions issue and UAC is disabled; I check that all before I ever came to you ... It is ADM v2.5.1.1 and I do get Windows errors reporting that the cause was bglmanx.dll after the CTD is reported and between an FSX restart being done.
When I remove KJFK from the library and use ADM v2.5.0.5 NO CTD's Ofcourse, I can't use ParkMe, XPOI, etc. then. :P :'(
Do you want me to post more screen shot of this ???
-
Am I to believe that you are stating that this is all in my head? Or all in 3 of my computers *heads*?
No, I believe that you are experiencing problems. What I don't believe, is they are CAUSED by the scenery or the Addon Manager. If they were, we should have hear other similar reports.
Its NOT a permissions issue and UAC is disabled
Sorry, but UAC doesn't have anything to do with file system permissions. UAC do not auto-magically grant write access to anything, the permissions set in the file system are always in place and, if they are messed up (it might happen when reinstalling Windows over an old installation without reformatting), the file UUID might be wrong and programs can have issues when writing files.
I'm just guessing, but I need to guess using YOUR description of the problem. Since YOU said the program crashes when saving the .REG file (which of course nobody ever reported it so far) and you say the EXE.XML is still written incorrectly, which of course doesn't happen here and also nobody else reported it so far, I can only guess your system have a problem when writing files. This is the only guess I can make based on YOUR report, and is compatible with the fact that it doesn't happen to anyone else and I can't reproduce it.
It is ADM v2.5.1.1 and I do get Windows errors reporting that the cause was bglmanx.dll after the CTD is reported and between an FSX restart being done.
Alright, then something in your system (that, apparently, nobody else is using) is MAKING the current version to crash.
When I remove KJFK from the library and use ADM v2.5.0.5 NO CTD's
Now you are saying something different from the last time. How are you supposed to get any help, if you keep changing your description of the problem ? You previously said that JUST removing JFK from the library, fixed the crashes. Now you are saying that you need to remove JFK from the library AND use the older version as well which, of course, is an ENTIRELY different thing, as far as possible solutions are involved.
However, as I've said many times already, as long as I don't get ANY other similar reports, I must assume it's "something" in your system and in your system only, that is not compatible with our software.
Do you want me to post more screen shot of this ???
You posted enough screenshots, there's no need to post any. As long as I can't reproduce the problem and nobody else is reporting, there isn't the slightest chance to ever START thinking how to possibly fix it.
-
Virtuali,
These 3 systems have been setup by either the manufacturor or the one, myself, and NONE of them are reinstalls of the OS or recovered point set backs. Please don't say "NO one" because this entire forum is full of issues with ADM; but the user may NOT have the exact issue I'm having, that might be true. But, How is it, that I am able to reproduce the exact same issue with ONLY ADM 2.5.1.1 on 3 different machines with no addons on two of them? Their (computers) all defaulted to Windows' default security parameters; no tampering on my part, only verification. Being frustrated with this, I decided recently, to test my theory with an earlier version of ADM. I am able to save the .reg files from my purchases and do other things without incident in the older version of ADM; With version 2.5.1.1, I get CTD's - Is that clear?
How many more people need to report this before you consider this a problem and try to fix it?
-
Please don't say "NO one" because this entire forum is full of issues with ADM; but the user may NOT have the exact issue I'm having, that might be true.
I AM saying "no one" because, the ONLY problems people usually have with the Addon Manager are:
1) QUIT to desktop (NOT CRASH) immediately at start, because they used to mix-match the .DAT between scenery and the Addon Manager. This shouldn't happen anymore, since the new installer always gets the most updated files from the internet at start. It might still caused issues, if one is *very* unlucky, and the internet connection drops exactly in the *middle* of the update, and some of the files would be the older version and some the newest. But it's very unlikely, and it's always solved by launching the installer again.
2) CRASH, immediately at start, with a bglmanx.dll error message, because sometimes FSX has a problem executing modules just trusted. This is usually solved by simply launching FSX again, sometimes after a reboot.
Problem 1) is now solved by the new online installer, problem 2) is more due to FSX (it's FSX that "decides" a module has problems, but how come that if you relaunch it, it works ? The "problem" module hasn't changed, obviously...), because it only happens when a newly trusted module is launched.
This covers 100% of the user reports about the Addon Manager. Your kind of crash is the only exception.
NOBODY reported a crash after a while just sitting on the apron doing nothing, like you are.
NOBODY reported a problem writing the EXE.XML, unless they had the file already corrupted by another product, but the *current* installer is able to fix all kind of corruptions, and nobody ever reported any kind XML problems since the current installer is online, except you.
NOBODY ever reported a crash writing the .REG file, in any version of the Addon Manager, including the FS9 ones.
I am able to save the .reg files from my purchases and do other things without incident in the older version of ADM; With version 2.5.1.1, I get CTD's - Is that clear?
It's clear, but still doens't make any sense. The routine that save the .REG file hasn't been touched in ages and it's always the same since the FS9 version of the Addon Manager. And of course, NOBODY reported THIS problem.
How many more people need to report this before you consider this a problem and try to fix it?
At least another one. But there's none right now. And, as I've said, many times already, at least more than 1 report is needed to be at least be worried. But to be FIXED, I need to be able to REPRODUCE IT.
-
NOBODY reported a crash after a while just sitting on the apron doing nothing, like you are.
You already fixed this with the last AFCAD update with all the PARKING 0 spots correctly labeled by type. So, I did everyone a favor, including you, by pointing that out and you fixed that CTD.
NOBODY reported a problem writing the EXE.XML, unless they had the file already corrupted by another product, but the *current* installer is able to fix all kind of corruptions, and nobody ever reported any kind XML problems since the current installer is online, except you.
Yes, and I only noticed it when I tried to use the AICarriers and found the listing missing from the ADDON's menu in FSX. Perhaps no one else noticed it? Or perhaps they just re-installed those statements as a work around and didn't bother you with it. Eitherway, all the installers I downloaded and installed, including the one yesterday, DID NOT leave those statements (or the contents of the file) alone but totally erased it in place of the installer one. That is STILL the case HERE.
NOBODY ever reported a crash writing the .REG file, in any version of the Addon Manager, including the FS9 ones. ... It's clear, but still doens't make any sense. The routine that save the .REG file hasn't been touched in ages and it's always the same since the FS9 version of the Addon Manager. And of course, NOBODY reported THIS problem.
I never had that happen until recently when I purchased FlorenceX and again, yesterday, when I purchased XCity Rome. The files were created during the purchase. But, after I re-opened the ADM v2.5.1.1 to "BACKUP" the ".reg" files for each of these products, I got CTD's with the bglmanx.dll errors. YES, I'm reporting it having tested it on 3 different machines.
How many more people need to report this before you consider this a problem and try to fix it?
At least another one. But there's none right now. And, as I've said, many times already, at least more than 1 report is needed to be at least be worried. But to be FIXED, I need to be able to REPRODUCE IT.
I can reproduce it; and I have on 3 different machines. Perhaps my all my screenshots and repeated posts have NOT convinced you of that? You need to debug it a little more; I'll pray you do by the time your next sceneries are released; continuing to ask you now is just a waste of my time; Correct?
-
You already fixed this with the last AFCAD update with all the PARKING 0 spots correctly labeled by type. So, I did everyone a favor, including you, by pointing that out and you fixed that CTD.
And this, of course, simply proves my point that the problem wasn't caused by the Addon Manager. And, simply proves my point that, if a problem is real, we fix it immediately.
Eitherway, all the installers I downloaded and installed, including the one yesterday, DID NOT leave those statements (or the contents of the file) alone but totally erased it in place of the installer one. That is STILL the case HERE.
You can write it in bold, red, all caps, but it doesn't change the fact that this is not what's happening. Tried with the files you sent me.
But, after I re-opened the ADM v2.5.1.1 to "BACKUP" the ".reg" files for each of these products, I got CTD's with the bglmanx.dll errors. YES, I'm reporting it having tested it on 3 different machines.
Since this feature is very important, considering that making a backup of the registry keys should be the first thing an user does after purchasing, you can't of course say the (like in the case of AiCarriers) "nobody noticed it". Considering that, according to your report, it happens with every scenery, including Aerosoft's and Cloud9's, we are speaking about MANY THOUSANDS of users that should have experienced a crash, and of course there's no trace of them, not here, not on Cloud9 or Aerosoft forums.
I can reproduce it and I have on 3 different machines.
Unfortunately, it's not you that are supposed to fix it. There's no way I can fix it, if I'm not able to reproduce it here.
Perhaps my all my screenshots and repeated posts have NOT convinced you of that?
You are still getting it all wrong: I DO believe you have issue, I simply said they do not happen here, and on anyone else's machine.
You need to debug it a little more
You probably don't know exactly what "debug" means. Debug means I must able to REPRODUCE the problem, in order to, as the terms says, trap the problem in the debugger, and see were it happens.
Failing to do that, I should at least be able to hear SEVERAL different users reports, in order to at least recognize a PATTERN, which is the only way to have the slightest hope to be able to fix a problem, even without being able to reproduce it.
Both cases are not possible, since I'm not able to reproduce it here, and there aren't any users reports except yours. Yours doesn't exhibit any special pattern, because you say it happens with a clean Vista installation with everything default. I'm sorry, but if this was the case, it SHOULD be reproducible and it SHOULD have happened to someone else.
-
Virtuali,
I understand your point about "reproducing it;" I have a Masters in Computer Science and Engineering so, I'm pretty sure that I know what "DEBUG"ing is. Or, at least I fooled all my professors that I did. ;)
All I can do is post the problems that I see and the possibility of "what they may be" based on observations. I do not have .net applications or any other developers tools on these systems and, ofcourse, your source code to give you a definitive answer; so I might be wrong about many things; that is why I'm coming to you; the developers - You would/should know more.
I was getting a series of CTD's with the KJFK package; Most of them are now gone thanks to all your updates/settings/suggestions. I even found a couple of issues with one of my 8800 video cards which has now been replaced. So, you have been helpful; that is NOT in disagreement. But the job is NOT finished. All I can do now is hope and pray that someone will have the exact *same* issue and post it on your site so that you can find the time to fix it.
Grazie!