FSDreamTeam forum
Products Support => Honolulu FSX/P3D => Topic started by: anappy on February 08, 2010, 01:40:42 am
-
Everytime when I fly a long flight and get close to HNL it crashes to my desktop. This is very frustrating when I have to finish my flight from Kahului
-
Does it happen on a short flight to HNL? Does it happen on a long flight to any where else? Thing is you might be out of avalible memory.
-
It only happens on long flight to HNL, when departing its fine and on short flights its ok
-
Same thing, it seems to happen on long flights, but when I do a short flight it works. Its like theres a time limit on the purchased one.
-
Its like theres a time limit on the purchased one.
There's obviously NOT such thing as a "time limit on the purchased one". Why, if something is wrong, someone always things it's related to trial and/or activation ?
The issue doesn't have anything to do with PHNL, other that the fact it's a fairly large scenery.
One possible cause is the airplane you are using might take too much memory ( there are "unoptimized monsters" out there, that take 1GB of RAM *just* for the airplane ) or might even leaking memory so, as soon as you enter in the PHNL area, were a large amount of data is being requested, if you were already on the borderline of exhausting memory, loading a large scenery will crash the sim.
You should try monitoring RAM usage with FSX running, and check if there's some kind of slow decrease over time, which might lead to a memory leak, and if there's a spike in usage, and by how much, when PHNL enters in range, which is exactly 10 nm from the center of the airport.
-
Its not the airplane, it happens with multiple different aircraft that I have had it happen with, the qw757 and the posky 767 and I believe the cls a330. The amt of ram shouldnt matter if the ctd comes some 80 miles out of hnl.
It has to be something scenery releated, I never had this issue before with the default scenery, as far as traffic goes, I have troubleshooted all of my hawaii releated flightplans, and come up with nothing, I use woai, and the rest of the fps that I have are all manually installed, I use the TSS audio environment for the ai aircraft.
I know there is no such thing as a timer for the purchased version I was just saying that as an observation because it happens to me when my flights are 6+hrs long.
I dont know what to say, I mean just because you cant recreate the problem on your end does not explain the problems that me and the 3 or 4 other people are having with this scenery.
Im thinking it has to be something dealing with how the scenery is coded and how that coding is translated by fsx when loading details from the afcad or scenery itself.
-
Its not the airplane, it happens with multiple different aircraft that I have had it happen with, the qw757 and the posky 767 and I believe the cls a330.
That doesn't automatically means it's the scenery.
The amt of ram shouldnt matter if the ctd comes some 80 miles out of hnl.
PHNL scenery range it's 10 nm, if the crash happens outside that range, it's not PHNL.
It has to be something scenery releated
No, it isn't, otherwise it would happen on every system that has PHNL installed.
I never had this issue before with the default scenery, as far as traffic goes, I have troubleshooted all of my hawaii releated flightplans, and come up with nothing, I use woai, and the rest of the fps that I have are all manually installed, I use the TSS audio environment for the ai aircraft.
That doesn't tell anything. The fact that doesn't happen with the default PHNL, doesn't automatically means there's something wrong with PHNL. As I've said already, if you are just on the *borderline* of exhausting RAM, whenever you load a large scenery, it might crash the sim, without the scenery having anything wrong.
I know there is no such thing as a timer for the purchased version I was just saying that as an observation because it happens to me when my flights are 6+hrs long.
Which clearly proves it can't be the scenery because, your memory exaustion didn't happen at PHNL (unless you were standing at PHNL for 6 hours), it happened along the way, when there wasn't any PHNL involved.
I dont know what to say, I mean just because you cant recreate the problem on your end does not explain the problems that me and the 3 or 4 other people are having with this scenery.
You said yourself that you have an easily replicable crash, when selecting the 4R approach that, as far as I understood, happened immediately, not after a long flight. This doesn't happen here.
And there aren't "3 or 4" people. It's just you and another user, that reports the runway not being visible in the GPS. Which is why I posted a screenshot, which clearly shows this doesn't happen.
So, the issue is not finding what's wrong with PHNL, but what *else* you and the other user have installed, that creates both the crashes and the problem with the GPS, which are probably related.
-
when I fly there I use the LVD 763 and it is about 10-25 nm out. What should I do?
-
when I fly there I use the LVD 763 and it is about 10-25 nm out. What should I do?
Try with a default airplane first. The scenery range it's exactly 10 nm so, ANY crash that happens before, doesn't have anything to do with the scenery, because it hasn't been loaded yet.
In this other thread:
http://www.fsdreamteam.com/forum/index.php?topic=2762.msg23057#msg23057
An user found the crash was caused by another AFCAD.
-
How much more RAM should i free up? I use lvd 763 for my VA when I fly here. Yes it happens 10 nm out. Any other thoughs, i dont want to waste a day flying and then ALMOST making it to HNL.
-
I'll ask again: does it happen with another airplane, possibly a default one ?
-
I'll ask again: does it happen with another airplane, possibly a default one ?
No. However I can't fly default aircraft for my VA. Should I just try to clear as many programs as possible off my computer?
-
A way to reduce the RAM allocation, is to close all the running processes that are not required when flying, like antivirus, firewall, disk defraggers. Anything which is not related to FSX.
In FSX, you can lower the RAM usage by lowering the "Level of Detail" slider to Medium or Small.
And, of course, the best solution would be just adding more RAM, and using a 64 bit OS. Under a 32 bit OS, especially with a video card with lots of memory, you are going to have RAM problems.
-
A way to reduce the RAM allocation, is to close all the running processes that are not required when flying, like antivirus, firewall, disk defraggers. Anything which is not related to FSX.
In FSX, you can lower the RAM usage by lowering the "Level of Detail" slider to Medium or Small.
And, of course, the best solution would be just adding more RAM, and using a 64 bit OS. Under a 32 bit OS, especially with a video card with lots of memory, you are going to have RAM problems.
Ok thanks this helps alot
-
Hi,
Since I did a complete reinstall of PHNL with the full v1.3 installer, I am experiencing a CDT after a minute or two of idle activity. This is with both the PMDG 748i and the default FSX Baron, just sitting at gate 29. When I performed the complete reinstall, I had removed all traces of the original version after using the add-remove process. I have searched my entire FSX directory structure for any filenames that contain the letters PHNL. Although I don't see any duplicate AFCADs I do see (what I think are) two exclusion files within the ..\FSDT\PHNL\Scenery folder. Could this be causing my CTD? This is using FSXsp2 on WinXP_x64. Files and dates are as follows:
..\FSDT\PHNL\Scenery\
AP_PHNL.BGL (dated 2/19/2010)
AP_PHNL_CVX.BGL (dated 2/19/2010)
cvx_PHNL.BGL (dated 9/5/2010)
Is the second cvx (exclusion) file supposed be there (active)?
-
Your files are all fine, both cvx are supposed to be there, because they do different things, and not just exclusion.
A repeatable 2 minutes crash, should have been noticed by everybody (and surely by us) so, I really doubt it's the scenery. However, you might try to have a look at the Windows Event Viewer (It's under Control Panel->System->Admins Tools), if there's some indication about *which* FSX module has crashed, this might help understanding the problem.
-
Thank you much Umberto. There was nothing in the event logs over the sequences of crashes. I did however, re-download and execute the standalone version of the FSDT control manager thingy (I forget the name at the moment). Several short tests with the Baron idling at gate 29 again seemed uneventful. So, I am now 4 hours into my original PMDG 748i flight from KLAX to PHNL with an hour left to go (currently 116nm from ToD). This is the flight that originally crashed as neared the bottom of descent yeseterday into the PHNL area.
Will advise one way or the other, shortly. :-\
-
Damn, another 4-1/2 hr flight resulting in a CTD at about 20nm from PHNL. >:(
What ever it is, it is sudden and without warning - boom! Gone! Staring at the desktop 1 second later...
-
Damn, another 4-1/2 hr flight resulting in a CTD at about 20nm from PHNL. >:(
What ever it is, it is sudden and without warning - boom! Gone! Staring at the desktop 1 second later...
thats whay happens to me in the LVD 763. I think this is becoming a larger problem
-
I would like to remind that, PHNL scenery range it's 8 nm. Before that area, we simply don't do anything.
The only thing related to PHNL in some way, that loads before that range, are the AFCAD with the approach procedures so, an error in the approaches, might cause a crash.
Note that, with PHNL 1.0.2 and up, the supplied AFCAD does not contain ANY approaches: they are coming from the MS default AFCAD.
And, sorry to repeat it but, when you are trying to FIND if the crash is related to the scenery, you need to use a default airplane.
If the crash happens only after a long flight, it means the possible memory leak is happening WAY before approaching the airport area, the fact that the actual *crash* happens there, might be simply because, if the airplane caused a memory exhaustion during the flight, what caused the crash was just the act of loading a new scenery, and that might have been any scenery but, of course, a with a large airport scenery, it's more probable, without the scenery having anything to do, other than just be large enough. But the problem was the memory was already dangerously low. If the problem was the scenery, it should crash regardless of how much memory is available.
-
ok i just wanted to add my two cents here in that i think it could be alittle more than just a memory leak and that there may be a fault w/ the scenery itself because in my testing when i try to load directly at PHNL sometimes it crashes and yet i can do the same thing at KJFK and KLAS, even fly into those airports without any CTD's.
I'll be upgrading to W7 in about a week and i'll be trying out this again to see if this improves anyhting.
-
I just flew from LAX to Honolulu and I made it. Try putting the detail radius to small
-
I just completed KDEN to PHNL in the 748i using both MSE-Colorado & FSDT PHNL with no problems. I also have all of FSDT's stuff as well as numerous 3rd party airports. To me this sounds like an OOM error which occurs in both FSX & Fs9 when using 3rd party add-ons for a prolonged amount of time on a 32 bit OS. The problem is well documented for both sims in the Avsim & FlightSim forums.
The short of it is windows virtual memory overloads and FS CTD's with no error message. The solution is either
1. ad the 3GB switch and make Fs9 or FSX large memory aware.
2. get a 64 bit OS.
I used to get CTD's like this all the time especially with PMDG's 744 and add-on airports. Frustrating as all &$#* especially on short finals Grrrrrrrr. Since moving to Vista64 and now Win7 64 the problem is all but a memory (ha!). I also used the 3GB switch for a short time and it really helped ;)
John
-
there may be a fault w/ the scenery itself because in my testing when i try to load directly at PHNL sometimes it crashes
I'm sorry but, unless the crash is repeatable on every system, you just can't say "it's the scenery". If it was, it would happen on every system, and we would had the forum flooded with messages (not just 1-2 random reports), and of course we would have fixed already, since any crash that is repeatable, is also fixable.
So, it's obvious that, in your specific case, it's something else that is crashing. When you load PHNL, it's not just our airport that is loaded, but of course it's the base scenery, meshes, landclasses, textures, default navaids, the airplane you are using, the weather, the AI airplanes with their textures, another scenery for that area you might have, etc.
If any of the above elements has a problem, you can get crashes on load, without being related at all to the PHNL airport scenery, and of course, fact you don't see this at other FSDT airports, doesn't mean anything, because they are positioned in an entirely different area.
-
there may be a fault w/ the scenery itself because in my testing when i try to load directly at PHNL sometimes it crashes
I'm sorry but, unless the crash is repeatable on every system, you just can't say "it's the scenery". If it was, it would happen on every system, and we would had the forum flooded with messages (not just 1-2 random reports), and of course we would have fixed already, since any crash that is repeatable, is also fixable.
So, it's obvious that, in your specific case, it's something else that is crashing. When you load PHNL, it's not just our airport that is loaded, but of course it's the base scenery, meshes, landclasses, textures, default navaids, the airplane you are using, the weather, the AI airplanes with their textures, another scenery for that area you might have, etc.
If any of the above elements has a problem, you can get crashes on load, without being related at all to the PHNL airport scenery, and of course, fact you don't see this at other FSDT airports, doesn't mean anything, because they are positioned in an entirely different area.
ok fair enough like i said i'll try it again under a new OS and see what happens then. i'll report back
-
and we all know that FSX uses alot of resources tto make its water
-
ok i'm just following up this issue that i've been experiencing at PHNL, so since last i posted i've upgraded to W7Ultimate, and everything has been running smoothly, even with PHNL until i re-installed UTII, for some odd reason when i load the scenery it CTD's and i get "a fatal error has occured" added to which after FSX shuts down i get a pop that says "this feature requies that smart assembly is available on this computer" also it states that "couatl" isn't functioning or something like that and i should reboot the PC.
I'm hoping that what i have underscored would give the devs some insight to what is going on here.
Regards
-
after FSX shuts down i get a pop that says "this feature requies that smart assembly is available on this computer"
This the final and definitive proof the issue doesn't have anything to do with any of our products, because this is a message related to a problem with the .NET framework installation so, the application that has crashed it's a .NET app.
Since neither FSX itself, nor any of our products, (not even the installers), requires, use or are affected by .NET, it means what is crashing it's another 3rd party addon that use .NET. And there are many of them around.
-
after FSX shuts down i get a pop that says "this feature requies that smart assembly is available on this computer"
This the final and definitive proof the issue doesn't have anything to do with any of our products, because this is a message related to a problem with the .NET framework installation so, the application that has crashed it's a .NET app.
Since neither FSX itself, nor any of our products, (not even the installers), requires, use or are affected by .NET, it means what is crashing it's another 3rd party addon that use .NET. And there are many of them around.
Then i take it the problem has to be UT2 because to test i only have these things installed although i just don't understand why it only happens w/ the PHNL scenery, if I uninstall the scenery everything runs fine.
well i'll link this post across at UT2 and see if anyone has a solution.
OK can you tell me what these two files are :AP_PHNL and AP_PHNL_CVX because i was told to make sure that there weren't any double afcads.
-
Then i take it the problem has to be UT2 because to test i only have these things installed although i just don't understand why it only happens w/ the PHNL scenery, if I uninstall the scenery everything runs fine.
As I've said, there's nothing in any of our products that is remotely linked to .NET so, if .NET is crashing, you can be sure it's not the scenery.
Fact that happens only if PHNL is installed, might due to a problem with an AI model that doesn't appear with the default airport, because of the AFCAD differences.
You might check this, by doing the opposite test: instead of uninstalling PHNL, try to uninstall UT2 and leave PHNL on.
OK can you tell me what these two files are :AP_PHNL and AP_PHNL_CVX because i was told to make sure that there weren't any double afcads.
You can be sure that everything that inside our folder, is supposed to be there. Those files are correct, one is the main AFCAD cad, the other contains some vector data for the highway traffic and the terrain exclusion zones.
If you want to search for duplicate AFCADs, you need to look in other folders. Use the free FSX airport scanner to do this.
-
I think that UT2 has released an update to address the issue of FSX crashing which is what i think i've been experiencing, before installing this hot fix i turned of "general avaition traffic" and the CTD's stopped but now i've applied the patch that reads "Adds Runtime to help stop FSX crashes related to AI aircraft system operations" i've enabled it again and so far so good at PHNL.
I'll keep testing to see if this was infact my issue and hope maybe it helps others w/ their CTD's if they are in fact using UT2.
-
My CTD wasn't UT2 related, but it was probably traffic related. I normally only use WoAI and AIG flightplans (converted to FSX format) which are fully tested and ready for use. While waiting for FSDT to 'finally' (sorry, couldn't resist) release PHNL, I had installed a custom Aloha Cargo traffic bgl which was modified prior to using the MRAI installer. I almost never hand-jam my own traffic text files but rely on those previously tested. I then recalled this single file which may have been corrupted by the MRAI flightplan installer becuase of my manual modification to the text files.
What kept nagging me is the fact that this CTD would also happen with the simple default Baron sitting on the tarmac, let alone my PMDG aircraft, and it would only happen near the Hawain islands. Then I removed this Aloha cargo traffic file yesterday and let it the sim sit there for about 5 hours without a CTD, using the PMDG 748i. I am now ready to try my PMDG 748i from LAX to HNL again - although I will probably have a few stiff drinks enroute, just in case ;)
-
Then I removed this Aloha cargo traffic file yesterday and let it the sim sit there for about 5 hours without a CTD, using the PMDG 748i.
Very good, I think this was the best possible test you could do. We can safely conclude the scenery is rock solid...
-
This is for anyone still having problems w/ the airport crashing your comp on approach set the level of detail radius to small. It works
-
Well, I hate to report that I've spent another few days continuing to troubleshoot the dang CTD using a saved scenario with the default Baron. I thought this was traffic related but after two more CTD's last weekend using the PMDG MD-11, I started looking at the issue, again. I went through all my WoAI and AIG traffic and absolutely can not find a specific file (or two) which reliably contribuites to the scenario. I can usually start at PHNL with the baron and it'll sit there all day. But (read on):
Basically, with the Baron, if start the sim, and then "Go To Airport" from the FSX menu and enter PHNL, it will CTD towards the end of the scenery loading bar graph. This occurs if I "jump" to PHNL from ImagineSim's KATL, Flytampa's KBOS, or FSDT's KLAS, and so on. "Go to" PHNL and boom, CTD.
This is driving me nuts! I don't have ANY CTD occurences ever with any other high-end scenery including all the FSDT FSX airports. None, noda, silch! It is only when PHNL is involved.
I have scanned my entire FSXsp2 dedicated raid-0 Velociraptor drive array and no other PHNL named files are found outside the FSDT directory so I am absolutely sure there is no AFCAD conflict. I have re-installed the standalone FSDT manager and the bglmanx.dll is version 2.7.0.21. I am using most of the popluar FSX packages which may or may not contribute to the CTD, including FSDT PHNL (from the lastest Full Installer), F1 UTX & GEX (all the latest updates), FSGenesis, (latest versions). FSUIPC 4.6 (reg'd), WoAI traffic, and AIG traffic.
I am running a tweaked WinXP_x64 rig with 6GB of DDR3-1600 RAM and a GTX285 with 1GB of VRAM. All are finely tuned to the NickN tuning threads on F1's webite. This absolutely should never happen with the default Baron. Something is wrong somewhere!
-
I am using most of the popluar FSX packages which may or may not contribute to the CTD, including FSDT PHNL (from the lastest Full Installer), F1 UTX & GEX (all the latest updates), FSGenesis, (latest versions). FSUIPC 4.6 (reg'd), WoAI traffic, and AIG traffic.
The obvious diagnostic process, in this case, would be as usual: disabling all your addons, one by one, and see if the crash is solved.
A very important concept should be clear: the fact that a crash happens at a specific airport, doesn't necessarily mean the *airport* it's a problem. With so many addons, you have a LOT of stuff at PHNL, that doesn't come with our scenery so, until you don't do what has been suggested above, you just can't be sure where the problem is.
Disabling doesn't always mean uninstalling: sometimes it's enough to just disable the scenery area in the Scenery Library. And, in case of products requiring Simconnect addon modules, it's enough to simply put the <Disabled>True</Disabled> command to their relevant module in the DLL.XML or EXE.XML files.
-
Speaking of disabling add-ons for troubleshooting purposes, why is it when I disable FSDT-PHNL (unchecked in the FSX scernery library manager) the scenery still seems to be fully active? I can still see all the FSDT buildings and so on, mixed in with the default scenery.
FSX should have no knowledge of the FSDT PHNL bgl's while inactive in the library, should it?
[Edit - a little while later]
- OK, I uninstalled FSDT PHNL (now back to default FSX PHNL) / "Go to Airport" menu from PHNL to KATL and back to PHNL = Good / No CTD
- Installed AIG PHNL Advanced Scenery/AFCAD for default scenery / "Go to Airport" menu from PHNL to KATL and back to PHNL = Good / No CTD
- Uninstalled AIG scenery and download FSDT PHNL v1.0.3 full installer and re-installed a fresh copy (no re-activation required)
- FSDT PHNL / "Go to Airport" menu from PHNL to KATL and back to PHNL = Bad / CTD when alomst finished reloading PHNL a second time.
Same scenery addons, traffic, date, time, etc, except the airport itself. Can you at least try "jumping" from one airport and back to PHNL, to see if you get any issues?
-
Speaking of disabling add-ons for troubleshooting purposes, why is it when I disable FSDT-PHNL (unchecked in the FSX scernery library manager) the scenery still seems to be fully active? I can still see all the FSDT buildings and so on, mixed in with the default scenery.
The buildings are not contained in the BGL that are referenced by the Scenery Library area, but are created by the Addon Manager. If you just uncheck the scenery area, buildings will stay there, until the next FSX restart.
Same scenery addons, traffic, date, time, etc, except the airport itself. Can you at least try "jumping" from one airport and back to PHNL, to see if you get any issues?
Sorry, but you are again jumping to the wrong conclusion. The fact that you have installed PHNL, which comes with a different AFCAD, due two different parking assignments, might trigger the appearance of different AI models comparing to the other scenery.
If THIS AI model has a problem, for example a corrupted/missing texture, you might get the wrong impression the problem is the scenery, when it doesn't have anything to do with it, other than attracting a faulty AI.
Can you at least try "jumping" from one airport and back to PHNL, to see if you get any issues?
If I'm saying all of this, it's because these tests have been made many times already. And, you are keep referring to Imaginesim KATL. Does the crash happens when jumping back/forth from EVERY other airport, or ONLY with Imaginesim KATL ?
In any case, you are saying to have made the test only by uninstalling AIG scenery. I've said you need to try to disable (which, as I've said, doesn't always mean uninstalling) ALL YOUR OTHER ADDONS. Have you done this ?
-
Well, after almost a month of trouble-shooting, I think I finally figured out what is wrong with arivals and CTD's into FSDT PHNL. It wasn't just PHNL either. I would also have periodic problems with KJFK and KLAS. It wasn't a particular bad traffic bgl, texture, or scenery file. I did have a saved repeatable scenerio using the PMDG 748i, starting about 30nm before the ToD.
I finally figured out that if I disable all my traffic files, I would have no problem. Easy enough - but, when adding traffic files back on, at some undetermined point, enough traffic would cause the CTD on the next execution of the saved scenario, anwhere from 22nm to 7 or 8nm towards the CKH VOR (never really in the exact same place).
What I did was disabled all the "Exit" entries in my AI aircraft cfg files so the FSDT gates didn't start moving as I neared the airport. Smooth as butter now on the paticular saved scenario that would always CTD, with some amount of AI enabled.
Is it possible the CTD is cuased by the park-me (jetways) moving or being overburdened within the FSDT engnine with lots of AI? I know you're not using default jetways, so I assume it's a custom thing within the coutl engnine, whether docking with AI or the user's plane?
-
Is it possible the CTD is cuased by the park-me (jetways) moving or being overburdened within the FSDT engnine with lots of AI? I know you're not using default jetways, so I assume it's a custom thing within the coutl engnine, whether docking with AI or the user's plane?
We are not using the Couat engine for jetways, at all. Our jetways are 100% FSX standard, handled entirely by FSX. We might be probably able to *fix* this issue, instead, if we where using our own, which is something we'll like to do at some time, since the FSX method has several glitches.
It might be interesting to check if you have crashes at default airports with many jetways, of course with your AI models with exits, so they'll use the jetways too. On default airports, you need to put the Scenery Complexity slider to "Extremely Dense", in order to see all the availble jetways.
However, removing the exits from the AI airplane might be a a good way to increase the fps, since the bones system FSX requires to handle moving jetways takes some hit on performances. It's possible that large airports with many jetways would expose some kind of bug in FSX that would crash when there are too many of them.
-
Is it possible the CTD is cuased by the park-me (jetways) moving or being overburdened within the FSDT engnine with lots of AI? I know you're not using default jetways, so I assume it's a custom thing within the coutl engnine, whether docking with AI or the user's plane?
It might be interesting to check if you have crashes at default airports with many jetways, of course with your AI models with exits, so they'll use the jetways too. On default airports, you need to put the Scenery Complexity slider to "Extremely Dense", in order to see all the availble jetways.
I haven't experienced any problems with FSX default airports, including those with modified AFCADs for increased AI parking, with lots and lots of AI, such as KLAX, KSEA, etc... This also explains why I wasn't seeing the issue with large ImagineSim airports such as KATL because their FSX add-ons dont' use default jetways (only a few gates move when set to a NAV freq.). I still think there is some kind of issue, whether by coding or CPU-loading, whereby this issue causes a CTD near FSDT airports. In theory, it should only cause a loss of FPS.
-
I still think there is some kind of issue, whether by coding or CPU-loading, whereby this issue causes a CTD near FSDT airports. In theory, it should only cause a loss of FPS.
The issue is: it's only you and another user (that seems to have solved it, and it wasn't related to our scenery either) discussing this thread. If the crash was consistent, we should have the forum flooded with hundreds of messages about this, and not just about PHNL, if it really affected all our airports that have jetways.
In any case, as I've said already, our jetways are fully handled entirely by FSX, there's nothing custom and there's no "coding" on our side. They ARE FSX default jetways. The only thing that change between the default ones, is their shape/textures, which can't obviously be the problem, because you said yourself it was fixed by removing the AI "Exits" section. Which means, the jetway displayed is exactly the same, shape and texture, just it doesn't move.
Note that, the jetway animation is something that involves shaders (vertex shaders in this case, which is different than pixel shaders used by water/land ) so, an explanation why it hasn't been reported by many users, is that might happen only with specific video drivers. Or video tweaks, perhaps even in combination with other addons that act on the shaders.
I'm sorry, but unless we get many (with "many", I would say something like at least 20-30) users reporting the problem as being repeatable, we have to assume it's nothing related to our sceneries. We have been doing animated jetways since Zurich was released in 2007, and we have them in all our sceneries, if they were the cause of a crash during approach, it should have been known by know.
-
Crash here, "couatl scripting engine has caused an error"
I also just started seeing this after ultimate traffic 2 was installed, never had a crash with your sceneries before
Using win7 64bit, nvidia latest drivers
Faulting application name: couatl.exe, version: 1.0.0.1020, time stamp: 0x4b5896c0
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x7efde000
Faulting process id: 0x920
Faulting application start time: 0x01caed995386c745
Faulting application path: C:\Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe
Faulting module path: unknown
Report Id: 82113e17-59a2-11df-9aa8-6cf049533a42
couatl.exe
1.0.0.1020
4b5896c0
unknown
0.0.0.0
00000000
c0000005
7efde000
920
01caed995386c745
C:\Games\Microsoft Flight Simulator X\fsdreamteam\couatl\couatl.exe
unknown
82113e17-59a2-11df-9aa8-6cf049533a42
-
I also just started seeing this after ultimate traffic 2 was installed, never had a crash with your sceneries before
After reading this message, I've installed UT2, CD version + 2.07 update, and there are no problems whatsoever: I even completed a full flight from KLAS to KPHX, with full traffic density, no crashes, and good fps too. Using Vista 64 and ATI 4870
-
fly around PHNL for a while, that's where I was seeing it
-
fly around PHNL for a while, that's where I was seeing it
Already did that, made a flight from PHNL to PHLI without any problems.
In any case, a crash in the Couatl.exe shouldn't be related to the area. Since you said yourself that it only happened after installing UT2, the location shouldn't matter, if there was a conflict between those two modules.
-
I think that UT2 has released an update to address the issue of FSX crashing which is what i think i've been experiencing, before installing this hot fix i turned of "general avaition traffic" and the CTD's stopped but now i've applied the patch that reads "Adds Runtime to help stop FSX crashes related to AI aircraft system operations" i've enabled it again and so far so good at PHNL.
I'll keep testing to see if this was infact my issue and hope maybe it helps others w/ their CTD's if they are in fact using UT2.
What patch is this??? Where can I get it?? Im a little behind on this thread, but Im still getting ctds when I am assigned a runway for approach into hnl.