Leaderboard

There's no copyright claim on the original script, so I've uploaded my version of it here... Original file courtesy of Manolo Velez. You'll need to open this in the SIOC utility. Open SIOC.exe Choose "Edit Script" Files -> Import TXT (and select this attached file) Save As... (it'll compile as an .ssi file) Once compiled you may need to click the "Reload" button in the man SIOC utility window. All done! (hopefully) I'm a novice when it comes to this stuff, so I'm afraid I can offer no support. (See latest version below...)

Hi @jonas_llubi, @Abt. I share you frustration with this. In fact, I spent the last 6 hours vibe coding an AI-assisted solution for a SIOC script that correctly handles the COM1/2 active/standby frequencies for both 25kHz and 8.33kHz frequencies. I also changed the logic so that it truly does work as a slave device, in that if MSFS changes the frequency itself (or another app like BATC etc does) then the updated frequency will appear in the panel, and it won't keep overriding MSFS. Limitations: It's really nasty code, made with the assistance of AI. Works with MSFS2020, but not yet tested for MSFS 2024. The SIOC script also doesn't appear to work for the Nav radios. I based it off the originally provided SIOC scripts from opencockpits (I'm not sure if I can share it openly with you, but there is no copyright notice on the original), and that original script doesn't work for Nav radios in MSFS2020 either. For me, the COM 1/2 radios were much more important. I can revisit the NAV modes later perhaps. In testing, the display does sometimes go black, and the panel appears to fail. To fix it, you have to just press the "Reload" button in the SIOC utility. I changed the logic so that it always initialises with the active COM1/2 frequencies from MSFS so that it doesn't reset anything if you have to restart multiple times in the middle of a flight. I hope it works as a stop-gap until something better comes along though! Edit: The NAV VOR and ADF radios don't work, but the ILS mode frequency and course values do work! If you're interested, let me know and I can send the script to you privately. Linguini

Thank you, I moved FSUIPC to starting first, and changed the MaxClients to 128. Now Everything is working well.

Thanks very much John, as always, just done what you explained, works perfect.

I've been struggling with this BlackSquare mixture thing for ages. Today, thanks to this thread, I've cracked it! As John said earlier, "Why not? Have you tried? It is incredibly easy and explained well:' I've used FSUIPC since forever and I maintain that it's like brain surgery, Easy when you know how. 🤣

Just a quick note to say thanks again John, I learned how to do the LUA scripts today and it works for the two runway turnoff lights on one button, I will now use for various other combos I want to do on the iFly!! For the benefit any newbies wanting to do iFly RWY TURNOFF on/off on one button, I am attaching the files, you just put them in the FSUIPC main install folder and instead of selecting Preset for the buttons, select "FS Control" and look for the commands "LuaIflyRFWYON or ...OFF., iFlyRwyOFF.lua iFlyRwyON.lua

I am not sure how to embed a pause/wait in a calculator code string and that sleep syntax is not familiar to me. There are a couple of other ways you could do this: 1. Use lua instead, e.g. ipc.execCalcCode("23 (>L:VC_Miscellaneous_trigger_VAL, number)") ipc.sleep(100) ipc.execCalcCode("25 (>L:VC_Miscellaneous_trigger_VAL, number)") 2.Define two separate presets: IFLY_RWY_ONa#23 (>L:VC_Miscellaneous_trigger_VAL, number) IFLY_RWY_ONb#25 (>L:VC_Miscellaneous_trigger_VAL, number) and then create a macro to call the first one, then pause (using the FSUIPC-added pause control), then call the second preset. You can also overload the assignments instead of using a macro if you prefer.

Thanks, John, that has worked perfectly. I don't know why my system thought I had the Steam version installed, I have never purchased or installed MSFS 2024 on Steam, only from the Xbox store. Anyway, followed your steps, and FSUIPC is now starting automatically with the sim. Thanks so much for taking the time to resolve this for me, and thanks again for a great product.

First, to understand profiles you should read the section User profiles for all control settings, on page 22 of the FSUIPC7 User manual/guide. Profiles are enabled automatically. Having profiles in separate files is generally only used if you have many profiles and these are quite large, as it separates them into different files. You do not have to use this feature when using profiles if you don't want to, but if you have already switched to profiles-in-separate files then thats ok. The changes you made will only be saved in the profile (and in the profile-specific file) if you clicked the profile-specific checkbox (in the assignments panel) when adding the assignment, and when you have added the currently loaded aircraft to a profile (or have created a new profile for the aircraft). Check your FSUIPC7.ini - they will have been added there to the general sections if you did not specify profile-specific. Note that when you create a new profile for an aircraft, or add an aircraft to an existing profile, it is a good idea to shorten the aircraft name (listed under the [Profile.xxx] section of your FSUIPC7.ini file) to a substring that matches all variants of that aircraft. This will prevent issues with the profile not being loaded when you use a new variant. Alternatively, you can set the UseAirLocForProfiles in parameter to Yes to perform matching on the aircraft folder name instead, but if you want to use this then do it now before adding the aircraft name/title to the profile. Again, see that section in the User manual for more details. John