I use the SDK tools in the usual way to create a bgl that contains the terrain mesh and custom generic textures (this is now incorporated into AutoAsm). It works fine in FS2002 but not in FS2004. When I try to load the scenery in FS2004 two things happen:1. The scenery load process takes about five minutes (normally about 40 seconds).2. The terrain appears correctly. The custom generic textures appear but they are *totally* blurred (possibly the lowest mip map resolution). I re-made the bgl with terrain mesh only. The load time is normal and the terrain appears correctly with the default generic textures. I made another test scenery and this showed exactly the same problem. The input for the custom generic textures is a .raw file. It appears there is some form of incompatability between the two sims relating to generic textures. Does anyone have any ideas? Many thanks. Best regards, Chris Inf file:=========================================[Destination]LOD = 8DestDir ="c:AutoTerrainKarakamMesh"DestBaseFileName = "textures"UseSourceDimensions = 1[source]Type = ClassU8SourceDir = "c:AutoTerrainKarakamMesh"SourceFile = "textures.raw"Lat = 2Lon = 40NumOfCellsPerLine = 512NumOfLines = 1024CellXdimensionDeg = 0.00276562CellYdimensionDeg = 0.00276562ScaleinMeters = 1.0====================================

Hi Chris.Is this a landclass you are creating? With a twin 'texture' folder to hold the new generic ground texures?Dick

Hi, Dick! Your post reminded me of something - and it's fixed! Many thanks. I've added to AutoAsm the ability to draw images to define terrain mesh and generic textures / landclass. Great for creating your own personal island.... The program converts your landclass .bmp image to a .raw image and feeds it to the SDK tools in the normal way (the .raw happens to be in the right format, which is handy - for example a zero index will create water). I am using the default generic textures, so there is no need for special textures in the texture sub-directory. However - when you mentioned the texture directory it rang a very loud bell. A year ago I had a similar problem. And the solution was to delete the empty texture directory. Sure enough, in FS2002 I had deleted the directory. I deleted the texture sub-directory in my scenery in FS2004 - and it works perfectly! So it's not a FS2004 problem, it may be a FS2002 peculiarity carried over into FS2004. I must say my scenery looks much better in FS2004. Microsoft have done a great job. Let's hope they don't drop the ball by making us wait almost a year for the scenery SDK! Once again, many thanks for giving me the solution - even if you didn't realise it! Best regards, Chris