Thursday, November 12, 2009

Lake Spotting

Decided to head back to the mountains today. When I started that way yesterday I could see some lakes off in the distance, so before getting in the plane tonight I got on Google Earth and came up with a flight plan. Heading ENE from Dalton you can fly over three lakes in a sequence, staring with Blue Ridge Lake, about 30 miles away, and then Nottley Lake (Blairsville) about 10 miles after that, followed by Chatuge Lake about 15 miles further out. There's a little airport in Blairsville, so I decided to take off from Dalton, head east-ish and fly over the lakes, then turn around after the third lake and land at Blairsville Airport to take a break.

Had a nice take off and climbed to a couple thousand feet before turning east. To make sure I didn't run into a mountain, I decided to climb to 8,000 feet above sea level, which is a good 2,000+ feet higher than the highest mountain in Georgia. At around 6,000 feet I started getting into clouds. They're one of the more realistic features in FSX:


At this point I'm roughly over Fort Mountain. I believe the road winding away below me is Highway 52. Anyway, I got to altitude and proficiently trimmed in for about 100 knots and holding my altitude between 8,000 and 8,100 feet. From there, the lakes were easy to spot, as was the airport. After about 30 minutes of flying, maybe a bit more, I got to the final lake and turned around, lining back up on the Blairsville runway.

As is my habit, I came in too high and too fast. I've really got to work on that. I landed pretty rough, with one tire in the grass even. Of course, that still counts as a landing, so I taxied to the one building and take a break. After reading some bed-time stories (to my son, not to the folks at the airport), I got back in the plane, taxied back out to the runway and took off for home. This time I settled in at 5,000 feet, which feels pretty low when you're flying over some of those mountains. While cruising, I got this close-up exterior view showing the detailing of the aircraft models in FSX:

Pilot looks kind of nerdy. I hope in the next version you can pick a different outfit. Anyway, a short while later I found myself almost out of the mountains. From the cockpit, I could easily identify Ellijay to my south and the major highways in the area, including 52 which crosses Fort Mountain out of Chatsworth. In fact, here's a picture from the cockpit just south of Fort Mountain at around 4,500 feet (after I had started my descent):

The winding road starting on the far left and then cutting through the image is Highway 52. I've ridden that climb from Chatsworth on my bicycle up to the Fort Mountain park entrance. Takes about an hour at the rate I climb. Anyway, there are two peaks in the foreground, one on each side of the support strut you can sea outside the window. The peak to the right of the strut, and further away from me than the left-peak is Fort Mountain.

So from there I continued my descent towards the Dalton airport. At about 2,000 feet I banked to the right to fly the downwind leg parallel to the runway, flew out over Dalton, did a 180, and continued my descent to land. This landing was much smoother than the one in Blairsville.

Wednesday, November 11, 2009

Touch-and-Go

Had a little time tonight so I did some daytime flying in nice weather for a change of pace. I decided to work on landings and the easiest way to do that is to fly touch-and-go patterns where you take off, circle the airport, land and then instead of slowing down and pulling off the runway, you go back to full throttle and take back off again to repeat the process.

Here's a nice shot of me flying the down-wind leg on one of the loops: As usual, I'm probably higher than I need to be and too close to the airport, but the clouds sure are pretty.




All three landings were successful - meaning that the airplane was still flyable afterwards. The middle landing was a little bouncy though. Need to work on that.

Here's another nice shot, especially of the clouds, showing me
crossing the end of the runway about to land:

A little later in the evening, I had a chance to fly again. Took off thinking of another touch-and-go, then decided to fly to Chattanooga, then changed my mind and decided to check out the mountains to the east. While approaching the mountains, I spotted another plane, which is rare because I have other aircraft traffic turned down very low. I wouldn't have seen it at all, but FSX flags other planes in the sky for you with their name, altitude and distance. I spotted that text long before the plane, but out of curiosity, I gained altitude and tried to intercept. The closest I got was about 1.1 miles away and about 3000 feet below him. Using the zoom function, I was able to see the actual plane and to get this image:
OK, not much to look at, but even at this resolution you can see a little dot below the red text. It was a Piper Cherokee 180 flying south at about 8400 feet.

And how about that daytime crescent moon?

Tuesday, November 10, 2009

Night Flying

I got home from work today and it was dark and rainy, perfect flying weather! OK, I know I can turn the rain on and off in FSX any time I want to, but there's something appealing about flying in "real" weather. I guess the rain in the simulator and the rain outside the window of my office just work together somehow.

I fired up the simulator and did a couple of pattern flights (take off, fly the pattern, land), just around the Dalton airport. It wasn't actually raining during the first flight, but it started pretty good by the second. Here are some screenshots - including some improved external views since I learned you can pause the sim, then change views, grab the shot, switch back to cockpit view, and resume flying:

As usually, coming in too high.

Too high? Really? From tower view it looks like I'm about to clip those trees.

Looking better. Red-over-white and clear of the trees. Hard to see the rain at this resolution.

Over the runway with landing lights on. Notice that the wind is pushing me off to the right so I've angled the plane to try to stay off the grass when I land.

Flair before landing (pulling the nose up so I touch down on the rear wheels only and at lower vertical speed.

Touchdown! Notice the puffs of smoke coming off the rear wheels and that my nose wheel is still off the ground. You can also see the rain better in this shot.

Well, enough fun for one night. Oh, and these are higher-resolution images than before. Right click and select "open in new tab" and you'll see the full sized version. Much easier to make out detail that way. Oh, and these two flights make my third and fourth successful landings with medium realism and crash-detection turned on. Woo Hoo!

Monday, November 9, 2009

Dual Monitor Test

On a lark, I decided to steal, er...borrow, my childrens' monitor (after they finished their homework of course), and see if I could get FSX to run on two screens.

It's actually easier that I thought, although you really need a stronger video card to drive two screens properly. More on that latter.

You start by setting up Windows for multiple monitor support and for extended desktop, where Windows treats the two monitors like one extended screen. Then you launch FSX and start a mission or free-flight or whatever normally. Once in the simulator, you activate the menu, go the view menu, select new view and then virtual cockpit. That opens a small window, sort of like a picture-in-picture on the main monitor, which you then drag to the second monitor and resize to fill the screen. Finally, you adjust the view angle on each screen so they line up correctly or as close as you can get them.

Here's a photo of the results:
A laptop with widescreen sits a good bit lower than a standard monitor on a stand, so I had to put a phone book under the laptop to compensate. The effect is still not perfect, but you clearly get a better view than with a single screen. Imagine three screens, and the peripheral vision effect you get from that!

As I mentioned earlier, my laptop's video capabilities were not made for gaming, so forcing it to output twice as many pixels resulted in a noticeable reduction in frame rate, to the point that it made flying more difficult. I still managed to take off, circle around a bit and land without crashing, but the landing was not pretty. The lag between control inputs and the screen updates was hard to adjust to so there was a lot of over-correction on the approach.

To make this work with acceptable frame rates I'd need to reduce the graphics quality a good bit. Then the question becomes whether that's worth the extra screen real estate you gain from this setup. With a desktop system and a gaming video card, you probably wouldn't have to make the trade-off.

The other thing I noticed, and perhaps there's a work around, is that only one screen is "active" at any given time, and only that screen pans when you change your point of view (looking left or right for example). Thus, any effort to look around breaks the illusion that you're looking at one really wide screen. Maybe there's a way to lock the screens so they pan together, but I've not figured that out yet.

More testing to follow...

Sunday, November 8, 2009

Getting Real (Part IV)

Touchdown (the crowd goes wild):

Actually, this is another tower-view image, taken shortly after touchdown. I was a little too busy to take pictures during those final moments, but I'm happy to say that even with crash detection turned on and reality set to medium, this counted as a successful landing. You can see that I'm a little to the left of the center-line, and have full flaps extended.

Satisfied with my accomplishment, I slowed down, exited the runway, and began to taxi back towards the hangers. Here's another tower-view image of my on the taxi-way:

I don't think the trees are actually that close to the airport in Dalton, but I've not been out there in a while. The runway that I've just pulled off of is at the bottom of the image.

OK, so this wasn't much of a flight, but as my first flight at medium reality and first with crash detection on, I suppose it counts as my first "real" landing. Congratulations to me on that one.

I completed the mission by returning to the hanger area, parking and turning off the engine. Here's a final exterior view of me proudly sitting in my parked plane without a scratch on it:







Getting Real (Part III)

After some mid-air course correction, I finally got sort-of lined up for landing and started my descent. In this image, you can see that I'm not lined up correctly and that I'm too high based on the white-0ver-white landing lights at the end of the runway:

Actually, at this image size, I'm not sure you can see more than a singe white dot towards this end of the runway, but trust me, I'm too high.

After banking left and then back right, reducing power and pulling the nose up, I got the plane into a steady descent on the proper glide slope and aimed at the runway. Here's how it supposed to look on final approach:




Again, at this resolution I'm not sure you can see the individual lights. Maybe they look a little pinker, but it's actually two sets of lights, with the top set showing red and the bottom set showing white.

I also took the few seconds I had before touchdown to switch to tower view and take an image of myself as seen from the control tower. Not much to look at without a zoom function or a good pair of binoculars, but here I am:


Actual landing photos coming up in the final post of this series. Future posts won't have this many images, but my sister has suggested that some of my earlier posts lack visual appeal, so I'm trying to compensate.


Getting Real (Part II)

As I continued climbing, I next took this picture looking directly behind me at the receding airport. During the takeoff, I did notice the airplane pulling to the left. That's one of the realism settings that's turned off on "easy" mode. Engine torque and several other factors cause single-engine planes to pull to the left, especially during take-off. The effect was manageable though, even without rudder peddles, but I suspect on "hard" mode you probably do need direct control of the rudder, and "auto-rudder" turned off to compensate for the added realism.
Anyway, I climbed up to about 2000-2500 feet above sea level (airport is at 714), and then banked to the left and did a 180 degree turn, heading back in the opposite direction. As I took off into the wind, this part of the flight is called the down-wind leg. You can see the airport off to my left in this image:

I continued in this direction, trimming out for level flight around 2500 feet, which is a bit high really for flying the pattern since I'll need to be about a thousand feet lower after I make the turn back towards the runway.

As I flew past the airport, I took this image showing the various hangers and buildings modeled in the program. Oddly, Airport Road, which runs along the far side of the airport when viewed from this direction, is not shown at all in FSX. It makes the airport look like its just out in the woods, inaccessible except by air. I suppose if they ever get MegaScenery Dalton posted, I can fix that:

I continued past the airport, but without realizing it, I let the wind push me in towards the airport, and push my heading slight to the west. Thus, when I turned 90 degrees to my left, and looked out the window, I was well past the airport and had to do a 270 degree turn back to the right to line up for landing. I'm sure that's not how you're suppose to do it, but it worked for me this time. More landing images coming up in the next post.