Roger Wensley

Spock here: I was able to move it, resize it, and all with Windows 7 too. So could not investigate further.

Why try to move it then? Why not just leave it until you don't want it anymore and then close it? Out of curiosity I will now open FS9 and see if it is even possible to move it; I never tried.

Andrew, Let us know here how it goes, as we will all be doing this eventually as Windows 7 (or the far worse 8.0 or 8.1) become unsupported. As an aside, I moved from XP to 7 in exactly the same way and it went ok.

Then I will add a bit more. Click on "file" and then "open" in Image Tool. Select 10 textures and click on "open". You will see the textures one at a time and if they have mips you will see those. The info for each texture will be on the right, so that will tell you they are 8 bit, 32 bit, DXT1, or DXT3. If they are 32 bit (or 24 bit) then click on "Image" and then "Format" and select either DXT1 or DXT3. If you have already seen they have no mips click on "Image" again and then on "Create Mipmaps". Then save. If when you select 10 textures nothing happens, select 8 instead; if they are too large then they overpower the prog.

Two last things to hep find a misbehaving texture. Look at the textures in the texture folders with the settings at large or medium icons, not at "list". Any texture that is 24 or 32 bit will show as a picture not an icon. It could, however, also be an 8 bit texture, and those are not a problem. To find a texture that is not mipped among a herd of mipped textures (and Tom rightly pointed that out as a possible problem that we hadn't mentioned) open them 10 at a time with the imagetool.exe that comes with SBuilder and you will be able to see if there are or are not mips; you can also check if a texture is an 8 bit or a 32 bit with it. Given that this seems to happen at more than one airport (is that correct?) I don't see it as an object texture problem, unless you have the same object at a lot of airports. Sid had one faulty texture with his apron lights, called "Zinc"; look for that. And if you already knew all that, sorry.

Tom, although I think his ground texture "fuzzy" problem probably isn't caused by an errant object texture as it seems to recover too quickly, until yesterday I also didn't think that a ground texture could cause a CTD!?! You know how making scenery goes, with FS9 sticking out a foot to trip you up whenever it can, and I am making CYRC at the moment. Yesterday it crashed, and removing the scenery objects and then the ground texture revisions showed me that it was a ground texture problem. It only occurs when I switch from Cockpit view to Top Down view in slew mode. The new ground textures are very normal, airport grass background and cool mixed forest to trim the size of the nearby town and I have used both hundreds of times before. A puzzle as to why, but it can be lived with.

I second that the 25 fps lock will give you the best chance of seeing properly rendered ground textures. Anything higher than that is anyway a waste as your eye cannot tell the difference between 25 and 35 fps.

Nels, I prefer my word to what you changed it to, "users". It captured the irritation engendered by a repetitive lack of response to pleas for feedback information. Which certainly has an effect, in that I find that I have no new project in mind.

This feedback problem is as old as the hills and is still hiding in the valleys. I made a very visble mistake in a recent FS9 post (that did not show up in my own installation) and 134 of the downloaders in the first 4 days did not tell me; happily the 135th did. Eight years ago another designer had an error in the AI of a post, and in that time none of the over 7,000 downloaders told him the AI just didn't work. When I told him he presumed that I had just misinstalled it, and his flabber was gasted when he found the error. The users just don't listen to the pleas for audience participation. Or maybe they can't read.