Leaderboard

It's not obviously clear from the SDK what the new (2024-native) livery structure should look like... But essentially liveries are now a child of the parent aircraft in 2024 VFS Child liveries don't have their own aircraft.cfg (and therefore no TITLE= line). Instead, they now have a livery.cfg that defines the parent aircraft (and engine-type relationship), with a [General] section where you can give a livery a name [Version] major = 1 minor = 0 [General] name="<Livery Name here>" So in 2024 native aircraft/liveries, TITLE returns the name of the parent aircraft only, and the new LIVERY NAME simvar exposes the name in [General] from the livery.cfg FS2020 aircraft and liveries that are "compatible" with 2024 (but are literal copy/pastes into the MS2024 community folder), still exhibit 2020 behaviour when it comes to TITLE, so aren't "problematic". But as developers slowly adopt the new 2024 livery packaging format, this will become more and more problematic to those of us who need livery info exposed. Thanks for the clarification around which SDK you're compiling against, and appreciate that FSUIPC serves both sims simultaneously at present. I'd have thought though, that any application that has historically relied upon livery detection would be interested in this feature potentially. As a VA we certainly have a requirement from an ACARS perspective, but appreciate this is probably the first your hearing of it. If this thread starts the ball rolling for others to chip in, awesome. If not, we'll have to potentially consider an in-house solution as you previously advised. TITLE has been around for donkey's years, has always served its purpose, and its frustrating that Asobo have decided to suddenly change this in 2024. Going forward, I for one certainly consider the new simvar as "core" as TITLE has always been. Thank you for engaging with this thread, and I'd ask (if possible) to keep this in the back of your minds when it comes to your wider development roadmap.

This one works, John! Matt

Sorry, I do see 16 now, I forgot that numbers start at 0. Thank you for your involvement, Ihave uninstalled one controller that is rarely used for the moment and solved the problem of two devices having the same GUID by re installing one of them.

Ok, I will leave it as is in the version I posted above.

I think I solved the problem. I followed this guide: https://flightsimulator.zendesk.com/hc/en-us/articles/360015893879-Checklist-How-to-troubleshoot-crashing-CTDs-issues and did the following. #1 SYNCHRONIZE TIME SETTINGS My time was set to "Adjust automatic daylight saving time" I turned this off. #2 Then “Set time zone automatically” to ON #3 Then "Synchronize your clock" Then this section. "LAUNCH MICROSOFT FLIGHT SIMULATOR AND TRY AGAIN" I bought msfs via Microsoft store, so now I did this. #1 install the Xbox app to my computer. #2 launch Microsoft Flight Simulator from the Xbox App. I was able to create a shortcut from the Xbox app that I was using. For now, this seems to have solved my problem, and I'm happy. 😊👍. Hope it might help others too. Kind regards Per, from Denmark.

I did look at it. I didn't know "Path of Flight Simulator installation" == "InstalledPackegesPath". I meant look at the value in the offset, i.e. log its value. I will update the offset status document to make this clear. Cheers, John

Trim wheels usually work on buttons, not an axis. Some have two buttons in each direction (one for fast movements and one for slow), others just one. For those using just one button, you can use the Rotaries.lua script to convert this to use two virtual buttons instead, to enable fast/slow trim in each direction. The Bravo trim wheel has one button in each direction. I showed how to configure the Bravo for basic operation, including the trim wheel, in the following post: That should work for quite a few aircraft, but it won't work for all aircraft, especially many add-ons, as those assignments use the default FS controls. For such aircraft, you should use a profile and override these with the specific controls for that aircraft, whatever they may be - usually using presets, input events or lvars. There are also many other ways yo assign trim, and it is up to you to decide what works best for the aircraft you are using. For example, see the following post: John

I don't have a physical trim wheel so have no experience with that, but I don't see why it would not be recognized as an axis in the sims. When you turn it does FSUIPC7 recognize it as an axis similar to what I showed above?

And a Happy New year to you as well! John

Hello John, And to confirm above : "my traffic" on ND has also returned with fsuipc 7.5.x ! Thanks for the help. Have a good Christmas and a happy New Year, Regards, Marinus Bergsma.

Yes, very strange... I will be releasing 7.5.1 later today, and I am going to switch to using version numbers on the downloadable file which should help with this cache issue. Cheers, John

This is an MSFS issue and nothing to do with FSUIPC. You should use the MSFS/Asobo forums for this issue, not this FSUIPC forum. Sorry, but I can only help with FSUIPC issues, not MSFS issues. I will leave this post in case anyone else has any suggestions, but you are better off using the Asobo forums for such issues. I have also moved your post to the FSUIPC7 / MSFS forum as you posted in the main support forum. John