johnfromoz

Thanks for the insight, Harald - I think I will reconsider buying the Mil after all! ^_^

Yes, I agree, I separate the regime of the 40s from the technology. I know of the AI Mil helicopters but wasn't sure about purchasing the MI8 (I think it was) as I didn't know anything about the company processing the money. MAIW have some good helo air files I sometimes transplant for personal use.

Yes, I understand the issue re the markings. I have the FS conversions to "Golden Wings" and "Silver Wings" on separate drives, and the Golden Wings has a few quick adjustments I can do to select the 1920s-early 1930s, the immediate prewar period, or early WW2. I'm going to have to add the marking to the Lufthansa aircraft for the later period! Interestingly, I have almost no purpose-designed AI aircraft in Golden Wings, nearly all are converted user-flyable models. Some needed no conversion to work well. You can probably get away with it in the 1930s, when skies were less busy! As for helicopters, in my modern FS9, I am doing the same as you are, it's satisfying to see them. I also have a lot flying in "Silver Wings" - mostly in places like Vietnam! Here's a crude illustration. All six AI helos are headed for "LZ Xray" out of Camp Holloway (Pleiku) either on strafing runs or for 'dust-off' and - a case in point to this thread - me flying this close tended to confuse the AI engine and they sailed off towards Cambodia!

Jive1, I have a fairly basic question. How do you know it doesn't turn? If you have flown alongside or near it, your presence can throw AI aircraft off an they will just chug off into the wild blue yonder. One way to avoid that is to track the aircraft itself from chase view, for which the default, I think, is Ctrl+shift+F to cycle forward, and Ctrl+Shift+V (or W) to cycle through all AI in the other direction. You may need to set this up in control assignments. Also I suggest you park at the field nearest where you think the trouble happens, switch off your engine then start tracking. Not turning, and not arriving, may be part of one problem, or two very different problems. For example, flying beside the AI might disturb turns, and not arriving may be an AFCAD issue. And AI do make some unexpected turns. I have tracked them on simple circuits and sometimes they are not square, but involve a few doglegs. I've even had AI appear to steer around landscape, quite unexpected but nice when it seems to happen. I often do as Tom and others say - drop the air file from a reliable AI aircraft into the new AI plane folder. I also change the aircraft.cfg to aircraft.txt, then copy over the aircraft.cfg from the same folder I got the air file from. Into that, working from the renamed aircraft.txt, I copy (and overwrite) all the [fltsim.X] entries, and the sections for [lights], and [contact points]. Also, if it's there, the [General] section. As Tom said, you will need to change the "sim=" line in each [fltsim.X] entry to identify the replacement air file. Don't know if this is accepted practice but it's worked fairly reliably for me. Harald, nice screen shot!

This is unfortunate. Frankly, I thought good web design included not burying the content under layer after layer of screens. And if there's a FAQ on the search function, I'm afraid I need a "search" option to locate it! But when it's found, one of the key searches is by author. It's already hard enough, here and elsewhere, to narrow searches for things like "Air France", where we get a heap of scenery for "France", or conversely, to get blanks for searches we know should bring results (as BAW345 said). I see the thread on the new format is locked and the library is under some kind of reconstruction. I hope this includes some retention of author names, and something good by way of search ability. AVSIM is too good a site to suffer the indignity of the changed file library.

<Sigh of relief>I keep coming back to FS cos you never know what kind of curve ball it will toss at you next!

Possibly the same Leuchars - which even worked on my old setup. I had a heavy Isle of Wight scenery which I ended up dumping, too, and that was the problem end of the UK! For a while I ran all of Maxted's small airfields, but they have been replaced one by one. I didn't find high numbers of sceneries to be a problem - as I said I have heaps of airfields and VFR items all close together in the UK and much of western Europe now, with no issues. AI can be a kick so the suggestion to switch it off makes some sense, but again I run plenty...John Hinson said on the other thread there's no scenery limit, just a limit as to what shows on the library list. That said, I had a scenery vanish only yesterday, had to re-enter it! But I both sympathise and fully applaud you being a scenery junkie.

This is what makes me wonder about southern UK. I have very dense airfields in, say, the USA, and parts of Europe, without the issues. I also have piled in all the nice little VFR items to view from my Chipmunk - from city centres to castles and piers and oddball memorials. With all manner of addons UK is still fine on my new setup, which was in fact built with FS9 in mind. So without having a specific fault to point at, and assuming the issue is a resource-hungry region, I wonder what differences between our systems there are which could provide clues, given I had the same problem on my older, slower machine? Seems trange to me. With defragging and reloading and all, your sceneries have probably had several different addresses on the disc - so Chock's idea makes some sense. If you do as he says and still get the problem, blame England! Then I guess it's down to finding ways to get more resources. Used to have a program called "EndItAll", for instance, which let you easily switch off stuff not needed when simming that took up resources in the background. You say it happens if you try to start a flight in the UK. Indeed that was my experience. Also moving into the area (Southern England) via the map did it. I could start at St Just, or somewhere past the Midlands, and fly in, but if I stopped to look at the map, it would crash in map mode too. And sometimes just crash when I had flown some way in.

I have no real answer except to comment that I always found England a problem (the FS version of it - which I love flying). My old system was borderline for FS9 and I regularly got crashes in the southern part, and also just over the channel, but few from the Midlands up. Is your problem by any chance worse in that area? I have not had the issue on my newer system, touch wood (Intel Core 2 Duo, 3 GHz, 2.75 Gb RAM, WinXP, with Nhancer for some settings we usually set within FS, and that rather than the latest Nvidia driver. I have no idea if that helps!)I am developing a view that southern England wants more system resources than we'd expect for some reason. This may be an FS9 secret nobody talks about.

I park my small Rapport next to my immense Charisma! Is this thread getting out of hand so soon? Then my work here is done!

I always suspected bumping against the ground in FS would chip the pixels... But it was remarkable that I fretted over this for a few weeks and in a couple of days after posting here, the bits fell into place! Been away from FS too long, losing my rapport...

Oops - misposted and deleted, apologies.

All fixed, once you guys got me thinking the right way! I had (by some flash of psychic ability, saving me going to the discs) a zipped folder of the default scenery/world/textures and just copied all the agn and their related bmps across - left alone the water textures and others I had replaced with third party stuff. I noticed in the course of it that a handful of agn files were much smaller than the originals, about 1/3 their proper size. How that happened I can only guess. Wear and tear? A dirty trick in some auto installer? Thanks for helping me dust off the FS cells in my brain!

Thought crossed my mind, but they are too disordered even for trees.Rhe shot is near Blinman, South Australia, a minute or so west of the airfield (on the racecourse) - unfortunately not a default field so unless VOZ has it, you may not! It happens in a lit of places - Goolwa airfield YGWA has the same all around it. It's occurring over wide areas - for example I flew Hawker, Wilpena Pound and Blinman and these clumps were dotted across the landscape. It should be open country with big empty fields or bushland, roadside trees, and occasional small towns. :) I did try VOZ through a few versions and gave up on it. Its file system was too chaotic for me, I couldn't be bothered sorting it out if I found a better scenery to replace one of theirs. Didn't like fiddling with the control panel either. Wasn't my scene - not to detract from the immense talents of John Venema and the very reputable designers who contributed, but I like more control over installation than it gave me. John V. clearly made good use of the experience in ORBX, which is beautifully constructed. I don't use FSX myself.

Thanks Dave (I remember work! I hear people still do it ;) ) Looked at my AGN files in World/Textures and nothing modified later than 2008. I don't think any live anywhere else. Back that far, I didn't have this problem, it's just appeared over the last few weeks. That does give me an idea, though. Rather than reinstalling I might try to just replace the World/texture .agn (and perhaps texture tiles) from the original disc. Thanks for the inspiration - I am still open to input if anyone happens to have encountered this but that's a place to start, and I didn't have one before!Hope your tea didn't go cold!