Tim013

Well, I'm just glad the IXEG is still being developed. I don't fly it much because the FMC scares me. Too many times, it hiccups with a mid flight route, or approach change. I can't take the stress of sweating out the EXEC key. For now, other tubes satisfy my airliner simming. I still have confidence that advances will be made, and pushed out to customers. Tim

I don't believe the second modifier is accurate. Some where in the vast universe, there will still be a life form, that thrives in temperatures near absolute zero, still waiting for the 1.5.2 patch. Alternate theory: "heat death of the universe" means we will get the update when hell freezes over. Tim

Anticipation is half the fun. Just think how sweet it's going to feel when the 1.5.2 update drops in..................................... August. Tim

Ooooooh. That is a nice livery. Tim

I'm liking the sound of 1.5.2 for sure. The 340 has been in the hangar awaiting this update, and I'm stoked to get it out and fly it again. Tim

Yeah, icing in XPlane is a little messed up right now. I personally have a hot key set up to turn on all anti-icing under the general Xplane commands. This stops the crazy high ice accretion rates. Tim

Yes, there is a REX training video on YT that shows this sunlight effect, causing the annunciator lights to washout. Unless v1.5.2 is going to include a virtual hand to shade the annunciator panel, I think they should be made brighter to accommodate X-Planes lighting limitations. The annunciators are visible more times than they are not. Tim

Glad to hear 1.5.2 is still in the works. The SAAB hasn't seen much air time since the A/P issue with 1.5.1. Tim

Great news that the AP will be tweaked. That is much appreciated for sure. Only other thing I'd like to see addressed are the annunciator lights on the instrument panel. They glow dimly at night, and are not visible during the day. Not a need to have, but would be a nice to have tweaked as well. Either way, version 2.0 will be a first day buy for me. Tim

A single joystick button assignment to toggle both CTOT arming switches. It would be nice to be able to activate both CTOT's with one joystick button, without having to look away from the runway. I've seen a few videos online where they don't activate CTOT until takeoff power is set on the takeoff roll. It would also help during landing as well. Just a thought for the next version Regards, Tim

Nice! That is so good to hear, and every SAAB driver is going to appreciate that a lot. I'm kicking myself for sitting on the fence way too long before buying this addon. It is such a fun aircraft to fly, and reminds me a lot of a baby MD-80, with all of the quirky procedures. One last thing, that's not as important as the autopilot, would be a fix for the system status annunciator panel lights that don't illuminate during daylight. (L BETA, AUTOCOARS ARM, etc...). Certainly not a deal breaker, but the light show during start up and departure is unique to the 340, and would be fun to have working. Finally, you have a definite customer here for version 2 whenever it comes out. I absolutely love these "transition" aircraft; not quite all steam gauge, not quite electronic display, and just automated enough to make things interesting. Thanks again for updating the autopilot. Regards, Tim

After gaining more time in the SAAB, which I'm really liking a lot, I too feel the autopilot bank angle is too shallow. It's typically turning at 15 degrees maximum, which is undermining itself when it comes to course intercepts. I get a lot of course scalloping and bracketing, to the point where I manually fly a lot of the sharper intercepts, rather than let the autopilot struggle. This isn't ideal when flying single pilot, in a two pilot certificated aircraft. I know version 2.0 is in active development, but I'd love to see a small tweak to the autopilot bank angle. Tim

Not just you. I bought the SAAB over the past weekend, and flew it a lot. It's a very enjoyable airplane. But, the audio issue you described is kind of annoying. With other default or addon aircraft, it doesn't matter when or how you plug in your headset, and it doesn't matter if it's jacks or USB. Only with the SAAB does it take one or two restarts of X-Plane to get all audio coming through the headset. Tim

Thanks for pointing that out. Tim

This is what I'm talking about. Anyone else have this happen? tim

Flew online today. The pilot and first officer side altimeters were reading 300 feet low. I was level at 13,000 feet. Both captain and first officer altimeters displayed 13,000 feet. The standby altimeter was reading 13,300 feet. Yes, all the kollsman windows were set to the same barometric pressure. Vatsim ATC showed me as 300 feet high from my assigned altitude, indicating 13,300 feet on their radar displays. Anyone have any insight for me? Just bought the SAAB yesterday, and would love to fly it online more. Thanks, Tim

That is very helpful. So it is needed for the AP to fly the couse, and the closer the course is set to the published course, the better. And if you are hand flying, then course setting doesn't matter, and you will still be able to follow the raw data of the localizer and glide slope in the form of the magenta diamonds. The reason I ask is I was watching a streamer who has a basic understanding of flying IFR, and he forgot to set the course for the ILS. Upon LNAV intercepting the localizer, the AP then proceeded to turn away from the localizer. He had the approach course dialed 150 degrees off of the correct course, so it got me thinking about "modern" AP's, FMC's, and PFD's, with regard to the raw data of a simple VHF receiver and pilot controlled OBS knob. Tim

This is more of a developer/Jan question; In a simple aircraft with, say, a BendixKing KX-155, dialing in the localizer frequency will allow you to track the localizer, regardless of how you have the OBS set. In other words, if the ILS front course is 275 degrees, even if you have the OBS set to 010, the KX-155 will still track the localizer, and the needle will center when you fly the correct heading. The rotating OBS setting means nothing to the receiver, and is irrelevant. My question is this. In the IXEG 737-300, what role does the course setting on the MCP play? If I have the correct localizer frequency tuned in the VHF radio, does the course setting in the MCP have any relevance, or is it just a reminder to you what the published course is? If the published front course has to be dialed in, how far can you deviate from the published course for the A/P to still track the front course? Is there a front course + or - a certain number of degrees wiggle room for the A/P to capture and track? Tim

That's good to hear. So if I download and install the update, I won't have to fiddle with Gizmo? Tim

What are autopilot modules?

I downloaded the installer this morning, and was so close to updating, but didn't. I think I'll stay with 1.2 for now. I hate self inflicted computer issues......LOL Tim

Sounds like you need more beta testers who are more representative of the community, and run multiple plugins. Of course there's no way to identify every conflict, but a general issue like "a lot of plugins" would be easily caught. Tim

Hey, that is pretty slick! The developers are going to hate it, since they've held fast to no pop outs, not even the FMS, saying it destroys the immersion. I like that script a lot. Nice work. Even though I'm at work, I just snagged it, in case they remove it....LOL!! Tim

What's this VNAV you speak of.....LOL. Flight sims are already nothing more than button pushing simulations. For me personally, I use LNAV, and the MCP for forward velocity, and vertical velocity. The funny thing is there has never, and I mean never, been an add-on aircraft that has been developed, that flys an acceptable VNAV profile. That's why I don't get whipped up over the VNAV shortcomings of every add-on. Tim

Looks good. I'm 99% sure this is my next purchase once 1.5 is released, and I can see some youtube reviews. To the AP issue: It seems that the oscillation, or porpoising at altitude, is an XP11 "feature" at this time. That issue has cropped up in other aircraft too, so it may not be the SAAB's fault. When you are satisfied with the progress, and send it to the store, will you be publishing a change log so we (as in prospective buyers...) can see what was done to make the XP10 version, a XP11 version? Tim