RKillins

Where is the SEL temp displayed in TopCat?

To apply reverse thrust to my PMDG 737NGX with my Saitek throttle quadrant, I have assigned switch 21 (which is the position below zero in the red zone of the left outside black lever). In the settings, repeat is maxed out to the right. I lever works fine for positive thrust, however, as soon as I engage the reverse thrust, buy dropping the lever into the red zone (trigger switch 21), I am no longer able to regain positive thrust with the lever. The lever moves freely, but there is no action on the PMDG's thrust levers. The only way I am able to have them move forward is to use F3. This is annoying. I'm guessing I don't have my throttle quadrant setup properly. Is anyone able to help me regain positive thrust with the lever after the reverse thrust is engaged without having to rely on F3, rather just by moving the lever forward (which would be expected).

Please refer to the attached video files to see what I am experiencing. (My apologies ... 120MB download from my smartphone camera) I can only record this externally, as FRAPS and other video capturing software doesn't catch it. https://drive.google.com/file/d/0B9EE-tbOy4bJWURhNDdjTGZQMVU/view?usp=sharing As I pan around the artifacts will increase or decrease in intensity. I can get this from both internal and external views and is not isolated to any one airport or aircraft. Eventually the effect will subside, until I change the view again, and it will start up again. It seems to happen only when stationary, ie I don't get it when taxiing or flying for example. It does not appear to do it in DX9. And ideas what the cause is and how I can resolve it? I am using Windows 7 Home Premium 64Bit FSX + Acceleration DX10 fixer 2.8 (AA = 8x CSAA) GEX, UTX Canada & USA, ASN 3071MB NVIDIA GeForce GTX 660 Ti in NV Surround mode across 3 23" monitors with a resulting 5760x1080 resolution Intel Core i7 2600K @ 3.40GHz, 8.00GB Dual-Channel DDR3 RAM fsx.cfg can be found here NI settings here (pg1), here (pg2), and here (pg3).

Thanks Michael for cleaning that issue up for me! Much appreciated. As far as your second question ... why not? LOL. Seriously, just for a something different really ... the magic of simulation. My flight originated from KTPA with the route in most part generated by RouteFinder.

I won't deny that I likely screwed up the CDU when compiling my route. Needless to say, after entering my route, and proceeding to define my approach, some discontinuities resulted. Although I struggle with the apparently easily removed discontinuities, this scenario has me stumped. I'm hoping someone can assist in helping me clean them up, and learn in the process. This is my approach into KSFO, using the Risti 4 arrival, Manteca (ECA) transition, for the ILS Rwy 28R with IAF ARCHI ... My last waypoint in my route was ECA. Here is the messed up route inthe CDU from the leg prior to ECA ... J58 DUGLE DIRECT ECA DIRECT CEDES - - - - - [][][][][] -- ROUTE DISCONTINUITY - DIRECT ECA DIRECT CEDES - - - - - [][][][][] -- ROUTE DISCONTINUITY - - - - - - ECA ECA.RISTI4 CEDES - - - - - [][][][][] - - - - - ARCHI APPR TRANS CEPIN ILS28R RWY28R MISSED APPR VIKYU I can get rid of the discontinuities by replacing the [][][][][] with the nav points immediately following, but then I am left with J58 DUGLE DIRECT ECA DIRECT CEDES DIRECT ECA DIRECT [][][][][] - - - - - CEDES DIRECT ECA ECA.RISTI4 CEDES DIRECT ARCHI APPR TRANS CEPIN ILS28R RWY28R MISSED APPR VIKYU If I erase DIRECT [][][][][] , I get a route discontinuity. Any erasures of duplicates just results in discontinuities. What is the correct procedure for getting back to normal. I assume it should be simply ... J58 DUGLE DIRECT ECA ECA.RISTI4 CEDES DIRECT ARCHI APPR TRANS CEPIN ILS28R RWY28R MISSED APPR VIKYU Rob

Nice! Thanks Steve for your awesome contribution to our hobby!

After having been working with and finding great satisfaction with Steve's DX Fixer since his first release, I have opted to invest further into my FSX experience with the purchase of UTX Canada, GEX and REX 4 - Texture Direct. I'm excited about flying with these new enhancements! I'm wondering if anyone flying with a similar addon library has any hints or tweaks that can be optimized with Steve's DX10 fixer? Are there any fsx.cfg or NI parameters that can be added, or changed in recognition to this new software? Any settings from within the software to optimize DX10 worth implementing? I'm also using the new Active Sky Next along with the FreeMesh X.

Thanks Michael ... I saw that date in the Readme but thought the release was a bit older than that.

Delete topic.

Can anyone recall the date that PMDG released the 1d service pack release for the 737NGX products? Can someone confirm my understanding that service pack 1d equates to version 1.10.6461? Yes it is.

Thanks Rostyslav, In my trials, their doesn't appear to be any performance difference whether one goes to NAV directly (as in tutorial 2) or stops at ALIGN first (as per the checklist I am using). It does appear however, to affect the ability to recover from a misclick. Going directly to NAV, and misclicking their after results in no map. Turning the misclicked IRS selector OFF, then carefully back to NAV, will recycle the alignment and provide the map.

Whats's the procedure for resetting the IRS. I messed up during normal startup procedure ... During normal startup, I did the following: 1) align IRS left selector 2) align IRS right selector 3) copied the GPS L position from the POS INIT page2 of the FMC 4) pasted it into the GPS position (from the POS INIT page1 of the FMC) 5) align IRS left selector 6) align IRS right selector But at step 5, I accidently switched the IRS left selector off. After I tried to to recover by flipping to NAV thereafter, I haven't been able to get a map on my MFD. I've tried to go back to the IRS panel, turn both IRS to OFF, and redo things, but I either get blinking align lamps, or an absence of a map. My faulty attempt: 1) IRS selectors off ... 2) after align lights extinguished ... irs selectors to align 3) ON DC lights replaced by ALIGN buttons illuminated. 4) ALIGN buttons start blinking with a code of -------0--08 5) Switching to NAV does nothing. Obviously, I'm doing something wrong. The GPS value in the CDU doesn't apperar to be able to be changed at this point.

Thanks Kyle, I had an opportunity to practice this and was grateful for the help. Worked flawlessly of course.

Thank you ... too kind. Signed by Mr. R.M. Killins

Thanks. My Signature is ny username. That is enough. But to appease ... Signed by Mr. R.M. Killins

I'm a novice FSX flyer, and am learning the ropes of flying the 737NGS. I've tried searching for an answer to my question, but failed likely because of figuring out how to phrase the query, so my apologies if the question is an assumed no brainer. I was unable to find it in the tutorials and not really interested in reading through 1500+ pages of Flight Crew Training Manuals. I trust someone here is willing and able to answer what is likely a very simple question. When I program my route, and I insert a SID for my departure, the end of the SID is defined by a pseudo waypoint of VECTOR before proceeding on the enroute portion of my flight. How do I get out of VECTOR? I can't seem to engage on of my flight plan. No doubt I'm doing something wrong ... but what is why I'm here. I will depart for the airport with the runway heading and SID altitude defined in the autopilot. I will engage the autopilot and hit LNAV and VNAV with the intent of the autopilot flying the lateral and vertical directions of the route. At the end of my SID, the PFD shows (Vector) in magenta. I will set a heading and follow that heading with the autopilot. But how to I get the autopilot to recognize the next waypoint to fly to it after the vector has been "cancelled" by ATC. ie ... resume flight plan.

I have recently purchased the PMDG 737NGX packages (600, 700, 800, 900 series) and have enjoyed the few flights I have taken with them. Today, I have discovered that I no longer have control of the rudder, ailerons or elevators with my Saitek Pro Flight controllers. The toe brakes work, and the throttles work. Everything works fine on other aircraft in my hangar, just not the PMDG 737s. I do not use FSUIPC for controllers, opting to remain with FSX's system. Not has changed in the configuration within FSX. The Windows 7 calibration for the controllers all show proper calibration and are all responsive. Thoughts anyone?

I am a happy customer of Steve's DX10 Scenery Fixer. I have just recently purchased the PMDP 737NGX series of aircraft, and I have come to notice what I think to be an anomaly with the cockpit VC dash. I've never experienced this aircraft outside my own system, so I don't know if what I am seeing is normal or not, but it looks a bit out of place. Not knowing much about graphics, I certainly can't begin to even explain it, let alone diagnose it, but I wonder if it is DX10 related ... shadowing perhaps? Here is a picture, with the solid bland gray shapes being outlined. I assume these might be shadows?

I know how -_- Thanks!

Hi Steve. The boxes are all unticked. They should be ticked as the manual says right?

I went into DX10 Scenery Fixer (2.4 build 63) today to do some adjustments and discovered all my option buttons, except Lights/Effects and debug, were greyed out and not accessible. What did I do?

So it is. Thanks.

Westair, you asked the exact question I was going to ask next. For me to have saved this new panel state, as a minimum the battery had to be on to power the CDU. Now, the newly saved panel state loads up with the battery on. Not exactly what I wanted. How do we save an altered cold and dark state when a power source was used to save the profile. Need to save with no active power source.

Perfect! Thanks folks!

Thanks folks ... So, if I am understanding properly, in the CDU adjust all my settings ... set cold and dark panel state, connect air, connect GPU, open whatever doors and save that as a uniquely named "panel state". Then, like I did with the PMDG provided cold'n'dark default panel state, use the newly created configuration as my startup default?