boez

May be worth adding a screen shot of that to the bug report thread on the official forums - if you’ve not already done that 🙂 https://forums.flightsimulator.com/t/default-jetways-broken-since-v1-6-3-0/737465 In my (limited to a few hours) experience not all airports are fixed although this could be the “handcrafted” airports which may need to be recompiled against an updated SDK?

When are you starting Atmos Core? I’ve found it best to wait until at least when the flight is fully loaded (i.e. ‘swooped in’) and at the final “click to fly” stage.

Bug reporting link found on Discord server 🙂

@timest I’m using latest version specifically for su4 beta and I find that autoloading of the “Weather” custom settings at startup of Atmos Core does not work. The ‘recent’ section of the home page of the app may indicate that my preset has been loaded but this is not the case. You can see the correct settings load if you then go on to manually click on the preset. Where is the best place to post a bug report? p.s. I only use the Weather custom settings so don’t know if this bug applies to auto loading of the other settings (Atmos and Environment).

Apologies if you already know this but once a slider is selected by the mouse you can use the keyboard arrow keys for a more precise change of the value. (I’d like to credit the previous poster who pointed this out but can’t find their post!)

Just for info the issue is actually with the hydraulics which of course affects the brakes (at least on certain aircraft). The SAAB 340 is where I first noticed it. Whether it breaks the brakes(!) depends on when the aircraft was last built as it is SDK dependent (newer ones aren’t affected) or whether the aircraft uses a custom hydraulic system. *note the SAAB brakes work for a few presses of the pedals - then as if the hydraulic fluid leaks out they stop working

The full preset name is “AB MSFS”. There is one in each category Weather, Atmos and Enviro. According to the creator @abennett you should load them via the 3 tabs and not those listed on the top 5 as they are older versions. Edit: I’ve now found the post where abennett explains this in more detail…

Yes that works without issue (and is how I have it set up).

I contacted JustFlight about this matter and they responded that it will be available to buy tomorrow (1st September).

Is that a lighter instrument panel mod? May I ask where you got that from?

New section in official forums now…

Downloaded and confirmed 1.5.1.0. All went smooth. Taking my usual first version flights now. Zero issues.

MSFS is trying to call a function named agsInit which I presume (based on the ags prefix) it is expecting to find in the amd_ags_x64.dll So either that DLL is missing (have you checked that DLL is in the MSFS application folder?), or, that function has been renamed or removed in the later version of the DLL. If that’s the case then you’ll need to go back to the older version that worked.

You’re getting confused. Your screen shot is showing application version 2.13 (the latest release version as of Jan 12). You have selected version 3.0 of the FG algorithm. But there is also an application version 3.0 (currently only in beta) which is algorithmically identical but has a major revision to the UI. edit: hadn’t seen the above post by Richard when I posted.

Version 2.13 has been released. 40% reduction in x2 mode is a major improvement. Cancelling my RTX5090 order right now 😉 2.13 released | 3.0 beta Happy anniversary, LSFG! LSFG 3 is built on a new, efficient architecture that introduces significant improvements in quality, performance, and latency. Key improvements include: Reduced flickering and border artifacts, with noticeable enhancements in motion clarity and overall smoothness. Lower GPU load: A 40% reduction for X2 mode compared to LSFG 2 (non-performance mode). Over 45% reduction for multipliers above X2 compared to LSFG 2 (non-performance mode). The "Resolution Scale" feature remains an excellent way to further reduce GPU load. For instance, setting it to 90% roughly aligns with the LSFG 2 "Performance" mode. Better latency: Latency testing with the OSLTT tool (at 40 base FPS, X2) shows approximately 24% better end-to-end latency compared to LSFG 2. https://steamcommunity.com/app/993090/discussions/0/598515385949554915/