jfjoubert

Hi, I'm also experiencing this behaviour with the sounds.

You're not alone... :wink:

Got it...

Warbirds, if you look right at the bottom of Kyle's original post you'll see the following line: And you will also be reminded to sign your full name in the forums.

Robert, I'm officially complaining (or is it complianting?) about your use of the word compliant, instead of complain... or something... oh whatever. I actually forgot what I was trying to complain about...

Hi, Are you guys struggling with using the NGX offsets via FSUIPC? Unfortunately I don't have any Jetmax hardware but I've been playing around with both Simconnect (via c# app) and FSUIPC to interface with the NGX and 777. Initially I've used 1 and 0 as parameters on some of the offsets, for example the landing gear. (offsets 74183 and 70087) It seemed to work but I got weird things happening... until I used the proper values for the parameters. Mouse left-click (536870912) and mouse right-click (2147483648). Autopilot and autothrottle disconnect switches also had problems with 0 and 1 as parameters... they will both disconnect but will automatically be silenced without you having to press the button twice. These parameters produce a "double-click" event of sorts. Using the proper mouse right and left click values fixed this. Maybe this has got nothing to do with your issue... just thought I would post this.

Brian, What worked for me was to disable "Mipmap VC Panels" under "View and Panel Settings" in the Graphics Settings. Your mileage may vary... (just to cover myself) ^_^

Kyle, it did mess up my NGX!!! The weather radar isn't working anymore.

It's simply one of those "must have" add-ons. I have wasted lots of money on half baked add-ons over the years... ASNext made me forget about them all. I will also not buy another add-on unless there's a free trial... with the exception of PMDG. They're exempt from this law. Bad things will happen if you don't buy their add-ons.

No problem... I understand your frustration with a CTD issue. Hope it gets resolved soon.

Kyle, you're welcome.

Kyle, Thanks for the moral support. Now I know how you must feel... :unsure:

Hi, my apologies for the "lesson". It wasn't meant to be one and I probably should've posted my observations in a different thread.

Not sure if this might be a bug, or whether it's by design... If you don't turn on the weather radar (WXR button on the EFIS control panel) and you press the "Test" button on the weather radar control panel, then you get a random "rainbow" self test pattern which seems a bit odd. This self test pattern starts and stops at varying positions and durations each time the "Test" button is pressed. Once the weather radar is switched on then the "Test: mode works 100% according to the Collins WXR 2100 Operators Guide. I was just wondering if this behaviour is correct... not that it's really important. I was just playing around with it. For those of you who are into the "as real as it gets" genre... try the following: (and only if you're interested... ^_^) Press both the Captain's and First Officer's "TFR" buttons... the weather radar will display the radar test pattern. According to the Collins Operators Guide this is due to the fact that the radar is no longer able to determine which settings to use (Captain's or First Officer's) to supply information to the EFIS. It's modelled perfectly in the 777.

Hi Guys, As far as I know there's no "de-register" option for the MD-11. 737 NGX, 747X etc., but only for the 777 via the FMC. You will therefore have a "limited" number of re-installs for all the pre-777 products by simply re-installing using your original key. I've re-installed my MD-11 and 737NGX a couple of times over the last 2 years... didn't de-register anywhere and there was no need for a support ticket. The 777 must be de-registered via the FMC... if you can't then you'll have to create a support ticket with PMDG for them to be able to verify your details and to assist in getting you up and running again. Once again, this is according to my limited knowledge... please don't shoot me if not 100% accurate. :huh: The "experts" will surely jump in and update where necessary.

Do we want it, or do we need it? Maybe we want to need it...

Yip, it is included. Have a look under <your fsx folder>\PMDG\PMDG 777X\SDK. Purchase and installation was a breeze.

Glad you got it sorted.

Jan, Was this the only log entry for FSX crashing? The reason I'm asking is that usually there might be more than one related to the same single crash event. The fact that the log is showing that the Fault Module is unknown could mean a lot of things... Antivirus app being used, any add-ons installed in FSX, windows/FSX compatibility issues etc. You didn't mention what OS you're running. Did you recently install any new add-ons for FSX? You might have to do a re-install of FSX, but let me know about your OS version and your current add-ons first. Thanks Jean

Jan, have a look at your Windows event log and check the log under Application. There should be entries at the time of the crash with some more info. Please post the event log details here and I'll see if it's something which I can help you with. No promises though... :huh:

Hi, I've recently upgraded to Windows 8 Pro 64 bit and have been flying the 737NGX for quite a while without any major issues. Ending a flight in the 737NGX with ESC results in a FSX CTD. I simply press CTRL-C to exit straight out of FSX. No CTD. Anyhow, let's move on to the MD-11. A couple of days ago I decided to install my MD-11 again. All went fine with the installation and activation until I selected the MD-11 in FSX under Free Flight. The usual "AIRAC loading" screen which pops up when you select the MD-11 didn't show. Clicking on Fly Now placed me inside a "Cold and dark" cockpit, with a twist. Everything was dead... displays, controls, sound... everything. I then decided to check the MD-11 Load Manager stand-alone application. It crashed with a weird error. Here's the entry from the Windows event log: Activation context generation failed for "D:\Games\FSX\PMDG\MD11_LoadManager.exe". Dependent Assembly Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8" could not be found. Please use sxstrace.exe for detailed diagnosis. There were also similar entries for PMDGOptions.dll, PMDGEvents.dll and PMDGSounds.dll. Running the MD-11 inside FSX didn't produce any errors, but as long as you stay in the "dead" cockpit the Windows event log is bombarded with the above event entry... the only difference is that it's now referencing the PMDG_MD11.DLL instead of the MD11_LoadManager.exe. This led me to believe that I'm missing some Visual C++ files. The MD-11 installation did install some or other C++ redistributable, which was annoying as it was downloaded during the MD-11 install. So I have no idea which version this was. I assume it installed the 2010 redist 64bit. FIX: What I did was to install Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17. The file is called vcredist_x86.exe. This is the 32bit version. The MD-11 Load Manager started to work and the MD-11 came back to life in FSX. Just thought I would post this for anyone else who might be running into this issue. Jean Joubert

Hi Christian, I'm having the exact same problem with the CTD when ending a flight in the PMDG 737NGX in FSX. I'm running Windows 8 Pro 64bit. I've installed the latest registered version of FSUIPC and I made the IncreaseUserVa change... still getting CTD. I can also reproduce the CTD by selecting the 737NGX, clicking on Settings, clicking on Free Flight, clicking on Settings again, clicking on Free Flight again. I'm out of ideas of what else to try. Any suggestions? Thanks Jean

Hi, thanks for the info. I had a look at the available offsets in the SDK, but there are no offsets indicating the state of the different modes... i.e. ARM, THR HOLD, FMA thrust mode etc. According to TUTORIAL #1, Page 0.00.70, the following will happen when reaching the T/D point: "The FMA thrust mode annunciates RETARD while the throttles are being moved back to idle, followed by ARM in white, which indicates that the autothrottle servo is disconnected from the physical throttles." Is there a way to infer these modes from the available offsets, or would this mean that PMDG will have to add extra values to the SDK to indicate the different "modes" of the plane? Anyone from PMDG willing to comment on this and whether it might be something you'll consider adding? Thanks.

Hi I need some help with the 737NGX autothrottle logic for building a motorised throttle quadrant. Could someone tell me how I could determine when the plane commands the autothrottles to on and when they're commanded to off again throughout all the flight modes? I need to power up my servos only when the plane is commanding the throttles and then remove power again when the AT disengages, for whatever reason. I just need to be able to determine when this is happening. Initially I can check for the TOGA button "press", but after this I still need to know when the AT disengages. I'm currently using FSUIPC to read the throttle positions from FSX as well as the 737NGX specific offsets for AT Arm and FD switches etc. Any help would be greatly appreciated. Regards