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.