downscc

ADE comes with an excellent user manual and is especially good at helping beginners step through the basics. Note in the manual that you will be required to download the P3D SDK and install it and then point ADE to where a couple of those files are located. Basically, the ILS is a part of the runway container. With the airport in plan view within ADE just double click on any one of the ILS components, or select the ILS from the Navaids List (Lists being on the menu bar), and make the changes you wish. Note you can set lat/lon for the LOC only, the GS and DME can only be moved by dragging. You didn't specify what was wrong with the ILS but you eluded to the fact that the reason was the displaced threshold, so perhaps the only thing you need to adjust is the GS location. Check the PAPI/VASI locations too.... you might be able to use Google Earth to figure out where the landing zone and PAPI's belong.

Hi Michael, you first should have installed the SODE engine before trying to use an addon scenery SODE jetways. I'm sure Justsim has instructions in their product manual on how to do this. For reference, the default keycommand for SODE jetways is the Tab key but if you have any FMS equipped PMDG airplanes they will take the Tab key for the FMS scratchpad function. It is easy to set a different keycommand for SODE and they include this in their documentation. I like to use Shift+J just because it is next to the default Cntrl+J (which will never work for anything but default jetways).

This is real easy to fix with ADE.

I've been trying to reduce these long frames ever since v4 was released. One thing I've found interesting when using Process Explorer to monitor activity is that the kernel activity (the orange activity as shown on the CPU activity graphs) goes very high during a long frame. However, I/O activity, which one would be associated with kernel functions, does not increase. This means managing the core loading or getting faster I/O will not solve the problem. What I think is happening is that the scenery object load routines do a scan of libraries, not once but every time an object is loaded. Orbx eluded to this problem when they release the Orlando Cityscape and said they were working with LM on this issue. This would explain why the kernel activity is high but the I/O isn't because the library data is cached but the routine still needs time to run through libraries multiplied by the number of objects. Bottom line, poor software engineering.

We found some addons add something like AFLT for P3D that is supposed to fix some kind of problem with P3D lighting (?) but it is very buggy and does things exactly like this. I found the source for AFLT: https://www.fsdeveloper.com/forum/threads/aflt-now-generates-simobjects-for-custom-airfield-lights.440454/

I don't think the license authentication is going to remain active with a new OS on a new mobo. I would definitely deactivate the P3D license and do a fresh install. It shouldn't be painless, the only scenery addons that will not automatically reappear are those that use the FSX method (scenery.cfg) of installation.

I use tools from Herve Sors such as the BGL Navaids Direct Editor for existing navaids, or the EasyNavs tool to add navaids not already existing.

Wait a sec... default jetways do not have signs on them. If you have SLI then there is a known problem with P3D texture based rendering such as used by FSDT in KORD and GSX2

If you downloaded the P3D installer last week then it already includes hotfixes. When LM issues an update for P3D, they always provide full instructions on how to install the update. Be sure to check there first.

Changing from SSAA to MSAA settings will have a significant impact on performance.

I usually group all my addons by developer, such that all FlyTampa products are in the same add-on.xml file. This is just a personal preference but I've also played with using discovery objects in the add-on.cfg file too so preferences are subject to change.

Long frames are caused by loading scenery objects, about all you can do is reduce the scenery display distance. Performance will suffer if you are using more than about 6.5 GB of your 8 GB VRAM. I've found that when using high resolution textures and complex scenery like Orbx Honolulu that I'm hitting 10 GB of my 11 GB VRAM and things turn into a slide show.

The B737 FMS will automatically reduce the speed for the approach such that the final segment is your Vref+5. The 777 does not do this but just slips a 170 in there. It is important to set those speeds on the LEGS page when you set up the approach if you intend to use VNAV such as on a RNAV(GPS) approach where LNAV/VNAV is used down to mins. Don't rely on the computer to fly the airplane. Some will advocate FLCHG or V/S but the important thing is to be in command. 210 kt 10-20 nm out is not too high, in fact one might keep it at 240 up to the final heading to intercept final, and then a good target might be 190 at 9 nm. On GS intercept drop the gear and start dropping flap out on schedule such that you are stabilized on speed and configuration not later than 1000 ft AGL (500 ft if it is CAVU and you are visual). You will get a no autoland if you are not in landing configuration and on speed about 1300 ft AGL.

Is that the native resolution for your monitor? My 4K TV UHD native setting is 3840 x 2160. Interesting.

Agree, this is quite common with lower quality addon airports where the AF file is used for placement rather than a separate placement bgl. It does the same thing either way.

The ImagineSim is actually representative of the final planned terminal configuration. The other one is obsolete.

This will happen at airports that are not compatible with GSX, usually because they name their gates differently from the convention that GSX uses. In these cases the first thing I do when I see that message from GSX is use the SODE menu to activate the jetway. I have the alternate SODE hot key assigned to Shift+J to make it easy because the default Tab is used by the PMDG FMS scratchpad. I have at least a dozen airports where I must use SODE instead of GSX for jetways.

My HWINFO application launches on startup of Windows. It's great.

I read much about this here and in the LM forum and have come to the following conclusions: First, it is wrong to think that core0 fully loaded is a bottleneck. LM has explained that they design the work flow such that this is intentional and they take advantage of multicore environment. Second, I've played with the exact thing you observed that by toggling core0 off and on it seems to redistribute the loading. However, I've never found that doing this has any impact on performance, frame rate, stuttering, long frames or anything that could be either quantified or qualified. It's a big no deal.

Agree... and my way of looking is that trim during flare is similar to trim during turns... don't do it. Use the control pressures in these cases and during most maneuvers.

I assume it's not. Same as ImagineSim locations that have their parking assist feature. You can still use GSX but the parking location must have type of marshaller set to none if you use the ImagineSim parking assist.

To add to Jon's reply, FlightAware doesn't capture flight routes at many non-US locations including EUControl, so what you are seeing is just the route from entry into FAA airspace. My work around is to use the exit point such as SUPRY then look at the ground track of the flight and from where it leaves land I can usually figure which track the aircraft was taking. Of course rebuilding the route from LHR to Wales or leaving Scotland is easy after you've done it a few time since there are only a few that are flown. Then one must evaluate the time frame and use a website such as https://blackswan.ch/northatlantictracks and back up the TMI (date) to get the same tracks as were available at the time of the flight.

Yeah... agree, I cannot picture the problem you are trying to describe. Did the airports move or did the scenery surrounding the airport (photoscenery) shift from the default landclass? And as for flipped... the airport is upside down?

This turned into an afternoon delight. My FB Manager was not indicating an available update so following the instructions from the FB Forum I downloaded the latest FB Manager and installed it, which resulted in five of my nine products being locked. A closer look revealed that those were all purchased via esellerate prior to the 2017 conversion to direct sales. This conversion was done successfully when I first installed a new FB Manager but now broken by the Manger update. Another look revealed the problem to be I changed email addresses after dropping AT&T U-Verse in 2018; fortunately, the FB website had a button to push to merger old and new email addresses from which point I was able to download the five new installers. Each installation required a download, removal via Manger of prior install, install new and configure and finally go back in with ADE and correct the three of the five that had wrong ILS configurations. I had so much fun... I just love this hobby!

Peter, Orbx questions really should be in the Orbx forum where I have always found help on any topic. The Central v4 also has a tool right on the product options bar to verify files, which I have found useful in correcting minor landclass texture issues. Bottom line, follow the instructions. Be sure to run Central once after the scenery component update and before launching P3D.