Mani thanks for this work Dave ! It's take some time to install it for me, because my Seattle region is expanded to the north up to Friday Harbor / Anacortes and so 76s is an inner airport for me. I had to move airport and models to new coordinates then it's not just done by moving the files from inner to outer folder :-). If you move the files only, you will see nothing :-)The name of the tiles will change and the distances between left bottom corner of the tile too. Using the move function of FLEDViewer and AirportEditor a coarse setting was done. After flattening parts of the area and runway I have moved the objects to fit the exact position of the high resolution background where you can see all buildings. A main problem was the fact that 76s runway is a ramp from 43m at 07 to 59m at 25 end. To save the natural elevation I must remove the flat grass and runway objects but you don't miss it inside the high resolution. AI planes must now turn in the middle of the runway, before the ramp starts to go up to 60m or the AI will move into the ground or floating in the air at the parking spot and that looks bad. Just to remember to expand the Seattle Region you need the Seattle Expansion Toolkit expandseattle.zip from the library.2 tiles north of Coupeville Nolf are in the set reaching up to Anacortes. When you expand your region one day you will need the adapted Eisenberg airport to use it, just contact me in that case.Default landing of AI was runway 25 but to avoid the ramp I forced it to use 07. To reach this I had to exclude all at the green runway node 25 and include all (no x) at node 07. To have traffic you must set the wind blowing from the east. East of Eisenberg, just passing Oak Habor and the Coupeville Nolf runway is in the top left corner. Trainer downwind 76sFinal 76s runway 07Arrow on the way down to 76s in the background you can see Oak Harbor, Jim, your lighthouse is in place now, looks good, thanks,Andre

Wow!!I don't use multiple exclamation marks often but the screenies look very good. I think I'll have to try the expanded Seattle pack.Please feel free to upload your adapted 76s and direct the library staff to this thread if they have a problem with it. That way we can all use it.I'm not doing much at the moment. I've just made a clean basic installation of FU3 for testing the next airport, having discovered a fault in my full installation. Sadly the fault is also in my last backup so I'll be spending some time soon rebuilding everything :( . When I ask for vectors ILS to any airport, approach comes back with '... will be vectors direct.' Very frustrating and it must have been lurking unnoticed for months. Ah well...Regards,D

Thanks Dave, There are few having installed the expansion, so I wait for an upload to the library.When you are ready with the expanded version contact me again to get tiles upgraded.They can't be loaded at avsim for policy reasons.If one of the few expanded region users want this version of Eisenberg I can send it by email.Deception Pass, north of Eisenberg 76s:-) Andre

As you might suspect I would be interested in the modified Eisenberg version that fits the expanded hi-res set-up.Hans Petter

As you might suspect I would be interested in the modified Eisenberg version that fits the expanded hi-res set-up.Hans Petter

Hi Hans Petter, yes sure I will send it ! after this restart I will take a second look at the elevation around Friday Harbor - still not adapted....later Andre

Thanks for the screenshots, Andre. Whilst I don't use FU3 anymore, it will always have a place in my heart, and those screenshots bring back happy memories. I particularly like that bridge!

As I added Eisenberg to the set of packages I hit the dreaded airport limit. The sim kept crashing until I removed another package. Since there's likely to be a few more airports as we focus on previously uncharted terrain, which ones should go to make room for the new ones? I'd say that real airports have priority and that fictitious ones that present a challenge come next on the list. Actually, we can keep them all as long as we remove the airport info from a sufficient number of airfields.

As I added Eisenberg to the set of packages I hit the dreaded airport limit. The sim kept crashing until I removed another package. Since there's likely to be a few more airports as we focus on previously uncharted terrain, which ones should go to make room for the new ones? I'd say that real airports have priority and that fictitious ones that present a challenge come next on the list. Actually, we can keep them all as long as we remove the airport info from a sufficient number of airfields.

I think comms frequencies will become a problem soon too (since I can still hear Everett ground when I'm parked up in Phoenix...). There just aren't enough sound files to go around. I can see heavy use of Unicomm frequencies becoming the norm.On a positive note, I just got my act together to use Cockpit designer and spend a very productive evening sorting out the rects in my favourite planes. Full AA & filtering and no 1 pixel gap, no mouse trails and no jumbled cockpits. Heaven!D