sddjd

Yep, been there- what is strange to me is the different lights behavior under EXACTLY the same configuration at different airports.... just curiosity at least.

Just came across this post, but have to thank the author. The above statement is something I think is lost today for the most part. It seems more and more often I hear even documentary figures blur the line between soldiers and the darker true believers. I had two grandfathers and an in-law grandfather all of whom served for their respective countries. All three shared their harrowing experiences openly and always without malice for their opponents; the common thread was as it was for almost all soldiers- a desire to get their jobs done for their homelands and find a way home to their families. It was truly something to see these three together - Wehrmacht, Marine, and Imperial Japanese Army trading jokes and jabs while watching their grand and great-grandchildren enjoy life without (hopefully) ever truly understanding what they had experienced.

Just a question more out of curiosity than any problem. I've been flying quite a bit using the Etihad Cargo version from the Ops Center. I've noticed that usually the automatic systems disable exterior lights while on APU power (logo, wing, etc), and understand the reasoning behind this. However, fairly frequently I'm able to turn on the logo and wing lights during pushback while still only on APU. The only correlating detail I can find is that it seems like the lights work on APU power when I'm at a hot location (GOOY for example). Leaving much colder locales (HKJK at 00:45 in Dec for example) seems to never provide exterior lights until engine start. Am I crazy (very possible) in seeing this connection? 😎

Sorry, yes, seems that the stuck key is registering in all modes when p3d is running....

Thanks Vic, been going through those and don't see any conflict/assignment mapped to the 8 key. Cleared all slew commands from both the keyboard and throttle, same result. Seems I have an uninvited mystery here.... I'd planned to hold off on 4.4. Perhaps I'll bite the bullet and go full reinstall 😎

Fired up P3d 4.3 today. Noticed my trim was runway into nose down position (mapped to up arrow/num pad 8). As soon as I'm in a flight in P3d my entire system is highjacked by what behaves like a stuck key. All windows constantly scroll to the top, and the menus in any application scroll wildly as if I'm holding down either the up arrow or the 8 key. Through a dozen tests I've confirmed that this only occurs once P3d launches a flight. Killing the program eliminates the problem. It manifests itself in ANY aircraft. How on earth is such a thing even possible? I've confirmed the program seems to think the 8 numpad key is stuck by deleting it in the slew mode control assignments. Renabling it immediately sends me around the globe. I really have no idea how to resolve this... it's not a Windows issue or hardware since it's only active when p3d is running. Thoughts or suggestions welcome!

Got here via a search as I had the same question/comment. Understanding that the original LCF release was a model-only add-on with no dynamics changes, I've gotten well used to flying my -LR all around the globe in place of an -ER; would love to revisit the LCF routes in v4 😎 If this departs from PMDG's true-to-life approach, understood, but if the LCF model add-on ever appears I'd immediately support it with my wallet!

Lol, AA is giving them a run for their money by hanging on to theirs while constantly stating their intentions to retire them. Can't wait to be able to fly JFK-ZRH in something that's not almost as old as I am. Still, for simming there are close to 700 767's still flying, and more cargo variants appearing so I hold out hope for Level D to beat the odds and release an updated version. Note, I also hold out hope to hit a lottery win - not sure which presents better odds...

Been searching this and the FSX forum but not finding anything- has anyone found a workaround to the ATC issue at UUEE? I'm referring to the behavior where ATC does not read back / respond though the prompts appear correctly as if they did. Thanks!

One thing missing from contributors who own the FSL product is their feedback on frame rates. There's no doubt FSL is the more accurate in terms of just about everything, but it would be helpful in a decision to know if that comes at the cost of sim performance for the OP.

Umberto, thank you for the detailed explanation on the methods used and why the option doesn't currently exist for AI. I look forward to the future steps you described in terms of optional AI jetways at the GSX level (and understand the risks inherent in allowing users to replace all of their AI jetways with detailed GSX models when said users will then gripe about their systems slowing). 👍

While I don't necessarily agree with the first statement (non AI compatible jetways), I'd like to know what's behind the position that enabling the jetways for AI would be a frame rate killer. I have many very complex add-on airports that host many many detailed jetways that dock to my AI with no frame rate impact, or at least one that is very low. I think this statement creates confusion among potential buyers, myself included. Not sniping or criticizing, but genuinely interested. Is there something different in the way FSDT jetways are coded that would bog down a system if all were active? I can imagine in particular transparent and highly detailed jetways presenting this issue, but at existing add-ons such as KCLT I'm confused. There are several FSDT airports I would own today if not for the non-AI docking jetways. Thanks!

Anyone else have the SP tank their autothrottle functionality in CRZ mode? Immediately after installing the updates I'm unable to complete a flight as the autoflight system ceases to control the engines in CRZ. No help on QW forums (beyond the usual "reinstall P3d and all your add-ons" suggestions 🙄 )

I use Airport Design Editor. My method is to load an AI aircraft into the sim as the user aircraft (copy one repaint, a panel and sound folder, then edit the config to make the "title" unique) and then slew around the airport gates while ADE is connected to the sim. Adjust the gate positions to align with the crosshairs in ADE, etc. In the case of RJBB/KIX, most of the heavy gates were too far from the jetways to activate SODE with all but the largest AI planes.

Update- I've revised my AFCAD parking positions, adjusted for aircraft size and relative location to the terminal/jetways. The jetways are operating correctly now 👍

F737NG- thanks, that's actually better news to me than it being a built-in issue with their jetways. I'd already started modifying my afcad for this one (adding directional pushbacks for better GSX operation). I'll play with the various parking positions this weekend and let you know if I have success with the jetways.

Are you having any trouble with the SODE jetways and AI? I can't seem to get them to dock to AI planes- only the user aircraft. I've posted over at FSDev but haven't had any pointers yet. Thx.

I'm running into an issue where many .rte files I've saved and used frequently are suddenly creating an "invalid entry" message when entered into the CO ROUTE field. This seems much more frequent after updating my product in the past two weeks. Did something internal change that might have invalidated the way my 777 is reading these previously working rte's? Thanks!

Based on this statement I'm looking for ideas on how to resolve the python27.dll located in the FSDT\Addon Manager\Couatl folder bringing down my sim twice in the past four hours, both times well into a flight: Couatl.exe 3.2.0.3997 5b0e87ef python27.dll 2.7.13150.1013 5922d35a c0000005 000e77f0 97c 01d43bf8613490eb D:\FSDreamteam\Addon Manager\Couatl\Couatl.exe D:\FSDreamteam\Addon Manager\Couatl\python27.dll 2776f125-aca7-4667-a3f0-1945a322cac9 Is there any way to diagnose this faulting module? No other fault time stamps exist in the system event viewer, but both these entries appear at precisely the moments P3d4.3 goes down. I've had other sim crashes that pointed to other faulting items; these today only log the above.

Thanks all for the tips- I've performed most of these checks already, which is my main cause for frustration. Seems like the classic causes for duplicate scenery bgl's don't yield results. SAS shows only the PHNL_ALT bgl as active, and it's alone in the correct location, but SAS also doesn't scan xml-added sceneries so it's of limited use in this case. I've combed my xml files as well as compared them to their backups (made prior to each major scenery install) to no avail, all entries are correct without duplications or ordering issues. Same for my cfg files. This has become stranger- I've been able to confirm that the PHNL visible below the add-ons is the default (via renaming the APX bgl as a test and restarting the sim). So, once back from work I'm going to start investigating all the airport related bgl's that may no longer be correctly excluding this base layer. The CVX files for PHNL appear to be in place. No idea why this came after the DD & ORBX installations- those are the sole changes to the scenery configs/xml's in quite some time but as always it could be purely coincidental. It would make zero sense that two sceneries more than 2K sim miles away would have affected PHNL. Time for mad scientist mode now 🛠️

Hi cmpbellsjc, Thanks, nope, only using UT2. When I use GSX to view the airport file it's correctly pointing to the FSDT afcad, yet P3d (4.3) doesn't list these gates at all when using the go-to-airport function. Somehow the sim and the add-ons (like GSX) are reading different files concurrently. If I warp to, for example, gate 25 heavy in GSX it places me correctly. If I use the go-to-airport function and select gate 25 it shows as small and places me nearby in the FSDT terminal. The file p3d is using is clearly a default, as some of the generic jetway markings are visible along with the default buildings. Since none of the scanning utilities come up with a result, I have no more ideas on how to find out WHERE p3d is finding this trash file....

I'm at wits end- I have 60+ sceneries installed, #1 on the list being FSDT PHNL. This past weekend I installed both ORBX Ketchikan/Pac Fjords and Drzw Seattle Airports. A week later I visit HNL and find my airport is somehow completely ruined. There is clearly another airport afcad for HNL active, as it's overruling my FSDT afcad (none of the parkings are correct, and default scenery buildings are visible). I've run, run again, and re-run airport scanning tools, disabled ALL scenery even remotely related to the Hawaiian islands, and still this default garbage is appearing. The scanners report that there are no other active HNL files, but the sim says otherwise. ORBX? Drzewiecki design? These are the ONLY two scenery changes made in months.... Right now I'm supremely pleased that my money was well spent adding those two products that apparently hosed my FSDT installation. Can anyone suggest another way to determine WHERE this phantom HNL afcad is sourced other than reinstalling 60+ sceneries? I cannot understand how it is overruling a scenery that is priority 1 in the xml list of add-ons.... 😡

June 2017 - "EARLY beta means EARLY." followed by a lock on the thread. How DARE the community ask for additional info after the developer makes an announcement of beta status... the nerve of those people upon whom their sales depend. July 2018 - Total updates/communication, zero. At 10 years (that's being charitable) to reach 88% completion we could expect an update next year, likely in the form of another "it's coming, stop asking" post. IMO it's truly surprising that the crowd at FSCon didn't react with jeers at their "announcement". The 757 is now like the Iraqi a300's still on Airbus' order books from before Desert Storm.

Zimmerbz, any more info on Imaginesim's version and how you got past your problem? I'm shopping KCLT and tried out FSDT's version- beautiful, except that one needs to thoroughly search their forums to reveal the fact that they disable all AI jetway connections in the name of performance with no user option to enable SODE for AI. For me it's a deal breaker. No matter how good the airport looks it's rather silly looking IMO to have an airport full of planes without jetways connected.

Thanks for the feedback, been away on biz so haven't been able to test much. I did confirm that it was only occurring with my pmdg aircraft, but also only at certain add-on locations (RJTT, EGLL for example) so it's likely that the culprit lies with the scenery instead. However, since moving to 4.3 and rebuilding the relevant files I have not seen the behavior, so it seems I just dodged the issue in another manner. Thanks.