craigewan

And "AMEN!" to that. For goodness sake, guys, the AVSIM staff are not providing us a product we have paid for, - they are all FS enthusiasts like us, except for one key thing - THEY are giving up their free time to provide (and now rescue) this service we all greatly appreciate. I salute them and will not for a second complain impatiently as they try to bring the library back from the brink, even though I feel its loss keenly, as a very enthusiastic user of, and occasional contributor to the library. Note to AVSIM staff - behind these few messages of patient support there is a vast legion of supporters who are totally behind you and share these sentiments. Don't be discouraged. Paul

Yesterday a mate of mine (hi John!) showed me his fsx installation on his beautiful toshiba laptop, (Centrino Duo and 512MB 7900 Go) and he had always complained of "micro-stutters" like you're having. I noticed he had the weather set to fair, which I didn't like at all - looks very unrealistic with far too much visibility even for a cloudless day (at least for the UK). I also wasn't too taken with other of his settings - poor vis quality in the VC and the aircraft generally, and I felt sure he should be able to get a better experience than that. So I maxed his aircraft gfx settings, inc maxing the global texture size and, (and I think this must be the big one) set his weather to gathering storms (or whatever its called - gives about 3/8 - 5/8 cloud and occasional lightning bursts). This cut the vis automatically to maybe 20 mi and introduced very realistic haze fx. I'd previously shown him some screenshots from my home installation and I remember him admiring the haze fx in them, but didnt at that time pick up on his comment, though was a little puzzled as the haze is a bog standard thing in fsx, and something it does very well indeed, IMHO. I now realise he was always setting the weather to "fair", perhaps thinking that would reduce load on the program. Well, after I'd mucked about with his settings he was astonished and asked what I'd done cos his micro-stutters had disappeared totally - he had it locked at 20fps and it stayed at that virtually constantly. So now what I think is going on is the reduced visibility with that weather setting is reducing the ground texture load which is probably what was causing his micro-stutters. Anyway, you might want to try the same. Hope this helps someone.

Actually, I just realised that since you only have a default installation, there might be a quicker method. Instead of deleting bits of scenery.cfg and then adding bits of the deleted stuff back in, since you can't have many entries in a default scenery.cfg just set Active=FALSE in the entries in the last half of the list, then proceed in the same manner as in my previous response. A binary algorithm in general will be quicker to pin down the fault than simply de-ACTIVE-ating each entry one at a time, and then re-running fs9 twice for each entry, though, of course that would work (eventually) as well.In my case the problem was tracked down to several downloaded sceneries, but since you don't have any addon sceneries it could be that my advice is way off target.Whatever it is, good luckPaul

I had this happen once, though not to a fresh installation. I tracked it down to a faulty scenery by effectively doing a binary search. i.e. after backing up the scenery.cfg, chop off the last half of it and run fs9 twice (the first time it /should/ do the database rebuild, the second time it shouldn't if there are no probs in the sceneries or scenery.cfg). If its ok, then put back just half of the bit you deleted, and run fs9 twice again. If there /is/ a problem on the other hand delete the second half of the already reduced scenery.cfg. And so forth. This way you'll narrow it down to whichever entry is causing the prob. Note it needn't be the scenery.cfg thats the problem, it could be the sceneries themselves. Even so, it'd be pretty weird for this to occur with nothing but fs9's standard scenery entries. I haven't a clue why that would happen.Paul

I am no expert but isn't your new graphics card (6800GS) a downgrade from your old one (6800GT)? Maybe this is why you are getting poorer performance? See this comparison:http://www.avault.com/hardware/getreview.a...ga6800gs&page=2good luckPaul

Tom Gibson wrote:>2. If you have TNG set in the flight plan, it must be a VFR>flight. IFR flights will just do go arounds.>>Hope this helps,>It certainly did. Changed them to VFR and now all is fine that I'vemanaged to check so far. Thanks to MikeS as well, good tip.ThanksPaul

No-one seems to have mentioned FSMovingMap. I use this with the US Nav charts and it seems to do what you want for the States. There are less detailed maps available for other bits of the world as well.Paul

Can anyone help me figure out what I'm doing wrong? I have used TTools and SimpleAI to produce all sorts of AI Traffic, but there are a couple of cases where the plane fails to land and will always abort and go-around. The airfields are my own creation - recently uploaded to AVSIM (EGPS, X6FS and X6ET) - and most a/c land ok, including TnGs if specified. Often the same a/c that wont land manage to take off from there perfectly well. Is it my AF2 file or the a/c that needs tweaking, or something else? I can't upload my AI Traffic for the airfields until I get this sorted.ThanksPaul

I've got a suggestion to make to Microsoft about protecting their investment in FSX. Its based on two observations, namely:* there will be two types of people who will install and use a pirated version of FS without having paid for a legit copy - the casual user who would never have bought a copy in any case, and the serious user who would have bought a copy if he/she couldn't get the freebie.* too often, developers' approaches to protection of their product are based on adding value to them, and not adding value to their customer, who after all is the one keeping them in a job. I feel the customer deserves a bit more respect. (The classic example of a developer getting this wrong is the whole VALVE/Steam/Half Life 2 debacle! >:-S )The casual user is a lost cause - if he/she pirates FSX its no lost sale to MS 'cos they'd never have bought a copy anyway. What you want to ensure is that those who would have bought a copy do so. And to do so in a way that reflects modern gaming usage - i.e. increasingly we have PC choices at home - as many have said on this forum we might like to install FS on more than one PC we own, and for various reasons - I have mine on my main PC (but not on my secondary one) and also on my laptop, even though its only ever me that uses it. I prefer to use the main PC as its more suitable, but at times I'm forced to use the laptop.The solution I have to offer is that MS add 25%-30% to the cost of the product to cover the inclusion of a well produced, well bound paper manual - a book, say 3/4" thick, with lots of added value. Here's my notional list of the contents:*early chapters on getting up and running, obviously. Include stuff for the dive-in-and-go user.*detailed introductions to the package contents - the aircraft and individual guides to flying each of them, checklists for those that want the fuller experience, tips about various sceneries in the fs world, with screenshots. Weather, ATC, etc.,.*detailed notes on learning to sim-fly as a back-up to the in-game flying lessons, and integrated with them - i.e. the in-game flying lessons will include reference to page whatever, and vice versa. Make the flying lessons assume the user has the book open beside him/her. But also make the book something that can be read when not at the sim, reading up on the flying lessons lying in bed or on the bus.*colour simulated charts for various flight adventures - make it international too - the purpose is to integrate this manual into the FS-experience as much as possible - dont just limit the charts to the built-in adventures, but make some for interesting parts of the world and interesting airports, so people can have their own adventures using the resources of this manual.*tweaking and hardware tips - explanation of fsX.cfg type matters or whatever is equivalent*introductory guide to add-on development issues - refer to the various payware and freeware add-ons that can be used, or online resources or whatever. Now I know this can get out of date, but probably most of it would still last the lifetime of the FSX product. Discussion of scenery addon issues - meshes, landclass, autogen, photosceneries, 3d object editing, etc.,.*at the end of the thing have many pages laid out to simulate a log book that the user can begin to fill in, but add bits to it to reflect its just a sim - such as the space to make reference to screenshots or names of saved flight files or recordings, so somebody looking through the logbook can see there's some files stored to show something of the flight. Maybe make the sim itself have a way of saving files indexed to the logbook? Other than that make it as much like a real logbook as possible. Again the purpose is to integrate the manual into the FSX experience and to add considerable value to it.With this added to the product I would guess that there would be hardly a single serious FS user who would NOT buy the full thing, even if they do use some no-cd hack to enable them to protect their investment by not risking damage to their precious FSX discs, even if they do install it on more than one personal machine, and even if it does cost a bit more. Such a manual would be indispensable to the experience of using FSX, and would be worth the premium in the price of the product, and would cost the pirate a fortune to photocopy only to produce something shabby compared to the proper lovely FSX manual.There are few dev houses in the world who could produce such a book, but surely MS is one of them. Especially since it would clearly return and protect their investment.Whaddya think?Paul

I found this thread when I googled that same 6025 error, and as a result I solved my problem. I post my solution for anybody else who stumbles across this thread trying to solve the same thing.In this thread, and others, I found a common idea is that it has to do with AI traffic and/or ATC. This set me thinking about a change I'd made to a traffic*.bgl using ttools 2 a couple of weeks ago. I'd swapped out an a/c that had bugs of its own for Bill Lyons gorgeous Challenger 2 which I wanted to try out as AI from places where I know Challengers operate in the RW. It worked fine as AI but it has turned out to be the source of this crash. Changed it for something else designed specifically for AI and the error went away.I should also say that this error was happening between 5 and 15 mins into a flight, and usually it just froze the flight sim /and/ the computer (with no error message being reported) and sometimes BSOD-ed (although that might have been an unrelated error, it hasn't re-ocurred since I changed the traffic*.bgl - so far!). Sometimes an error message would flash up subliminally, too quick to read, but today I got the error message in a static window, giving me the opportunity to do a google search for it.Hope this helps somebodyPaul

This once happened to me and was very annoying. In my case it was down to a particular freeware scenery add-on, and when I got rid of it everything was fine. How I found which addon caused the problem was to use a binary search approach. First copy your scenery.cfg somewhere safe, 'cos this approach is going to mangle it. Then edit the copy which is still in your flight simulator 9 folder by deleting the last half of it (doesn't need to be exactly half, but do take note of the highest scenery number in the bit that remains). Start up fs9 let it rebuild, then quit fs9, before re-starting it, and if the rebuilding dialogue shows in this second start (*) then you still have the error which must therefore be in the first half of your scenery.cfg, i.e. in the bit you didn't delete. If it doesn't produce the re-build dialogue then the error is in the bit you deleted. Copy back the pristine scenery.cfg, and now only delete the last quarter of it (again doesnt need to be exactly 25%). And repeat the process until you narrow it down to a handful of scenery entries. At which point you can just set them one by one to "Active=FALSE" to see which is the troublesome one. I hope I've made myself clear cos its not that complicated to do, and my scenery.cfg had several hundred entries when I did this.(* I'm a bit hazy about whether you really do need to do this twice - it was a couple of years ago that I did this).Good luck in getting it sorted.craigewan