touchdown84

Does that mean there is already some work done understanding on the structure of the scenery/airport BGLs from 2024? Because I couldn't find any information on the structure anywhere and for a small project I want to read part of the BGLs, but can't figure out what has changed from the offsets/field sizes etc. since 2020. If there is already some structure documented somewhere it would be nice to see that.

I think there is something weird with linked templates when you add a "Fast Turn" assignment to an aircraft where a linked template already contains a normal (slow) turn assignment. In that case the slow turn assignment in the template is never triggered, when slow turning nothing happens and only when fast turning the direct assignment in the aircraft is triggered. When I apply the template directly to the aircraft everything works as expected, as well if both assignment (slow & fast turn) ar both part of the linked template.

Just use 105 Render Scaling with or without TAA, there is an OBVIOUS difference in aliasing, especially visible on sharp edges (e.g. wings in external view), TAA is doing the heavy lifting there. It is applied in two completely different stages of the render pipeline, Render Scaling affects the initial internal render resolution and TAA is a post-processing effect. By the way, combining different AA methods has always been a thing, like MSAA+SGSSAA, and especially when one of the passes is a post-processing effect like FXAA or TAA.

I think you misunderstood the information text in the settings, Render Scaling > 100 does not "switch" from TAA to SSAA. TAA and Render Scaling are applied sperately for a combined result. The information text just states that it is recommended to use TAA when using Render Scaling < 100, as hard upscaling is increasing aliasing. But that does not mean you can't use it as well when downscaling (super-sampling).

It cleans/sharpens up some more edges, I use a large 42" display, that increases the perception of aliasing. Even with frame gen I'm limited by CPU anyway.

For me, at 4K, TAA + 105% Render Scaling looks good.

Hello, I see a weird behaviour when I want to merge a template into an aircraft configuration when the template already includes a linked template. When I do not merge but replace (or apply to an empty config) everything works fine. But when I merge, the linked template is not added as a linked template to the aircraft but the content is instead applied hard to the aircraft config (including e.g. aircraft automated scripts). Also during the merge dialog when I can select what entries from the template should be merged there is nothing mentioned from the linked template. I would expect to be added as an linked template (ignored when that aircraft already has that template linked), or at least offer to de-select those entries in the merge dialog. And another thing regarding templates, when during export I de-select a script group related to that template, it still gets added to the exported file. Seems a bit confusing to me.

Don't forget to apply the additional 20% discount code if you already own the 146.

Aerosoft has a sale on the Honeycomb Alpha for 199.99€ (may vary a bit depending on VAT) until end of week (regular current price is 280€, old release price was 250€). Probably mostly interesting for German/EU customers due to shipping (e.g. 6.99€ shipping in Germany or free if you buy anything else as they have free shipping to Germany from 200€). https://www.aerosoft.com/de/shop/flight/hardware/yokes/2567/honeycomb-alpha-flight-controls

It does not contain any physical media (confirmed in the Aerosoft forum), just an activation code for the MS store. I guess they learned from their stupid DVD-DRM decision for the 2020 physical edition.

I just ordered the Collectors Edition from Aerosoft, I think the value for the physical extras is ok. It's 60€ more than the digital Aviator Edition here (280€ / 220€, no shipping costs for Germany). And I also only already have bought one of the extra planes inlcuded in the Aviator Edition.

Just Flight is working on the A300B4.

I know, but I find it easier to edit the txt file directly.

I am using this https://de.flightsim.to/file/38162/x-touch-mini-gauge-for-use-with-aao-axis-and-ohs It's a bit complicated to set up and you have to assign the controls for the X-Touch in a separate config file, but it also allows you to control the LEDs.

I think you can make duplicate names unique by appending the name with its coordinates in the gfp file, see this post in the Navigraph forum regarding the gfp export from Simbrief: https://forum.navigraph.com/t/gfp-format-garmin-gtn-wrong-export-for-ambiguous-waypoints/11182