JGregory

You posted the same question yesterday (7355-x-aviation-saab-340a-doors). Please refer to my reply and do not double post.

You have a lot of plugins. I would suggest you remove all the other plugins (except Gizmo) and then see what happens. If you can then load the Saab, put the other plugins back in (one at a time) and see which one causes the problem

Standard camera controls will move you from the cockpit to the cabin. No other plugin is necessary. You will need to open the cockpit door as you can't "walk through it"!

Yes, they should be reset after engine start. Also, I noted in your screenshot that your prop RPM was very high... should have been around 1250. This would not have an effect on the pressurization problem you had... just thought I would point it out.

Glad you got it worked out!

Go here http://www.x-plane.com/downloads/landing/ and download the installer. Then run it and when it asks if you want to download the beta, DO NOT check the checkbox. Once it runs it will install any missing files.

Ned... The problem is NOT with the Saab... it is X-Plane itself. You need to update X-Plane.

Ned, Sounds like there is a problem with your X-Plane installation. You should run the X-Plane installer and it will update anything that is missing (make sure you DO NOT choose the checkbox for beta (unless you want to upgrade to 10.5 beta). Let me know how that works.

Ned, Can you confirm that you have the following file (cycle_info.txt) in your X-Plane folder.... X-Plane/Resources/GNS430/navdata/cycle_info.txt

Ned, I would like to see a copy of your Log.txt file as well.

Omar, I don't see anything wrong with your setup. The CABIN PRESS annunciator will light up when the cabin pressure is > 10k or the diff press is > 7.5. I assume the screenshot is from when you were still on the ground? Before the flight, did you reset the bleed valves? It would help to have a screenshot of the pressure panel when you are in flight, just prior to reaching 10k ft. ] Also, please send us (attach) your Log.txt and GizmoLog.txt files next post.

Learn, Please tell us what steps you took to try to pressurize so we can see what may have gone wrong.

More like the perfect storm. Developers do not usually diagnose problems or debug code in their aircraft if it is being run in beta software. Too many variables to deal with. That's why it is unlikely you will get any "suggestions".

No, we will not be using the "mixture" axes. We will most likely be using the "prop" axes, as that would correlate more directly to the function of the Condition Levers. I believe the mixture "issue" is a known bug and has been fixed for the next update.

I'll let the IXEG guys answer for their part of this, but, isn't Mac OS Sierra still in beta? If so, I would think that all bets are off with regard to X-Plane until Apple releases Sierra to the public as being final.

Pontus, I cannot completely diagnose what you are showing without a clear step-by-step list of what you did, with screenshots after each step. Like this... 1. Autostart. (screenshot (as described below)) 2. CL to max. (screenshot (as described below)) etc. The screenshots should be of the entire overhead panel, main panel, and pedestal... so I can see all the controls and annunciators. Also, please attach your Log.txt and GizmoLog.txt files from a flight where these conditions occurred.

That depends on a lot of factors, many of which we don't even know at this point.

Pontus, I cannot recreate the “state” of the Saab in the first picture you provided. I would also need to see the “entire” panel, similar to screenshot #4. In addition, when you provide screenshots, I need to know ALL the steps you took to get to that “state”. As for screenshots 2, 3, and 4: In screenshot #2 the right battery is powering the R GEN bus, therefore the annunciator is OFF. In screenshot #3 you stated that the right generator was on. Just because the generator switch is in the “ON” position does not mean that the generator is on. My guess is that the generator relay was open and if you had set the switch to “RESET the R GEN bus annunciator would have extinguished. Screenshot #4 is the same scenario as #2, the right battery is powering the R GEN bus. And, if the left engine was running and the left generator was on, the “closed” bus-tie would allow the R GEN bus to be powered from the L GEN bus. The Saab electrical system is fairly complex. There are many variables that can effect how the power is distributed. We have thousands of customers who have found the Saab to be a very accurate simulation. I am happy to answer most questions, but I simply do not have the time to explain every detail of the internal workings of the electrical system.

We have an internal work list but will not be making it public. A list will be published when the update is ready for download.

How is it a cop-out? The Saab 340 did not come from the factory with an FMS. MANY of them have had Garmins installed years later. Seems to me our our version is following what is available in the "real" world. The Citation II we are simulating also DID NOT have an FMS installed from the factory. And, the real world CII that we are using as a reference resource does not have an FMS. But, it does have two Garmins, a 430 and a 530!! We do have a business plan that includes aircraft with an FMS. This is a major undertaking and we will only do it when we can do it right. You have the right to buy whatever you choose. We respect that and we understand we can't make EVERYONE happy.

As you referenced, the memory being referred to in the installer is VIDEO memory. Not system RAM. Without more specific information about your system, I can't answer your question specifically. Video memory is that which is associated with your video card (the GTX660). The lights on the overhead panel indicate whether or not the "bus" is powered. The light are "OFF" when the bus has power. The GEN busses can be ON or OFF depending on many circumstances, and can be OFF even when the generator is running. Again, you have not provided enough information for me to give you a more specific response. You can "engage" the starter with the CL in the "Fuel Cutoff" position. This is known as dry motoring and IS modeled in our simulation. But dry motoring is not considered the "more correct" way to start the engine. The Saab does prevent the starter from engaging in certain circumstances, such as the when the engine is spinning down after being shut off.

Christian, It looks like you have a corrupted file, or a file with bad data. I think the best solution is to re-install the aircraft.

Andy, I'm only trying to explain what the Log.txt said. I cannot diagnose your system, sorry.

The Log.txt line that I posted indicates CPU memory, which is "regular" RAM. Many things can have an affect on memory usage.

The Log.txt does not indicate the specific reason for why X-Plane quit. However, this line in the Log.txt file is a hint as to what the reason probably is... "SkyMaxx Pro: WARNING! CPU free memory at 33148 KB. X-Plane may crash due to lack of memory. Close other applications, reset your settings, or remove memory-intensive add-ons such as photo-scenery." Meaning... you are exceeding your hardware memory limits.