Polar1955

After flying the FF 757, 767 and IXEG 737 for last 6 to 8 months, I decided to go back and begin flying GA acrft as I usually do when jets nn a rest. When I loaded XP10 and tried to load a GA acrft (3rd party and XP acrft) they too crashed the sim. At this point I knew I had a problem w/in XP, not the SAAB 340 update. After performing 4 typical checks with no positive results, I had one last thing to try, the Nav Data update done back in June. After activating the original GNS file in the Resources folder of XP, my problem was solved. This did not show up in my Log file or Gizmo file. One thing I learned many many years ago, always back up files with any change made. I hope my error here will save some poor soul in the future.

The suggested fixes do not work, acrft will not load. Is there anyway to re-install the previous version?

Ok, Thank you...same scenery as before however and no additional plugins since last update of Saab but will give it a go

Still no airplane to fly

I have downloaded the new update for Saab 1.4.1 several times still CTD. I have tried two (2) different drives and nothing seems to work. I am using XP 10.51 and up till now all updates and the acrft have loaded with no issues. I have included my Log Text and Gizmo text. Any ideas? Thank you Log.txt GizmoLog.txt

Thank you, I will look this over

I like number 1 solution will have to try WED, had something like it in FS9 and used it for adding objects, ramps etc.

I like the the startup procedures, never been one for the short cuts, I will take your advice on saving situations, only problem so many airports do not have a parking space which I require eg. cargo, and thus saving those arrivals saves a lot of time for the departures, but I will give it a go. Thank you for your input

Thank you mmerelles appreciate your explanation, I am aware of the custom views and use them all the time. As for the tech XP CL vs Prop, etc. Thank you for those explanations. There are so many things about XP I really like over MSFS and thus I have not flown FS9 since my first day w/ XP. I had a lot of stuff w/ FS9 and I have just wrote it all off, I do miss my PMDG stuff MD-11, 747, Feelthere ERJ's and EMB's and Ifly 737's planes that gave me thousands of hours of flying fun, and I mean thousands. But I have been doing a lot of GA flying since moving to XP, and enjoy it. Hoping for some improvements in XP to bring it up to par w/ MSFS in some ways, seasons eg. but overall it has been a great change and wish more of my fellow MSFS would see the great things XP provides. In your explanation regarding complex acrft and plugin problems, is it then best not to save too many or no situations?

First, your views are saved with each aircraft automatically, That's good to know

"Saved flights", under XP menu "File" then "Saved Situation" I guess I am accustomed to MSFS after 15 years and am still learning about XP, Saved Flights vs. Save Situations. So under this menu of XP, I saved acrft situations which save my cockpit views for each acrft so I don't have to redo everything each time I load a different plane. Now as for the control axis, those are under another setting of XP and as you know are universal for all acrft, my thought is that if I save a situation such as an acrft which uses the "Prop" axis assignment and then disable that axis and assign "None" to it for an acrft such as the SAAB, is it possible that the previous "Prop" axis assignment is somehow interfering with the SAAB because it has been saved in the "Save Situation" for another acrft even though it has been assigned "None". XP or the SAAB have retained the initial program setting for the axis, in this case, fuel cutoff. Now exit XP the fuel cutoff axis left in the full detent position and then loading XP and the SAAB with that lever still in the full detent position has been retained by the SAAB even though that axis will be changed from a "Prop" assignement to "None". The SAAB for whatever reason will read the axis as in the cutoff position no matter what is done in the "Settings " menu after XP is loaded because the setting is universal for XP and the SAAB may not be able to read the setting difference once XP is loaded. To correct this I place the axis in the full up position before loading XP and thus once loaded the axis is not being read in the cutoff position by XP and hence the SAAB. Start the SAAB re-assign the axis to none and go from there, it is working for me with this procedure. Seems unlikely but is the only explanation I can come up with.

The condition levers, CL's, or props in XP. Did you see my post from above July 10, here it is, "Is it possible that saved flights having the CL's, (XP Props) assigned in another acrft in XP joystick settings is the reason why these levers must be full forward even though they have been disabled in XP after starting the SAAB. I have saved flights in XP using other acrft eg Carenado planes w/ the levers already assigned, as well as views then disable the CL's in order to fly SAAB as the instructions indicate must be done, the saved flights remain, do these settings fully get disabled? Hope this makes sense.... By the way I removed Xassign some time ago because I felt it was not necessary as long as I saved a plane type w/ my views etc. for that acrft.

The levers were assigned CL's, but after starting XP and SAAB they were assigned None as per instructions.

You have solved the problem for me, I have had no problems starting engines as long as I move my CL's full forward before starting XP. Six (6) flights over past 3 days.... P.S. No Cl assigning issues either

Have you tried before loading XP pushing your control levers full forward, so as not to load levers in fuel cutoff position? Then removing the CL's assignment in joystick menu to "None" If need be, reload XP w/ the above completed, I would like to know if you are experiencing problems after doing this?

Two flights tonight and no start problems using procedure I have spoke of in previous threads , still an issue w/ assigning the right CL but has not required a restart of XP, I just played w/ said lever until the lever was properly assigned and moved as designed. JGregory I think moving the condition levers full forwards before starting XP is the solution, seems odd, but I have had perfect starts by doing this everytime so far. Is it possible that saved flights having the CL's assigned in another acrft in XP joystick settings is the reason why these levers must be full forward even though they have been disabled in XP after starting the SAAB. I have saved flights in XP using other acrft eg Carenado planes w/ the levers already assigned, as well as views then disable the CL's in order to fly SAAB as the instructions indicate must be done, the saved flights remain, do these settings fully get disabled? Hope this makes sense.... By the way I removed Xassign some time ago because I felt it was not necessary as long as I saved a plane type w/ my views etc. for that acrft.

I don't know what it is w/ this throttle system etc. but I hope I have it fixed. I am sure the developers had their reasons for the CL's being set up the way they are but not being a pro, someone will nn to explain it, I have never seen anything like that before, usually once the controls are set up it works that way for all acrft. The throttle pop up to me is very understandable due to the various throttle positions for the SAAB. Many Thanks to JGregory for his insight and help on this problem I hope the karma lol stays w/ me us.

Thanks, I was aware of that and just forgot to change those settings, in any event I fired up the acrft w/ no problem, I will continue to fly the plane and if the described procedure I am following fails I will contact you. By the way, after changing the CL settings in the assignments of XP I did assign the Cl's in SAAB pop before starting the engines,( I still had the levers full forward before starting the XP) not sure why this is necessary but it works.

Some good news: Did not reboot computer w/ each attempt, reloaded XP for each of the 4 starts I got 2 good starts w/ CH condition lever axis out of the detent position and levers full forward, did not assign levers till both engines started. With CH levers in the full detent on third attempt the engines failed to start The next attempt number 4 was a success using the new procedure. It is late here but I did have issues assigning the condition levers, getting axis 13 okay what should have been axis 12 was getting the number 10 on 2 starts, was able to correct on the 4th. I will look into this tomorrow to insure it is not me or my axis levers. Important note, the levers must be full forward before starting XP Your idea seems to have real promise here, good work

So what are you telling us we should do, push the condition levers for the CH axis to the full up, before assigning them? I will try starting with condition levers full forward ( and using only SAAB controls) then after start if successful will assign levers for the CH axis. You may wish a step by step procedure so as to make it clear as to what to do. If I read you correctly, this is something I looked into and tried, I will try again so as to see if it does fix the problem. I got a good start using the above procedure as I outlined, I will nn to try this many times to see if your idea continues to work as I have had times where I can get multiple starts before encountering another bad series starts. Thank you for your idea, hope this is the fix

I have had this problem since I purchased the acrft over a year ago. It seems to be a random problem, but the problem is more then not, and not even the auto start will get it going. I was a MSFS user going back to FS2000 until switching to XP last year and all my experience has led me no where for a solution to the problem. Cameron gave me some ideas to check but they did not pan out as the possible cause. I am hopeful that a solution may be found as I love the plane, but as of a week ago I gave up on my abilities to find the cause. P.S. I might add that when I first got the plane it was the only add-on I had so I don't think it is any plugin, etc.giving us grief.

The folder (opensceneryx) is the folder which is placed in the custom scenery of XP , correct....new to XP Thank you for all your great work