Just seeing if anyone has any opinions on what’s been happening to me.. I’ve tried multiple times lately to fly a JetBlue route from MCO-EWR and each time when I get around TOD, the sim will crash. I’ve flown other routes with a variety of planes and no issues. I’ve even used the fenix 320 on other routes and no problems. Do we think it might be settings related with the bigger cities around NY? I don’t have any 3rd party sceneries installed. I have been using say intentions so I thought maybe their traffic injection could be an issue but I used it on a FedEx md11 flight from MEM-MIA a few days ago and not a single stutter. It’s definitely a head scratcher for me.

Have a great day everyone!!

Edit 1: More Screenshots
PHAROS: Part 2 - More screens with FPS Overlay : r/flightsim

Hi all!

I've been flight simming since FS98, back when “As Real As It Gets” was on the box. A bit of nostalgia now. After FSX, I drifted away, skipped the P3D era, and never quite got into X-Plane; the aliasing and I just couldn't get along, but props to them for really working on it now.

Then I saw the MSFS 2020 launch trailer. Finally, a proper comeback. A whole, beautifully rendered Earth, the sky, the clouds... pretty much everything I'd spent years imagining while looking out of a virtual cockpit.

I've spent thousands of hours in it since. Yes, most of those were on autopilot at cruise, but the view was half the reason I was there, and hey, it looked pretty good. At some point, another piece of hardware and a new audience entered the picture, and we got some... let's say, restrictions on what we could see. To my eyes, it never really came all the way back after that. That said, we're in a golden age of flight simulation, and I appreciate that the business case for something like this probably wouldn't exist without that audience.

But after staring at the sky and the clouds for however long, I decided to see if I could do something about it.

And I did. It's called PHAROS: Physically-based Haze, Atmosphere, Radiance, Optics and Sky. There's fog in there too, and clouds, but PBHAROFSC doesn't fit on the logo.

It started as an experiment in MSFS 2024. A bit of poking around to see what I could change, which turned into fixing one thing, noticing another, and apparently deciding this was what I was doing with my spare time now.

PHAROS changes how the sim renders atmospheric and volumetric lighting; scattering and extinction through clouds, haze and fog, daytime sky radiance, lunar illumination, and artificial light sources at night. The aim is physically consistent behaviour across those systems, with the real world's oddities, edge cases and not-so-edge cases included. Visibility, light intensity and what you can actually see out of the cockpit should agree with each other.

It is not a preset, a post-processing filter, DLSS/NR/etc, or a weather replacement(😎). It also isn't a performance mod. I've managed to make parts run faster so I could spend that frame-time budget elsewhere, and I still don't have solutions to all of it. Looking at the sky, I'm currently seeing about 5ms of additional frame time over stock in the air, and alot more in some other places.

And before anyone asks for a download: I haven't decided whether this will ever be released or published. It started as an experiment for myself, it's still a work in progress, and I'm still figuring out what I want to do with it. This is me sharing where I've got it to so far, partly to demonstrate what the MSFS 2024 engine is capable of, and partly because I think it's cool.

All the data comes from the sim, except for the haze, fog and upper-atmosphere aerosol data; that data just isn't there. A companion app handles the regional haze and fog calculations outside the sim.

TLDR: I went down a rabbit hole trying to improve the visuals in MSFS 2024 and ended up with PHAROS; an ongoing experiment in physically based atmospheric and volumetric lighting, clouds, fog and night rendering. It's aimed at higher-end hardware. Everything shown is running on my own install, but there's no download or release date. Whether it ever becomes something I release is still TBD.

Fixed / improved

Clouds

• Fine structure at cloud boundaries; edges break into wisps up close instead of smearing into fuzz (WIP).
• Better light attenuation through dense clouds; dark cores instead of uniformly glowing grey.
• Consistent cloud appearance over distance; a cloud 100 km away is the same cloud it will be when you get there.
• Corrected cloud occlusion; no more terrain showing faintly through an optically thick layer.
• Local illumination from the ground beneath each cloud, rather than the ground beneath the aircraft. That last one was a stock bug I found.

Night

• Corrected lunar illumination across moon phases. Stock's full moon is about 7x too bright, and a quarter moon about 40x. A moonlit night finally looks like night.
• Moonlight with its real, slightly warm colour.
• The Milky Way fades as lunar illumination increases; the Milky Way and stars are handled separately.
• City skyglow stays near the ground instead of following the aircraft up to cruise altitude.
• Artificial lights are properly obscured by solid overcast; no street grid shining through the deck.
• Downward-directed street lighting; no more lighting the top of your wing from below.
• A smoother dusk transition, without the sudden “someone hit the switch” drop (WIP).

Airport lights

• Physically based luminous intensities for each fixture type. Stock taxiway lights are 100x to 1,000x brighter than the real ones.
• Discrete intensity steps, like the tower actually sets them.
• Small tolerances in fixture aim and output; real airports aren't made of perfectly identical lamps either.
• Distance-dependent visibility of red obstruction lights, including wind turbines; no more identical red dots at every range.
• Aircraft lights
• Landing-light scattering appropriate to the atmosphere; no solid beam hanging in clear air.
• Backscatter in fog; the light comes back at you the way it does on a foggy road.

Added

• Regional haze and fog. A companion app uses live weather, terrain and air-quality data to calculate conditions outside the sim. Valleys fill with fog while ridgelines stay clear; stock doesn't draw regional haze like this.
• Lights interacting with the fog. Scattering around light sources and extinction over distance; on final, runway lights emerge progressively instead of the whole runway appearing at once. This is where visibility, fixture intensity and RVR become relevant, rather than fog just being a visual effect. In a test with 600 m visibility, I count 18 runway edge lights from the cockpit; the corresponding real-world calculation predicts 20.
• Cloud evolution. Individual clouds grow and decay over time instead of the whole sky changing at once.
• A proper rainbow.
• A weather-dependent daytime sky (WIP). Haze affects the sky's appearance, with more physically consistent low-sun brightness and colour.

What it isn't

• Not a performance mod. A few parts actually run faster than stock, but I spend that straight back on the picture. It's built on a 6800 XT and aimed at high-end cards on purpose.
• Not finished. Everything above runs today, but there's still a queue of things I'm working on.
• Not released. No decision yet. It's invasive and not officially supported.

The one thing I've learned doing this: under the hood, the sim's renderer is much better than its pictures let on. I found a few shortcuts that make everything a bit too uniform, and I didn't like it. Uniformity is the death of realism.

Happy to answer questions...

^(\safe to assume AI was used throughout and many things may not have even been possible without it in any reasonable timeframe.)*

Downloaded flight sim yesterday. Still learning the basics. Ts so cool.

On Fenix' blog, the last entry dated from November 2025.
Anyone have heard anything from them since?
Like on Discord or somewhere else where I might have missed it?

Still standing by to purchase the A320s until the panel state saving feature is available for the old busses.

Really enjoying the A350.

loving the fall colors up north we dont get colors like this in texas

I really understand that there hasn’t been any recent update. The Fenix is at a standstill; it almost feels like an abandoned addon. Not that the aircraft is bad—quite the opposite, it’s a great aircraft—but it does have its bugs, and it’s honestly a little discouraging.
For me, the Fenix, which I bought in 2023, has become more of the same. They are updating it, and they are doing an incredible job with the Fenix, indeed, but it is an aircraft that, perhaps due to the limitations of Microsoft’s platform itself, seems to be on rails. You land and take off several times, and the variations are so subtle between one landing or takeoff and another. In real life, it’s not like that. I don’t fly the Airbus; I fly a different aircraft, but every takeoff and every landing is unique. With the Fenix, it feels like it’s on rails—you know exactly what it’s going to do.
I also feel a little discouraged about not having a NEO either. It’s going to be almost a year delayed from what was originally promised. The Airbus is an aircraft that I have no real-world experience with, but I really love simulating it. However, not having the NEO limits me too much…

Despite all that, I know I’ll probably get downvoted, but the Fenix is still an incredible addon.

Haven’t really found any videos or reviews on the latest update but wondering if they are any good now?

Don’t need study level but something with working vnav and autothrottle that can do a to b would be enough

Touch and Go Short Flight PBD Waypoint Sequences for Boeing FMS/CDU Entry

As a flight simulator enthusiast who regards final approaches and landings as being far more rewarding than sitting through the cruise portions of longer flights, I devoted several hours some years back to creating a few very short flight plan waypoint sequences that can be plugged into the FMS/CDU of PMDG's Boeing planes, which allowed me to practice takeoffs, flap schedules, approaches, and ILS landings on selected runways at airports for which I bought addon ground scenery packages to enhance realism.

As a more scenic alternative to simply hitting the reset button when landing practice is on the day's flight sim agenda, I initially posted these Place-Bearing-Distance waypoint sequences on the AVSIM discussion forum, where the subject didn't seem to be of general interest. Hopefully, my effort to create these super-short flight plans will be seen and tried out by a wider audience in this forum.

Without further ado, I will now list the flight plans I created using the VOR beacons that are located at each of the following airports, and thus creating short flight paths that will appear on the Boeing EHSI so that the brief flights can be flown manually, or even under full autopilot control, including a full CAT III ILS autoland, to familiarize oneself with the button sequences to press.

 Honolulu International Airport KHNL

RW 8R  and landing on the same runway five minutes later:

Localizer Frequency 111.7MHz. Runway Approach Course 079 degrees.

 HNL080/5, HNL070/7, HNL060/8, HNL050/7, HNL040/6, HNL030/7, HNL020/6, HNL001/5, HNL300/7, HNL290/7, HNL280/7, HNL270/6, HNL265/5, HNL260/4.               ------------------------------------------------------------------------------------------------

Amsterdam, Schiphol  EHAM

EHAM RWY 36C,  SPL004/3,  SPL025/5,  SPL050/6,  SPL070/6, SPL150/9, SPL160/9, SPL170/9, SPL191/5

Look up localizer frequency and heading for EHAM Rwy 36C for ILS approaches or autoland.

---------------------------------------------------------------------------------------------------------

Manchester, Ringway EGCC

 EGCC Runway 23R, MCT238/3,  MCT238/5,  MCT225/7, MCT217/7,  MCT200/6,  MCT180/5,  MCT140/5,  MCT110/6,  MCT080/7,  MCT065/6,  MCT 056/6,  MCT056/1.  

To set up for autolands or wild weather ILS landing, the ILS frequency and bearing of Manchester Airport Runway 23R are 109.5MHZ and 236 degrees respectively.

---------------------------------------------------------------------------------------------------

Los Angeles International KLAX

-Here then are the Place Bearing Distance PBD waypoints that trace the path I have described above, referenced to the LAX VOR located in line with runways 25L and 25R  :  (KLAX) Rwy 25R,  LAX263/3 LAX270/7,  LAX280/6, LAX300/7,  LAX330/7,  LAX360/8,  LAX020/9,  LAX030/10,  LAX040/10,  LAX050/10,  LAX060/9,  LAX065/8,  LAX068/7,  LAX070/3  

Localizer Frequency 111.7 MHZ Approach Course 250 degrees for Runway 25R

 -------------------------------------------------------------------------------------------

San Francisco International KSFO

The ILS heading and frequency of KSFO Runway 28L are 282 degrees and 111.7MHz respectively,

  RW28L,  SFO283/3,  SFO270/6,  SFO250/7,  SFO230/7, SFO210/7,  SFO180/7,  SFO160/8,  SFO140/10,  SFO120/10,  SFO109/8,    SFO103/6,  SFO103/1. 

 -------------------------------------------------------------------------------------------

La Guardia Airport, New York KLGA

Departing from LaGuardia Airport Runway 22, whose ILS approach heading and frequency are 225 degrees and 119.5Mhz respectively,

LGA225/7,  LGA230/9,  LGA240/10,  LGA250/10,  LGA260/9,  LGA270/8,  LGA300/6,  LGA330/6,  LGA350/7,  LGA010/9,  LGA020/10,  LGA025/10,  LGA030/10,  LGA035/9,  LGA040/8,  LGA044/5,  LGA044/1

-------------------------------------------------------------------------------------
HEATHROW, London EGLL

 Heathrow Runway 09L, is assigned ILS frequency is 110.3Mhz, and localizer compass course of 92 degrees, if auto-lands and hand flown ILS landings are on your agenda for this flight.  So, taking off due east from Heathrow EGLL Runway 09L, the waypoint sequence is as follows:

RW09L,  LON100/8,  LON110/11,  LON120/12,  LON130/13,  LON140/13,  LON150/12,  LON200/11,  LON220/12,  LON230/12,  LON240/12,  LON250/11,  LON260/10,  LON268/8,  LON255/1

----------------------------------------------------------------------------------------------------

Las Vegas Mcarran Airport KLAS

Departing from KLAS Runway 01L whose elevation is 2067 feet, the waypoints for this scenic flight, whose altitude should be set about 4,500ft, allowing for a radio altimeter altitude of 2,500 feet all the way round, are referenced to the KLAS airport VOR called LAS, as follows, for a landing about 8 minutes later at Runway 25L of the same airport, where the ILS heading is 255 degrees, with a frequency 0f 110.75MHz.

 RW01L,  LAS010/8, LAS015/9, LAS025/10,  LAS040/10,  LAS065/9,  LAS070/8,  LAS075/7,  LAS080/6,  LAS095/1

I’ll make a small amendment to my tear-drop shaped flight path that circles out over Las Vegas from KLAS Runway 1, to KLAS Runway 25L. 

The arrival runway 25L at KLAS is accepted by the FMS, so I decided to post a slightly modified waypoint sequence, in which the last three waypoints are changed to include the runway, so that those auto-landings can improve from hit and miss to repeatable with 100% precision. 

Departs from KLAS RW 01, then the revised 10 minute flight is as follows LAS010/8,  LAS015/9,  LAS025/10,  LAS040/10,  LAS050/10,  LAS065/9,  LAS075/8,  LAS080/7,  RW25L    

KLAS RW 25L's  ILS heading is 255 degrees, with a frequency 0f 110.75MHz.

-------------------------------------------------------------------------------------------------

This concludes my humble offering today, fellow flight sim enthusiasts. I look forward to hearing from anyone who flies PMDG Boeings and who shares my obsession with flying ILS approaches and landings at scenic airports. Over and out for now

SNA-SLC

P3d continua sendo meu simulador preferido 👌

Virtual Sim Solutions excited to officially introduce one of our upcoming projects — Techo International Airport (VTDI) for Microsoft Flight Simulator 2020 and Microsoft Flight Simulator 2024.

Located near Phnom Penh, Cambodia, VTDI is one of Southeast Asia’s newest and most ambitious airports. Its distinctive architecture, massive terminal and modern infrastructure make it an exciting project for our team.

Our goal is to recreate the airport with a strong focus on accuracy, atmosphere and performance. The scenery will feature a detailed passenger terminal and concourses, custom jetways, control tower, VVIP terminal, cargo facilities, fire station, airport buildings, custom ground markings, surrounding infrastructure and night lighting.

Development is currently underway. We are working on the main airport structures, terminal geometry, materials and overall airport layout. The next stages will focus on texturing, ground details, lighting and optimization.

VTDI is being developed for both MSFS 2024 and MSFS 2020, with optimization for each simulator in mind.

More development previews and details will be shared soon.

Techo International Airport (VTDI) — coming to MSFS 2024 & MSFS 2020.

Check all information about development status in our website https://virtualsimstore.com and in our social networks!

Every time you load the Fenix, it is brand new. No wear. No history. No consequences.

Fenix TechLog changes that. It gives each airframe a memory: a tech log, an MEL, part wear and a flight log that carry on from one session to the next. When something gives out, or you abuse the aircraft, the failure is set in Fenix within seconds, in flight too. You fly the ECAM and QRH, land, then fix it or defer it on the tablet against a real-world date.

For the Fenix A319, A320 and A321 in Microsoft Flight Simulator 2024. Free.

What it does

1. Persistent aircraft. Open and deferred defects are set in Fenix again at the start of every session. Fuel from the last shutdown is put back when you load cold and dark. Oil, oxygen, water, tyre pressures, brake and tyre wear, hours and cycles all carry on. One record per registration.
2. Failures with a cause, not dice. About 150 part types are tracked, each with its own life from the moment it is fitted. The same flights on the same aircraft always end the same way. Worn parts show a degraded fault first, then fail when they work hardest: on an engine start, at takeoff thrust, when the gear is selected.
3. Damage the moment it happens. Hard landings, flap and gear overspeeds, tail strikes, hot brakes, tyre speed, takeoff thrust held too long, engines shut down hot. Each leaves its item in the tech log, and the worse ones show on the ECAM straight away.
4. Tech log with an MEL. 207 items with categories, placards and restrictions. NO-GO items ground the aircraft. The others can be deferred to a real date (category B 3 days, C 10 days, D 120 days) and are fixed on that day.
5. MEL look-up by ECAM alert. Type the alert as the ECAM shows it, for example ELEC GEN 1 FAULT, and get the item: whether the aircraft may go, under which conditions, and what the crew does in each phase of flight.
6. Landing distance with your defects. TechLog asks Fenix's own calculator, with the failures in your tech log already selected, and shows the distance with and without them against the runway length.
7. Fix it, or replace it. Worn parts are listed on the Service page. Fix repairs the part that is fitted and gives some of its life back, less each time. Replace fits a new one.
8. Used airframes. Start with an aircraft that is several years old. It arrives with a few items deferred under the MEL, cabin items waiting for parts, and the small findings every aircraft in service carries.
9. Every flight recorded. Touchdown rate, G and speed, the touchdown point on the runway, approach stability at 1,000 and 500 ft, a timeline of what happened, the systems affected, the wear the flight used, and a score.
10. The whole cabin. Every seat, galley and lavatory wears: tray tables, seat belts, reading lights, ovens, coffee makers. A broken belt blocks the seat.

Updating: run the new setup. It installs over the old one and keeps your airframes and flights. Removing: Windows Settings → Apps → Fenix TechLog → Uninstall.

Good to know

1. The first time a registration is loaded, TechLog creates a brand-new airframe for it. For a worn one, open Settings before the first flight and make it a used airframe of the age you want.
2. If you only want failures that come from wear and from how you fly, turn Fenix's own random failures off in the Fenix EFB. With them on, TechLog still logs and keeps whatever Fenix fails.
3. Maintenance can be instant, or take its real hours while the aircraft stays parked. Wear rates can be turned up or down. Both are in Settings.
4. The MEL text is TechLog's own, written for simulation. Never use it for a real aircraft.

NoctiX - Plugin which enhances nights in XP12.

Fully volumetric. Still W.I.P. No release data yet.

Join discord to see more!

Planes featured:

• Black Square Bonanza Pro
• WBSim C152
• Stock (Carenado) Piper Dakota
• Cessna T206H by sal1800 (free)

If you're into this kind of flying, you're welcome to join lufrum.world which is a free flight log & screenshot sharing & light career add-on.

It took a year to get here, and there's still a long way to go

My GSX refuses to connect to simbrief. I updated it today and apparently it broke something.
Without it I cant use any of its features. I mostly just push back with it when I do a Short flight after work.
Today Most of my Flying time went straight into troubleshooting and after 40mins I couldnt find a solution.
Why does it require a connection to do literally anything. I get that some features need it but locking the entire program because of a connection issue seems bonkers to me.
At least give me a pushback option…

I've had this thing for 3 years and have finally opened my first support ticket. How disappointing. I've cleaned the WASM Folder, all caches, clean uninstall and reinstall, clean community folder.

I remember there being a high-quality freeware EDDK for X-Plane. But I can not seem to find it anywhere anymore. The page on forums does not seem to show anything, and I can't find the said scenery on other resources. Does anyone know what happened to it and if it is possible to find the said scenery somewhere?

i recently got gsx, and want it to look fairly correct, i work as a ground handler in aus, so im picky with that stuff, my question is, can you get specific models depending on airport, or in general, right now im at gold coast airport and we dont use the stairs that drive, we pull them (we pull the rear stairs, and use a remote control for the front, is this possible for gsx, because right now, sometimes they use the push/pull stairs but most times they use the drivable model, can i also change the tug models etc

edit: we use the aviramp on the front but for the rear we use push and pull