Jump to content
The simFlight Network Forums

FSUIPC7 version 7.5.0-beta Installer now available (for MSFS2020 and MSFS2024)


Recommended Posts

Posted
3 minutes ago, Djeez said:

I just installed the new version and tried some of my home cockpit functions for the Cessna.

And are they working or not? And is your issue with FSUIPC or with MSFS2024? If everything still works in MSFS2020 but not in MSFS2024, I would suspect that the issue is due to changes in MSFS2024, and such issues I will investigate later (and maybe better to raise a separate topic for this). If its no longer working in MSFS2020 with this version and previously was, then I need further details.

Basically I want to confirm this version is working as usual in msfs2020, and any specific issues for MSFS2024 (not working, and previously working in MSFS2020) I will investigate further, but after I have officially released 7.5.0. I already have several issues that I need to investigate further and most probably report to Asobo. But such details take time and won't hold-up the release.

John

 

Posted

Could someone who has an MS Store install of MSFS2024 please let me know where the WASM persistent storage area is for this version, i.e. where your FSUIPC_WASM.log file is located.
Is it under:
    AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\Packages\fsuipc-lvar-module\work
or maybe under
   AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\WASM\MSFS2020\fsuipc-lvar-module\work

?

 

Posted

It seems to be under:

AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvar-module\work

I installed just for MSFS2024, leaving 7.4.18 alone for FS20

Martin

Posted
21 minutes ago, pointy56 said:

It seems to be under:

AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\LocalState\WASM\MSFS2020\fsuipc-lvar-module\work

Ok, thanks.

John

Posted
2 minutes ago, M.ALVEGA said:

Just installed the FSUIPC7 version 7.5.0-beta and it is not starting with MSFS 2024.

Can you please show me / attach your InstallFSUIPC7.log file please.
Did the installer detect your MSFS versions? Did you install one copy of FSUIPC7 for both MSFS2020 and MSFS2024, or did you install two copies, one for each version?
Can you also check the EXE.xml file for MSFS2024 (the location should be in your installation log if you don't know where it is) - has that been updated correctly? You can also attach that if in doubt.

John

Posted

Your install log and EXE.xml both look good. Sometimes MSFS just doesn't start entries from the EXE.xml and I don't understand why. Everything I know on this matter can be found in the following FAQ entry - although this is for MSFS2020, it also applies to MSFS2024 (although paths will vary):
    

John

Posted

Installation went well and I am able to start both MSFS2020 and 2024. 

My issue is that the FSUIPC binding for aileron, elevator, rudder and toe brakes no longer work.  I always override all MSFS and SPAD bindings to those because I like having the ease of FSUIPC settings when calibrating each axis.

Added/edited: If it would help to revert back to the MSFS2020 version only I would do that and not use 2024.

Posted
8 minutes ago, Sim_Dude said:

My issue is that the FSUIPC binding for aileron, elevator, rudder and toe brakes no longer work.

In both MSFS2020 and MSFS2024? For all aircraft? Are you using a single installation for both NSFS2020 and MSFS2024 or separate installations?
There should be no (or very little) change using this version with MSFS2020 compared to the previous version. So, if your assignments are no longer working in this version (or both), please show me your FSUIPC7.log and FSUIPC7.ini files for this version.
If your issue is with MSFS2024 only, please show me the files from that version instead.
Also please attach your InstallFSUIPC7.log so that I can verify that there were no issues during installation.

John

Posted

I should add that I cleared the rudder and toe brake axis when I couldn't get them to work.  You might not see the settings in the current "ini" file.

Posted

You were using the Fenix A320 in that test. The only axes you have assigned for that aircraft are aileron and elevator:

Quote

[Axes]
PollInterval=10
RangeRepeatRate=10
0=CX,256,F,65695,0,0,0    -{ TO SIM: AILERON_SET }-
1=CY,256,F,65694,0,0,0    -{ TO SIM: ELEVATOR_SET }-

In fact, those are the only assignments for ALL aircraft, except the "Pilatus PC-12/47 5-Blade Executive WAT Black Grey" where you only have the toe brakes assigned:

Quote

[Axes.SWS PC12]
RangeRepeatRate=10
0=BX,256,D,7,0,0,0    -{ DIRECT: LeftBrake }-
1=BY,256,D,8,0,0,0    -{ DIRECT: RightBrake }-

I don't have the Fenix and so have no idea if those controls are working for this aircraft (although I think it uses the _EX1 variant for throttle). Were those working in 7.4.18? 
Can you try a default Asobo aircraft (such as the C172), and see if those assignments work for this aircraft?

 

Posted

I added this statement before you posted: 

"I should add that I cleared the rudder and toe brake axis when I couldn't get them to work.  You might not see the settings in the current "ini" file."

I will try with the MSFS2020 and 2024 Bonanza A36 or Baron. I am more likely to fly those.  Should I create specific profiles?

Posted
23 minutes ago, Sim_Dude said:

Should I create specific profiles?

That is up to you. If you fly GA aircraft, I think its a good idea to set-up your general profile for such aircraft using the default FS controls (with axes assigned using 'Send direct to FSUIPC calibration and calibrated). Most GA aircraft will use the same FS controls, so you shouldn't need a profile for your axes, but if you want to use presets (or lvars, etc) or Input Events for anything (mainly used for buttons/switches, but can be used for axes) then these should be aircraft/profile specific.

Also, whenever you add an aircraft to a profile (including when creating the profile) you should edit the aircraft name in the [Profile.xxx] section of your FSUIPC7.ini to a substring of the aircraft name to catch all variants (i.e. remove any livery or tail number information). e.g. in the ini file you posted, you would change:

Quote

[Profile.SWS PC12]
1=Pilatus PC-12/47 5-Blade Executive WAT Black Grey

to

Quote

[Profile.SWS PC12]
1=Pilatus PC-12

John

Posted (edited)

hello

I install msfs2024 and sim on loading goes CTD, i restart computer and worked, then i quick to destop it freezes.

On second atempt it gives CTD when appearing, loading world objects.

Unistall and everything works great.

since i unistall, my bad, i havent the crash reports

My msfs2024 is from steam, i install via download from the forum

Edited by Firewiz
Posted
8 minutes ago, Firewiz said:

I install msfs2024 and sim on loading goes CTD, i restart computer and worked, then i quick to destop it freezes.

On second atempt it gives CTD when appearing, loading world objects.

For all such issues with MSFS2024, you should check the Asobo forums, I cannot investigate MSFS CTDs. FSUIPC7 is a separate application and in no way can cause MSFS to CTD. And the WASM is a WASM - the whole point of this is that its sandboxed, and if this crashes it should not affect MSFS.
What exactly freezes - FSUIPC or MSF? How are you exiting MSFS/FSUIPC? Maybe show me / attach your FSUIPC7.log file when this occurs and I can check it for errors.

But I can't help with MSFS CTDs. I also get MSFS CTDs with 2024, as I assume do a lot of people, and these are certainly nothing related to FSUIPC.
You can also show me /attach your FSUIPC7.log file from when you get a CTD and I can check that, but I doubt it will help.
You could try exiting FSUIPC7 once it is auto-started (presuming you are using auto-start) and start it manually once you have an aircraft loaded and are ready-to-fly. Does that help? 

John

 

Posted

I have just release 7.5.0d - can all users using this beta please update.
There is no change in the installer - this looks pretty stable and complete now.
The major change is with the WASM module - I have updated this to be more compatible with MSFS2024. There are also some changes to FSUIPC7 to accommodate the WASM changes: as the WASM wasn't working 100% correctly with MSFS2024, previous versions of the 7.5.0beta needed to stop the WAPI when changing aircraft to ensure lvars were loaded correctly. This is no longer necessary and has been removed.

I am hoping this will be the last beta release of 7.5.0, and would like to release this version as the latest official version at the weekend (Friday evening maybe).

John
 

Posted

How about the elevator and aileron? Just checked and those both work here. Maybe check the assignments in MSFS2024 - check the general and profile assignments and make sure they are empty.
You haven't calibrated the Aileron, Elevator or Rudder - you should always calibrate when assigning direct to FSUIPC calibration, but this shouldn't prevent them from working.
Maybe also check any assistance options to make sure that they aren't interfering.
Can you set logging for Axes Controls, and generate another log file with that set - just load the aircraft, move the various axes then exit.

Also, I have just release 7.0.5d - please update to this version first.

I am finishing for the evening now - will check further tomorrow.

John

Posted
  • Installed v7.0.5d
  • Set logging for Axes Control to ON.
  • Verified assistance is off.
  • Verified no MSFS2024 bindings to keyboard or other equipment.
  • Went through and setup and calibrated every axis. 

I could start the plane but couldn't move with toe brakes normal and reversed. I probably went too far with moving all the different axis around but something wasn't right still.

FSUIPC7.ini FSUIPC7.log

Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.