roland_lfor

I'm using this in VR with an old rig, and it's great. The performance impact is variable along weather conditions - cloud layer, thickness, haze. I think the most important impact comes from haze when you have it everywhere including at high levels. I cap fps to 30 and use Vector XR to insert frames to reach 90Hz for the G2. So as soon as I keep 30 fps I'm good. It's usually the case except with the Fenix.

New version 0.7 available : News

Yes sure, to avoid conflict

As a VR simmer, I discovered that FSRealistic Pro is able to make camera moves based on G force or turbulence to the headset, which build a very interesting combo with UTL. Without camera shake it's difficult to feel turbulences in VR, and FS24 "camera shake" option does not apply to VR.

just bought it, but it's unable to download weather forecast from NOAA. Message displayed in the app: Online weather authorization required. Any tips? Does someone can share the Discord server link?

The best setting is the one that match your taste, experiment 🙂

Interesting new feature: it has a slider to add texture inside the cloud, which add matter and relative speed effect in. No more need to use CloudSurf addon for me. Nice to get everything in the same addon :-)

New version 0.6.1 online:

Author @tomwhoca found the cause of this cyclic stutter and has already a fix 🙂

This MOD is very interesting, however on my system it introduces a cyclic 1 second period stutter. Anyone else? Ticket opened on GitHub.

You probably have an old version of the in game BATC panel. Try to update it as it's not part of BATC core installer.

No but you can use Ordenator or other tools to reduce to 2k or 1k and compute Mipmaps. But don't forget to rebuild the layout.json after, otherwise you won't see them in FS24.

wondering if it's a Fenix Tech Log feature that tells you to wash the aircraft?

Excellent, thank you so much

Thanks a lot to integrate VectorXR support! Can you give the link to test the 0.5.4.5-test8 version?

Unusable here as well. Background Fenix exe's start and close after few seconds. Log-display.txt shows connection issues before closing.

Hi, a revolutionary addon offers now Frame Generation (among other enhancements) for all, I mean also for AMD GPU's. Thanks to @Reset XPDR to raise this on his AutoFPS thread! It's named VectorXR. It works perfectly with my AMD 7900XT :)

deleted

Very nice shader addon. And good news, it works also in VR (without needs to activate the OpenXR API during ReShade installation process)

Alternatively one can run a local LLM on his own GPU even without internet access, it's quite impressive. Then you you use and pay your own power consumption ;) I asked to a local Ternary-Bonzai-27B LLM if can help me on maintenance subjects of an A320, here is the answer: Of course! I can help you with maintenance on the A320ceo (the "classic" A320 fitted with CFM56-7B or Trent 800 engines, in contrast to the A320neo/LEAP/PW1000 variants). Today's date is 15 October 2026 — handy for aligning task deadlines if needed. To steer the assistance in the right direction, here are the main areas I can help you with: 1. Inspection and check organization - A-check, B-check, C-check, D-check: duration, intervals, typical tasks - Preparation and drafting of the maintenance log (MLR, faults, MEL/CFL) 2. Technical documentation - AMM (Airbus Maintenance Manual): how to work with its chapters - TRB/SRM (Troubleshooting and Repair / System Reliability Management) - FCL (Fault Correction Logic), **EPC**, **EAD** - AD / EAD / EDD / CD: maintenance instructions, interpretation 3. Systems (depending on your area of interest) - Avionics and AFCS / FMS - APU (PW127M): APU checks, EGT, APU test - Hydraulics (green/yellow/blue systems) - Electrical / buses - Propulsion: CFM56 / Trent 800, engine inspections, TSO, ducts - FWM / EGT / BITE, PMA - MEL/CFL: approvals, restrictions 4. Troubleshooting & hands-on work - Reading fault reports (PFA, fault reports) - System troubleshooting, root cause analysis - Preparing a **maintenance report** or a **fault analysis** 5. Training / exams - A&P, AME, or an A320 maintenance module - Review focused on a specific module (e.g., "APU checks," "hydraulics troubleshooting") To get started effectively, tell me: 1. Your background (A320 technician, AME, student, etc.) 2. The specific subject you want to work on 3. The context: exam, hangar work, fault analysis, or just general knowledge? I'll then adapt to your level (basic explanation / technical / AMM references). 🛫

Vincent, in France with french VFR rules you may try AiTC, yet very impressive. https://aitc.aero/fr/

Yes, and with visible differences in size and foliage day by day during transitions.

More density. I have Bijan too. What is better with BB for me is: diversity in type and size. Day by day progression of trees during spring and fall in leave density and tree size. What I miss from Bijan is the light and bright green color of leaves during early spring (north hemisphere).

Density has drastically changed with the first update. This comparison should be done again.

Release notesWhat changed in each FFB-Bridge build, newest first. The desktop app links here when it finds an update. 1.4.4FFB-Bridge 1.4.4 repairs a serious 1.4.2 regression on the MOZA AY210 that left the yoke without centering load, airspeed feel, or stick weight while engine and ground vibrations continued, adds a base damping floor and working base-resistance controls for the AY210 family, fixes helicopter autopilot follow never moving the stick on non-MOZA devices, and adds conditional support for the MOZA AY90. MOZA AY210: stick feel restoredCentering load, airspeed feel, and stick weight render again. In 1.4.2 the AY210's static forces were routed through a firmware mechanism that accepts commands but does not physically render them on this base, and the effects created at arm were additionally silenced by the follow setup, so only engine and ground vibrations came through. Trim and the airspeed load now render through the standard spring and direct force channel, the same progression the base had in 1.4.0: resistance starts at low airspeed and builds continuously with speed. Confirmed on a physical AY210. Forces survive autopilot engage and disengage. Entering or leaving autopilot follow is a firmware boundary on MOZA bases after which previously loaded effects go silent. Every effect is now refreshed at that boundary, on the AY210, AY90, and AB9. Autopilot follow itself still runs through the firmware servo, which is unchanged. Trim behaves like 1.4.0. The elevator trim wheel shifts where the yoke settles through the normal centering spring on cable-linked aircraft. MOZA AY210 and AY90: base damping while armedThe base keeps a minimum resting resistance while armed. Arming zeroes a MOZA base's own damping so the bridge can render its own feel; on the AY210 family nothing was put back, and with forces restored an undamped direct-drive yoke could oscillate when released away from centre. While armed the base now holds a minimum of 10% damping, 5% friction, and 5% inertia, measured on a physical AY210. The Base resistance sliders now work on these bases. Hardware, MOZA, Base resistance saved values on the AY210 family previously had no physical effect. Your setting now replaces the default minimum; an aircraft profile can ask for more but never less. Helicopter autopilot follow moves the stickAutopilot follow works with force trim configured. On helicopter profiles the force trim system owned the centering spring outright, so the autopilot follow cue never reached the device on the SideWinder FFB2 and other non-MOZA sticks, in both simulators, even with the follow slider raised. While the autopilot is engaged it now owns the spring; holding the trim release still frees the cyclic; and on disengage the force trim holds the cyclic where the autopilot left it, the way a coupled autopilot flies through the trim system. New device: conditional support for the MOZA AY90The MOZA AY90 FFB base (346E:1003) is supported conditionally. It runs as an AY210-family base: raw HID and DirectInput on Windows, evdev on Linux, IOHID on macOS, firmware configuration ownership, autopilot follow, and the same damping floor. Support is based on three approved ffb-probe reports and the AY210's validated behavior; it has not yet been validated on a physical AY90. If you fly one, reports of anything that feels or behaves wrong are welcome through Support.