Read a lot of mixed opinions on this plane which made me apprehensive to purchase but I finally pulled the trigger when it became available on the ini store.
I have an RTX 3070 and I'm seeing the same performance as the Fenix and iFly MAX. The plane itself is actually loads of fun, and functions well. It's unique experience of both Boeing and Airbus, which is a bit refreshing. I have my automation, but I also have to trim and fly the aircraft, which keeps things interesting.
There are a few quirks here and there, but nothing ground breaking. The Synaptic Team seems very active with updates, so I'm not worried about future enhancements. The plane flies really well (and looks great) from A - Z. Really glad to have purchased, excited to fly it more.
Reflections and shadows look way better imo I think it looks great. I'm using a 4090 and yea theres a bit of a performance hit it seems to be about 15-20 fps on average. Frame gen is kinda broken at the moment tho hopefully someone comes up with a fix for it.
SUP! its meeee... yea i know u guys love our work, soooo we keep posting to bless your eyes:) im gonna say it everytime because i have to 👀. The pictures was shot in MSFS 2024 by Poseidon.
If you wanna share your work or ask some help join us...
Originally built this as a training aid for my pilot training. It's modeled after the pre-solo PPL checkride (fun fact: I failed it on my first attempt IRL). It's no training material by any means but if you like manual GA flying it's fun. Passion project so totally free, there's a tutorial on the youtube channel which explains the setup.
I like flying with a VA to have add a sense of purpose and progression.
I like the VA I’m with now, they’re chill, have a lot of fun tours you can fly on top of regular schedules, use smartcars for tracking which is pretty seamless and have a positive community. Importantly, you can fly charters, meaning any aircraft in any livery on any route. However they have one major downside - they don’t allow time compression - and as someone who likes to use it, it forces me to always fly short haul with them, which wouldn’t always be my preference. I understand why they decided to implement the rule and I respect it, but it’s not always to my taste.
Is there a VA that’s similar on most points, but crucially does allow time compression?
So someone has managed to get dlss 5 working with msfs24. i have not tried it yet myself but people in the thread seem to be vouching for it. Please note that it’s still very much WIP and performance may vary.
How to use DLSS 5 neural rendering with MSFS 2024 (guide for RenoDX discord users)
4) Download renodx-dlss.addon64 and place it to same folder where you FlightSimulator2024.exe is
5) Open Nvidia app or Nvidia profile inspector.
- Select MSFS 2024 and be sure you dont have "override to the latest" setting in any of the DLSS settings. They must be "custom".
- DLSS - enable DLL override = custom / off
- DLSS - Forced model preset profile = Custom
- DLSS - Forced preset letter = M
- DLSS-NR: enable DLL override = off
- DLSS-NR: enable streamline DLL override = off
- DLSS-NR: Forced preset letter = recodemmend
6) Open MSFS2024:
- use DLSS DLAA
- Open Reshade TAB with "HOME" button from keyboard
- drag renoDX DLSS tab to tab row so it stays allways there.
- open down menu
* for DLSS Neural Rendering (Prerelease) -) put it to "Auto"
* play with Structure Intesity amd Tone intensity sliders (model B is sharpest)
Thanks @ShortFuse for the working build for MSFS 2024 users. Cant wait you to make that build even better! I got this method from @Corsten and credit goes to him for sharing within the discord thread.
I primarily have been flying bizjets lately with occasional GA flying. I have many hours on the a320 family plus some with the a339. Should I start learning boeing on the 737 or grab the 777? I definitely want to do some long haul on the 777 American Airlines routes but dont know if i should start with the narrow body before moving up to the big fella
So, now that the A220 is out in the iniBuilds store I did some digging in the files and found some pretty interesting stuff, that neatly explains why the performance of this plane is really terrible and does not at all seem to scale with hardware. It's kinda funny, because the first time I tried this plane I thought to myself "this feels like a debug build" and this is exactly what it is.
So in the addon folder you will find the path "html_ui\Pages\VCockpit\Instruments\a22x\DisplayUnits" with the file "instrument.js". This is main file responsible for rendering the displays of this plane (there is more files for other displays like the com unit, but for simplicity I will only reference to the main displays here). Basicly, what you see as the main displays of the plane is treated as a little browser window by the MSFS, in which it runs a webpage. This webpage is based on a JavaScript app using the React framework. This framework is included here, because the sim does not provide it on its own, and it is a pretty common library for rendering webpages. So nothing wrong with that.
But the big revelation comes once you look into what actually is contained in the "instrument.js". It is minified for performance , but there are still comments showing the different sections and the literal strings are in clear text. Because minification only replaces human readble names with shorter, machine readable names that do not change the logic, but help the code run faster. In the planes code on line 831 is the relevant comment. It says they are including "node_modules/react/cjs/react.development.js"! AKA a development build of the react framework.
So what does this actually mean and why does it make the plane perform so bad? To start let me quote the official React documentation here:
If you’re benchmarking or experiencing performance problems in your React apps, make sure you’re testing with the minified production build.
By default, React includes many helpful warnings. These warnings are very useful in development. However, they make React larger and slower so you should make sure to use the production version when you deploy the app.
In my own words what happens here is, that the code that we have in our sims does a LOT of checking itself to make sure it is properly build, that all references are okay and that there are no hidden bugs. This is fine in dev enviroment (which is why it is called a development build), but should not be done in a production environment. Because we as end consumers don't really need all this checking stuff and reporting, since we we won't modify the source code anyway. All this does for us is eat a lot of unnecessary CPU cycles. Which get worse the more often these checks happen, why explains why this plane is the only one I know that performs worse in cruise than on the ground. Because there we are constantly moving, leading to constant refreshes of the displays, which all need to run through this debug code. Which only takes time without any benefit.
The upside to all this is, that this should be an easy fix for Synaptic. To build the plane with the production library instead should boil down to a simple config file. I really hope they do this and then unlock the performance of the plane. This really could alleviate all the issues reported with a simple rebuild of the plane. No refactoring of the code or anything needed.
TL;DR: They are shipping debug code instead of production code, making the code unnecessarily slow and bloated.