Well .......perhaps Jim and Bill are right, perhaps your problems are not related to only using 2 gigs of ram to run your FS ????

I will keep an eye on this thread......but I will now shut up

Good luck either way

Cheers

Romflyer

 

I thought you were going to follow your own advice. His crashing or freezing has nothing to do with memory or flagging the FS9.exe.

If he followed the advice of turning off his AI and add on sceneries completely. Then turning on each add on 1 by 1 until he finds which one is causing the problem. Can he fly the same routes without problems with everything turned off is what were trying to figure out.

 

:lol: :lol: :lol: :lol:

Jim, If you go back and re-read that thread http://forum.avsim.net/topic/429619-fs9-crashes-right-before-a-landing/  the OP says that originally he got an OOM message but later his sim was just crashing/CTDing/freezing without that specific message......this fits with my experiences, it fits with Jeff's earlier remarks, and even though you don't like it...it fits with the problems of the OP in this thread.

There is not a single OOM message being reported by the user in this very thread. I really don't give a rat's behind about any other thread but this one. Comparing this to that to another to what happened 12 days ago to what happened 3.274 years ago means squat. I take each problem as a unique occurrence because every computer, OS, environment, FS install, and add on is different and to use a wide paint brush to solve everything is providing a disservice to the OP. 

I agree there's a lot more going on here than there was with that other issue.  And we went through all the other troubleshooting steps with him first, so the issue was isolated before we went the direction we did. 

Cheers!!

Well billy .........yes I'm talking to you Mac .... I took your first poke at me pretty graciously, there is absolutely no need for you to be making this personal.

We have a different opinion on what is happening with the OPs install.... That's it

So settle down

 

At this point it seems he has checked all his Afcads, turned off all his traffic, he has de-activated all his scenery, he has flown over the area a few times more and had a freeze/CTD/crash on one flight but not the other.....?

 

So ...... What's next?......Jim ?.....billy ?

What's next for you, us, or the OP?

Ok this is what I did JS I unchecked everything restarted FS rebuilt the scenery. Rechecked everything back restarted FS rebuilt scenery and all went well that time no freezes

 

He was suppose to fly the area with everything unchecked and zero AI. And try to duplicate the freeze or crash. If the affected area don't freeze, Then check each scenery one by one until he's able to re produce the freeze/crash at the same point where it occurred.

What's next for you, us, or the OP?

I'm not really understanding what your statement means .....I think it was supposed to be some sort of an insult????

My question was what do you think the OP should do next?.......at least Mac had something intelligent to say.

The problem with fixating on scenery is that he has flown through the area a couple of times with no issue.........which brings us to something variable like traffic..... But he has this turned off.....?

So as long as your not gonna take it personally I'm asking you what should the OP do next?

The OP should supply all of us with more information as to the general state of his FS9 install as it stands right now. The lack of information is not helping anyone at this point.

 

If I wanted to insult you, I sure would have made it a lot clearer that I was.

Time to close this thread?

Why? The OP has yet to find a solution.

Well, I read through this thread from the beginning, and it's beginning to show the signs of degradation common to some topics in this forum.  It was simply MY observation only and was in the form of a question.

 

OP states a problem .....gets one or more suggestions .....OP tries possible solutions .....OP has no luck ......gets another solution .....gets post that maybe the OP didn't post all/accurate symptoms .....frustration of responders sets in ......responders question each other's solutions ..... OP has fallen out of thread ......"You talkin' to me? You talkin' to me? You talkin' to me? Then who the hell else are you talking to?... you talking to me? Well I'm the only one here" thread shows up ......"if I'd be talking to you, you'd be looking out of your nose" comes in as a response ....etc.

 

Like I said, just my observation .......

If we closed every thread that got a little testy, there wouldn't be anything left in the forum to read.  We're all big boys and girls here, presumably.  No one is served by mods closing active threads just because a couple of kids are arguing with each other in the schoolyard.  If there's a problem, work it out.  That's what PM's are for.

Cheers.  :smile:

I have been having the same issue on the East Coast, in the northeast corridor.  I file a flight plan from KIAD to KBOS, routing is KIAD, OOD, J42 to PUT, to KBOS.  When heading from IAD to the OOD VOR, the sim freezes up at EXACTLY the same spot EVERY time, 91 miles from the OOD VOR.  The sim freezes (not CTD and no error messages) with both the iFly 737 and the Posky/PSS merge 773.  I am sifting through all my addon sceneries (of which I have waaaaay too many, both pay and free) right now, but I have to agree that I don't think it is a memory issue.  This is 100% "repeat-able" for me....When I fly out of DCA on the same route (KDCA to OOD, J42 to PUT, etc), no problems, but it happens every single time in exactly the same spot out of IAD.  I have disabled my KIAD add-on scenery and still the same results, still freezes, but when I disable my KBWI scenery (KBWI2k5v2 by Matthew Perry and Joshua Broadwater), I make it through without freezing.  So then, when I tried to file a plan out of KBWI, the sim freezes and won't even load the scenery (it loads if I just "go" to the airport, though, without filing a plan from BWI), so maybe the culprit is in there (KBWI) somehow.  I am not saying that this particular add-on is at fault....it may be how it interacts with another add-on or utility. I will let you know what more I find out.  Whether I discover that this is the culprit or not, I am reasonably certain it will be an add-on scenery or conflict.  Just out of curiosity, what BWI do you (the OP) have? 

 

= = = = = = = = = = = = = = = = = = = = = = =

Steve Kareta

FS2004 / AS6 / UT / one-zillion add-ons / Win-7 Gateway Dual-core / 4 Gb ram / Palit/NVidia Geforce GTX-460-1gb

Hey Steve, welcome to the conversation ...... Your issue does sound similar however much more consistant than the OP's......? A lot of things happening in a very small area.

Out of curiosity, are you currently using all of your 4 gigs of ram, or are you leaving FS restricted to 2 gigs?

I have to admit that I have not played with any of the memory settings, and have not applied any of the "memory switches" or patches that I have seen discussed here in this thread.  In all honesty, I have been getting great frames and no stutters, even at the most dense payware add-on airports I have, with dense weather (AS6), with AI traffic at 80% (I have all the WOAI for N America sets), max vis at something like 80 miles, mips at 4, but all my other sliders maxed.  I even have the anti-aliasing ON in FS (gasp!!!, and I have used NVidia Inspector to tweek my card a bit, but nothing is overclocked).  At airports like Cloud-9's DCA or any of my FlyTampa places (BOS, TPA) I'm getting 35-FPS or better, and 50+ in cruise, so I have not had the need to explore opening more memory on my rig.  Yes, THIS is why I've stayed with (or more accurately, come back to) FS2004!!!

 

Going back to the original OP's issue, I again took the first part of the trip out of IAD towards BOS yesterday, with my KBWI disabled, and no freeze.  To point, it may not be that specific airport or AFCAD that is causing the jam, but it may be how it is interacting with another add-on, ATC, or AI traffic.  More research is still in order when I have the time.  Has anyone experienced freezes related to ATC?  Is there any conflict between using a standard "FS9-issued" routing vs the routings using , say, Navigraph data (ie: A waypoint perhaps being different between the two)?  Reaching even farther outside, any conflicts between DTX3 and 32-bit textures (if using both types at the same time for different areas)?   And the hunt continues.....