Duncan MacKellar Posted June 19 Posted June 19 Yes - HWI for MSFS will be released tomorrow or Monday, once things have settled. 6 2 Quote
Sandro Strohmaier Posted June 19 Posted June 19 Does that include a complete Lvar List for other Hardware Solutions? Thanks Sandro Quote
Jon Beniston Posted June 20 Posted June 20 On 6/19/2025 at 1:58 PM, Duncan MacKellar said: Yes - HWI for MSFS will be released tomorrow or Monday, once things have settled. Are you referring to this: https://www.flightsimlabs.com/index.php/hardware-interface/ - so we'd need to pay $100+ just to use the FCU? Quote
Duncan MacKellar Posted June 20 Posted June 20 6 minutes ago, Jon Beniston said: Are you referring to this: https://www.flightsimlabs.com/index.php/hardware-interface/ - so we'd need to pay $100+ just to use the FCU? Nope. That's for P3D. Wouldn't work with MSFS. Quote
Deniz Sarper Posted June 23 Posted June 23 On 6/19/2025 at 2:58 PM, Duncan MacKellar said: Yes - HWI for MSFS will be released tomorrow or Monday, once things have settled. Hi @Duncan MacKellar is it already released or still in final movement ? Kudos to the NEO release to all of you Best regards Deniz 1 Quote
stephen speak Posted June 23 Posted June 23 27 minutes ago, Deniz Sarper said: Hi @Duncan MacKellar is it already released or still in final movement ? Kudos to the NEO release to all of you Best regards Deniz Not released as yet from what I can see..it will probably be later in the day as that’s usually when releases/updates happen 1 Quote
Deniz Sarper Posted June 23 Posted June 23 1 hour ago, stephen speak said: Not released as yet from what I can see..it will probably be later in the day as that’s usually when releases/updates happen Yeah let's see and wait Quote
Duncan MacKellar Posted June 23 Posted June 23 7 hours ago, Deniz Sarper said: Yeah let's see and wait Realistically, today is going to slip - Sorry about that. We got tied up chasing some aircraft-related issues around. I will let you know in here once I upload it, regardless of today or tomorrow. 3 2 Quote
Deniz Sarper Posted June 23 Posted June 23 57 minutes ago, Duncan MacKellar said: Realistically, today is going to slip - Sorry about that. We got tied up chasing some aircraft-related issues around. I will let you know in here once I upload it, regardless of today or tomorrow. Hi @Duncan MacKellar thanks for the info you dropped here. I can totaly understand this. Releases are never a good point to ask for an additional Software to drop keep your heads up. Take your time. Best regards Deniz Quote
RUIZ Christopher Posted June 24 Posted June 24 Can't wait as well. But take your time to make something great. Thanks for the hard work. Quote
David Reage Posted June 27 Posted June 27 I'm looking forward to news on this front too. I'm looking forward to buying the A321 NEO, but want to confirm compatibility with my Skalarki Desktop gear (and whether there is a cost from FSL for that compatibility or not) first. Quote
Lefteris Kalamaras Posted June 27 Posted June 27 We have some very good news coming on that front as well - just a weeee bit more patience pls . 3 Quote
Sandro Strohmaier Posted June 27 Posted June 27 3 hours ago, Lefteris Kalamaras said: Thanks for that. Very nice. But for all other DIY cockpit builders, a complete list for LVars and simEvents would be great. There is an Excel file with some of them in an other topic, but for a homecockpit a complete list is needed. Any Chance to get a complete list? Quote
Lefteris Kalamaras Posted June 27 Posted June 27 Hi Sandro, you and I have been discussing this via tickets, no? so give us some time - we're working on it... 1 Quote
Sandro Strohmaier Posted June 27 Posted June 27 9 minutes ago, Lefteris Kalamaras said: Hi Sandro, you and I have been discussing this via tickets, no? so give us some time - we're working on it... Hey Lefteris, yeah, some weeks ago, but with the hard work you put in the NEO the last weeks i tried not to stress you with tickets anymore ;-) Many of my community Members are asking for a Livestream in the NEO, and i would do everything to use your product for that, because in my opinion it's actually the best Airbus product available. I know its not easy, but is there a timeline for the LVars? Days? Weeks? Months? Centurys ? Greetings from the Flightdeck 1 Quote
tiago diogo Posted June 27 Posted June 27 Hi, I bought today NEO, can you help me how to connect skalarki fcu to msfs? step by step. best regards Quote
RUIZ Christopher Posted June 27 Posted June 27 I do not manage to make it work properly. Is there any option that we should use in the settings? The FSLabs option is greyed out. It seems that SkalarkiIO profiler misses the right profile. When selecting "Pro Sim 32x" in the options and starting the aircraft, I have the behavior that "Bus tie" push button and a few others are set to off on the overhead without being possible to switch it on. But radio media panel, ATC, MCDU inputs seems to be interpreted correctly. When selecting "Fenix", the bus tie is on but no other peripherical is working. Some overhead buttons are working but not everything. Let me know if there is something I miss in the configuration. @Alexander Petrenko Doc can be found in a PDF file located here: C:\Program Files\FlightSimLabs\HWInterface\MSFS\Documentation Quote
RUIZ Christopher Posted June 27 Posted June 27 FSLabs stays greyed out whatever simulator I chose in the option. I checked that the module has been installed via Skalarki IO installer and yes [UPDATE] Was able finally to check P3D / FSLABS in the settings of Skalarki IO profiler. It seems that there is a bug in the UI. FOr those who also see the option greyed out, you should select a random one (like prosim) then switch to another sim in the list, switch back to P3D and the FSLabs option will not been greyed out anymore... weird... I'll now test the hardware integration Quote
Malcolm Rouse Posted June 27 Posted June 27 1 hour ago, RUIZ Christopher said: FSLabs stays greyed out whatever simulator I chose in the option. I checked that the module has been installed via Skalarki IO installer and yes [UPDATE] Was able finally to check P3D / FSLABS in the settings of Skalarki IO profiler. It seems that there is a bug in the UI. FOr those who also see the option greyed out, you should select a random one (like prosim) then switch to another sim in the list, switch back to P3D and the FSLabs option will not been greyed out anymore... weird... I'll now test the hardware integration Let me know how you get on i can't connect my Skalarki FCU for love and money . Quote
David Reage Posted June 27 Posted June 27 Awesome! Neo purchase and many flights coming this weekend. Quote
RUIZ Christopher Posted June 27 Posted June 27 I've performed a few tests and it seems to work properly on both 2020 and 2024. that awesome! Thank you folks. Things that I've noticed with the mini Overhead is that the default state sometime is not properly set. For example, randomly the "int lt ann lt" is set to "test". Just adjusting the button physically makes the trick FOr those who are setting things up. Here are a few tips. 1. You should have the fslabs module installed for SKalarki io profiler tool. You can reinstall if if needed using Skalarki IO installer. If so, click on Modify and ensure that fslabs in P3D section is checked / installed. 2. Create a new profile on Skalarki IO profiler app. In "settings" select P3D V4/V5/V6 in the dropdown menu and check the box FSLabs. If the box is greyed out, try checking another box, change the sim version in the list, back to P3D and it shouldn't be grey'd out anymore. Seems like a bug in the UI. 3. You should also install the FSlabs HW Interface provided a bit higher on this thread. On the main interface of the tool, click first on "COmponent configuration" and check the hardware you have. If you have the mini ovh the box is on the bottom right. More info can be found on the official documentation: C:\Program Files\FlightSimLabs\HWInterface\MSFS\Documentation Now... How to run it ... 1. First, run the sim and start a flight 2. Run skalarki io profiler app. Ensure that sdk and profile are both running 3. Launch fslabs Hardware interface tool. click on "connect MSFS" then "connect hardware". Note that if you used different ports, you might edit them. This is detailed in the documentation 3 2 Quote
Malcolm Rouse Posted June 28 Posted June 28 10 hours ago, RUIZ Christopher said: I've performed a few tests and it seems to work properly on both 2020 and 2024. that awesome! Thank you folks. Things that I've noticed with the mini Overhead is that the default state sometime is not properly set. For example, randomly the "int lt ann lt" is set to "test". Just adjusting the button physically makes the trick FOr those who are setting things up. Here are a few tips. 1. You should have the fslabs module installed for SKalarki io profiler tool. You can reinstall if if needed using Skalarki IO installer. If so, click on Modify and ensure that fslabs in P3D section is checked / installed. 2. Create a new profile on Skalarki IO profiler app. In "settings" select P3D V4/V5/V6 in the dropdown menu and check the box FSLabs. If the box is greyed out, try checking another box, change the sim version in the list, back to P3D and it shouldn't be grey'd out anymore. Seems like a bug in the UI. 3. You should also install the FSlabs HW Interface provided a bit higher on this thread. On the main interface of the tool, click first on "COmponent configuration" and check the hardware you have. If you have the mini ovh the box is on the bottom right. More info can be found on the official documentation: C:\Program Files\FlightSimLabs\HWInterface\MSFS\Documentation Now... How to run it ... 1. First, run the sim and start a flight 2. Run skalarki io profiler app. Ensure that sdk and profile are both running 3. Launch fslabs Hardware interface tool. click on "connect MSFS" then "connect hardware". Note that if you used different ports, you might edit them. This is detailed in the documentation Hello Uninstalled and then followed all your steps still not working i'm afraid But thanks very much for all your help . Quote
RUIZ Christopher Posted June 28 Posted June 28 @Malcolm Rouse can you say a bit more? The behavior you have, which step are you stucked at? Quote
David Reage Posted June 28 Posted June 28 19 hours ago, RUIZ Christopher said: FOr those who are setting things up. Here are a few tips. Thanks so much for this. The one thing I’ve noticed is that if I create a new profile, which I would intend to use as my FSLabd profile, any edits I make and save are also saved in my other profile, which is otherwise set up for their aircraft in MSFS. Quote
RUIZ Christopher Posted June 28 Posted June 28 2 minutes ago, David Reage said: Thanks so much for this. The one thing I’ve noticed is that if I create a new profile, which I would intend to use as my FSLabd profile, any edits I make and save are also saved in my other profile, which is otherwise set up for their aircraft in MSFS. Yes indeed. I guess that's the behavior of the app unfortunately. So if you want to switch from one aircraft to another, you'll have to manually change the options :/ ... 1 Quote
Or Ben Ari Posted June 28 Posted June 28 19 hours ago, RUIZ Christopher said: I've performed a few tests and it seems to work properly on both 2020 and 2024. that awesome! Thank you folks. Things that I've noticed with the mini Overhead is that the default state sometime is not properly set. For example, randomly the "int lt ann lt" is set to "test". Just adjusting the button physically makes the trick FOr those who are setting things up. Here are a few tips. 1. You should have the fslabs module installed for SKalarki io profiler tool. You can reinstall if if needed using Skalarki IO installer. If so, click on Modify and ensure that fslabs in P3D section is checked / installed. 2. Create a new profile on Skalarki IO profiler app. In "settings" select P3D V4/V5/V6 in the dropdown menu and check the box FSLabs. If the box is greyed out, try checking another box, change the sim version in the list, back to P3D and it shouldn't be grey'd out anymore. Seems like a bug in the UI. 3. You should also install the FSlabs HW Interface provided a bit higher on this thread. On the main interface of the tool, click first on "COmponent configuration" and check the hardware you have. If you have the mini ovh the box is on the bottom right. More info can be found on the official documentation: C:\Program Files\FlightSimLabs\HWInterface\MSFS\Documentation Now... How to run it ... 1. First, run the sim and start a flight 2. Run skalarki io profiler app. Ensure that sdk and profile are both running 3. Launch fslabs Hardware interface tool. click on "connect MSFS" then "connect hardware". Note that if you used different ports, you might edit them. This is detailed in the documentation Thankyou for these! i followed the steps but still no luck. i noticed that the "Aircraft Interface" in the IO Profiler turns green, the FCU comes a live and then it turns red again - "SDK : Not Connected".... Quote
RUIZ Christopher Posted June 28 Posted June 28 @OrB> is the FSLabs Hardware interface up and running? You should click on connect MSFS and Connect Hardware as well. Quote
Malcolm Rouse Posted June 28 Posted June 28 5 hours ago, RUIZ Christopher said: @Malcolm Rouse can you say a bit more? The behavior you have, which step are you stucked at? Ok I've uninstalled Aircraft HWI CC and profiler . As well Nool VDGS ( Causes FPS issues maybe ) Installed CC NEO ( Only ) HWI and Profiler . Started MSFS 2020 Loaded NEO Cold and dark Ran Profiler in admin Run HWI press connect etc FCU still wont work . Quote
Tom Hyde Posted June 28 Posted June 28 I'm getting the same issue Chris Ruiz had with the overhead where the bus tie is off in sim but pressing it on the full overhead hardware does nothing to overcome this. This is with A21N have tried a reinstall of HWI, repair of FSL libraries and NEO to no avail, it is showing green on the Skalarki profiler, desktop line FCU, ABRK, and MCDU work fine (although FCU will make the 100/1000 switch work in opposite if it does not match the sim when connecting through HWI. Quote
Or Ben Ari Posted June 28 Posted June 28 4 hours ago, RUIZ Christopher said: @OrB> is the FSLabs Hardware interface up and running? You should click on connect MSFS and Connect Hardware as well. Yes, up and running. Even showing good connection with msfs and the hardware. Before connecting, If I will change the altitude select (on the aircraft fcu )Skalarki fcu will come alive with the right numbers but will immediately stop responding after 1 second. Quote
RUIZ Christopher Posted June 29 Posted June 29 On 6/28/2025 at 3:07 PM, Tom Hyde said: I'm getting the same issue Chris Ruiz had with the overhead where the bus tie is off in sim but pressing it on the full overhead hardware does nothing to overcome this. This is with A21N have tried a reinstall of HWI, repair of FSL libraries and NEO to no avail, it is showing green on the Skalarki profiler, desktop line FCU, ABRK, and MCDU work fine (although FCU will make the 100/1000 switch work in opposite if it does not match the sim when connecting through HWI. I had same issue when the Settings on Skalarki io profiler app was not set to "FS Labs". Ensure that it's set according to the screenshot. Also, check the right panel you have on the Hardware Interface options. Quote
RUIZ Christopher Posted June 29 Posted June 29 On 6/28/2025 at 2:59 PM, Malcolm Rouse said: Ok I've uninstalled Aircraft HWI CC and profiler . As well Nool VDGS ( Causes FPS issues maybe ) Installed CC NEO ( Only ) HWI and Profiler . Started MSFS 2020 Loaded NEO Cold and dark Ran Profiler in admin Run HWI press connect etc FCU still wont work . Malcolm, your first screenshot shows that no Skalarki Hardware is connected to your computer. All Hardwares are on "No" status in red. I'll first investigate that because it should be shown in Green if correctly connected, powered on and recognized. Quote
Tom Hyde Posted July 1 Posted July 1 On 6/29/2025 at 11:31 PM, RUIZ Christopher said: I had same issue when the Settings on Skalarki io profiler app was not set to "FS Labs". Ensure that it's set according to the screenshot. Also, check the right panel you have on the Hardware Interface options. So I have traced it back to the Profiler defaulting to desktop line overhead, if I change to 2017 #3 version and selecting the available options that are present on the panel it seems to work now after a sim and profiler restart but I will test properly when the weather isn't so hot hopefully tomorrow! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.