Althar93

Thanks for the info, I will patiently wait for the next update to what is already a phenomenal piece of software. As for the failures, I do quite enjoy them and the fact they keep me on my toes & require me to practice emergency procedures for when it does happen. Funnily enough, I tend to react to bugs in the same way I would to genuine failures. I might have to video record/capture the flight next time round in case I need to go back & see where & when I went wrong. I have not seen any IVAO/X-IVAP/SAAB related conflicts/issues mentioned on the web and/or in this forum so it is unlikely there is any correlation but the fact that I was supposedly operating within the standard flight operations makes me skeptical. So far, I must have flown 10/20 flights offline since I bought the aircraft with no issues, whereas the only 2 online/IVAO flights I attempted have resulted in engine fires only a few minutes after takeoff (roughly in the same place & time) As for my previous "stress-test", I kept the sim running for an extra 20 minutes or so (so about 40-50 minutes of deliberate engine stress), flying straight at 2500ft AGL with max power, max condition levers, engine temperatures above 980, torque & all dials in the red & beyond for the whole duration but nothing caught fire...

I will make sure to check next time - I was very careful with the engines : My settings were as follows : CTOT set to 100% (so reduced from the prescribed 108%) & disabled before initiating the climb Low climb mode Odd thing is that I am currently running a test flying session offline just pummeling the engine (max power, max conditioner lever, CTOT to 110% during takeoff), with temperatures way above 971 for both engine. This test has been running for well over 30 minutes now, yet the engines haven't melted down yet... I want to believe I did something wrong twice in my two online flights but I can't really get my head around why when being careful things go wrong & when being wreckless & pushing the engines, all goes well...

Hello, I seem to be experiencing a recurring issue with engines failing/catching fire (my two first IVAO flights with this Aircraft in a row now after a few flights locally with absolutely no problems) - for now I will attribute this to my inability to properly operate the aircraft. That being said this is also the second time I have experienced the same somewhat annoying bug, specifically, the repro is : Right engine fire Pull the right engine fire handle Causes the Gizmo log to print out the following error : error: 2218.238: RunLuaFunction(xp): main: [string "JGX.1.Saab.00.lua.aes"]:8357: dref.setInt: Expected two arguments. Following this, power levers & conditioner levers remain stuck in place & become unresponsive to either the Joystick input, Keyboard and/or mouse The remaining engine cannot be turned off & will keep delivering the same amount of power that was showing on the dials at the time of pulling the lever. I was thankfully able to turn back to the airport (this was shortly after take off at 2500ft AGL in the initial climb), land & slam the brakes to kill off the 185kt of thrust still produced by the left engine which I was not able to power down and/or turn off.

Hello again and thanks for the swift reply. I have only experienced this issue once so far. I will remember to have my screenshot app running next time to capture it if it does occur again. As far as I remember both props were rotating perpetually following the failing starts - this may be due to me not aborting the start up properly but would explain why the autostart did not work afterwards either. Anyway, I will keep and eye out for this glitch and report back with more information if it does happen again. Cheers,

Hello all, I have recently purchased the SAAB 340. I am still in the process of reading through the systems manual, practicing various situations & getting myself familiar with the aircraft but so far I have been loving it. I really admire the dev's rendition of the plane & they have done a phenomenal job. Unlike a PMDG (or just Boeing), or a fair few of the paywares/aircrafts I have bought in the past, which are of high quality but tend to feel very clinical, the SAAB just feels genuine, with its assets & flaws (yes heading knobs I am talking about you...). Anyway, enough with the introduction - I have recently been experiencing what I believe might be a bug (could well be my inability to operate this plane): I fired up a flight yesterday & during the preparatory checks I noticed the fuel temperature was only +02C I attempted to start engine #1 from external power but this failed : The engine oil dial rose to about 30-50 & did not go any higher The engine temperature rose to 20C & never went down even after the failed start The propeller did start rotating (visual & audio cue) but complete ignition never happened The engine RPM rose somewhat & then just stayed there (can't remember the value but it was pretty low) After the failed start, I attempted engine #2 with exactly the same issue - a few additional attempts later, the "L Alpha" & "R Alpha" came on & I could not figure out how to turn these off / heat up the engines/fuel. Finally, after half an hour of struggling I decided to try Autostart, which also failed with "RPM too high" (which I presume was due to the needle that never went down again) Does this sound like a bug, or does the aircraft actually model fuel / fuel line freezing? If so, how do I heat up the fuel/engine again using external power / batteries? I can attempt to repro the situation again if fuel icing is not something that is modelled & this is a genuine bug. Thanks in advance for any feedback/answers,