AFavors

HIGH 1M'S maybe 2, but with current setup I shouldn't get OOM's till around 3.5M. Anyway I haven't been able to reproduce the black screens. I'm still having issues at this point, but don't think its PMDG's problem. Thanks as always, and I'll let you know if anything else (like this) pops up. Only other concern...(i think I responded to someone else's post) is having to "allow" Navigraph access with every load of the B747-8. I'm heading to check if there's a remedy in the other topic now. 

The only AV i run is microsoft security essentials, and its never been a problem before. But I will try it! As for FSX, I always run it as admin

Hello all, Just this evening I had a CTD while vacating the rwy in Anchorage after a flight from MYNN. I tried to get the whole error report but it was quite lengthy, and I couldn't copy or past it. I'll give you guys all the info I was able to receive and relocate through the event viewer and last problem reports. I was flying the 747-8F. Weird thing was, after the crash I tried to restart the flight and and screens were black and controls unresponsive. I was able to push any buttons or click any knobs. Here's everything I could retrieve...

AppName: fsx.exe      AppVer: 10.0.61472.0     AppStamp:475e17d3
ModName: pmdg_747qotsii.dll      ModVer: 1.0.0.0      ModStamp:5c328a23
fDebug: 0       Offset: 004376b3
 

Binary data:

In Words

0000: 006E0055 006E006B 0077006F 0000006E
0008: 0000

In Bytes

0000: 55 00 6E 00 6B 00 6E 00 U.n.k.n.
0008: 6F 00 77 00 6E 00 00 00 o.w.n...
0010: 00 00 ..

Source
Microsoft Flight Simulator®

Summary
Stopped responding and was closed

Date
‎2/‎2/‎2019 7:01 PM

Status
Not reported

Description
A problem caused this program to stop interacting with Windows.
Faulting Application Path:    C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exe

Problem signature
Problem Event Name:    AppHangB1
Application Name:    fsx.exe
Application Version:    10.0.61472.0
Application Timestamp:    475e17d3
Hang Signature:    7416
Hang Type:    0
OS Version:    6.1.7601.2.1.0.768.3
Locale ID:    1033
Additional Hang Signature 1:    74167c54b519e3d44b2dc8d4b03b5f77
Additional Hang Signature 2:    7449
Additional Hang Signature 3:    74499b888e28fd75fe7a0a3a9661d3e4
Additional Hang Signature 4:    7416
Additional Hang Signature 5:    74167c54b519e3d44b2dc8d4b03b5f77
Additional Hang Signature 6:    7449
Additional Hang Signature 7:    74499b888e28fd75fe7a0a3a9661d3e4

I could not get the rest of the info from the PMDG one that was part of the error report from FSX. Thanks in advance 

Same problem for me as well. I checked the option to remember, updated operation center, and 748 to the latest versions. I run the FSX version of the QOTSII, and have a full chart/fms service with Navigraph.

Issue seems to be resolved. (Or), a one-time fluke. 

This is so weird! Sitting on the ramp at EHAM, configuring the plane for departure. Its new to me, until recently(before update), I had not had 1 issue with this aircraft. Not even the Caution light! I just did the research on that while here, so my next plan is to try it again, and change the panel state in the process. I'll report back in about an hour.

Hello All, Been having a problem since the latest update to QOTS. So far all the info I have on the problem is this: 

APPNAME: FSX.EXE      APPVER: 10.0.61472.0     APPSTAMP:475E17D3
MODNAME: PMDG_747QOTSII.DLL      MODVER: 1.0.0.0      MODSTAMP:5955CDCA
FDEBUG: 0       OFFSET: 00337393

From the error report (it attempted) to send to Microsoft. I'm in the process of gathering more Info, But was wondering if this has been seen, as of yet?

Aaron

thanks

Not a Hardware problem. I have the same issue at times. Its like someone is intentionally turning the sound off and on. I'm waiting on the fix for it myself.

Disregard...Having different issue

Yes, I use ASN. But while I was checking multiple aircraft to research the failure. It was not active, and I tried different locations. But thanks for that tip. I will look further into that as well.

New twist to the weirdness... I just went back and attempted to load an older saved flight, and it loaded with the doors open and fully operable. The standby FD works and I've been able to cycle through the door commands, successfully, numerous times. So apparently I can't start a new flight but might can fly an old one!

Already did, Thanks a lot for your help Dan. I'll be sure to post the resolution when/if we find it. This has to be the weirdest problem I've come across to date. Monday and Tuesday, I flew this aircraft and I had no problems. Late Tuesday night, however, (on my return flight from Rio to Heathrow) I was delayed on departure due to not being able to open the doors. I initially thought it was because ground ops were automatic and I was trying to open the doors after the FO armed them all and was prepping the plan for dep. I ignored the problem and just took off anyway. During the fight is when I noticed the problem with the standby flight display, and realized something else must be wrong. All day yesterday and today have been spent trying to figure this thing out. Hopefully, with any luck,  this great tech team here @PMDG will have me back up and flying in no time. I'll be sure to keep you posted.

I was actually in the process of doing that. No luck! I even turned the ground operations to auto. Shut down engines and set chocks. When the T7 tried to open the doors, I did get the message from fsx saying the main exit was opening. But it didn't open. Its almost like the open command was wiped from the system. Even still the fmc command never changed.

Yes. I just selected the aircraft from the selection screen and placed it at the gate. By default my panel state will load in the same condition. Engines off and gpu connected. I don't have any pre-SP1 saved panel states or flights.

YES

Hello All,

I'm having an annoying new problem, that just arrived out of the blue. I am unable to operate any of the doors (pass or cargo) on any model (200, 300, or Freighter). I tried uninstalling and reinstalling, to no avail. I have all the latest service packs (1c in each), and there was no changes in hardware or software leading up to this problem. Also I cannot use the standby flight display. The gauge is still there, of course, but it is blank. I'm not experiencing this problem with any other PMDG addons, nor have I ever had (or heard) of anything like this before. When I cycle through the door commands on the FMC, It goes from disarm to open, but when open is selected, it does nothing. And close never appears as an option. It goes right back to ARM. For the cargo doors, the same thing. when I select open, nothing happens and close never appears. I even tried the old Shift+E, and still nothing. I don't even get the green message from FSX saying main exit opening/closing. 

Please help 

I do it all the time. and yes the windows have to be undocked in order for it to save them this way. You will have to have multiple saved games (for every different livery you fly in if you want each and every plane to react the same way). when in the aircraft you want (say at the end of your flight) with the panels in the position you want save the game. once you restart your sim and select that saved game. the panels will be there. even on multiple monitors. if you try to go into a previous game where the you haven't done this. they will not change places miraculously. as far as making them open up on multiple monitors. yes they will. just don't click the close box to make them disappear. if you want to close them just click on the panel itself to make it return to its normal position. clicking on the panel again will re-open it in the position you selected

I just started having this problem as well

Aaron

Hello dmwalker,

Thanks for the info, but where do I find the right .cfg file. I see a lot of them in the FSX folder

Aaron

Hello,

Just finally updated to the latest version of the 777-300 (I believe 6061) and now on load up the aircraft is bouncing up and down. I really didn't think I needed an update as I only purchased the 777 on Aug. 1st, which was after the update was released. But the operations manager kept saying it was out of date. Previously I had no problems at all. Is there a quick fix, or something I did wrong that can rectify this, short of uninstalling both the 772 and 773 and reinstalling.

Aaron Favors

Well... I set up FSX to run as admin and all WAS well. Except for that spawns another problem!! Now that m panel states save... an even biggerproblem arose. Now My FSUIPC has disappeared from the FSX addons menu. And all of a sudden I get a pause every so many minutes in which the sim won't respond. I had FSUIPC doing a save every 10-15 min for crash recovery purposes. But the pause is more frequent than that. But even more iomportantly, I can't get to FSUIPC to stop it and see if thats the problem.

Hmm... Interestingly I must not have been!! I thought I had set it up to always be ran as admin, but after checking that was the only program not set up this way!! Wow... Thanks David. I just changed it, so I'll let you know after this flight, when I can restart the system.

Hello all,First of all. I have my start-up state as the NGX LONG. I hope that isn't the problem... But I can't seem to save the last panel state. For instance, last night I succesfully saved my flight while on the ground at KAUS. After preparing my next flight, I decided to call it a night. But before doing so I saved my panel state and named it "Previous" Likewise in FSX I saved the flight as "Last" (as FSX had a default file for "Previous") and I didn't want to confuse the two. Goodthing I did because when I awakened this morning my pc had mistyeriously shut down. Once I got FSX reloaded with the "Last" flight I thought every thing was fine, however, when I went to look for the "Previous" panel state it wasn't there. (even thought it SUCCESFULLY saved last night.) I've spent the whole morning trying to save panel states but the only ones the fmc will recall are the default, cld/drk, long, short. This is most annoying because I have all random failures, as well as, service based failures enabled. and every time it restarts...I'm back to square one!!! But for some odd reason. It doesn't go back to the very beginning, because when I check the failures page in the fmc. What should have went back to next service: 250 hours is only 234. Not a big problem except for the fact that I'd gotten down to 184 hrs till next service before retiring for the evening. And have yet to experience an inflight failure. And sad to say never will if the counter keeps resetting. Any one with advice...I'm all ears!!

+1

Herman,You were exactly right. did a RTO at KORD 32L from just before v1.Temps shot up to about 3.0, 4.3 by the time I taxied back to the runway for departure again. Thanks for all the help. I guess, in retrospect, I was actually doing something right for a change. Meaning, I wasn't stressing the aircraft to bad with my landings or braking habits.lol Not to mention I generally don't use the auto brakes on landings unless its a very short runway (less than 8000ft), or am at maximum weight capacity.the highest setting I've had to use was 2 when landing at KSNA 19R which was only 5701ft.