shortspecialbus

FSINN is horribly broken with regards to air temperature. Don't use its weather. -stefan

They're investigating a fix. If/when they find one, they don't have to tell anyone how they did it. That's just silly - why would anyone think they're entitled to programming practices? If PMDG wants to share, and they often do, then that's great, but you don't get to demand it. You spend even more money on Microsoft Windows - do you demand that they post updates on how they code everything and throw a huge fit on a forum for every bug you find? I try to stay out of these things, but it's just getting ridiculous. They're aware that there's a problem and they're trying to fix it. Why wouldn't they? Have they ever in the past shown a 'sorry, you already paid us so we no longer care about you' attitude? They're not the un-nameable company. They may occasionally come across as arrogant, and sometimes they can be a bit obnoxious (I once got into an e-mail spat with someone, maybe Robert, about having to pay for a re-download after the policy changed that wasn't in place when I bought it - it ultimately ended up positive even though I'm sure both of us were less than thrilled) but seriously, they're not ignoring the freezing/CTD/other problems. That's just ridiculous. The inability to activate is probably a higher priority - those people can't use the plane at all. Try to relax and be patient. If you're so furious about being unable to use the plane due to CTDs or whatever, maybe ask for a refund or something until they get it sorted out. Otherwise try un-overclocking and see if that helps. Try lowering settings and seeing if that helps. If nothing else, any positive results you get via that can be communicated to PMDG to help them with the issue. Stop demanding that PMDG owes you anything other than the software and support. Updates on exactly what they're doing are nice but none of us have the right to demand them. Apologies for the rant. It's just getting tiresome. -stefan

I picked up a Macallan 15 the other day, it's pretty good. I've also got a cragganmore 12, an Arbelour 16, and a Glenkinchie 12 at the moment. Still trying to find a good speyside that I like. -stefan

You pay $460,000.00 for your scotch? Can I come drink at your place please? -stefan

The TrackClip Pro is worth its weight in gold. -stefan

Check your failures. For whatever reason, every time I load a livery I haven't used before, there's a BRAKE SYSTEM failure of some sort. Clearing the error makes the brakes start registering temperatures. -stefan

Seattle is just a disaster even with the default scenery. In the attempts to make it detailed, Microsoft made a giant mess. I have just sort of given up flying large aircraft anywhere near seattle and just stick to the A2A Accusim cub to tool around the PNW airports. -stefan

You need to move closer to the window either with camera controls, EZDOK, or TrackIR. It's not visible by just turning the hat. -stefan

Yes, that's what he means. -stefan

It could be, but unlikely, related to uiautomationcore.dll crashes. Do a search for that and you'll find the fix. It could also be related to HIGHMEMFIX not being enabled. Try a search for that as well. Good luck!-stefan

I have the throttles calibrated through FSUIPC so as to not lose reversers below the detent on my CH Throttle Quadrant. When I get home from work, I can post steps I took for this if anyone's interested. So far, it's worked fine with the NGX but I make no promises. Any interest? -stefan Edit: I also do the same thing as the guy above me who posted while I was posting - idle reverse and full reverse are nice.

This is probably the first post I've ever seen complaining that bugs were fixed. -stefan

For what it's worth, I've done YSCB-YBCS a few times and had no issues. The only crashes I've had seem to be flying the NGX around the Seattle area. I'm guessing the combination of NGX, ORBX, and maybe a weather program + HD clouds etc just eventually kills FSX. We're really pushing the engine past what it was designed for, a few g3d.dll failures are likely to happen in dense/highly detailed areas when as many addons as we're all running are stacked on top of each other. My suggestion for now is to lower scenery complexity and/or autogen when flying into problematic areas, as much as I hate to do so. -stefan

Since that page seems unavailable, the point being made was that PMDG has flagged it as a bug and is fixing it for an update. So yeah, it's broken on the ground in taxi but it will be fixed. -stefan

In the sim, and I believe in the real plane as well, the guard can only be down with the switch in one position (On or Normal or whatever) so simply verifying they are closed is enough. -stefan

Thanks for sharing. -stefan

This is one of the more hilarious complaints I've seen yet. -stefan

Set it to NAV, not ALIGN. Please read the manual. -stefan

Does this count as the panel freeze/lockup issue that's being tested? For unrelated reasons, I completely reinstalled the OS and FSX and all the addons onto a brand new hard drive, and the issue persists. -stefan

I had that exact same crash between vancouver and seattle on a PAKT-KBOI route. It is likely related to the seattle area with FTX PNW. -stefan

The sounds get glitchy sometimes with view switches. Try pressing 'q' twice after you switch views and see if it's still an issue. -stefan

Skipping the route entry and manually entering all the legs did indeed seem to work. I'll just do that for now. Thanks! -stefan

I have a reproducible (for me, at least) issue with the CDU and the map display. Basically, the map display freezes in a sense, and the CDU breaks. My steps to reproduce (literally everything): -Load Alaska Air 737-800 WL-Set Payload to: 132 passengers (single class)----Cargo is 8753 in front, 9524 in rear-Set fuel to 20950-Load Cold and Dark panel state-Enable ground power-Turn on battery-Turn on standby power-Turn on ground power-Turn IRS switches to NAV-CDU:----POS INIT------PAKT as reference airport------Enter IRS position from GPS----ROUTE------PAKT as ORIGIN------KBOI as DEST----DEP/ARR------Runway 29 selected for DEP------RNAVZ 28L, EMETT trans----RTE------DIRECT -> ANN------J502 -> SEA------J20 -> DNJ------Clear the discontinuity by upselecting EMETT-Activate and Exec the route-Switch map to PLN-Activate LEGS on CDU Try stepping through route. The STEP bug will not exist or move, and the map is forever stuck on PLAN mode. You can attempt to change it but it's stuck on PLAN, and the FO's map is stuck on whatever mode it was on. You can still change the range of the map, but it will be (at least for me) stuck on the broken PLAN map. The CDU is also messed up at this point. I attempted to save the panel state to include in a bug report, but it just goes to a black screen when i hit the LSK to save the panel state. The PAYLOAD screen is also messed up, as well as a number of other pages such as POS INIT. I am able to reproduce this consistently, including waiting a day and across a reboot. I'd be curious if anyone else is as well, or if there's a solution, or if I'm doing something wrong here. I'd also be happy to open a support ticket if someone from PMDG asks me to. Here's a screenshot. You can see the map is not selected to PLAN mode, and I also threw in a CDU page of the fuel. Thanks! -stefan

Look up the uiautomationcore.dll issue, this sounds like it might be that. The short fix to try is to download the Windows Vista version of the file and copy it into your FSX root directory. -stefan

The NGX does not include weather radar, as it is impossible to accurately simulate in FSX. As for the activation question, I don't believe it will be an issue, as I once had to install the MD-11 or something twice in short order. I don't know the exact criteria for failure (and I doubt they'll tell you) but I don't think it will be a problem. -stefan