Daedalus,

 

don´t know if this might help you or others, but i can tell you what i have running on my P3D V3.4 system. (See System specs in my signature) :

Orbx with all the bells and whistles, AS2016+ASCA,EZCA,loads of payware Airports (Flytampa, Taxi2Gate, UK2000, etc)

PMDG NGX+777, Majestic Dash, and so on....

I´m not using Nvidia Inspector, but using DSR instead, ingame AA, Vsync on, Triple Buffer on, frames unlimited. Usually i get around 40-50 fps, smooth and no stutters with PMDGs and dense scenery settings and that´s what i get with the TFDi as well.

 

Lars 

 

Thank you Lars. I have something smoother now. I restored the nvidiainspector profile to default and overcloked again, it is fine now. Unlimited fps always give higher frames but locked usually is smoother. Still testing.

Do you think watching some MD-11 tutorials would help understand this aircraft more?? Years and many hours of flying the NGX and I admit to being a bit stumped with this one!!

Yes! The FMS (MCDU) and autopilot are very similar to that in the MD-11, which makes sense, as the 717 was actually a McDonnell Douglas aircraft, designed at the same time as the MD-11.

 

Many of the MD-11 techniques used in programming the FMS, and operating the autopilot are identical on the 717.

Judging by your type ratings,  you have quite the aviation background. On my airplane, (FADEC) we wont abort a start unless it gives a specific EICAS message and at that point the FADEC has already aborted the start for us. All we have to do is put he thrust lever back into the SHUTOFF detent. Does the 717 leave it up to the pilots to abort starts or will it still abort a start on its own if it perceives a pending hot start, hung start or other start malfunction/ Just curious.

 

The 717 has auto abort functions (even for hung), but our policy was that if you had to wait for FADEC to catch it, you were doing it wrong. I only experienced the FADEC aborting the start when we had an igniter out. You'd then notice it wasn't lighting off, N2 spinning down... and then try again, and get a successful start (because the FADEC now tried with the working igniter). MEL has you put the start selector from AUTO to ON. 

My FPS is fine, 20-30 in the VC and 40-60 in the exterior. Running FSX:SE. The only issue I have is a CTD during nearly every flight I do with this thing.

Please open up a ticket with us - the second the display lag is fixed we will nail down CTDs are soon as possible.

 

 

If the A/T operates the same as the MD-11 (which I believe it does), the EPR rating will be applied automatically, and the A/T is armed by pressing the "Autoflight" button once, while on the ground (usually when lined up on the runway).  The throttle is then advanced manually and at 60% N1, the A/T will take over and advance the throttles to take off EPR.   Eg. There is no seperate A/T arm button - the autoflight button is used to arm, and a coloured border should appear around the FMA on the PFD.
 
As for disengage - the button is on the throttles in the real aircraft (a la MD-11).  PMDG's MD-11 had an assignable custom key command for this, which made it convenient.   If there is no equivalent on the TFDi 717, then I guess you'd have to click the button on the throttles, with your mouse - not ideal in the landing phase!
 
....alternatively you could try the default FSX/P3D "autothrottle" key command (Shift+R, I think?), to see if that has been binded to the function, and will disengage the A/T.

 

Bill -- Thank you very much... I didn't have a chance to test it thoroughly tonight; but I'm thinking these procedures will apply perfectly to the 717.  I never owned the MD-11, so I'm riding a bit of a learning curve here.

Many of the MD-11 techniques used in programming the FMS, and operating the autopilot are identical on the 717.

 

Very true. I was a bit lost with the autopilot and the FMS at first but then my experience in the PMDG MD11 came rushing back and I felt at home again.

PMDG provides some very good tips for Boeing pilots transitioning to the MD-11... most of this also applies to the B717:

 

http://support.precisionmanuals.com/kb/a18/tips-for-boeing-pilots-learning-the-md-11.aspx

PMDG provides some very good tips for Boeing pilots transitioning to the MD-11... most of this also applies to the B717:

 

http://support.precisionmanuals.com/kb/a18/tips-for-boeing-pilots-learning-the-md-11.aspx

Thank you! Very good !

I just opened the add on manager and it looked like an update quickly downloaded, not sure what it did.

I and a few others were up all night trying to help their programmer determine the cause of the stuttering display issues many had. He was able to figure out the culprit (yay!) so that's hopefully the new code being downloaded. I'm sure they will make an official announcement soon.

Seemingly the update had a positive effect: VAS remaining is currently over 1GB as I fly over the SW USA. FPS mid to upper 30's with ORBX everywhere, settings mostly maxed. Previously after 15 minutes with this aircraft only 500MB or so would remain. I noticed the "XGauge" has been removed from the panel.cfg file...

 

PMDG provides some very good tips for Boeing pilots transitioning to the MD-11... most of this also applies to the B717:

 

http://support.precisionmanuals.com/kb/a18/tips-for-boeing-pilots-learning-the-md-11.aspx

Thanks much for this, very helpful page. 

Man, I see a Christmas present for myself tonight, I have been following this topic closely over the last few days taking note of the feedback and observations as well as the developers' response, so all I am going to add here is, thank you to all those who have offered their views, more so to those who stayed up late to help the developers isolate issues, and definitely to the developers for the positive engagement they have with their customers. Well done!

 

Merry Christmas all and happy flying.

Just wanted to say what an amazing aircraft. I am truly shocked that this is your first release as it is on par with the pro's. I will log many many hours in this 717. The VC, external, systems and sounds are all wonderful. I am not getting any performance issues, quite the opposite rather as it is performing great for me. I'm not having any FPS or VAS issues what so ever. Thank you to the TFDi team!

Here's a data point for P3D 3.4.9 - nothing scientific but in a moderately detailed area with AI, I measured 225Mb lower memory usage and about 1.5 FPS better with the 717(inc. WX radar) compared to the NGX.

Has anyone noticed their 717 sinking into the ground using ORBX's YMML? Mine sinks down to the wings.