FSDreamTeam forum
Products Support => Honolulu FSX/P3D => Topic started by: bkircher on February 07, 2010, 07:19:33 am
-
Hi there
For some strange reason I keep getting a CTD when I am assigned my approach into HNL. Everytime when the atc assigns me runway 4R ils, right after I accept it, the sim crashes. It does the same for other runways as well. At first I thought it was an AI traffic issue, so I turned off all my ai and the problem did not exsist. WHen I turned it back on the problem came back, but what leads me to believe its not ai, is the fact that I never had this problem before I had the FSDT version of the scenery, all I had before was a stock airport and a afcad by Ray Smith.
As far as my afcad goes, yes I have tweaked it, but not modified any of the approaches or anything, all I have changed is some parking assignments and added ga parking. I am thinking about loading default data from the default airport within ade as another form of troubleshooting the problem.
Its very strange. Any ideas?
-
Check again if it happens with the AFCAD we supply with the scenery.
-
It does, it always has. I have never changed anything regarding approaches in the afcad. Jst parking assignments, so I would think it wouldnt make a difference on if I changed parking assignments or not. But I did just add the stock data from with in ade for navaids and approaces. That seemed to have fixed the problem, but since I did that, I lost the star runways feature that your afcad came with. So I got it to stop crashing, but I lost one of the nice features your afcad had and came with. Any further suggestions? Here is what my afcad looks like now with the default data loaded.
-
It does, it always has.
Strange, because nobody else reported it.
I have never changed anything regarding approaches in the afcad.
There's nothing to change, because there are no approaches in our AFCAD to begin with. That's why I find odd that it would crash when selecting a runway in the ATC, which would suggest something is wrong with the approaches. But we haven't included any! The approaches are coming from the default AFCAD.
But I did just add the stock data from with in ade for navaids and approaces. That seemed to have fixed the problem, but since I did that, I lost the star runways feature that your afcad came with.
As I've said, I don't see how duplicating the default approaches in the scenery would fix a crash, that hasn't been reported by anybody else.
In any case, I've just tried doing a full IFR flight to PHNL and, no crashes whatsoever, using the 4R ILS approach so, I must assume there's something else in your system that is creating that problem.
-
I dont know what to say other than, yes me duplicating the approaches fixed the problem. Before I did this, on my flight before I got a ctd, I saved the flight then duplicated the fde, resumed the flight, and I didnt get a ctd.
-
Hi there
For some strange reason I keep getting a CTD when I am assigned my approach into HNL. Everytime when the atc assigns me runway 4R ils, right after I accept it, the sim crashes. It does the same for other runways as well. At first I thought it was an AI traffic issue, so I turned off all my ai and the problem did not exsist. WHen I turned it back on the problem came back, but what leads me to believe its not ai, is the fact that I never had this problem before I had the FSDT version of the scenery, all I had before was a stock airport and a afcad by Ray Smith.
As far as my afcad goes, yes I have tweaked it, but not modified any of the approaches or anything, all I have changed is some parking assignments and added ga parking. I am thinking about loading default data from the default airport within ade as another form of troubleshooting the problem.
Its very strange. Any ideas?
I'm having the same issues! I just purchased three of these sceneries and just went out to test PHNL first and on approach to 4R the sim freezes and then CTD, i don't have any other PHNL scenery installed and also i noticed that i can't get runway info from the gps, i have to go to map view to retrieve the info.
Any thoughts?
-
i don't have any other PHNL scenery
A conflicting scenery doesn't have to do another specific PHNL scenery but, for example, an additional AFCAD that is supplied with an addon traffic package ? What traffic are you using ?
installed and also i noticed that i can't get runway info from the gps, i have to go to map view to retrieve the info.
Apart that I don't have any crashes, as you can see, runway info in the GPS works just fine here, see the attached screenshots.
-
A conflicting scenery doesn't have to do another specific PHNL scenery but, for example, an additional AFCAD that is supplied with an addon traffic package ? What traffic are you using ?
I'm using UT2, i double checked for additional afcads but there aren't any, although i did have Ray Smiths afcad installed, i removed it and the ctd does not occur anymore!
Apart that I don't have any crashes, as you can see, runway info in the GPS works just fine here, see the attached screenshots.
Having said that i can't get the runway info to show though and for some reason the ils to 4R gets messed up everytime i try an approach the AC goes in the opposite direction, the localiser just sends me of on another course, i'm miffed Huh
-
i did have Ray Smiths afcad installed, i removed it and the ctd does not occur anymore!
I was fairly sure of that...
Having said that i can't get the runway info to show though and for some reason the ils to 4R gets messed up everytime i try an approach the AC goes in the opposite direction, the localiser just sends me of on another course, i'm miffed ???
Which shouldn't happen because, our AFCAD does not include any ILS so, whatever localizer info you get, should normally come from the default scenery. If you see anything different, then it's another scenery in conflict.
Note that, this doesn't have to be an AFCAD: it's possible to include an ILS even in a normal old-style SCASM-type BGL so, this can be anywhere, and it will not be found by any of the AFCAD utilities out there or those that looks for duplicate airports.
-
author=virtuali link=topic=2762.msg23057#msg23057 date=1265633395]
Which shouldn't happen because, our AFCAD does not include any ILS so, whatever localizer info you get, should normally come from the default scenery. If you see anything different, then it's another scenery in conflict.
Note that, this doesn't have to be an AFCAD: it's possible to include an ILS even in a normal old-style SCASM-type BGL so, this can be anywhere, and it will not be found by any of the AFCAD utilities out there or those that looks for duplicate airports.
I checked your afcad w/ AFX and the ils info is there "AP_PHNL.BGL" complete with LOC,GP and DME? It's in the scenery folder of PHNL.
-
I checked your afcad w/ AFX and the ils info is there "AP_PHNL.BGL" complete with LOC,GP and DME? It's in the scenery folder of PHNL.
No, it's not.
It's just that AFX is also showing you the underlying info coming from the default scenery, for your convenience.
I guess that, if you try to *edit* the ILS, it will create a COPY of it, to be included in the AFCAD when you compile it back, so the edited version will take the precedence over the default navaid, which is what you normally want to do, and it's the same behaviour of the old AFCAD utility.
-
I checked your afcad w/ AFX and the ils info is there "AP_PHNL.BGL" complete with LOC,GP and DME? It's in the scenery folder of PHNL.
No, it's not.
It's just that AFX is also showing you the underlying info coming from the default scenery, for your convenience.
I guess that, if you try to *edit* the ILS, it will create a COPY of it, to be included in the AFCAD when you compile it back, so the edited version will take the precedence over the default navaid, which is what you normally want to do, and it's the same behaviour of the old AFCAD utility.
Oh ok thanks for that bit of info, i guess i'll go try that approach again and hope for better luck this time around maybe i'll use some other equipment for a test flight just to ensure the fault is not with the AC.
Thanks much
-
The only thing that doesnt make sense is the fact that the ctd happens when ATC assigns me an approach into HNL. Also when the ctd happens, I do not get an out of memory error message.
-
The only thing that doesnt make sense is the fact that the ctd happens when ATC assigns me an approach into HNL. Also when the ctd happens, I do not get an out of memory error message.
I can report that i did a successful ils approach into 4R without a hiccup with the PA airbus ;D
Beikircher i don't know if you may have overlooked the other part of Ray's afcad which is what i did and that is to remove both bgl files, one from the add-on scenery folder and the other from scenery/ world/ scenery that should stop those CTD's that you are experiencing.
-
Ya I have both of those removed. I have no idea whats causing the issue.
-
So if the case is right that Im running out of memory, is there a way that I can like defrag my memory to reduce the amt of memory that is being used?
-
OK i think i have now narrowed the issue i've been having w/ the freezing that comes on approach to PHNL, ive noticed it only occurs at dusk, night or dawn, even if i load the scenery from a runway or gate, the same issue of the scenery freezing.
Could this be a texture issue w/ the some night time textures or something? just a guess.
Regards
-
Hmm interesting. Ill have to see if I get the ctds on approach at that time of day.
-
Yes, there is a missing texture, if was discussed here:
http://www.fsdreamteam.com/forum/index.php?topic=2743.0
we already fixed it in the version for the patch, but in the meantime, you can try the solution posted in that thread.
-
Yes, there is a missing texture, if was discussed here:
http://www.fsdreamteam.com/forum/index.php?topic=2743.0
we already fixed it in the version for the patch, but in the meantime, you can try the solution posted in that thread.
Yup that did it, no more freezing, alas! ;D
wait a minute i think i was a bit to hasty to jump for joy, it just happened again! Now why is this happening intermittently i have no idea, at this point i'm just miffed. maybe when the update is released it would work itself out mysteriously, for now i give up :(
-
With those textures that were needed from the FLL scenery seems to have done the trick for the time being. I did not get a ctd, but the buildings were very slow to load. Not sure why. The cargo buildings loaded right when I was about to touch down, and usually the buildings are loaded some 5miles out.
-
The cargo buildings loaded right when I was about to touch down, and usually the buildings are loaded some 5miles out.
Have you followed all the discussion about the Anti-popup slider ? That controls the loading range for objects.
-
No I have not, where is that? Sorry about that. Thanks for all the help Umberto
-
Well, it was on the KFLL forum, however the concepts are valid for any of our sceneries. Basically, with the Anti-popup slider, you can increase the range of objects ( 1.0 means as they are designed, 10.0 means 10x bigger range, etc.), at the cost of fps. Just try with different settings, depending on your system.
-
Ok ya I got it and see it. Now is that just for your scenerys that the anti pop up slider works for?
-
Yes, only objects handled by the Addon Manager.
-
Ok gotcha. THanks Umberto!!!!
-
I set the anti popup slider to 20, and when I was landing the buildings still poped up around a 1 mile final. Any suggestions?
-
I set the anti popup slider to 20, and when I was landing the buildings still poped up around a 1 mile final. Any suggestions?
If by "buildings", you mean the main terminals, these are not handled by that slider, and are not even using dynamic loading range so, they are always loaded when in the scenery range, which is 8 nm for PHNL so, it's just not possible they would load at 1 nm.
Don't confuse buildings, with additional extra detail on them, which is the LOD in action.
For example, a building might load at 8 nm, but a more detailed version of it will load closer. This doesn't have anything to do with the Anti-popup and, since it's NOT causing pauses (because the object is loaded entirely with all its LODs only once), will stay like this.
The things that are controlled by the Anti-popup slider are smaller details, like ground vehicles, cars, signs, 3d taxilghts, etc..
-
Ya I was refering to the terminal buildings. Ok, I thought that the anti slider controlled all buildings, but ok I understand now. Wasnt sure 100%