Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Fenix update

Featured Replies

Saw installer update it was quick but no product update yet thats weird maybe something's coming in future 

Rich Sennett

               

  • Replies 34
  • Views 9k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • GSX modifies the XML of Fenix aircraft models so that it can add it's seated passengers. This was the way that GSX formulated without directly editing the model itself. Anyway, when Fenix launcher lau

  • An installer update, but no AC updates here. Latest according to official discord announcement still __**2.3.0.553**__ Source: https://discord.com/channels/736572376967282769/736710909887643

  • How you'd expect the FSDT Installer could modify an .XML file without modifying it ? Attaching passengers by modifying the exterior .XML is the only way to achieve that with the absolute best per

12 hours ago, Luis Hernandez said:

AFAIK, only the WXR...

Not so sure about that. From Dave

"Hi - just to clarify, our stance isn't "we won't do it because it's not good enough", it's "we can't reasonably do it as it's not natively supporting all display rendering methods in the SDK yet"
to implement WXR on our displays would take months of work, and then potentially have unsolvable perf issues. Trust that we've not given up on this, it's just not as simple as for the other guys using a less performant but easier to implement renderer"
 

Cheers,

John Tavendale
Textures by Tavers - https://www.facebook.com/texturesbytavers

My MSFS2024 SU2 Beta aborts on loading the Fenix aircraft.

If I use an empty Community folder, the SU2 works fine eg with the cessna 152 as a test.

I have to localize what item in the Community folder is not compatible with the SU2.

Any sugestions?

Peter

 

Windows 11 / MSFS 2024 from MS-Store and Fenix A320

17 minutes ago, PeterKoller said:

My MSFS2024 SU2 Beta aborts on loading the Fenix aircraft.

If I use an empty Community folder, the SU2 works fine eg with the cessna 152 as a test.

I have to localize what item in the Community folder is not compatible with the SU2.

Any sugestions?

Peter

 

It was mentioned in this thread

Nealy every 3 Party Aircraft may have issues actually due to some changes by ASOBO

 

Edited by mobiel

23 minutes ago, mobiel said:

Nealy every 3 Party Aircraft may have issues actually due to some changes by ASOBO

 

My sim is constantly crashing if I attempt to change livery on either ini A350 or Fenix A320.

1 hour ago, PeterKoller said:

Any sugestions?

AIG or FSTL models in use?

They cause CTD's in SU2 Beta.

3rd party a/c crashing for me too.

  • Commercial Member
16 hours ago, Lucky38i said:

realistically GSX needs to find a way that doesn't induce a failed hash check. Hash checking is industry standard for updaters

How you'd expect the FSDT Installer could modify an .XML file without modifying it ?

Attaching passengers by modifying the exterior .XML is the only way to achieve that with the absolute best performances possible and with zero extra Simconnect traffic required to keep passengers attached to the airplane.

We tried the alternative (attach dynamically with Simconnect) years ago and, not only the amount of Simconnect traffic added required to move all 100+ passengers together with the airplane at each frame was not tolerable because it affected the whole sim, but the inherent Simconnect lag made impossible for passengers to stay perfectly attached (as they are now) when the airplane accelerate to normal speed, it basically worked only on ground (with all the extra Simconnect traffic which was affecting everything), so the current method is the only one possible with the current SDK.

Now, if MS/Asobo ever took into consideration our suggestion to add an "Attach API" (similar to what we *have* in P3D), where you can issue a single command to attach an object to another one, and then they would stay glued together perfectly without requiring any extra code, until you detach it again, we could obtain the following benefits:

- There wouldn't be any need to modify the airplane exterior .xml files to add passengers.

- Marketplace-bought airplanes could be supported (right now they can't, because we can't access their .xml files, since they are encrypted)

- Any plane would work, no matter how its files are arranged, instead of having to deal with so many different styles in the FSDT Installer, which leads to unnecessary complexity.

- We could enable the Seating editor, which is already in GSX but disabled for users (since right now it only generate a profile that is read as input to automatically create .gltf files when building GSX, so it's useless for users), which would allow everybody to define all seating positions, so users could just share airplane profiles with included seated passengers with no need for us to individually support new airplanes coming out, which takes time and requires users to wait for new airplanes to be supported.

And of course, an "Attach API" could allow so many other things that might be interesting to all add-ons developers, like simulating any kind of task where you are picking/dropping things like cargo or anything else, so it would be a very useful addition to the SDK.
 

Edited by virtuali

27 minutes ago, virtuali said:

How you'd expect the FSDT Installer could modify an .XML file without modifying it ?

Attaching passengers by modifying the exterior .XML is the only way to achieve that with the absolute best performances possible and with zero extra Simconnect traffic required to keep passengers attached to the airplane.

We tried the alternative (attach dynamically with Simconnect) years ago and, not only the amount of Simconnect traffic added required to move all 100+ passengers together with the airplane at each frame was not tolerable because it affected the whole sim, but the inherent Simconnect lag made impossible for passengers to stay perfectly attached (as they are now) when the airplane accelerate to normal speed, it basically worked only on ground (with all the extra Simconnect traffic which was affecting everything), so the current method is the only one possible with the current SDK.
 

I'm well aware your hands are tied in this situation and you did find the most ideal solution, it does have it's "annoying" ( I don't find it a problem) side effects. I was simply answering the question that was asked of me. Expecting Fenix updater to not do checksums on their files is silly. That's why I said realistically GSX would be the one to find a way to mitigate this issue. Though in reality this is the best solution you could find and I don't blame you for that. Like I said, your hands are tied.

My actual answer is what I Said in my original post.

Quote

My advice is, ignore any update on the Fenix launcher if you use GSX seated passengers, unless Fenix announces an actual update.

Though @mspencer didn't think that was sufficient. Oh well.

  • Commercial Member
1 hour ago, Lucky38i said:

Expecting Fenix updater to not do checksums on their files is silly. That's why I said realistically GSX would be the one to find a way to mitigate this issue.

Well, fact is, it's impossible for GSX to mitigate this. Well, not really "impossible" but, more precisely, it's unrealistic because, a "possible" way to do this from GSX side would be:

- Having an always-running monitoring app that start with Windows, and will detect at any time if you are trying to start the Fenix updater (or any other airplane updater, for that matter).

- Having that app force-quit the airplane updater before it could do anything, so we could revert the changes to the airplane .xml exterior files first.

- Restart the updater it previously forced-quit, so it won't be triggering an update check.

That's the only possible way to do it entirely from GSX's side. Highly invasive and possibly very unreliable.

 

5 hours ago, Simon_C said:

My sim is constantly crashing if I attempt to change livery on either ini A350 or Fenix A320.

CTDs here as well if the Fenix is only close to 2024 SU2. Move it out of your community folder and try again. 350 just loaded fine. Same as the RJ

Phil Leaven

i5 10600KF, 32 GB 3200 RAM, ASUS 4070 12GB EVO, Asus ROG Z490-H, 2 WD Black NVME for each Win11 (500GB) and MSFS (1TB), Rolling Cache 16GB, Photogrammetry always OFF, Live Weather and Live Traffic always ON, Res 2560x1440 on 27"

1 hour ago, virtuali said:

Well, fact is, it's impossible for GSX to mitigate this. Well, not really "impossible" but, more precisely, it's unrealistic because, a "possible" way to do this from GSX side would be:

- Having an always-running monitoring app that start with Windows, and will detect at any time if you are trying to start the Fenix updater (or any other airplane updater, for that matter).

- Having that app force-quit the airplane updater before it could do anything, so we could revert the changes to the airplane .xml exterior files first.

- Restart the updater it previously forced-quit, so it won't be triggering an update check.

That's the only possible way to do it entirely from GSX's side. Highly invasive and possibly very unreliable.

 

Hence my... actual answer

I am still trying to find out why my landings all the sudden is up to -650fpm despite the ROD is showing 100-200feet below 50 feet when the nose comes down. If i leave the nose come down it feels like a slam but how is -5-600 feet possible?

Also when doeing touch and goes at EKCH 04L the aicraft bounce up and down when retracting to flaps to 1+F .(trim reset to neutral)

Weight 61 tons. 8000kg fuel

I dont think its this update btw.

Michael Moe (Fenix A319, MSFS2020)

Edited by Michael Moe

Michael Moe

 

fs2crew_747_banner1.png

Banner_FS2Crew_Emergency.png

5 hours ago, Lucky38i said:

 

My actual answer is what I Said in my original post.

Though @mspencer didn't think that was sufficient. Oh well.

This post is far more annoying than the initial problem. Don’t tag me please. 

10 hours ago, PeterKoller said:

My MSFS2024 SU2 Beta aborts on loading the Fenix aircraft.

If I use an empty Community folder, the SU2 works fine eg with the cessna 152 as a test.

I have to localize what item in the Community folder is not compatible with the SU2.

Any sugestions?

Peter

 

Hi all

After some more tests with the MSFS2024 SU2 Beta I found out that two of my items in the community folder make the Sim crash:

The Fenix A320 (I am not complaining. I know that the Fenix has the experimental status in MSFS2024, just as an info).

The Injector of FSLTL.


If I take out this two items the SU2 works perfect for my with very good framerate and super scenery.

Peter

Edited by PeterKoller

Windows 11 / MSFS 2024 from MS-Store and Fenix A320

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.