NZFF

I'm having a bit of an issue currently with my venerable AucklandCity suddenly causing OOM errors (even though I've tried all the usual OOM black magic and memory/display settings tweaks and keep my HD well defragged).

So ... I'm now trying to see whether there's something that clashes with it. In the process, I keep looking at these two settings and realise that I've been mystifed ever since I've had MSFS (don't ask how long *that* is ). I've Googled it in the past, but never found a sensible answer.

1) Cache this scenery
2) Use this scenery directly

It defaults to 2) ... but what are the advantages/disadvantages to each? Is this *disk* cache or *memory* cache?

Related to 1) and 2), we have a global option to "Empty the cache on exit". Is the cache re-used somehow? Even if I have it set to "Yes", is it possible that I have a corrupted cache that's screwing my NZAA up?

It's possible that there may not be a clash/problem with the scenery itself - simply that its very complexity tips me "over the limit", memory-wise - a shortage maybe caused elsewhere by some other memory-sapping add-on. I don't seem to have any problems anywhere else.

Hopefully, Rob's new (more FSX compliant) AKL will get me out of this mess - but I'm intrigued all the same.

In previous versions, this only worked with CD-based scenery. This goes back to early days when nobody had a lot of disc space to spare. You could run the scenery from the CD (slow on some systems) or cache it on your hard drive for speed. I think that FSX may be the same.

Try this site and read up on all the things you can change to get more out of it http://www.simforums.com/forums/forum_posts.asp?TID=29041

My flps went from 3 to 30 flps with all the changes mentioned for my system ,being only a 3.0 ghz single core ,this is with everything at very high settings , i followed all the updates info and nhancer settings plus i did some changes to the way fsx deals with my widescreen in the CFG file plus a couple more " 110% enhancement of fsx for me "

creator2003 wrote:

QUOTE (creator2003 @ Nov 2 2009, 11:44 PM) <{POST_SNAPBACK}>

Try this site and read up on all the things you can change to get more out of it http://www.simforums.com/forums/forum_posts.asp?TID=29041

My flps went from 3 to 30 flps with all the changes mentioned for my system ,being only a 3.0 ghz single core ,this is with everything at very high settings , i followed all the updates info and nhancer settings plus i did some changes to the way fsx deals with my widescreen in the CFG file plus a couple more " 110% enhancement of fsx for me "

Yep - that's the one I've been using (thanks). I think it's the most comprehensive thread of all of them. There's always the odd chance that some of these settings totally stuff your install, but I'd implemented most of those tweaks a fair while back. This OOM problem appears to have started during a period when I specifically hadn't been tweaking.

I'm gradually removing my latest add-ons - Squawk Box related stuff etc. for when I was playing with VATSIM. Still crashes when I enable with my other scenery (yet it's been working fine for *years*. Back to the drawing board!

toprob wrote:

QUOTE (toprob @ Nov 2 2009, 09:30 PM) <{POST_SNAPBACK}>

In previous versions, this only worked with CD-based scenery. This goes back to early days when nobody had a lot of disc space to spare. You could run the scenery from the CD (slow on some systems) or cache it on your hard drive for speed. I think that FSX may be the same.

Thanks Rob. If anyone here ought to know, it'd be you
So ... in that case, *should* I be caching it (which I'm currently not!). <??>. I'd be caching stuff that's already on the HD <??>.