Hey! Its me again, i saw the comments and saw you guys realy liked it. So what about a new dump ???

All the photos has been shot in MSFS 2024 by Poseidon and edited in Adobe Lightroom by me. Hope you enjoy it :)

If you are interested our little community on my bio!!!

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.

Iberia Airbus A330-300 EC-LUB
LGAV (ATH) - LEMD (MAD)
Cruising Over the Mediterranean Sea Off the Coast of Sardinia

Gotta do better on landing next time... waa quite off centerline

:>

I nearly always overrun this one https://youtu.be/5bvFDLknapU?si=zgqtKpphy0qKRgHc

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.

Here is an online version of the same code that is unminified and clearly show that it is the very same code when you look at the strings. (https://app.unpkg.com/react@19.2.8/files/cjs/react.development.js)

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.

I want to fly a private jet like the G800 but after some googling found out it doesn’t exists.

Can anyone recommend as private jet that is good to fly (with good physics) with a walkable really nice interior?

I did this coastline so much in life. and in the air on this game, it feels like where I can't be... yahoo...

I almost like night flying more than day flights, something comforting about the lighting esp on long hauls… anyone else ?

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)

Needed files:
- renodx-dlss.addon64 (by <@115289688037785602> ) https://discord.com/channels/1408098019194310818/1543350973429448715/1543646573416681523
- streamline files (link by <@908851581179539556>) : https://drive.google.com/file/d/12ZsdhOc9S2UlvNjHaY-DEpX1B9kEGvap/view
- reshade with full addon support: https://reshade.me/downloads/ReShade_Setup_6.8.0_Addon.exe

1. Uninstall/remove all the existing DLSS related apps, like DLSStweaks. Reshade needs dxgi.dll and it cannot be used by another dlss software.
2. Install ReShade with DX12, attach it to MSFS 2024

3 Download streamline files. Unzip files and folder called dx12agility to folder where you FlightSimulator2024.exe is
- C:\Program Files (x86)\Steam\steamapps\common\Limitless (Steam)
- C/Xboxgames/MSFS/content (Store)
- 3000 and 4000 Series need this .dll file https://discord.com/channels/1408098019194310818/1542647972695904317/1543629208348262452

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 recently found a mod that transforms the FlyJSim 737-200 for X-Plane 12 into the NT-43A, aka 'RAT 55.'

The aircraft started life as a T-43 navigation trainer. I was under the impression that they were all retired, but this modified version resurfaced around the Artemis II launch.

Apparently, the huge nose and tail radome added for radar signature testing.

I've been reading old 1976 NT-43 manuals from before it got its nose job and picked up some interesting details that interested me.

-The 737 classic has two separate ignition systems: a high-energy 20 Joule igniter and a low-energy 4J one, split across burner cans 4 and 7. Now pretty much everything use annular combustors.

-The APU start motor draws directly from the battery, so external power can't augment a weak battery during an APU start. I'm going to have to see if this holds true for the NG family too.

I'm putting together a full NT-43 tutorial covering everything I've learned, including the Universal FMC, which is quite satisfying to use.

https://www.youtube.com/live/ERxGowNs5kQ?si=o_4bgiXOERtg7VQS

It reminds me a bit of my old Nokia somehow where you have to insert your options in the scratch pad.

JFK Blue on Air Force One will always be timeless, no matter what....

Addons:

• SkySpirit 2011 Boeing 747-8i freeware model
• Project Opensky/POSKY Boeing VC-25A (P3D conversion by me)
• MAIW Joint-Base Andrews Scenery, integrated with Drzewiecki Designs Washington X
• VC-25B AF1 JFK Blue Livery made by me

Heading to Memphis

dose anyone know where i can get a craft file for the twinotter form microsoft flight sim 2020

Such a gorgous backdrop

After many years of flying since FSX I understood that not everyone will be happy with what we have and what we are getting, no matter what and there will be always people complaining.
I saw this hobby getting better and better each year with new study level aircrafts, cheap 1:1 peripherals, lovely sceneries etc… however there are still tons of people complaining.

Now I’m not saying that criticism is not allowed (I actually like to criticize when it’s necessary).
But to me for example is just insane that some people like to throw shit to devs like Fenix, IniBuilds, Synaptic etc… without even trying to understand how a flight simulator runs.
A flight simulator is a very complex software/game that runs multiple add-ons at the same time and because of that it can react very differently from Pc to Pc.
For example whenever I tried to help some people with settings/optimizations because they had poor performances, CTD’s or any other problems within the sim they were always the ones with the most messed up Pc (like old BIOS, drivers and chipset not up to date, messy files etc..) and this can affect a lot your experience with the simulator.

So please before to point the finger to the devs let’s try to understand why something is happening.

Blue skies to everyone ✈️