A new updated Oi4FS24 that is compatible with both MSFS2020 and MSFS2024 is now available

[mvr1918]

A new updated Oi4FS24 that is compatible with both MSFS2020 and MSFS2024 is now available from rksoftware.


If you have a license for an older version of Oi4FS and are using MSFS2024, you can get the latest Oi4FS24 for MSFS2020/MSFS2024.

This new version does not work with Prepar3D!

How to get the new version if you if you have an older version of Oi4FS?

Order the Oi4FS24 for MSFS2020 / MSFS2024 update from:

https://www.flightsim4fun.com/shop.html

A download link will then be sent to your email address.

Skjermbilde 2024-12-22 105048.png (165.21 KiB) Viewed 16028 times

Oi4FS24 has the following airplane drivers to be used in MSFS2020 and MSFS2024. * Some of these airplanes are still not available in MSFS2024.

Skjermbilde 2024-12-22 105423.png (20.16 KiB) Viewed 16028 times

The airplane drivers below are add-on airplane drivers that can be purchased from https://www.flightsim4fun.com/shop.html#/

Skjermbilde 2024-12-22 105727.png (11.24 KiB) Viewed 16028 times

The PMDG airplane drivers should work OK in both MSFS2020, and when the airplanes are released by PMDG for MSFS2024, they should also work OK in MSFS2024.

The MS B737Max and Working Title B747 airplane drivers work only in MSFS2024 and are needed to have the modules listed below to fully work.

The following Opencockpits modules can be used with the MS B737Max and the MS B737Max add-on driver:

MCP, EFIS1, COM1, COM2. CDU1 , NAV1, NAV2, and ATC

The following Opencockpits modules can be used with the Working Title B747 airplanes and the WT B747 add-on driver:

MCP, EFIS1, COM1, COM2. CDU1, and ATC

[Abtzero]

Do I have this update already?
My window looks the same, but why the heck does it not show any version number?

I am asking, because the MCP with MS747 does not work for me (while it does with MS2020 and the pmdg aircrafts).
The mini guide does not tell me what to do, except "select..." - and what do I do then???

What I do:
- click on CONFIGURE
- click on MS B747
- click on MS B747 v5.0
- click on MCPv2
- click on MCP
- click on MSB747 v5.0 SSI
- click on MCP MASTER=15.5.1.147
(the last two entries disappear, when clicked - what does this mean? Is this ok? Why is there no explanation?)

What do I do then?
The CONFIGURE Window is still there.
I click on DRIVERS - correct?

And now?
I click on the radiobox "MS747".
The sioc window comes up and minimizes
The small cockpit window saying "OIMS747 driver activated" comes up.
The sim (MSFS 2024 with MS/asobo B747) is running, the aircraft ready to depart on runway with running engines.
But the MCP is dark

In SIOC
the Devices Window shows:
IDX=*.IOCard-MCP - Device = 147

the LOG window shows:
Welcome to SIOC by Manuel Vélez
Starting SIOC
Loading SIOC config .INI :
F:\FS-Tools\IOCards\SIOC\sioc.ini
Initializing IOcard Module
Loading SIOC Script :
sioc.ssi
IOCP client connected


FSUIPC Module
FSUIPC Status: OK
SImulator: dFK

IOCP Server
HostAdress: 192.168.10.3
Clinets connecteds: 1

IOCP Client Module #0
HostAdress: LOCALHOST
Status: active - non-connected


IOCP Client Module #1
HostAdress: LOCALHOST
Status: Disabled

What do I do now?

[mvr1918]

Why didn't you do as stated in the miniguide? Read once again, no reason for me to repeat it here.

Why did you
- click on MSB747 v5.0 SSI
- click on MCP MASTER=15.5.1.147

Where did you read that ?
Didn't you see the ToolTip message saying if you click those lines it would delete the lines you just configured

[Abtzero]

OK, that was my fault.
I shoul not click on something in the 5th listbox.
Closing the the interface an restarting the app having "Autostart enabled made the thing run.
Thank You so far.

Still missing is, what to do after clicking the 4th item. There is no "Save" or "Exit" or "Start" button.
After Going back to "DRIVERS" I cannot click an a radiobox on the right. This is also far from self-explaining or intuitive.
The mini guide does say nothing about these topics.

I never saw the tooltip, because I never rested the mouse long enough on the listbox.
A little label would be better. And finally a label that shows the version number of the app, woukd be great.

It works now. I hope, I remember this setting up newer aircrafts in future.

[Abtzero]

EDIT:
It does not work for 100% (with MSFS 2024 and the asobo/MS B747.).
The MCP shows some digits corresponding to the sim and let me enter Altiude, Speed and Heading.

A/T ARM, LNAV and VNAV LED do not work.
I forgot to mention that I also habe Left B737 EFIS.
So I included this also in the setup.
The EFIS does not work at all.
I do not know, itf the EFIS is supposed to work at all with the 2024 7B47, as it is a B737 EFIS.

[mvr1918]

Check that you have the rksoftware-oi4fs_bridge directory in MFS2024's Community folder. It should have been installed when you installed Oi4FS24. If it is not in the Community directory, copy it over from the OI4FS24 directory.

EFIS should work . Read documentation to find out which modules works for which driver.

[Abtzero]

OK, thank You so far.
The rksoftware-oi4fs_bridge folder was present in the community folder.
Choosing again the modules/drivers every time adds a new MCP and EFIS with different numbers to the list box on the very right.
That was the problem I guess. I removed those with the wrong numbers on the list and now the EFIS works. Great!
The software shoud remove the assignments to modules when an existimgs assignment is called again to prevent this to happen.

Now there are still some single issues with the MCP and the MS B747.
N1 button and LED does not act/light up with thr THR button/led in the sim.
The THR LED never lights up and the button does not ket the sim enter HDG mode.
Pressing the heading encoder button does not let the sin change the heading.
The HOLD LED not always lights up with the LED in sim, but I don't know die to the different flight modes, when it should light up.
I am not sure, if I saw it lit at any time. Maybe but I do not know in what sim condition.
Anyway, the LED is not in sync with the HDG SEL of the sim.

The VNAV/LNAV and VOR LOC and APP leds/button I could not test without a flightplan.

[Abtzero]

And the same with the 787:
not all button/LEDs work. Sure they have slightly different meanings at the 737 but they could be assigned to work with the 787.
So far I noticed, that
at least the VNAV LED never lights up/is not in sync with the sim,
The VS LED does not light up,
pressing the HDG encoder button does not enter HDG SEL mode in the sim.
The HDG SEl button, which would vbe the HOLD button does not enter HDG mode nad the LED nver lights up/is not in sync with the sim.

[mvr1918]

Hi,
Thanks for reporting these issues.
That is the only way to improve these drivers as I do not have time myself to constantly testing all airplanes in both MSFs2020 and MSFS2024. Due to the never ending MSFS/ASOBO updates and changes to everything.

As an example the same airplane in MSFS2020 and MSFS2024 does not use exacly the same variables to interact with cockpit functions.

The main focus and driver in Oi4FS24 is the PMDG B737 driver. That has priority ONE and will be supported to my best ability.

The other drivers are "free addon driver" to use your B737 Opencockits modules also with other airplanes. It takes a lot of effort to have these drivers work 100% due to the nature of MSFS2020 / MSFS2024. There are a myriad of variable names for each airplane and the naming convetions seems to be up to indiviuals rather than having a strict company rule and way to set name to variables.

I will hopefully have a new release of OI4FS24 after the BIG update from ASOBO later this month that will fix some of the issues described above.

[Abtzero]

I know, that it takes a lot of effort to identify these variables in MSFS 2024 and to test them in the end. So thank You for Your work!
I am looking forward to the updated versions.