A few things to figure out but overall I was very pleased with my first Cold and Dark startup test using the new Sim-Avionics!

Just got an email from Eren over at Revolution-Simproducts, you know, the company that makes the best TQ ever that I use in my cockpit. Well, now they are making Boeing 737 Landing Light Switches! Very cool and very affordable! If I didn’t have real landing light switches already I would be ordering these right away. Check out the detail!! Great job Revolution, keep it up!

Since my last major test flight, I’ve added many new things to the simulator. The overhead, the throttle quadrant, the interface cards, radios, the cdu and more. Well, it was time to run the test flight from KLAX to KRIV to test everything out! Found several bugs I’ll have to fix, but that is exactly why I do this test flight. Sit back and relax and enjoy the flight!

Holy cow, did one little job turn into a day of work!

So, this morning I decided I’d investigate why my Fire Warning light on my glare wasn’t coming on. I fiddled with the TSR settings, checked off a couple boxes and then well nothing worked. After checking them on, suddenly, my Fire Warning light worked. Go figure. My guess, a bad config file or setting in one and unchecking/rechecking those boxes resolved it.

Of course, since TSR is the one doing the logic, you can only initiate failures (that show up on real hardware) within TSR. FSX’s failures light like the software panels in FSX, but won’t interact with pmsystems or TSR it seems. Ohwell. Just means if I want to automatically do failures, I have to buy pmInstructor. Who’d of thought?

OK, I guess that was too easy for me. Because then I started on all these minor issues that I have just put aside, until today. I wanted to have better overspeed and stall sounds. I got those working properly in pmsounds.

Then, I wanted to finally find something for the tire scrubber sound and braking sound to be used with the autobrake pro of the TSR software. (Through pmsounds) I found some sounds, and now have those working, cool!

After that I found better cockpit sounds, better apu starter sounds, and a whole slew of other 737 sounds. I updated those in pmsounds, killer!

Finally, I had never addressed the issue of flaps within the PFD software. (That runs as an EICAS for my middle screen) If I set flaps 5, it would show 1 on the eicas. If I set flaps 15, it would show 5. So, I went into the PFD, the EICAS and the FO PFD software and set the aircraft type to CDU.

I then went into the CDUType file (that is OUTSIDE netdir…) and set in all my flap settings. The flap pos and rel pos should be the same. IE 1 and 1, 5 and 5, 15 and 15, 30 and 30, etc.

So FINALLY… if I call Flaps 15, it shows 15 on the EICAS.

Holy cow, really cool to get all those little things out of the way and working, finally!

Update: So after updating all my Project Magenta Software and following Nat’s tips below, I’ve successfully landed twice with the glideslope and the auto pilot. So far, so good! I’m going to keep testing.

Update2: All of my test flights have worked perfectly! I’ve manually entered in the fuel in pounds, and making sure my flaps are set properly at the right time on landing has worked perfectly every time since!

Ok so I’ve had this on again off again glide slope problem for ages now.

Click here to view a movie of the issue. I obtain the g/s, and then while coming in to the beam the plane just starts to climb.

I inquired to PM support, GoFlight support and put up a post here on the FDS forums.

Nat was kind enough to give me some tips:

One thing I noticed was that all of my project magenta software was out of date. I updated everything and unlike I did before in the CDU (Pressing the button to have the gross weight put in automatically) I put that info in myself.

Sure enough, I landed OK.

So, I’m going to try the flight 3 more times in a row to get a bigger sample size to see if the issue is indeed fixed.