scandinavian13

Go to your PMDG Setup > Simulation settings and check to make sure your setting is not "IN HOLD/ARM MODE ONLY."  If it is, when the plane is in descent it will enter HOLD mode and allow you to override the throttle with your hardware,  If your hardware is still where you left it when you took off, when the plane hits HOLD mode, the throttles will sync to your hardware and you'll have an issue.  Either turn this mode to a setting where your hardware never overrides the AT, or get in the habit of setting your hardware on the idle stops before descent.
 
...also, have a gander at the into manual.  It describes all of the settings, and quirks of the plane.

The controls for the cargo temp are up on the overhead maintenance panel according to the manual.  Have a look up there (not shown in your screenshot).

It's listed here:
http://www.support.fs2crew.com/help/manuals/page.aspx?pageid=help_and_trouble_shooting

Make sure you didn't move your eyepoint around.  If you move it too far back, you'll end up in the headrest and unable to click things in the vc...

FSX issue.  It's a stuck water/snow effect.  Google it.  It's well known.

Fair enough - good questions.
 
For what it's worth, I don't think any of us have created GSX profiles even for our own use.

Welcome!
 
If you wouldn't mind, there should be a little "Best Answer" or something click box to the right of each post.  If you could check that box so that anyone who comes across this post later on would know that your question was answered (and have the answer at the very top), that would be great!

Most likely the FO using the trim buttons on the yoke.

Haha - nope. It means that you found that the NGX is behaving as its supposed to.
 
At around that time, the commanded AT mode is called ARM. In the real plane, the plane is essentially allowing the throttles to be manually adjusted (or closed) as necessary, while still remaining on AT. It will pick back up after taking off and take control of the throttles again. This is the real behavior.
 
In your situation, it's hitting ARM mode and - just as in the real plane - allowing you to take over fine tuning the throttles (or giving you a chance to close them if anything happens.) the difference is that in the real plane, the throttles are servo-controlled, so before dumping to ARM, the throttles are in the exact spot the AT last set them. Since your hardware does not have servos, however, it immediately drops to wherever you left it.
 
This is why there is an option in the FMC menus to allow you to tell it to ignore your hardware at any time your AT is on. I mentioned this before, and based on your reports, I do not believe you are operating in be proper mode. If you want it to behave like all other ATs you're used to, you should set it to always override your hardware (I can't remember if the setting in the menus is NEVER OVERRIDE THE AT, or ALWAYS OVERRIDE THE HARDWARE, but you essentially want it to ignore the hardware at all times while on AT.)

If you're trying to fly in LNAV, you can't adjust the CRS.  If you'd like to adjust the CRS and keep the AP on LNAV until you get closer, single click the V/L button (VOR/LOC), and then adjust the CRS.  It will automatically click back over to LNAV when it senses you're not messing with the CRS anymore.
 
If you'd like to exit LNAV to go to V/L, press V/L twice (if you're not using NAV mode on the AP, you only need to press it once).
 
These concepts are expanded upon in the tutorial flight.  I suggest checking it out.
 
 
 
As for it choosing the Runway 4 course, I couldn't tell you why it's doing that other than the fact that it's getting a conflict (because it's detecting two LOCs on the one freq).  If you force it to the other by rotating the CRS bug, it should be fine.  The only CRS bug that matters is the one on the side the aircraft is using (you'll note, there's a button on the panel that says PILOT/COPILOT just above the DME gauge, to the left of the ND).  If it says PILOT, it's using the pilot-side CRS bug.  No matter how much you flip the COPILOT side CRS around, it won't pay attention to it in the least.

Forum search always helps...
 
Check this thread out:
http://forum.avsim.net/topic/360706-ngx-fsx-crash-on-exit-poll/
 
There should be a number of possible fixes there.

It's a point at which you should (note: not must) switch from one VOR to the next.  In this case, from OLM to BKE.
 
 
 
Nope.  It's doing the radio switching for you (and is also picking up signals from GPS, so the VORs are redundant).
 
 
 
Nope.  MEA is minimum enroute altitude and has nothing to do with aircraft separation.  It's referring to the possibility that there may be a drop in your navigation signal between those two VORs.  As such, it's providing a changeover point close to where that may occur (if you look at the en route H-1 chart, you'll note there is no changeover symbol there).