Products Support > Honolulu FSX/P3D
Crashes to desktop **solved**
virtuali:
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.
jordanal:
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. :-\
jordanal:
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...
anappy:
--- Quote from: jordanal on March 07, 2010, 12:09:25 am ---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...
--- End quote ---
thats whay happens to me in the LVD 763. I think this is becoming a larger problem
virtuali:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version