Speedbird193

No problem here with Flow in 7.1. Perhaps a conflicting addon? Have you tried reinstalling Flow?

As stated in my initial post, there are before & after screenshots in the linked GitHub repository.

The latest version provides an option to keep the glow around the sun. You can set it via the ReShade menu.

They also said they wouldn't do a NEO, and here we are...

Amazing update, they really keep setting (and re-setting) the bar. I’m sure I’m reading too much into this, but Amir talking about the A330 descent modes really makes me wish they’re working on one in the background…

It's a game changer! The overall scene looks so much more realistic now. That said, I agree it's a shame the community has to fix things that Asobo seemingly can't be bothered to address themselves. Installation guide It's actually quite straightforward. I didn't have ReShade installed before adding the DLSS Ghosting Fix and this mod, and the whole process took me about five minutes. 1. Download RHI Download ReShade Helper Installer (RHI) from GitHub. 2. Download the camera FX mod Get the files from the msfs2024-camera-fx-off GitHub repository and drop them into the following RHI folder: Users\[your username]\AppData\Local\RHI\Custom\Addons 3. Install ReShade Open RHI and click Install ReShade at the top (you might have to run as Admin). 4. Select MSFS 2024 Select Microsoft Flight Simulator 2024 from the menu on the left. 5. Enable the custom add-on Under Shaders and Addons, click Select, scroll down and tick the entry under Custom Addons. 6. Manually copy the camera FX file RHI only copies the main file into your MSFS 2024 folder, so you'll need to do this last bit manually. Navigate to the folder containing your MSFS 2024 executable. The GitHub instructions show the Steam location; if you're using the Microsoft Store/Xbox version, it's under: XboxGames\Microsoft Flight Simulator 2024\Content Copy the msfs2024-camera-fx-off file into that folder. 7. Disable the effects in-game Launch MSFS 2024, load into a night scene and use these keyboard shortcuts: - Ctrl + Shift + F5 – Toggle lens flare (easier to test during bright day scenes with the sun visible) - Ctrl + Shift + F6 – Toggle bloom - Ctrl + Shift + F7 – Toggle the overblown star-shaped lights Each shortcut toggles its respective effect on or off. The difference is pretty obvious, particularly with the star-shaped lights, which look ridiculous with the effects enabled. And that's it! Once you've toggled the effects off, you shouldn't need to touch RHI or the keyboard shortcuts again, and there's no extra app running in the background. One thing to keep in mind: the GitHub repository is updated frequently, and the msfs2024-camera-fx-off file is tied to the sim version and shaders. Keep an eye on the repository and, when an update requires it, download the latest version and replace the file in your MSFS 2024 folder. There's also a helpful YouTube tutorial from Island Sim Pilot explaining how to install ReShade using RHI. His video focuses on the DLSS Ghosting Fix, but the process is essentially the same, apart from the additional manual file copy described above. Hope this helps anyone else wanting to give it a try!

I posted this in the DLSS Ghosting fix thread, but thought it deserved its own discussion. Someone released a ReShade mod to turn off lens flare, bloom and the excessive "star" or "halo" lights in MSFS24. Comparison pictures are included in the link. GitHub - joaobettu/msfs2024-camera-fx-off: ReShade add-on that removes the lens flare, bloom and lens dirt from Microsoft Flight Simulator 2024 · GitHub It works the same way as the DLSS Ghosting Fix, just enable once via ReShade or RHI and enjoy. I just did EGLC-EGPH-EGLC at dawn/night with all 3 toggles active and it was a completely new sim experience. Great to see the community fixing what MS/Asobo haven't managed to fix for years. Note that if you use RHI to install it, you need to manually copy the "msfs2024-camera-fx-off" file to your MSFS executable folder as RHI only copies the ReShade files. This file is needed to make the bloom toggle work.

Lots of mention of “POI light fixes” in the Gaya section. Can anyone confirm if the overexposed landmarks have been fixed?

Haven't tested it yet, but someone else has seemingly fixed lens flare and bloom via reshade in the same way: Asobo won't let us disable bloom and lens flare in FS2024. So I made something... : r/flightsim

Excellent news! A high quality LEMD is long overdue - the LVFR version really doesn’t cut it in 2026.

Currently on an Alienware AW3423DWF. Had it for 3 years and absolutely love it, I couldn't go back to anything but OLED. The image quality is on another level with HDR. I never noticed any flicker using TAA. No issues with burn in either after 3 years of pretty much daily use. VRR flicker can easily be managed by sticking to a stable frame rate - it only flickers when it jumps massively across FPS and even then it's only really noticeable during dark scenes/night flights. Set a frame limit in MSFS and let GSync handle the rest and there will be no flicker. I'm now waiting for my new AW3926QW - 5K2K OLED which should be another step up in image quality. Ordered the day it was released in the UK, but seems they underestimated demand quite a bit as my current delivery date is 4 December.

I use this with the A350: JP Jump Ahead – A tool to skip long cruise segments as an alternative to simrate acceleration. - Utilities for MSFS | Flightsim.to I can get it to 8x without a single problem, but because ini's internal implementation maxes out at 4x, the fuel burn and elapsed time remain at 4x. That tool lets the user sync the fuel burn to simbrief values at any given point, so I just sync every few hundred miles. That works, apart from the A350 yelling at me that there's a fuel leak, because it doesn't understand that I used the external tool to adjust my fuel burn to correctly sync to the 8x. I've done this a few times and no issues at all with flying it at 8x, but the fact that I have to use an external tool to then fudge the fuel burn to match my flight plan and the aircraft then getting confused because of the fuel sync is just silly. It clearly shows that technically it's easily possible to implement 8x in the A350, and all ini would have to do is add that option natively and then build a proper fuel and elapsed time sync to go with the 8x. I can fly PMDG aircraft up to 16x over water and it works perfectly, so I personally think ini are just lazy to implement anything above 4x.

Thanks for everyone's opinions on how I should enjoy my hobby. Your approval of how I simulate my flights means a lot to me, so I'll just go find another hobby now to escape the shaming looks of all the real-time apostles. On a serious note, I really don't understand why some people feel the need to police how other people flight sim. If you have 16 hours to sit in front of a screen and stare at water then well done you. I have a job, a family and limited spare time. If I want to use time compression while flying over an ocean for endless hours then I really don't see how that is impacting your enjoyment of how you like to simulate your flights, but I guess people feel the need to correct other people's opinions on everything these days. I think you'll also find that "real" long haul pilots fly real planes with a crew of pilots and get paid for that. They don't sit in front of a screen and tap themselves on the shoulder for not using naughty time compression. This places makes me laugh sometimes...

Again, only up to 4x time acceleration on an aircraft that flies 16 hour routes. Why are ini allergic to 8x - PMDG have managed to do it for decades, I just don't get it.

Community hotfix until MS gets a fix out: Points of Interest night lights fix - Scenery Enhancements for MSFS | Flightsim.to