sddjd

Just as likely it’s coincidental with my update. Been to their forums, but it’s hard enough getting support for their current products let alone UTII. That place is a ghost town 😎

Anyone have a sudden issue with UT2 starting after moving to v4.5? I did the full migration and UT works in the sim under Addons, but the actual UT2 program won't launch now....? Gets through the loading screen and just vanishes.

With regard to ORBX PAKT, has anyone modified their AFCAD in a way that gets AI moving correctly to/from the terminal to the runway? Is it a matter of lowering the airport altitude by 80'....? Just not sure what steps to take....

Came here out of curiosity based on yet another ctd. You're not suffering in silence, nor is it you. While "Couatl is one of the addons that simply CANNOT crash the sim" removing the coutal-based scenery WILL eliminate the crashing issue. Similarly, it wasn't couatl causing the north Atlantic crashes, though a couatl patch addressed the problem for most (no end of arguments about how it was really couatl revealing a flaw in p3d and so not a couatl issue....). Just wrapped up a 5.5 hour flight to HNL to see the airport come into view, start loading the buildings, hang, spinning wheel, crash.... definitely no way it could be the HNL scenery tho. Of course it's all a smear campaign against couatl... so much so that other scenery designers are indicating "no couatl required" in their sales pitches.🤡

i7 6850k (6 x 3.8/3.6). I've been watching/testing the sim again lately (been away) and have noted that the panning stutters occur even when frame rates are off the charts; for example at certain areas I'll be in the high 70's due to low demand scenery, and will still have the microstutters when taxiing the aircraft through turns. I've worked with various refresh rates available on the monitor, 30hz through to 75hz. Contrary to what seems to have worked for many, syncing the monitor to 30hz and setting 30 as a frame-rate limit within p3d results in worse panning behavior than just leaving things at unlimited and 60 or 75hz. As your question implies I'm thinking this is either related to processing power or to an inherent limitation in my monitor, though the latter seems less likely due to the smoothness of spot view panning... Task manager shows the typical core1 being maxed by the rendering process, while other cores are at low utilization during flights or airport navigation even at heavy sceneries. 1080 is rarely much above 60-70%. I guess I'm willing to upgrade mobo and cpu, but as always the hesitation is to risk a full rebuild without a tangible improvement.

Actually, I ran into the exact same issue and know for certain I had AI detection active. Seems that somehow in the installation process it's getting reset (maybe through a SODE check?). Either way, super simple fix but good thing for other buyers to know to check right away.

This is ADE indicating that it can't locate the bgl's embedded in the file you've opened to edit (not too uncommon, but the failure of the black box compile is more unusual but not unheard of). First thing to try is to use ADE's Library Object Manager and add file / add folder - point it to your scenery folder (the suspect scenery that is) and let it work. It should find and add the definitions to ADE, potentially allowing you to compile successfully. It's not foolproof, but one way to check after the LMO runs is to reopen the file and click on a black box- it should change to the footprint of the actual object if it's found.

So, any word on L2 and AI compatibility? As beautiful as the models are it’s still too great a loss in realism to give up AI jetway docking at large airports.

I had similar issues, eventually found the X models on skysim’s Update page that will display in v4. However, the qw lcd gauges are qw model dependent and won’t start up when another aircraft model is linked. The shots are beautiful but it appears the model combo is something OTHER than what is described. Countless other users are attempting the same and searching the web for methods without success. Don’t get me wrong, I really want it to be possible, but I’m filing this one under hoax until some facts are posted to support it.

Yes, which further puts into question the other post showing a functional merge with, to date, no substantiation.

Yep, tried just about every different combo I could think of (757 & panel into 767 folder, vice versa, etc). Even just adding the model to the 757 folder and assigning it via the .cfg "breaks" the LCD gauges (this isn't really viable in the long run as the contact points are wrong, but was done to first try to address the gauges issue). For whatever reason the LCD's seem bound to the QW model unfortunately. It throws error code -6, which I wasn't able to locate in the QW forums or elsewhere. Without a link to the Youtube process vaguely referenced in the other thread it's looking like this is another 767 unicorn.

Yep, tried all the "normal" steps- seems like there may be some dependencies on the QW models themselves that are preventing the lcd gauges from starting up. All the steam gauges are functioning.

I'm finding nothing on Youtube related to the QW757 and SS767. Do you have a link? None of the standard methods are working for this combo here...

Agree, and we've both accomplished merges with other combinations (I've done many with more complex add-ons that the QW757)- this one however isn't working as expected, possibly related to the SS767. The models will display, but the QW main displays throw errors. Similarly the external wing views display the QW model instead of the SS model. The linked thread did appear to prove it's possible, but the author is so far avoiding detail on what steps were taken (three answers so far, not one substantiation).

Once you're in your sim in the top down view you can open the airport in ADE. Click "connect" in the upper right corner, then click the "Lock" button. ADE will show your aircraft (red crosshair) and lock the view to your position in the sim.

magic, any chance of posting instructions for this merge? A few of us have been struggling with getting this to work / appear in-sim. Thx!

I must have the same inability to search as you do ejoiner, as I haven't been able to find anything online by anyone who's accomplished this. Have you been able to get the visual model to appear in p3d? I can't seem to get past this step, even though I've taken the same steps as in the past with other model merges.... It will list as an aircraft in the selection menu, but will not load/preview the exterior.

The taxi lights are actually present, but are loaded into p3d below the ground plane (you can test this by panning a spot view down to ground level until it starts to clip). I couldn't figure a way to fix this. As for ADE, keep in mind that the stock airport file has an insane number of apron objects that exceeds the max the program will compile. I ended up doing a huge rework on my own, but it was a major project (no issue with landing/taxi lights however). As has been noted, probably just worthwhile to wait for the new version as Overland's, while a good example, is certainly showing its age.

Aha, yes you are correct! My fault for viewing on a mobile screen 🤐

Bigsky, that photo indicates a double airport - the default jetways are showing up where duplicate parking spots are appearing. My guess is that you may be missing the exclusion of the default airport in the A_A scenery folder. I can check this afternoon as I'm using the same in v4 without similar issues (not flawlessly, but well enough to use however).

Exactly- top down view is the most effective as you can have ADE and your sim open side-by-side while you move around the airport (make sure to connect, then lock ADE to your sim).

"I saw many of you have problems with the scenery because it is not installed properly." Is anyone having issues with the KSAN update related to FTX Central? I made the mistake of upgrading to the latest version to try to address my misaligned jetways, and now have an unusable product. Sadly I have no way to go back to my previous version. 1. The frame rates are appallingly bad in the new version, single digits, whereas the previous version reached an average in the high 20's on my system. 2. FTX Central will not manage the product- the control panel refuses to save any changes to the scenery, specifically FTX Mode and Static Aircraft options. No amount of selecting, closing ("your changes will be saved when you close this window"...) the control panel, etc, makes any saved changes to the scenery. I've uninstalled completely, rebooted, reinstalled, rebooted, countless times. Even after a clean new install via FTX the control panel doesn't function, and the "verify files" button seems to think EVERY file need updating and downloads the entire 5gb again and again. Just to ice the cake, apparently this endless loop has hosed my P3d install to the point of not starting.... ORBX's support forum was helpful enough to provide the following advice: "...uninstall, reinstall and then leave it alone while it is working. Verify files is not there to solve problems with frame rates, it is there to solve problems with the product." Hm, apparently the point that it is NOT working was skipped over. Quite disappointing to see that my detailed problem report wasn't even read, so in light of such proactive support of their product I'm reaching out here to see if anyone has had a similar breakdown between FTX Central and KSAN or any similar experience.

Agreed, I finally bit the bullet and spent an hour going through all my AI cfgs to correct the wingspan value to match the real-world aircraft. I originally was using a guideline similar to the link posted above, but found that using actual values allows me to better control certain types within an airlines- for example there are frequent times where I want 773's to park in certain spots due to tail clearances to taxiways behind (HAAB is a good example). There is a 12' winspan difference between these two, so accounting for that in the AFCAD helps keep them out of parking that might be wide enough but too short for the AI to appear correctly. Can be tedious, but the real world values can help fine tuning AI to a level beyond just the airline code.

Is anyone else having a terrible frame rate hit when in spot view of the 757? VC and all others are great, but spot is abysmal, dropping into the teens....?

Also agree with this- the try-before-you-buy option is excellent and something I wish was pervasive in the scenery addon community. I did some heavy editing to the FEDEX ramp, but that's not something I find unique to FSDT and it's something I tend to do to gain better control of what the AI does. Out of the box it works just fine. If you do try, I'd also recommend also doing some night flying to get a feel for the shimmers apparent on the runways under landing light illumination. This is a built-in limitation of the scenery due to its age, but is also something FSDT has acknowledged and would eventually be eliminated in any future iteration/update. Overall IMO that is a small price to pay to be able to use a good rendition of MEM 👍