Jump to content

Search the Community

Showing results for tags '777'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • The Hangar
    • ON APPROACH - Topics
  • Touring Club's Tours
  • Touring Club's Submissions
  • Hurricane Hunters's Topics
  • Air Corps's Forum


  • TSL Liveries
  • Misc Downloads
  • Touring Club's Flight Plans
  • Touring Club's Downloads
  • Hurricane Hunters's Downloads
  • Air Corps's Downloads

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



I am a

A little about me...

Local airport ICAO

Website or Social Media Page

How did you find TSL?

Found 16 results

  4. External preview for the upcoming PW-4090 package. It is still work in progress, but based of previews, its something to look out for! LINK TO SOURCE: https://www.airdailyx.net/article/turbine-sound-studios-777-update/
  5. New video posted by VAS aviation: LINK TO SOURCE:
  6. AGENCY: Federal Aviation Administration (FAA), DOT. ACTION: Notice of proposed special conditions. SUMMARY: This action proposes special conditions for Boeing Model 777-8 and 777-9 airplanes. These airplanes will have a novel or unusual design feature when compared to the state of technology envisioned in the airworthiness standards for transport-category airplanes. This design feature is folding wingtips. The applicable airworthiness regulations do not contain adequate or appropriate safety standards for this design feature. These proposed special conditions contain the additional safety standards that the Administrator considers necessary to establish a level of safety equivalent to that established by the existing airworthiness standards. LINK TO SOURCE: https://www.federalregister.gov/documents/2017/11/01/2017-23698/special-conditions-the-boeing-company-model-777-8-and-777-9-airplanes-folding-wingtips
  7. Captains, We have just pushed a few small, cleanup updates that should be propagating out in the PMDG Operations Center as we speak. (It takes a few hours to reach all sectors of the globe, so if you don't see them this instant, don't panic- it just takes a bit to boil out there...) The 777-200LR/F got a very small update that was focused on cleaning up a couple of items that we captured during research for a pending update on the 747- and since the item affected all product lines, the 777 update became necessary. You can check the change log for a list of minor items that were also included. (Note: The 777-300ER was not updated because it gets it's behavioral logic from the base package, and as such an update wasn't needed.) The 737NGX (both the 800/900 base package and the 600/700 expansion) were updated to clean up a few items that we missed during the round of updates related to Prepar3D v4 compatibility. Primarily these are very small items, but we also had a few texture/lighting/click spot anomalies that we wanted to address within Prepar3D v4- and this update should take care of those. This update series also wraps in a couple of minor items that were pass-down fixes from our continued work on the 747-400, and you can read the change log for more details if you like. Livery Update for the DC-6 for FSX/P3D: We pushed the "Independence" livery that Pete Sterling created last week. This originally started out as an internal piece but it came out so beautifully we felt that it should be shared. Pending updates for the 747-400: We have some items we are wrapping up to push out for the 747-400, but they are still being worked internally. We also have a massive amount of stuff we are holding back because it will get previewed with the 747-8, and those previews should start up here fairly soon. We are WAY (way way) behind on that project thanks in large part to the all-hands effort required to get all of the Prepar3D v4 compatibility taken care of- but last I checked it seemed everyone was back to using the time clock in the 747-8 assembly hall, so this is indeed a good thing. Stay tuned- we will have more for you soon! LINK TO SOURCE: https://www.avsim.com/forums/topic/519789-13sep17-updates-pushed-for-737ngx-all-and-777-200lrf-product-lines/
  8. 5 EURO COUPON CODE FOR CURRENT FS2Crew 777 CUSTOMERS: 77764 or 30% Discount with a VA discount code Yes, the product need to be purchased again. https://www.fs2crew.com/cart/categories/Special-PMDG-777-Area/
  9. Version 1.0.0


    PMDG Operations Center compatible. See readme.txt for removal of topside wing registration...
  10. View File TSL PMDG Boeing 777-300ER Series Livery PMDG Operations Center compatible. See readme.txt for removal of topside wing registration... Submitter OMGEDSON Submitted 01/07/2017 Category Patron Repaints  
  11. Version 1.0.0


    PMDG Operations Center compatible. See readme.txt for removal of topside wing registration...
  12. View File TSL PMDG Boeing 777-200LR Series Livery PMDG Operations Center compatible. See readme.txt for removal of topside wing registration... Submitter OMGEDSON Submitted 01/07/2017 Category Patron Repaints  
  13. I like to document findings for future reference, here are some I think could help many pilots of the 777! I had a similar problem when I started messing with FS Real Time. It'd just do a clean CTD when it was adjusting the time. Also, when fiddling about with the various menus it would do it. Read around, found a lot of mentions for a "UIAutomationCore.dll", apparently an old FSX fix. I dropped that in my P3D folder and the CTDs stopped. Other than that, you'd need to figure out the error that's being reported. You'll still see clean CTDs being tied to a specific .dll, service or other when looking through the event viewer. Then you can Google that specific event in relation to P3D. AVSim also has an extensive troubleshoot guide. source: @Sethos via Reddit Out of Memory. With any other payware aircraft, one normally gets an Out-of-Memory notification with FSUIPC dings leading up to the crash. With the PMDG777 and P3D, no such warning. It simply quits to the desktop with no error message. I've done what you have: Clean install of everything. Same result. Crash with no error. In FSUIPC, setup an offset to measure VAS inside the P3D: VAS FSUIPC Monitor This will show you how much VAS is remaining. Do you select a STAR and arrival runway before takeoff? If you do, stop doing that. If there is a radial intercept in the missed approach leg, it will leak memory at about +/-100 Mb per hour. This is a known bug documented in AVSIM where some get a CTD after three hours of flying. If you're starting out with 300-500Mb at departure, you'll be OOM within three hours. source: tateep via Reddit
  • Create New...