home.social

#simpit — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #simpit, aggregated by home.social.

  1. Thrustmaster rudder pedal repair

    I repaired my old Thrustmaster rudder pedals. That’s the one I upgraded using an Arduino Pro Micro before (PeerTube, YouTube) to get rid of their old D-Sub connector so this device is really old and probably belongs into a museum. I doubt I’d get any replacement parts for this from the vendor nowadays.

    Their sliding beds are made of some sort of plastic and this started to become brittle over the years. When I noticed that one side was coming apart I found several more hair fractures so I had to stop playing with the pedals for a while.

    Yesterday I went with one of the sliding beds to the Swablab, our local maker space, and considered cutting and milling new parts of wood, when a fellow maker suggested to use some leftover HPL pieces for the job.

    This was far less complicated compared to what I had in mind and I went for it. After a few minutes in the workshop I ended up with two new sliding beds that I mounted today. Worked like a charm.

    I went with Liquid Moly LM47 for some lube, simply because I have a tube of that around from working on the car. That’s grease for stuff like bearings and probably overkill for the job.

    Couldn’t be happier. The pedals are back into service and feel even better than before (probably thanks to the new grease) and I avoided once more going for expensive modern replacements. I’m also probably the only one with rudder pedals with wood aesthetic now 🤓

    https://beko.famkos.net/2026/04/16/thrustmaster-rudder-pedal-repair/ #DIY #flightsim #homeCockpit #simpit #Swablab #Thrustmaster
  2. Thrustmaster rudder pedal repair

    I repaired my old Thrustmaster rudder pedals. That’s the one I upgraded using an Arduino Pro Micro before (PeerTube, YouTube) to get rid of their old D-Sub connector so this device is really old and probably belongs into a museum. I doubt I’d get any replacement parts for this from the vendor nowadays.

    Their sliding beds are made of some sort of plastic and this started to become brittle over the years. When I noticed that one side was coming apart I found several more hair fractures so I had to stop playing with the pedals for a while.

    Yesterday I went with one of the sliding beds to the Swablab, our local maker space, and considered cutting and milling new parts of wood, when a fellow maker suggested to use some leftover HPL pieces for the job.

    This was far less complicated compared to what I had in mind and I went for it. After a few minutes in the workshop I ended up with two new sliding beds that I mounted today. Worked like a charm.

    I went with Liquid Moly LM47 for some lube, simply because I have a tube of that around from working on the car. That’s grease for stuff like bearings and probably overkill for the job.

    Couldn’t be happier. The pedals are back into service and feel even better than before (probably thanks to the new grease) and I avoided once more going for expensive modern replacements. I’m also probably the only one with rudder pedals with wood aesthetic now 🤓

    https://beko.famkos.net/2026/04/16/thrustmaster-rudder-pedal-repair/ #DIY #flightsim #homeCockpit #simpit #Swablab #Thrustmaster
  3. Thrustmaster rudder pedal repair

    I repaired my old Thrustmaster rudder pedals. That’s the one I upgraded using an Arduino Pro Micro before (PeerTube, YouTube) to get rid of their old D-Sub connector so this device is really old and probably belongs into a museum. I doubt I’d get any replacement parts for this from the vendor nowadays.

    Their sliding beds are made of some sort of plastic and this started to become brittle over the years. When I noticed that one side was coming apart I found several more hair fractures so I had to stop playing with the pedals for a while.

    Yesterday I went with one of the sliding beds to the Swablab, our local maker space, and considered cutting and milling new parts of wood, when a fellow maker suggested to use some leftover HPL pieces for the job.

    This was far less complicated compared to what I had in mind and I went for it. After a few minutes in the workshop I ended up with two new sliding beds that I mounted today. Worked like a charm.

    I went with Liquid Moly LM47 for some lube, simply because I have a tube of that around from working on the car. That’s grease for stuff like bearings and probably overkill for the job.

    Couldn’t be happier. The pedals are back into service and feel even better than before (probably thanks to the new grease) and I avoided once more going for expensive modern replacements. I’m also probably the only one with rudder pedals with wood aesthetic now 🤓

    https://beko.famkos.net/2026/04/16/thrustmaster-rudder-pedal-repair/ #DIY #flightsim #homeCockpit #simpit #Swablab #Thrustmaster
  4. Thrustmaster rudder pedal repair

    I repaired my old Thrustmaster rudder pedals. That’s the one I upgraded using an Arduino Pro Micro before (PeerTube, YouTube) to get rid of their old D-Sub connector so this device is really old and probably belongs into a museum. I doubt I’d get any replacement parts for this from the vendor nowadays.

    Their sliding beds are made of some sort of plastic and this started to become brittle over the years. When I noticed that one side was coming apart I found several more hair fractures so I had to stop playing with the pedals for a while.

    Yesterday I went with one of the sliding beds to the Swablab, our local maker space, and considered cutting and milling new parts of wood, when a fellow maker suggested to use some leftover HPL pieces for the job.

    This was far less complicated compared to what I had in mind and I went for it. After a few minutes in the workshop I ended up with two new sliding beds that I mounted today. Worked like a charm.

    I went with Liquid Moly LM47 for some lube, simply because I have a tube of that around from working on the car. That’s grease for stuff like bearings and probably overkill for the job.

    Couldn’t be happier. The pedals are back into service and feel even better than before (probably thanks to the new grease) and I avoided once more going for expensive modern replacements. I’m also probably the only one with rudder pedals with wood aesthetic now 🤓

    https://beko.famkos.net/2026/04/16/thrustmaster-rudder-pedal-repair/ #DIY #flightsim #homeCockpit #simpit #Swablab #Thrustmaster
  5. Thrustmaster rudder pedal repair

    I repaired my old Thrustmaster rudder pedals. That’s the one I upgraded using an Arduino Pro Micro before (PeerTube, YouTube) to get rid of their old D-Sub connector so this device is really old and probably belongs into a museum. I doubt I’d get any replacement parts for this from the vendor nowadays.

    Their sliding beds are made of some sort of plastic and this started to become brittle over the years. When I noticed that one side was coming apart I found several more hair fractures so I had to stop playing with the pedals for a while.

    Yesterday I went with one of the sliding beds to the Swablab, our local maker space, and considered cutting and milling new parts of wood, when a fellow maker suggested to use some leftover HPL pieces for the job.

    This was far less complicated compared to what I had in mind and I went for it. After a few minutes in the workshop I ended up with two new sliding beds that I mounted today. Worked like a charm.

    I went with Liquid Moly LM47 for some lube, simply because I have a tube of that around from working on the car. That’s grease for stuff like bearings and probably overkill for the job.

    Couldn’t be happier. The pedals are back into service and feel even better than before (probably thanks to the new grease) and I avoided once more going for expensive modern replacements. I’m also probably the only one with rudder pedals with wood aesthetic now 🤓

    https://beko.famkos.net/2026/04/16/thrustmaster-rudder-pedal-repair/ #DIY #flightsim #homeCockpit #simpit #Swablab #Thrustmaster
  6. I'll miss my #HOTAS / #HOSAS / #SIMPIT / #DIY #Discord channels starting next month.

    Anyone knows some alternative Spaces on #Matrix by chance?

    I'm aware of matrix.to/#/#hotasdiy:matrix.o channel.

    Edit: Getting somewhere: matrix.to/#/#aerospace-space:h

    Moving my 🤓 Discord space here matrix.to/#/#bekomotion:matrix shutting down there.

    Acronyms:
    HOTAS = Hands on Throttle and Stick
    HOSAS = Hands on Stick and Stick
    SIMPIT = Simulation/Simulated Cockpit

    #HomeCockpit #FlightSim #Joystick #Gamepad #Controller

    ♻️ 🙏

  7. I'll miss my #HOTAS / #HOSAS / #SIMPIT / #DIY #Discord channels starting next month.

    Anyone knows some alternative Spaces on #Matrix by chance?

    I'm aware of matrix.to/#/#hotasdiy:matrix.o channel.

    Edit: Getting somewhere: matrix.to/#/#aerospace-space:h

    Moving my 🤓 Discord space here matrix.to/#/#bekomotion:matrix shutting down there.

    Acronyms:
    HOTAS = Hands on Throttle and Stick
    HOSAS = Hands on Stick and Stick
    SIMPIT = Simulation/Simulated Cockpit

    #HomeCockpit #FlightSim #Joystick #Gamepad #Controller

    ♻️ 🙏

  8. I'll miss my #HOTAS / #HOSAS / #SIMPIT / #DIY #Discord channels starting next month.

    Anyone knows some alternative Spaces on #Matrix by chance?

    I'm aware of matrix.to/#/#hotasdiy:matrix.o channel.

    Edit: Getting somewhere: matrix.to/#/#aerospace-space:h

    Moving my 🤓 Discord space here matrix.to/#/#bekomotion:matrix shutting down there.

    Acronyms:
    HOTAS = Hands on Throttle and Stick
    HOSAS = Hands on Stick and Stick
    SIMPIT = Simulation/Simulated Cockpit

    #HomeCockpit #FlightSim #Joystick #Gamepad #Controller

    ♻️ 🙏

  9. I'll miss my #HOTAS / #HOSAS / #SIMPIT / #DIY #Discord channels starting next month.

    Anyone knows some alternative Spaces on #Matrix by chance?

    I'm aware of matrix.to/#/#hotasdiy:matrix.o channel.

    Edit: Getting somewhere: matrix.to/#/#aerospace-space:h

    Moving my 🤓 Discord space here matrix.to/#/#bekomotion:matrix shutting down there.

    Acronyms:
    HOTAS = Hands on Throttle and Stick
    HOSAS = Hands on Stick and Stick
    SIMPIT = Simulation/Simulated Cockpit

    #HomeCockpit #FlightSim #Joystick #Gamepad #Controller

    ♻️ 🙏

  10. I'll miss my #HOTAS / #HOSAS / #SIMPIT / #DIY #Discord channels starting next month.

    Anyone knows some alternative Spaces on #Matrix by chance?

    I'm aware of matrix.to/#/#hotasdiy:matrix.o channel.

    Edit: Getting somewhere: matrix.to/#/#aerospace-space:h

    Moving my 🤓 Discord space here matrix.to/#/#bekomotion:matrix shutting down there.

    Acronyms:
    HOTAS = Hands on Throttle and Stick
    HOSAS = Hands on Stick and Stick
    SIMPIT = Simulation/Simulated Cockpit

    #HomeCockpit #FlightSim #Joystick #Gamepad #Controller

    ♻️ 🙏

  11. Switching to a touch panel display in my VF-1 inspired home cockpit panel

    Finally replaced the old display with a new touch display in my VF-1 inspired home cockpit panel.

    The old display was salvaged from a laptop years ago and while it was working fine it also has a very bad viewing angle. I also got really tired of it’s glaring reflections so I experimented with an anti glare foil. This reduced the reflections a lot (worth every cent) but couldn’t help with the bad viewing angle, of course. I now had an idea how this could look though so I decided to buy into a replacement kit.

    The new display is the N173HCE-E31, a 17.3" with a resolution of 1920x1080. The touch controller registeres as a USB HID pointer/mouse by ILITEK and is basically sitting on top of the display. The kit included a PCB, that was advertised as VS-RTD2556HC-V2 controller by VSDISPLAY but came without any data sheet and I have no idea who really made this.

    Thing is this PCB runs very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use an USB PD power supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised but VSDISPLAY does not list this particular configuration in it’s datasheets. I contacted them via mail and they confirmed that this is not theirs. Theirs is apparently also strictly 5V/12V so that matches the picture I get.

    Mine is equipped with the IC RTD2556VD that does not match the list of supported ICs. Theirs has 2556TE_R20.1 printed on the PCB. Mine has 2555TF_R30.1 printed on. It’s like 99% similar but differently routed. It also mentions E470791 JPX-D which seems to point to the PCB manufacturer Dongguan Jingweixin Circuit Co Ltd but that is where my GoogleFu left me. I did also find the very same pictures on other offers, each stating a completely different controller model 🤷

    Anyway. I tried different configurations and while it works with 5V at ~2A I feel way more comfortable with 12V at ~0.8A on full brightness + blue color. I also attached a passive cooling block I had laying around and slapped a fan on top. Now it’s only “comfortable” warm to the touch after running for an hour.

    Sadly I do not have any device with DP ALT providing more than 5V and the PCB will always switch down to 5V the moment the USB-C dedicated for the display signal is used as well, even when a proper USB PD power supply is attached on it’s dedicated power connector. I could only keep it at 12V with my VITURE USB-C XR charging adapter, which can indeed provide 12V and more via USB-C while still allowing DP-ALT + USB2. There went my plans to only have a single cable for all, DPPD and the USB2 lanes for the ILITEK pointer, because I really do not want to block this adapter all the time.

    So now I have a dedicaded USB PD power supply at 12V connected, a HDMI connection for the display and an additional USB2 for the touchpanel pointer – and on top of that the little fan, that I simply connected to the micro USB2 socket on the PCB to provide it with 5V.

    This also means that my Linux PC can not know that both, touch panel pointer and display, belong together. As a result all touch panel inputs were all over the place and not limited to a single display. Apparently KDE has an option in it’s graphical settings where this can be easily configured. Gnome does not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel in Gnome too! And while the real manufacturer for the controller of the new display is still a mystery to me I found the following snippet in my monitor configuration $HOME/.config/monitors.xml after plugging the controller in:

    <monitorspec>    <connector>HDMI-2</connector>    <vendor>RTK</vendor>    <product>0x2555</product>    <serial>0x20230705</serial></monitorspec>

    The touch panel is, according to lsusb, connected as ID 222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input with gsettings to this specific display:

    gsettings set org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/222a:0001/ output "['RTK', '0x2555', '0x20230705']"

    Works like a charm but what a mess. I still wish I had a data sheet for this so if you know more kindly drop me a comment!

    The last thing to fix was the already mentioned reflective glare. For this I went with a screen protector by BROTECT (that name still makes me laugh), that promises beside anti scratch also an anti glare effect without limiting the view angles (some foils do this to enhance privacy).

    Attaching the foil was straight forward. The trick is to make sure that not a single dust particle is around during the process. To help with this I used an air humidifier to raise the humidity in the room before I even started. After that I removed the protective cover from the display and started slapping on the foil with the provided mounting card (yay, cardboard again). This was the very moment one of my curious cats decided to investigate my actions and jumped onto the table almost giving me a heart attack. The last thing I needed was cat hair all over the place and indeed after a lot of hissing I had to make good use of the also provided adhesive sticker to catch all dust particles in the last corner. Cats!

    The end result is like night and day. I do no longer see any light sources or myself clearly reflected on the display. The touch panel is still accepting inputs just fine and the colours look very bright from any angle, especially with HDR enabled. This will also ease it’s cleaning because the cockpit panel is collecting dust like crazy due to the gradient of the panel. I usually use a vacuum cleaner for this and the foil will help a lot to avoid scratches.

    Replacing the old display was also a task on it’s own. The old screws didn’t fit, of course, so I kinda had to build little adapters from leftover angle and wood pieces. Very ugly but good enough – this is just a toy after all 🤓

    Ah yes and now that I have a touch panel I also have to rewrite my HUD app, of course 🙃

    This content is licensed under a Creative Commons Attribution 4.0 International license.

    https://beko.famkos.net/2026/01/14/switching-to-a-touch-panel-display-in-my-vf-1-inspired-home-cockpit-panel/

    #flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit

  12. Switching to a touch panel display in my VF-1 inspired home cockpit panel

    Finally replaced the old display with a new touch display in my VF-1 inspired home cockpit panel.

    The old display was salvaged from a laptop years ago and while it was working fine it also has a very bad viewing angle. I also got really tired of it’s glaring reflections so I experimented with an anti glare foil. This reduced the reflections a lot (worth every cent) but couldn’t help with the bad viewing angle, of course. I now had an idea how this could look though so I decided to buy into a replacement kit.

    The new display is the N173HCE-E31, a 17.3" with a resolution of 1920x1080. The touch controller registeres as a USB HID pointer/mouse by ILITEK and is basically sitting on top of the display. The kit included a PCB, that was advertised as VS-RTD2556HC-V2 controller by VSDISPLAY but came without any data sheet and I have no idea who really made this.

    Thing is this PCB runs very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use an USB PD power supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised but VSDISPLAY does not list this particular configuration in it’s datasheets. I contacted them via mail and they confirmed that this is not theirs. Theirs is apparently also strictly 5V/12V so that matches the picture I get.

    Mine is equipped with the IC RTD2556VD that does not match the list of supported ICs. Theirs has 2556TE_R20.1 printed on the PCB. Mine has 2555TF_R30.1 printed on. It’s like 99% similar but differently routed. It also mentions E470791 JPX-D which seems to point to the PCB manufacturer Dongguan Jingweixin Circuit Co Ltd but that is where my GoogleFu left me. I did also find the very same pictures on other offers, each stating a completely different controller model 🤷

    Anyway. I tried different configurations and while it works with 5V at ~2A I feel way more comfortable with 12V at ~0.8A on full brightness + blue color. I also attached a passive cooling block I had laying around and slapped a fan on top. Now it’s only “comfortable” warm to the touch after running for an hour.

    Sadly I do not have any device with DP ALT providing more than 5V and the PCB will always switch down to 5V the moment the USB-C dedicated for the display signal is used as well, even when a proper USB PD power supply is attached on it’s dedicated power connector. I could only keep it at 12V with my VITURE USB-C XR charging adapter, which can indeed provide 12V and more via USB-C while still allowing DP-ALT + USB2. There went my plans to only have a single cable for all, DPPD and the USB2 lanes for the ILITEK pointer, because I really do not want to block this adapter all the time.

    So now I have a dedicaded USB PD power supply at 12V connected, a HDMI connection for the display and an additional USB2 for the touchpanel pointer – and on top of that the little fan, that I simply connected to the micro USB2 socket on the PCB to provide it with 5V.

    This also means that my Linux PC can not know that both, touch panel pointer and display, belong together. As a result all touch panel inputs were all over the place and not limited to a single display. Apparently KDE has an option in it’s graphical settings where this can be easily configured. Gnome does not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel in Gnome too! And while the real manufacturer for the controller of the new display is still a mystery to me I found the following snippet in my monitor configuration $HOME/.config/monitors.xml after plugging the controller in:

    <monitorspec>    <connector>HDMI-2</connector>    <vendor>RTK</vendor>    <product>0x2555</product>    <serial>0x20230705</serial></monitorspec>

    The touch panel is, according to lsusb, connected as ID 222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input with gsettings to this specific display:

    gsettings set org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/222a:0001/ output "['RTK', '0x2555', '0x20230705']"

    Works like a charm but what a mess. I still wish I had a data sheet for this so if you know more kindly drop me a comment!

    The last thing to fix was the already mentioned reflective glare. For this I went with a screen protector by BROTECT (that name still makes me laugh), that promises beside anti scratch also an anti glare effect without limiting the view angles (some foils do this to enhance privacy).

    Attaching the foil was straight forward. The trick is to make sure that not a single dust particle is around during the process. To help with this I used an air humidifier to raise the humidity in the room before I even started. After that I removed the protective cover from the display and started slapping on the foil with the provided mounting card (yay, cardboard again). This was the very moment one of my curious cats decided to investigate my actions and jumped onto the table almost giving me a heart attack. The last thing I needed was cat hair all over the place and indeed after a lot of hissing I had to make good use of the also provided adhesive sticker to catch all dust particles in the last corner. Cats!

    The end result is like night and day. I do no longer see any light sources or myself clearly reflected on the display. The touch panel is still accepting inputs just fine and the colours look very bright from any angle, especially with HDR enabled. This will also ease it’s cleaning because the cockpit panel is collecting dust like crazy due to the gradient of the panel. I usually use a vacuum cleaner for this and the foil will help a lot to avoid scratches.

    Replacing the old display was also a task on it’s own. The old screws didn’t fit, of course, so I kinda had to build little adapters from leftover angle and wood pieces. Very ugly but good enough – this is just a toy after all 🤓

    Ah yes and now that I have a touch panel I also have to rewrite my HUD app, of course 🙃

    This content is licensed under a Creative Commons Attribution 4.0 International license.

    https://beko.famkos.net/2026/01/14/switching-to-a-touch-panel-display-in-my-vf-1-inspired-home-cockpit-panel/

    #flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit

  13. Switching to a touch panel display in my VF-1 inspired home cockpit panel

    Finally replaced the old display with a new touch display in my VF-1 inspired home cockpit panel.

    The old display was salvaged from a laptop years ago and while it was working fine it also has a very bad viewing angle. I also got really tired of it’s glaring reflections so I experimented with an anti glare foil. This reduced the reflections a lot (worth every cent) but couldn’t help with the bad viewing angle, of course. I now had an idea how this could look though so I decided to buy into a replacement kit.

    The new display is the N173HCE-E31, a 17.3" with a resolution of 1920x1080. The touch controller registeres as a USB HID pointer/mouse by ILITEK and is basically sitting on top of the display. The kit included a PCB, that was advertised as VS-RTD2556HC-V2 controller by VSDISPLAY but came without any data sheet and I have no idea who really made this.

    Thing is this PCB runs very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use an USB PD power supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised but VSDISPLAY does not list this particular configuration in it’s datasheets. I contacted them via mail and they confirmed that this is not theirs. Theirs is apparently also strictly 5V/12V so that matches the picture I get.

    Mine is equipped with the IC RTD2556VD that does not match the list of supported ICs. Theirs has 2556TE_R20.1 printed on the PCB. Mine has 2555TF_R30.1 printed on. It’s like 99% similar but differently routed. It also mentions E470791 JPX-D which seems to point to the PCB manufacturer Dongguan Jingweixin Circuit Co Ltd but that is where my GoogleFu left me. I did also find the very same pictures on other offers, each stating a completely different controller model 🤷

    Anyway. I tried different configurations and while it works with 5V at ~2A I feel way more comfortable with 12V at ~0.8A on full brightness + blue color. I also attached a passive cooling block I had laying around and slapped a fan on top. Now it’s only “comfortable” warm to the touch after running for an hour.

    Sadly I do not have any device with DP ALT providing more than 5V and the PCB will always switch down to 5V the moment the USB-C dedicated for the display signal is used as well, even when a proper USB PD power supply is attached on it’s dedicated power connector. I could only keep it at 12V with my VITURE USB-C XR charging adapter, which can indeed provide 12V and more via USB-C while still allowing DP-ALT + USB2. There went my plans to only have a single cable for all, DPPD and the USB2 lanes for the ILITEK pointer, because I really do not want to block this adapter all the time.

    So now I have a dedicaded USB PD power supply at 12V connected, a HDMI connection for the display and an additional USB2 for the touchpanel pointer – and on top of that the little fan, that I simply connected to the micro USB2 socket on the PCB to provide it with 5V.

    This also means that my Linux PC can not know that both, touch panel pointer and display, belong together. As a result all touch panel inputs were all over the place and not limited to a single display. Apparently KDE has an option in it’s graphical settings where this can be easily configured. Gnome does not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel in Gnome too! And while the real manufacturer for the controller of the new display is still a mystery to me I found the following snippet in my monitor configuration $HOME/.config/monitors.xml after plugging the controller in:

    <monitorspec>    <connector>HDMI-2</connector>    <vendor>RTK</vendor>    <product>0x2555</product>    <serial>0x20230705</serial></monitorspec>

    The touch panel is, according to lsusb, connected as ID 222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input with gsettings to this specific display:

    gsettings set org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/222a:0001/ output "['RTK', '0x2555', '0x20230705']"

    Works like a charm but what a mess. I still wish I had a data sheet for this so if you know more kindly drop me a comment!

    The last thing to fix was the already mentioned reflective glare. For this I went with a screen protector by BROTECT (that name still makes me laugh), that promises beside anti scratch also an anti glare effect without limiting the view angles (some foils do this to enhance privacy).

    Attaching the foil was straight forward. The trick is to make sure that not a single dust particle is around during the process. To help with this I used an air humidifier to raise the humidity in the room before I even started. After that I removed the protective cover from the display and started slapping on the foil with the provided mounting card (yay, cardboard again). This was the very moment one of my curious cats decided to investigate my actions and jumped onto the table almost giving me a heart attack. The last thing I needed was cat hair all over the place and indeed after a lot of hissing I had to make good use of the also provided adhesive sticker to catch all dust particles in the last corner. Cats!

    The end result is like night and day. I do no longer see any light sources or myself clearly reflected on the display. The touch panel is still accepting inputs just fine and the colours look very bright from any angle, especially with HDR enabled. This will also ease it’s cleaning because the cockpit panel is collecting dust like crazy due to the gradient of the panel. I usually use a vacuum cleaner for this and the foil will help a lot to avoid scratches.

    Replacing the old display was also a task on it’s own. The old screws didn’t fit, of course, so I kinda had to build little adapters from leftover angle and wood pieces. Very ugly but good enough – this is just a toy after all 🤓

    Ah yes and now that I have a touch panel I also have to rewrite my HUD app, of course 🙃

    This content is licensed under a Creative Commons Attribution 4.0 International license.

    https://beko.famkos.net/2026/01/14/switching-to-a-touch-panel-display-in-my-vf-1-inspired-home-cockpit-panel/

    #flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit

  14. Switching to a touch panel display in my VF-1 inspired home cockpit panel

    Finally replaced the old display with a new touch display in my VF-1 inspired home cockpit panel.

    The old display was salvaged from a laptop years ago and while it was working fine it also has a very bad viewing angle. I also got really tired of it’s glaring reflections so I experimented with an anti glare foil. This reduced the reflections a lot (worth every cent) but couldn’t help with the bad viewing angle, of course. I now had an idea how this could look though so I decided to buy into a replacement kit.

    The new display is the N173HCE-E31, a 17.3" with a resolution of 1920x1080. The touch controller registeres as a USB HID pointer/mouse by ILITEK and is basically sitting on top of the display. The kit included a PCB, that was advertised as VS-RTD2556HC-V2 controller by VSDISPLAY but came without any data sheet and I have no idea who really made this.

    Thing is this PCB runs very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use an USB PD power supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised but VSDISPLAY does not list this particular configuration in it’s datasheets. I contacted them via mail and they confirmed that this is not theirs. Theirs is apparently also strictly 5V/12V so that matches the picture I get.

    Mine is equipped with the IC RTD2556VD that does not match the list of supported ICs. Theirs has 2556TE_R20.1 printed on the PCB. Mine has 2555TF_R30.1 printed on. It’s like 99% similar but differently routed. It also mentions E470791 JPX-D which seems to point to the PCB manufacturer Dongguan Jingweixin Circuit Co Ltd but that is where my GoogleFu left me. I did also find the very same pictures on other offers, each stating a completely different controller model 🤷

    Anyway. I tried different configurations and while it works with 5V at ~2A I feel way more comfortable with 12V at ~0.8A on full brightness + blue color. I also attached a passive cooling block I had laying around and slapped a fan on top. Now it’s only “comfortable” warm to the touch after running for an hour.

    Sadly I do not have any device with DP ALT providing more than 5V and the PCB will always switch down to 5V the moment the USB-C dedicated for the display signal is used as well, even when a proper USB PD power supply is attached on it’s dedicated power connector. I could only keep it at 12V with my VITURE USB-C XR charging adapter, which can indeed provide 12V and more via USB-C while still allowing DP-ALT + USB2. There went my plans to only have a single cable for all, DPPD and the USB2 lanes for the ILITEK pointer, because I really do not want to block this adapter all the time.

    So now I have a dedicaded USB PD power supply at 12V connected, a HDMI connection for the display and an additional USB2 for the touchpanel pointer – and on top of that the little fan, that I simply connected to the micro USB2 socket on the PCB to provide it with 5V.

    This also means that my Linux PC can not know that both, touch panel pointer and display, belong together. As a result all touch panel inputs were all over the place and not limited to a single display. Apparently KDE has an option in it’s graphical settings where this can be easily configured. Gnome does not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel in Gnome too! And while the real manufacturer for the controller of the new display is still a mystery to me I found the following snippet in my monitor configuration $HOME/.config/monitors.xml after plugging the controller in:

    <monitorspec>    <connector>HDMI-2</connector>    <vendor>RTK</vendor>    <product>0x2555</product>    <serial>0x20230705</serial></monitorspec>

    The touch panel is, according to lsusb, connected as ID 222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input with gsettings to this specific display:

    gsettings set org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/222a:0001/ output "['RTK', '0x2555', '0x20230705']"

    Works like a charm but what a mess. I still wish I had a data sheet for this so if you know more kindly drop me a comment!

    The last thing to fix was the already mentioned reflective glare. For this I went with a screen protector by BROTECT (that name still makes me laugh), that promises beside anti scratch also an anti glare effect without limiting the view angles (some foils do this to enhance privacy).

    Attaching the foil was straight forward. The trick is to make sure that not a single dust particle is around during the process. To help with this I used an air humidifier to raise the humidity in the room before I even started. After that I removed the protective cover from the display and started slapping on the foil with the provided mounting card (yay, cardboard again). This was the very moment one of my curious cats decided to investigate my actions and jumped onto the table almost giving me a heart attack. The last thing I needed was cat hair all over the place and indeed after a lot of hissing I had to make good use of the also provided adhesive sticker to catch all dust particles in the last corner. Cats!

    The end result is like night and day. I do no longer see any light sources or myself clearly reflected on the display. The touch panel is still accepting inputs just fine and the colours look very bright from any angle, especially with HDR enabled. This will also ease it’s cleaning because the cockpit panel is collecting dust like crazy due to the gradient of the panel. I usually use a vacuum cleaner for this and the foil will help a lot to avoid scratches.

    Replacing the old display was also a task on it’s own. The old screws didn’t fit, of course, so I kinda had to build little adapters from leftover angle and wood pieces. Very ugly but good enough – this is just a toy after all 🤓

    Ah yes and now that I have a touch panel I also have to rewrite my HUD app, of course 🙃

    This content is licensed under a Creative Commons Attribution 4.0 International license.

    https://beko.famkos.net/2026/01/14/switching-to-a-touch-panel-display-in-my-vf-1-inspired-home-cockpit-panel/

    #flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit

  15. Switching to a touch panel display in my VF-1 inspired home cockpit panel

    Finally replaced the old display with a new touch display in my VF-1 inspired home cockpit panel.

    The old display was salvaged from a laptop years ago and while it was working fine it also has a very bad viewing angle. I also got really tired of it’s glaring reflections so I experimented with an anti glare foil. This reduced the reflections a lot (worth every cent) but couldn’t help with the bad viewing angle, of course. I now had an idea how this could look though so I decided to buy into a replacement kit.

    The new display is the N173HCE-E31, a 17.3" with a resolution of 1920x1080. The touch controller registeres as a USB HID pointer/mouse by ILITEK and is basically sitting on top of the display. The kit included a PCB, that was advertised as VS-RTD2556HC-V2 controller by VSDISPLAY but came without any data sheet and I have no idea who really made this.

    Thing is this PCB runs very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use an USB PD power supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised but VSDISPLAY does not list this particular configuration in it’s datasheets. I contacted them via mail and they confirmed that this is not theirs. Theirs is apparently also strictly 5V/12V so that matches the picture I get.

    Mine is equipped with the IC RTD2556VD that does not match the list of supported ICs. Theirs has 2556TE_R20.1 printed on the PCB. Mine has 2555TF_R30.1 printed on. It’s like 99% similar but differently routed. It also mentions E470791 JPX-D which seems to point to the PCB manufacturer Dongguan Jingweixin Circuit Co Ltd but that is where my GoogleFu left me. I did also find the very same pictures on other offers, each stating a completely different controller model 🤷

    Anyway. I tried different configurations and while it works with 5V at ~2A I feel way more comfortable with 12V at ~0.8A on full brightness + blue color. I also attached a passive cooling block I had laying around and slapped a fan on top. Now it’s only “comfortable” warm to the touch after running for an hour.

    Sadly I do not have any device with DP ALT providing more than 5V and the PCB will always switch down to 5V the moment the USB-C dedicated for the display signal is used as well, even when a proper USB PD power supply is attached on it’s dedicated power connector. I could only keep it at 12V with my VITURE USB-C XR charging adapter, which can indeed provide 12V and more via USB-C while still allowing DP-ALT + USB2. There went my plans to only have a single cable for all, DPPD and the USB2 lanes for the ILITEK pointer, because I really do not want to block this adapter all the time.

    So now I have a dedicaded USB PD power supply at 12V connected, a HDMI connection for the display and an additional USB2 for the touchpanel pointer – and on top of that the little fan, that I simply connected to the micro USB2 socket on the PCB to provide it with 5V.

    This also means that my Linux PC can not know that both, touch panel pointer and display, belong together. As a result all touch panel inputs were all over the place and not limited to a single display. Apparently KDE has an option in it’s graphical settings where this can be easily configured. Gnome does not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel in Gnome too! And while the real manufacturer for the controller of the new display is still a mystery to me I found the following snippet in my monitor configuration $HOME/.config/monitors.xml after plugging the controller in:

    <monitorspec>    <connector>HDMI-2</connector>    <vendor>RTK</vendor>    <product>0x2555</product>    <serial>0x20230705</serial></monitorspec>

    The touch panel is, according to lsusb, connected as ID 222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input with gsettings to this specific display:

    gsettings set org.gnome.desktop.peripherals.touchscreen:/org/gnome/desktop/peripherals/touchscreens/222a:0001/ output "['RTK', '0x2555', '0x20230705']"

    Works like a charm but what a mess. I still wish I had a data sheet for this so if you know more kindly drop me a comment!

    The last thing to fix was the already mentioned reflective glare. For this I went with a screen protector by BROTECT (that name still makes me laugh), that promises beside anti scratch also an anti glare effect without limiting the view angles (some foils do this to enhance privacy).

    Attaching the foil was straight forward. The trick is to make sure that not a single dust particle is around during the process. To help with this I used an air humidifier to raise the humidity in the room before I even started. After that I removed the protective cover from the display and started slapping on the foil with the provided mounting card (yay, cardboard again). This was the very moment one of my curious cats decided to investigate my actions and jumped onto the table almost giving me a heart attack. The last thing I needed was cat hair all over the place and indeed after a lot of hissing I had to make good use of the also provided adhesive sticker to catch all dust particles in the last corner. Cats!

    The end result is like night and day. I do no longer see any light sources or myself clearly reflected on the display. The touch panel is still accepting inputs just fine and the colours look very bright from any angle, especially with HDR enabled. This will also ease it’s cleaning because the cockpit panel is collecting dust like crazy due to the gradient of the panel. I usually use a vacuum cleaner for this and the foil will help a lot to avoid scratches.

    Replacing the old display was also a task on it’s own. The old screws didn’t fit, of course, so I kinda had to build little adapters from leftover angle and wood pieces. Very ugly but good enough – this is just a toy after all 🤓

    Ah yes and now that I have a touch panel I also have to rewrite my HUD app, of course 🙃

    This content is licensed under a Creative Commons Attribution 4.0 International license.

    https://beko.famkos.net/2026/01/14/switching-to-a-touch-panel-display-in-my-vf-1-inspired-home-cockpit-panel/

    #flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit

  16. Chirp chirp chirp little chicken – interfacing Ace Combat 7 for some sweet telemetry for my VF-1 inspired home cockpit

    So what happens when sheer stubbornness, a glorified button box, Ace Combat and the Unreal Engine Scripting System meet? Pure magic. I got the game to spew out a constant stream of telemetry data and events in search for more immersion in my VF-1 inspired home cockpit. The approach is the very same that I used for X4 Foundations before: Side load lib Luasocket, get a network connection established and start dumping extracted game data to it. This is highly experimental and the result of hacking away for the last ~4 nights. This video demonstrates the results:

    https://makertube.net/w/cbXJAveVgVTGVEi58akVTA / https://www.youtube.com/watch?v=50J-gjkgJxE

    To be perfectly clear: I am aware that Ace Combat is not a “flight sim”, not really worth of an API, and I know that DCS or BMS does it better and in greater detail and even with realism. This is not the point. I started working on this just for fun and to satisfy my own curiosity to see *if I can make it*. This may be hard to believe but chipping rocks together until the computer does what I want is “quality time” for me 🤓

    You may have noticed that I’m a Macross fan and that my SimPit is heavily inspired by a VF-1 Valkyrie and that I usually use a modded VF-1 plane in AC as well. This is my personal substitute for the lack of any decent Macross / Robotech game since Macross VOXP.

    This said I usually fly Space Pew Pew games with this cockpit so everything you see going on is designed for _space_ and not for flight sim. This is also why I sometimes talk about “ships” or “docked”. This is wording found everywhere in my plumbing pipeline for telemetry. All games I play, that can use this, send their data over this. The idea is that I do not have to rewrite half of the connected systems for every game so I transform the data into a unified format before.

    You can read more about this on the dedicated project website https://simpit.dev (and here, of course). I will soon update it with some more details for Ace Combat. If this looks like something you’d like to try let me know, I’d love to connect. I’m active on various social media. Please do let me know if you find this inspiring.

    https://beko.famkos.net/2025/12/31/chirp-chirp-chirp-little-chicken-interfacing-ace-combat-7-for-some-sweet-telemetry-for-my-vf-1-inspired-home-cockpit/

    #AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1

  17. Chirp chirp chirp little chicken – interfacing Ace Combat 7 for some sweet telemetry for my VF-1 inspired home cockpit

    So what happens when sheer stubbornness, a glorified button box, Ace Combat and the Unreal Engine Scripting System meet? Pure magic. I got the game to spew out a constant stream of telemetry data and events in search for more immersion in my VF-1 inspired home cockpit. The approach is the very same that I used for X4 Foundations before: Side load lib Luasocket, get a network connection established and start dumping extracted game data to it. This is highly experimental and the result of hacking away for the last ~4 nights. This video demonstrates the results:

    https://makertube.net/w/cbXJAveVgVTGVEi58akVTA / https://www.youtube.com/watch?v=50J-gjkgJxE

    To be perfectly clear: I am aware that Ace Combat is not a “flight sim”, not really worth of an API, and I know that DCS or BMS does it better and in greater detail and even with realism. This is not the point. I started working on this just for fun and to satisfy my own curiosity to see *if I can make it*. This may be hard to believe but chipping rocks together until the computer does what I want is “quality time” for me 🤓

    You may have noticed that I’m a Macross fan and that my SimPit is heavily inspired by a VF-1 Valkyrie and that I usually use a modded VF-1 plane in AC as well. This is my personal substitute for the lack of any decent Macross / Robotech game since Macross VOXP.

    This said I usually fly Space Pew Pew games with this cockpit so everything you see going on is designed for _space_ and not for flight sim. This is also why I sometimes talk about “ships” or “docked”. This is wording found everywhere in my plumbing pipeline for telemetry. All games I play, that can use this, send their data over this. The idea is that I do not have to rewrite half of the connected systems for every game so I transform the data into a unified format before.

    You can read more about this on the dedicated project website https://simpit.dev (and here, of course). I will soon update it with some more details for Ace Combat. If this looks like something you’d like to try let me know, I’d love to connect. I’m active on various social media. Please do let me know if you find this inspiring.

    https://beko.famkos.net/2025/12/31/chirp-chirp-chirp-little-chicken-interfacing-ace-combat-7-for-some-sweet-telemetry-for-my-vf-1-inspired-home-cockpit/

    #AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1

  18. Chirp chirp chirp little chicken – interfacing Ace Combat 7 for some sweet telemetry for my VF-1 inspired home cockpit

    So what happens when sheer stubbornness, a glorified button box, Ace Combat and the Unreal Engine Scripting System meet? Pure magic. I got the game to spew out a constant stream of telemetry data and events in search for more immersion in my VF-1 inspired home cockpit. The approach is the very same that I used for X4 Foundations before: Side load lib Luasocket, get a network connection established and start dumping extracted game data to it. This is highly experimental and the result of hacking away for the last ~4 nights. This video demonstrates the results:

    https://makertube.net/w/cbXJAveVgVTGVEi58akVTA / https://www.youtube.com/watch?v=50J-gjkgJxE

    To be perfectly clear: I am aware that Ace Combat is not a “flight sim”, not really worth of an API, and I know that DCS or BMS does it better and in greater detail and even with realism. This is not the point. I started working on this just for fun and to satisfy my own curiosity to see *if I can make it*. This may be hard to believe but chipping rocks together until the computer does what I want is “quality time” for me 🤓

    You may have noticed that I’m a Macross fan and that my SimPit is heavily inspired by a VF-1 Valkyrie and that I usually use a modded VF-1 plane in AC as well. This is my personal substitute for the lack of any decent Macross / Robotech game since Macross VOXP.

    This said I usually fly Space Pew Pew games with this cockpit so everything you see going on is designed for _space_ and not for flight sim. This is also why I sometimes talk about “ships” or “docked”. This is wording found everywhere in my plumbing pipeline for telemetry. All games I play, that can use this, send their data over this. The idea is that I do not have to rewrite half of the connected systems for every game so I transform the data into a unified format before.

    You can read more about this on the dedicated project website https://simpit.dev (and here, of course). I will soon update it with some more details for Ace Combat. If this looks like something you’d like to try let me know, I’d love to connect. I’m active on various social media. Please do let me know if you find this inspiring.

    https://beko.famkos.net/2025/12/31/chirp-chirp-chirp-little-chicken-interfacing-ace-combat-7-for-some-sweet-telemetry-for-my-vf-1-inspired-home-cockpit/

    #AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1

  19. Chirp chirp chirp little chicken – interfacing Ace Combat 7 for some sweet telemetry for my VF-1 inspired home cockpit

    So what happens when sheer stubbornness, a glorified button box, Ace Combat and the Unreal Engine Scripting System meet? Pure magic. I got the game to spew out a constant stream of telemetry data and events in search for more immersion in my VF-1 inspired home cockpit. The approach is the very same that I used for X4 Foundations before: Side load lib Luasocket, get a network connection established and start dumping extracted game data to it. This is highly experimental and the result of hacking away for the last ~4 nights. This video demonstrates the results:

    https://makertube.net/w/cbXJAveVgVTGVEi58akVTA / https://www.youtube.com/watch?v=50J-gjkgJxE

    To be perfectly clear: I am aware that Ace Combat is not a “flight sim”, not really worth of an API, and I know that DCS or BMS does it better and in greater detail and even with realism. This is not the point. I started working on this just for fun and to satisfy my own curiosity to see *if I can make it*. This may be hard to believe but chipping rocks together until the computer does what I want is “quality time” for me 🤓

    You may have noticed that I’m a Macross fan and that my SimPit is heavily inspired by a VF-1 Valkyrie and that I usually use a modded VF-1 plane in AC as well. This is my personal substitute for the lack of any decent Macross / Robotech game since Macross VOXP.

    This said I usually fly Space Pew Pew games with this cockpit so everything you see going on is designed for _space_ and not for flight sim. This is also why I sometimes talk about “ships” or “docked”. This is wording found everywhere in my plumbing pipeline for telemetry. All games I play, that can use this, send their data over this. The idea is that I do not have to rewrite half of the connected systems for every game so I transform the data into a unified format before.

    You can read more about this on the dedicated project website https://simpit.dev (and here, of course). I will soon update it with some more details for Ace Combat. If this looks like something you’d like to try let me know, I’d love to connect. I’m active on various social media. Please do let me know if you find this inspiring.

    https://beko.famkos.net/2025/12/31/chirp-chirp-chirp-little-chicken-interfacing-ace-combat-7-for-some-sweet-telemetry-for-my-vf-1-inspired-home-cockpit/

    #AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1

  20. Chirp chirp chirp little chicken – interfacing Ace Combat 7 for some sweet telemetry for my VF-1 inspired home cockpit

    So what happens when sheer stubbornness, a glorified button box, Ace Combat and the Unreal Engine Scripting System meet? Pure magic. I got the game to spew out a constant stream of telemetry data and events in search for more immersion in my VF-1 inspired home cockpit. The approach is the very same that I used for X4 Foundations before: Side load lib Luasocket, get a network connection established and start dumping extracted game data to it. This is highly experimental and the result of hacking away for the last ~4 nights. This video demonstrates the results:

    https://makertube.net/w/cbXJAveVgVTGVEi58akVTA / https://www.youtube.com/watch?v=50J-gjkgJxE

    To be perfectly clear: I am aware that Ace Combat is not a “flight sim”, not really worth of an API, and I know that DCS or BMS does it better and in greater detail and even with realism. This is not the point. I started working on this just for fun and to satisfy my own curiosity to see *if I can make it*. This may be hard to believe but chipping rocks together until the computer does what I want is “quality time” for me 🤓

    You may have noticed that I’m a Macross fan and that my SimPit is heavily inspired by a VF-1 Valkyrie and that I usually use a modded VF-1 plane in AC as well. This is my personal substitute for the lack of any decent Macross / Robotech game since Macross VOXP.

    This said I usually fly Space Pew Pew games with this cockpit so everything you see going on is designed for _space_ and not for flight sim. This is also why I sometimes talk about “ships” or “docked”. This is wording found everywhere in my plumbing pipeline for telemetry. All games I play, that can use this, send their data over this. The idea is that I do not have to rewrite half of the connected systems for every game so I transform the data into a unified format before.

    You can read more about this on the dedicated project website https://simpit.dev (and here, of course). I will soon update it with some more details for Ace Combat. If this looks like something you’d like to try let me know, I’d love to connect. I’m active on various social media. Please do let me know if you find this inspiring.

    https://beko.famkos.net/2025/12/31/chirp-chirp-chirp-little-chicken-interfacing-ace-combat-7-for-some-sweet-telemetry-for-my-vf-1-inspired-home-cockpit/

    #AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1

  21. Yeah, it started talking to my cockpit panel 🤓

    Still a little rough on the edges but it's getting there.

    Getting target data, a shiton of plane telemetry aaaaand the radio chatter 🤓

    And most important: Angry blinken lights are now blinking angrily.

    Missile! Missile!

    #AceCombat7 #HomeCockpit #ViperPit #SimPit

  22. Yeah, it started talking to my cockpit panel 🤓

    Still a little rough on the edges but it's getting there.

    Getting target data, a shiton of plane telemetry aaaaand the radio chatter 🤓

    And most important: Angry blinken lights are now blinking angrily.

    Missile! Missile!

    #AceCombat7 #HomeCockpit #ViperPit #SimPit

  23. Yeah, it started talking to my cockpit panel 🤓

    Still a little rough on the edges but it's getting there.

    Getting target data, a shiton of plane telemetry aaaaand the radio chatter 🤓

    And most important: Angry blinken lights are now blinking angrily.

    Missile! Missile!

    #AceCombat7 #HomeCockpit #ViperPit #SimPit

  24. Yeah, it started talking to my cockpit panel 🤓

    Still a little rough on the edges but it's getting there.

    Getting target data, a shiton of plane telemetry aaaaand the radio chatter 🤓

    And most important: Angry blinken lights are now blinking angrily.

    Missile! Missile!

    #AceCombat7 #HomeCockpit #ViperPit #SimPit

  25. Yeah, it started talking to my cockpit panel 🤓

    Still a little rough on the edges but it's getting there.

    Getting target data, a shiton of plane telemetry aaaaand the radio chatter 🤓

    And most important: Angry blinken lights are now blinking angrily.

    Missile! Missile!

    #AceCombat7 #HomeCockpit #ViperPit #SimPit

  26. Wohoo. I'm getting cockpit telemetry of #AceCombat7 in LUA.

    Starting poking around #UE4SS mod for #AceCombat and slammed rocks together for 2 hours and it started chirping altitude, speed and health 🤓

    Just a proof of concept so far but this looks promising.

    #HomeCockpit #ViperPit #SimPit

  27. Wohoo. I'm getting cockpit telemetry of #AceCombat7 in LUA.

    Starting poking around #UE4SS mod for #AceCombat and slammed rocks together for 2 hours and it started chirping altitude, speed and health 🤓

    Just a proof of concept so far but this looks promising.

    #HomeCockpit #ViperPit #SimPit

  28. Wohoo. I'm getting cockpit telemetry of #AceCombat7 in LUA.

    Starting poking around #UE4SS mod for #AceCombat and slammed rocks together for 2 hours and it started chirping altitude, speed and health 🤓

    Just a proof of concept so far but this looks promising.

    #HomeCockpit #ViperPit #SimPit

  29. Wohoo. I'm getting cockpit telemetry of #AceCombat7 in LUA.

    Starting poking around #UE4SS mod for #AceCombat and slammed rocks together for 2 hours and it started chirping altitude, speed and health 🤓

    Just a proof of concept so far but this looks promising.

    #HomeCockpit #ViperPit #SimPit

  30. Wohoo. I'm getting cockpit telemetry of #AceCombat7 in LUA.

    Starting poking around #UE4SS mod for #AceCombat and slammed rocks together for 2 hours and it started chirping altitude, speed and health 🤓

    Just a proof of concept so far but this looks promising.

    #HomeCockpit #ViperPit #SimPit

  31. 🤓 🚨

    Finally updated #x4simpit with changes that were rotting on my disk for months now. The following new events for my #x4foundations ship telemetry mod are available:

    * Docked
    * Undocked
    * UnderAttack
    * ReceiveText
    * Heatwarning

    Plus a bunch of fixes: github.com/bekopharm/x4-simpit

    #homeCockpit #SimPit #SpacePewPew

  32. 🤓 🚨

    Finally updated #x4simpit with changes that were rotting on my disk for months now. The following new events for my #x4foundations ship telemetry mod are available:

    * Docked
    * Undocked
    * UnderAttack
    * ReceiveText
    * Heatwarning

    Plus a bunch of fixes: github.com/bekopharm/x4-simpit

    #homeCockpit #SimPit #SpacePewPew

  33. 🤓 🚨

    Finally updated #x4simpit with changes that were rotting on my disk for months now. The following new events for my #x4foundations ship telemetry mod are available:

    * Docked
    * Undocked
    * UnderAttack
    * ReceiveText
    * Heatwarning

    Plus a bunch of fixes: github.com/bekopharm/x4-simpit

    #homeCockpit #SimPit #SpacePewPew

  34. 🤓 🚨

    Finally updated #x4simpit with changes that were rotting on my disk for months now. The following new events for my #x4foundations ship telemetry mod are available:

    * Docked
    * Undocked
    * UnderAttack
    * ReceiveText
    * Heatwarning

    Plus a bunch of fixes: github.com/bekopharm/x4-simpit

    #homeCockpit #SimPit #SpacePewPew

  35. 🤓 🚨

    Finally updated #x4simpit with changes that were rotting on my disk for months now. The following new events for my #x4foundations ship telemetry mod are available:

    * Docked
    * Undocked
    * UnderAttack
    * ReceiveText
    * Heatwarning

    Plus a bunch of fixes: github.com/bekopharm/x4-simpit

    #homeCockpit #SimPit #SpacePewPew

  36. 🔖 https://www.digitaljoshua.com/modular-flight-simulator-panels-and-button-boxes/

    Not often I’m mind blown by what some people come up with to scratch their itch. Swapping panels easily thanks to cable management kits is a great and cheap idea.

    https://beko.famkos.net/2025/06/11/15629845/

    #flightsim #homeCockpit #simpit

  37. 🔖 https://www.digitaljoshua.com/modular-flight-simulator-panels-and-button-boxes/

    Not often I’m mind blown by what some people come up with to scratch their itch. Swapping panels easily thanks to cable management kits is a great and cheap idea.

    https://beko.famkos.net/2025/06/11/15629845/

    #flightsim #homeCockpit #simpit

  38. 🔖 https://www.digitaljoshua.com/modular-flight-simulator-panels-and-button-boxes/

    Not often I’m mind blown by what some people come up with to scratch their itch. Swapping panels easily thanks to cable management kits is a great and cheap idea.

    https://beko.famkos.net/2025/06/11/15629845/

    #flightsim #homeCockpit #simpit

  39. 🔖 https://www.digitaljoshua.com/modular-flight-simulator-panels-and-button-boxes/

    Not often I’m mind blown by what some people come up with to scratch their itch. Swapping panels easily thanks to cable management kits is a great and cheap idea.

    https://beko.famkos.net/2025/06/11/15629845/

    #flightsim #homeCockpit #simpit

  40. Project introduction Short: DIY #Macross inspired #SimPit in the making for more immersive #Space Pew Pew #Gaming

    ⚠️ Loud

    Music CC BY 4.0 "Piledriver"
    by Jason Shaw on audionautix.com/

    Project website on SimPit.dev

  41. Project introduction Short: DIY #Macross inspired #SimPit in the making for more immersive #Space Pew Pew #Gaming

    ⚠️ Loud

    Music CC BY 4.0 "Piledriver"
    by Jason Shaw on audionautix.com/

    Project website on SimPit.dev