Strange, I have never gotten credit for a separate failure points wise. It does say that it noticed a failure etc... But I also never said it was a problem or would cause one if you left them on. I still recommend having others off because if you do get one that FSP doesn't recognize, you will need to land of course and if on a long flight FSP will penilise you for not landing at the correct airport as well as other things. I have owned FSP for years and never seen it recognise anothers failures the way you say. One issue I have that's not really an issue, is with the Duke B60 I often have it tell me something went wrong in flight and I must have failures on in another failure generator even though I do not. It doesn't deduct anything of course but wish I knew why it thinks the Duke is a flying failure :(

Hi Derian,Glad to help and glad to see you got the plugin working. As for FSP/Concorde. I don't know since I don't own it. I would check the FSP forum if no one here can vouch for it. I couldn't see why not since someone will surely create a profile for it if they haven't already done so.

Compatible, just makesure you disable the max descend rate stuff, as the Concorde tends to descend at 5000+ fpm ;)

I've have'nt used it lately,mostly I just straight up go flyin.......LOL I should get back to using it.:(

A question about FSPax from my side:The failures work for every FSX aircraft automatically or something needs to be tweaked in there? And how often the problems occur? Random? Thnxx

it works automatically but may be forced by modifying "manual_failure.cfg" placed in SimROOT\FsPassengers\config directory.

Strange, I have never gotten credit for a separate failure points wise.

I could be remembering it wrong. I do remember it saying that there was a failiure and the FSPax beleived it was caused by the add-on aircraft itself, and I thought I remembered it even knew what the failiure was (Gear wouldn't lock down iirc)One failiure I have always found to be an adventure is engine failiure on takeoff. The first time that happened to me (in the Coolsky Super 80 Pro), I learned my lesson to watch those engine readouts very closely when first throttle up to mid power. Had another incident about a month ago on VATSIM, using the Leo Maddog out of St Louis. Sadly, that ended in tragedy, landing in a guys pool instead of being able to make it back to the airfield.

Hi Derian,Glad to help and glad to see you got the plugin working. As for FSP/Concorde. I don't know since I don't own it. I would check the FSP forum if no one here can vouch for it. I couldn't see why not since someone will surely create a profile for it if they haven't already done so.

Alright cool, i'll go ahead and buy the concorde then. I'm in for a good year of studying to learn how to fly that old beast xD

I have thought about getting it and getting it as fast and high as possible then opening my doors to see how fast my passengers start to drop off, haha.

I just wanted to update my posting that FSP did not award points for failures outside of itself. I noticed this morning that it actually does, but not in the way it should to make it worth the effort. Either way, I was wrong Scott and you were 100% correct, sorry about that :wink:However, what I was going by in my head is still important for me being that FSP does infact award 50 points for a failure outside of its own failure system, but that's it. The main part of FSP's points are in it's failures and the ability for the pilot to react correctly. So one failure could generate several hundred points for each failure. I think the main thing is that if you have a major failure from say the PMDG failures while using FSP, you will be penalized if you follow correct FSP procedures after. That being if you declare an emergency (another spot that gives a high value of points, plus you will be forced to land at an airport other than what's specified. That isn't a huge deal since you can cancel your destination in the FSP menu.Some failures also award a high amount of points if the pilot performs certain procedures but it depends on what your options are. One instance is if you declare an emergency you're suppose to change your squawk code to 7700 (there are a few different codes for various situations). So all in all I just don't like the amount of points I lose to justify having an outside failure. The trade off is too large, 50 points for a possible few hundred you may have gotten otherwise.Anywho, I just wanted to clarify and point out that Scott was correct and I was wa wa,,, wrro,,,, ummm, not correct :(

One last thing I feel I need to add...If through my encouragement and/or bragging of this product has caused anyone to get it, then feel free to question me whenever you'd like for support since I feel responcible should anyone need to suffer in it's forum. The absence of the Developer Dan,, has really set their forum well below acceptable in every way imaginable.Just this week alone I have had 4 posts deleted that actually answered the OP's question and just went there to check on some others and saw this, hahaha.Talk about coming to the party late with the wrong info...http://www.fspassengers.com/forum/read.php?f=2&i=27964&t=27964This is a very common thing there, and happens all the time, so just wanted to offer my available brain "Cell" if anyone has issues and cannot get answers or rather not subject theirself to utter agony of their recent forum.

Hi Dan since ur in the helping mode in the fsp :) when flying the md-11 i keep getting the pen for the strobe not being turned on when entering the rwy although i switch on the landing lights and strobe on at the same time but i dont get the pen for the landing lights. I suspect its a bug for pmdg aircraft

Well that particular topic is a pretty hot one at the moment and would first read this:http://www.fspassengers.com/forum/read.php?f=2&i=21895&t=21895If you still have questions, let me know. Personally I never ran into any issues with it, but have them mapped to toggles to throw on as soon as I am entering the runway.

Hi Dan yea just read the lat post in fsp he last one wasnt there the last time i checked. Anyway i have tried every which way to not to get a pen for he strobe for entering the rwy, i used the key board shortcut and using the switches in the overhead panel but to no avail. The strange thing is that i dont get a pen for exiting the rwy only for entering the rwy so was wondering when do u turn on the strobe?

Hi Peter, I throw the switch for the strobes and landing lights just as my nose is entering the side of the runway (shortly after the hold short markings). I actually don't normally run with light penalties on because of some other inaccuracies, like I like to put my landing lights on when crossing other runways and then off again once clear and FSP doesn't seem to know why I'm doing it. I also like to come to a complete stop once cleared the runway I land on and start cleaning up the aircraft but like the issue your seeing, FSP expects my lights to be of ASAP without giving me a couple seconds to get to them sometimes.I wonder if maybe there are certain airports that maybe the AFCADs are just messed up and FSP thinks you entered the runway sooner than you have?

I actually don't normally run with light penalties on because of some other inaccuracies

Same here. It has issues with many addon aircrafts, like the PMDG JS4100, where Conspic lights are what FSPax calls Landing Lights. Also, it is SOP on most aircraft that when you fly through a cloud in night time, you turn off the strobes, as it becomes blinding as the clouds reflect the light back toward the plane, another thing FSPax does not like to see. and just to add, as far as the landing lights being off ASAP, while it is very very hard to do in FSX if you do not map those lights somehow to a shortcut button on your yoke, this is infact how things are done in real life, those landing lights go off immediately. Been on planes where they go off while the plane is still in the runway just starting to turn off. But I figure like you, I am doing the best I can, get off my back FSPax!Cheers