Speed Of Flight

I agree, and I thought of that also. I have a thumb wheel for pitch trim, but it was set to neutral. Also, the "ALTN TRIM" control was set to the center position on preflight. I dont know what happened. Cycling either/both stop to stop didn't seem to help, and trim was going to full nose up. After a little bit, and using the disconnect switches, it stopped, and I can't explain why. I'll try again. At work, I'd have cycled the circuit breaker. Odd.

Mine is continually trimming the stab to full nose up in flight. I used the L and R stab disconnect switches to disable the drive, but does moving this file to the desktop fix that? If not, what can be done?

Different issue, perhaps a fail, but different kind. Install is ok, I'll make a different post. Thanks again for your help. Very enjoyable, and has been for years.

Uninstalled the 773ER via control panel, and reinstalled. It appears in the Ops Center and the "Select Aircraft" list. I'll try and fly it and see how it works out. It appears to load just fine. Thank you for all your help! I believe this problem is resolved. I'll try and fly it, and see how it goes.

Ok, now the 773 doesn't show in the "Select Aircraft" window of FSX:SE. The Ops center shows it as installed and up to date, but also doesn't show it in the "livery Manager" window. Restarted the PC, and still not there. The 772LRF is there, and my past liveries also, but no 773ER. It shows version 1.10.8886 for the 772LRF and 1.10.8414 for the 773, but no liveries available, and can't be selected.

Ok, somebody waved their magic wand. I just downloaded the package from the link again, and the .exe shows to be version 1.10.8448. I'll try it again...

No UAC enabled on this machine. I see the log file, here's the latest: 2019/01/09 09:35:28 [PMDG 1] ===== PMDG updater commencing 2019/01/09 09:35:28 [PMDG 1] Setting up for 77L / XSE 2019/01/09 09:35:28 [PMDG 1] PMDG Updater: Version A18 - Build timestamp Sep 12 2017, 23:29:10 2019/01/09 09:35:28 [PMDG 1] Finding installed PMDG product version 2019/01/09 09:35:28 [PMDG 1] Installed PMDG product version: 1107025 2019/01/09 09:35:28 [PMDG 1] Fetching available product information for XSE... 2019/01/09 09:35:29 [PMDG 1] Retrieved data about PMDG product 6: PMDG 777-200LR/F for FSX 2019/01/09 09:35:29 [PMDG 1] Retrieved data about PMDG product 15: PMDG 777-200LR/F for FSXSE 2019/01/09 09:35:29 [PMDG 1] >>> Product: PMDG 777-200LR/F for FSX 2019/01/09 09:35:29 [PMDG 1] Finding install-directory this product's simulator... 2019/01/09 09:35:29 [PMDG 1] If a registry key error appears, disregard - it simply means you do not have that simulator installed. 2019/01/09 09:35:29 [PMDG 1] Sim install directory in registry is C:\Program Files (x86)\Steam\steamapps\common\FSX\ 2019/01/09 09:35:29 [PMDG 1] PMDG 777-200LR/F path should be C:\Program Files (x86)\Steam\steamapps\common\FSX\\PMDG\PMDG 777X\ 2019/01/09 09:35:29 [PMDG 1] 1107025 is out-dated and must be updated with the full installer. 2019/01/09 09:35:29 [PMDG 1] Please check to ensure that you have updated to the minimum version. 2019/01/09 09:35:29 [PMDG 1] Log into your account at precisionmanuals.com, click on 'View Previous Orders' and then your order number. 2019/01/09 09:35:29 [PMDG 1] >>> Product: PMDG 777-200LR/F for FSXSE 2019/01/09 09:35:29 [PMDG 1] Finding install-directory this product's simulator... 2019/01/09 09:35:29 [PMDG 1] If a registry key error appears, disregard - it simply means you do not have that simulator installed. 2019/01/09 09:35:29 [PMDG 2] Failed to open registry key! 2019/01/09 09:35:29 [PMDG 1] I found no sim install corresponding to product ID 15; skipping. 2019/01/09 09:35:29 [PMDG 1] Installed products that failed to update: 0 2019/01/09 09:35:29 [PMDG 1] Installed products successfully updated: 0 2019/01/09 09:35:29 [PMDG 1] Done.

Ok, I've done that, and the download links are to the same version requiring the update. The links are to the version I purchased in 2014, or so it seems. R-click on "Properties" of the .exe, and it says it's file version 1.10.7025. I've done what you said, and the Ops Center keeps trying to update it. Any ideas?

Old thread, but I didn't really want to start a new one. I haven't been flying a lot, but starting the Operations Center showed updates for the 772LRF and 773 for FSX:SE. I ran the updater, and it seems that it broke somewhere. I uninstalled both the 772LRF and 773. Then, went to the customer download area, and downloaded the files and reinstalled just the 772LRF. Now, the Ops center shows an update notification every startup, but doesn't appear to update. It shows this notification every time I start OC. Is it possible my download links are to an ancient version that can't be updated? Do I need new files altogether? If so, one would think the customer page should have links to the most up-to-date version. Should I start a ticket, or is there a link to an updated version that I'm missing?

Tried all that you told me to, but it still does it.

Thank you sir.

Ticket: 334-1FF4B825-0423 Started a ticket, on December 26, for which there has been no response yet. Been a week. Would have at least expected some troubleshooting questions by now. When I open Ops Center, and then select the B777 livery downloader, I get this message: An exception has occured! Please contact PMDG support by submitting a ticket at http://support.precisionmanuals.com for help with resolving this issue. Press "Copy to clipboard" below and then paste the information into your support ticket. Additionally, a log file has been created at: c:\users\parts\appdata\roaming\pmdg\pmdg operations center\PMDG Operations Center.log Please attach this file to better help us fix this issue. The application will now exit. 01/02/17 18:57:51 Exception: Unknown Exception at 0x6CC1AF3E 6CB90000 C:\WINDOWS\SYSTEM32\MSVCR100.dll +0008AF3E (0, 0, 0) 6CB90000 C:\WINDOWS\SYSTEM32\MSVCR100.dll +0008AF8A (0, 0, 0) 68E30000 c:\program files (x86)\pmdg operations center\Product Module 777 XSE.dll +0001B4B2 (FFFFFFFF, 83572A8, 10) 6C7E0000 C:\WINDOWS\SYSTEM32\Cabinet.dll +00011160 (FFFFFFFF, 83572A8, 10) 6C7E0000 C:\WINDOWS\SYSTEM32\Cabinet.dll +00010772 (10, 68E4B490, 8358584) 6C7E0000 C:\WINDOWS\SYSTEM32\Cabinet.dll +0000EA4F (68E68A74, 0, 68E4ADB0) 68E30000 c:\program files (x86)\pmdg operations center\Product Module 777 XSE.dll +0001AA29 (10E5E70, 835F7E0, 68E68A74) 68E30000 c:\program files (x86)\pmdg operations center\Product Module 777 XSE.dll +000234A1 (C5377B05, 0, 68EE4680) It's different every time I see it, or at least I think it is. What do I do next? Hope this helps, and that someone will respond.

An exception has occured! Please contact PMDG support by submitting a ticket at http://support.precisionmanuals.com for help with resolving this issue. Press "Copy to clipboard" below and then paste the information into your support ticket. Additionally, a log file has been created at: c:\users\parts\appdata\roaming\pmdg\pmdg operations center\PMDG Operations Center.log Please attach this file to better help us fix this issue. The application will now exit. 12/28/16 19:30:36 Exception: Access Violation at 0x72BA2AC9 72AF0000 C:\WINDOWS\SYSTEM32\WININET.dll +000B2AC9 (72BA28D0, 52EA4CC, 52EA460) 72AF0000 C:\WINDOWS\SYSTEM32\WININET.dll +000B28FC (72BA28D0, 52EA4CC, 52EA460) 72AF0000 C:\WINDOWS\SYSTEM32\WININET.dll +000B241A (52EA460, B4DF68, B60B00) 72AF0000 C:\WINDOWS\SYSTEM32\WININET.dll +000B30A4 (B60B00, 5CDF7D4, 5CDF83C) 72AF0000 C:\WINDOWS\SYSTEM32\WININET.dll +000BF806 (B4D450, 0, 27D) 72AF0000 C:\WINDOWS\SYSTEM32\WININET.dll +000BF62C (B55160, 0, 27D) 76A30000 C:\WINDOWS\System32\KERNELBASE.dll +000D4EBA (5CDFAA0, 5795500, B4D454) 771B0000 C:\WINDOWS\SYSTEM32\ntdll.dll +00037ED3 (5CDFAA0, 575ACA0, B4D454) Looks like this error is slightly different every time it comes up.

Confirmed works in FSX:SE. I use it, and have logged more hours in this bird than any other. Trouble-free install into FSX:SE here, although this is the only sim I run. I don't know about having it dual installed into vanilla and steam versions.

Thank you for anything. It seems like nobody had any desire to even acknowledge that this is a problem. I have an open ticket, and got no response from that yet, either. This is at least acknowledgement. Thank you! Ticket number 334-1FF4B825-0423