#simpit — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #simpit, aggregated by home.social.
-
Thrustmaster rudder pedal repairI 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 -
Thrustmaster rudder pedal repairI 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 -
Thrustmaster rudder pedal repairI 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 -
Thrustmaster rudder pedal repairI 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 -
Thrustmaster rudder pedal repairI 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 -
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 https://matrix.to/#/#hotasdiy:matrix.org channel.
Edit: Getting somewhere: https://matrix.to/#/#aerospace-space:hacklab.fi
Moving my 🤓 Discord space here https://matrix.to/#/#bekomotion:matrix.org 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
♻️ 🙏
-
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 https://matrix.to/#/#hotasdiy:matrix.org channel.
Edit: Getting somewhere: https://matrix.to/#/#aerospace-space:hacklab.fi
Moving my 🤓 Discord space here https://matrix.to/#/#bekomotion:matrix.org 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
♻️ 🙏
-
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 https://matrix.to/#/#hotasdiy:matrix.org channel.
Edit: Getting somewhere: https://matrix.to/#/#aerospace-space:hacklab.fi
Moving my 🤓 Discord space here https://matrix.to/#/#bekomotion:matrix.org 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
♻️ 🙏
-
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 https://matrix.to/#/#hotasdiy:matrix.org channel.
Edit: Getting somewhere: https://matrix.to/#/#aerospace-space:hacklab.fi
Moving my 🤓 Discord space here https://matrix.to/#/#bekomotion:matrix.org 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
♻️ 🙏
-
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 https://matrix.to/#/#hotasdiy:matrix.org channel.
Edit: Getting somewhere: https://matrix.to/#/#aerospace-space:hacklab.fi
Moving my 🤓 Discord space here https://matrix.to/#/#bekomotion:matrix.org 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
♻️ 🙏
-
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-1inspired 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, a17.3"with a resolution of1920x1080. The touch controller registeres as a USBHIDpointer/mouse byILITEKand is basically sitting on top of the display. The kit included aPCB, that was advertised asVS-RTD2556HC-V2controller byVSDISPLAYbut came without any data sheet and I have no idea who really made this.Thing is this
PCBruns very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use anUSB PDpower supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised butVSDISPLAYdoes 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 strictly5V/12Vso that matches the picture I get.Mine is equipped with the IC
RTD2556VDthat does not match the list of supported ICs. Theirs has2556TE_R20.1printed on thePCB. Mine has2555TF_R30.1printed on. It’s like 99% similar but differently routed. It also mentionsE470791 JPX-Dwhich seems to point to thePCBmanufacturerDongguan Jingweixin Circuit Co Ltdbut 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
5Vat~2AI feel way more comfortable with12Vat~0.8Aon 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 ALTproviding more than5Vand thePCBwill always switch down to5Vthe moment theUSB-Cdedicated for the display signal is used as well, even when a properUSB PDpower supply is attached on it’s dedicated power connector. I could only keep it at12Vwith myVITUREUSB-CXRcharging adapter, which can indeed provide12Vand more viaUSB-Cwhile still allowingDP-ALT+USB2. There went my plans to only have a single cable for all,DP,PDand theUSB2lanes for theILITEKpointer, because I really do not want to block this adapter all the time.So now I have a dedicaded
USB PDpower supply at12Vconnected, aHDMIconnection for the display and an additionalUSB2for the touchpanel pointer – and on top of that the little fan, that I simply connected to the microUSB2socket on thePCBto provide it with5V.This also means that my
Linux PCcan 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. ApparentlyKDEhas an option in it’s graphical settings where this can be easily configured.Gnomedoes not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel inGnometoo! 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.xmlafter 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 ID222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input withgsettingsto 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
HDRenabled. 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
HUDapp, of course 🙃This content is licensed under a Creative Commons Attribution 4.0 International license.
#flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit
-
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-1inspired 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, a17.3"with a resolution of1920x1080. The touch controller registeres as a USBHIDpointer/mouse byILITEKand is basically sitting on top of the display. The kit included aPCB, that was advertised asVS-RTD2556HC-V2controller byVSDISPLAYbut came without any data sheet and I have no idea who really made this.Thing is this
PCBruns very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use anUSB PDpower supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised butVSDISPLAYdoes 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 strictly5V/12Vso that matches the picture I get.Mine is equipped with the IC
RTD2556VDthat does not match the list of supported ICs. Theirs has2556TE_R20.1printed on thePCB. Mine has2555TF_R30.1printed on. It’s like 99% similar but differently routed. It also mentionsE470791 JPX-Dwhich seems to point to thePCBmanufacturerDongguan Jingweixin Circuit Co Ltdbut 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
5Vat~2AI feel way more comfortable with12Vat~0.8Aon 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 ALTproviding more than5Vand thePCBwill always switch down to5Vthe moment theUSB-Cdedicated for the display signal is used as well, even when a properUSB PDpower supply is attached on it’s dedicated power connector. I could only keep it at12Vwith myVITUREUSB-CXRcharging adapter, which can indeed provide12Vand more viaUSB-Cwhile still allowingDP-ALT+USB2. There went my plans to only have a single cable for all,DP,PDand theUSB2lanes for theILITEKpointer, because I really do not want to block this adapter all the time.So now I have a dedicaded
USB PDpower supply at12Vconnected, aHDMIconnection for the display and an additionalUSB2for the touchpanel pointer – and on top of that the little fan, that I simply connected to the microUSB2socket on thePCBto provide it with5V.This also means that my
Linux PCcan 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. ApparentlyKDEhas an option in it’s graphical settings where this can be easily configured.Gnomedoes not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel inGnometoo! 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.xmlafter 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 ID222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input withgsettingsto 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
HDRenabled. 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
HUDapp, of course 🙃This content is licensed under a Creative Commons Attribution 4.0 International license.
#flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit
-
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-1inspired 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, a17.3"with a resolution of1920x1080. The touch controller registeres as a USBHIDpointer/mouse byILITEKand is basically sitting on top of the display. The kit included aPCB, that was advertised asVS-RTD2556HC-V2controller byVSDISPLAYbut came without any data sheet and I have no idea who really made this.Thing is this
PCBruns very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use anUSB PDpower supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised butVSDISPLAYdoes 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 strictly5V/12Vso that matches the picture I get.Mine is equipped with the IC
RTD2556VDthat does not match the list of supported ICs. Theirs has2556TE_R20.1printed on thePCB. Mine has2555TF_R30.1printed on. It’s like 99% similar but differently routed. It also mentionsE470791 JPX-Dwhich seems to point to thePCBmanufacturerDongguan Jingweixin Circuit Co Ltdbut 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
5Vat~2AI feel way more comfortable with12Vat~0.8Aon 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 ALTproviding more than5Vand thePCBwill always switch down to5Vthe moment theUSB-Cdedicated for the display signal is used as well, even when a properUSB PDpower supply is attached on it’s dedicated power connector. I could only keep it at12Vwith myVITUREUSB-CXRcharging adapter, which can indeed provide12Vand more viaUSB-Cwhile still allowingDP-ALT+USB2. There went my plans to only have a single cable for all,DP,PDand theUSB2lanes for theILITEKpointer, because I really do not want to block this adapter all the time.So now I have a dedicaded
USB PDpower supply at12Vconnected, aHDMIconnection for the display and an additionalUSB2for the touchpanel pointer – and on top of that the little fan, that I simply connected to the microUSB2socket on thePCBto provide it with5V.This also means that my
Linux PCcan 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. ApparentlyKDEhas an option in it’s graphical settings where this can be easily configured.Gnomedoes not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel inGnometoo! 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.xmlafter 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 ID222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input withgsettingsto 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
HDRenabled. 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
HUDapp, of course 🙃This content is licensed under a Creative Commons Attribution 4.0 International license.
#flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit
-
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-1inspired 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, a17.3"with a resolution of1920x1080. The touch controller registeres as a USBHIDpointer/mouse byILITEKand is basically sitting on top of the display. The kit included aPCB, that was advertised asVS-RTD2556HC-V2controller byVSDISPLAYbut came without any data sheet and I have no idea who really made this.Thing is this
PCBruns very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use anUSB PDpower supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised butVSDISPLAYdoes 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 strictly5V/12Vso that matches the picture I get.Mine is equipped with the IC
RTD2556VDthat does not match the list of supported ICs. Theirs has2556TE_R20.1printed on thePCB. Mine has2555TF_R30.1printed on. It’s like 99% similar but differently routed. It also mentionsE470791 JPX-Dwhich seems to point to thePCBmanufacturerDongguan Jingweixin Circuit Co Ltdbut 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
5Vat~2AI feel way more comfortable with12Vat~0.8Aon 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 ALTproviding more than5Vand thePCBwill always switch down to5Vthe moment theUSB-Cdedicated for the display signal is used as well, even when a properUSB PDpower supply is attached on it’s dedicated power connector. I could only keep it at12Vwith myVITUREUSB-CXRcharging adapter, which can indeed provide12Vand more viaUSB-Cwhile still allowingDP-ALT+USB2. There went my plans to only have a single cable for all,DP,PDand theUSB2lanes for theILITEKpointer, because I really do not want to block this adapter all the time.So now I have a dedicaded
USB PDpower supply at12Vconnected, aHDMIconnection for the display and an additionalUSB2for the touchpanel pointer – and on top of that the little fan, that I simply connected to the microUSB2socket on thePCBto provide it with5V.This also means that my
Linux PCcan 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. ApparentlyKDEhas an option in it’s graphical settings where this can be easily configured.Gnomedoes not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel inGnometoo! 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.xmlafter 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 ID222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input withgsettingsto 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
HDRenabled. 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
HUDapp, of course 🙃This content is licensed under a Creative Commons Attribution 4.0 International license.
#flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit
-
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-1inspired 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, a17.3"with a resolution of1920x1080. The touch controller registeres as a USBHIDpointer/mouse byILITEKand is basically sitting on top of the display. The kit included aPCB, that was advertised asVS-RTD2556HC-V2controller byVSDISPLAYbut came without any data sheet and I have no idea who really made this.Thing is this
PCBruns very hot and the noted input voltage isn’t explicitly stated. An attached image suggested to use anUSB PDpower supply without 20V so I was looking for it’s datasheet to check if I was just holding it wrong. Picture me surprised butVSDISPLAYdoes 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 strictly5V/12Vso that matches the picture I get.Mine is equipped with the IC
RTD2556VDthat does not match the list of supported ICs. Theirs has2556TE_R20.1printed on thePCB. Mine has2555TF_R30.1printed on. It’s like 99% similar but differently routed. It also mentionsE470791 JPX-Dwhich seems to point to thePCBmanufacturerDongguan Jingweixin Circuit Co Ltdbut 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
5Vat~2AI feel way more comfortable with12Vat~0.8Aon 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 ALTproviding more than5Vand thePCBwill always switch down to5Vthe moment theUSB-Cdedicated for the display signal is used as well, even when a properUSB PDpower supply is attached on it’s dedicated power connector. I could only keep it at12Vwith myVITUREUSB-CXRcharging adapter, which can indeed provide12Vand more viaUSB-Cwhile still allowingDP-ALT+USB2. There went my plans to only have a single cable for all,DP,PDand theUSB2lanes for theILITEKpointer, because I really do not want to block this adapter all the time.So now I have a dedicaded
USB PDpower supply at12Vconnected, aHDMIconnection for the display and an additionalUSB2for the touchpanel pointer – and on top of that the little fan, that I simply connected to the microUSB2socket on thePCBto provide it with5V.This also means that my
Linux PCcan 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. ApparentlyKDEhas an option in it’s graphical settings where this can be easily configured.Gnomedoes not [yet?] have such an option in it’s graphical settings. There is however a way to enforce the mapping of the touch panel inGnometoo! 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.xmlafter 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 ID222a:0001 ILI Technology Corp. Multi-Touch Screen. Armed with that knowledge I can limit it’s input withgsettingsto 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
HDRenabled. 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
HUDapp, of course 🙃This content is licensed under a Creative Commons Attribution 4.0 International license.
#flightsim #gamingonlinux #gnome #homeCockpit #linux #linuxgaming #simpit
-
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.
#AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1
-
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.
#AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1
-
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.
#AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1
-
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.
#AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1
-
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.
#AceCombat #AceCombat7 #arwes #flightsim #gaming #gamingonlinux #homeCockpit #linuxgaming #macross #Robotech #simpit #SpacePewPew #UE4SS #VF1
-
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!
-
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!
-
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!
-
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!
-
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!
-
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.
-
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.
-
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.
-
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.
-
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.
-
Playing some Ace Combat 7 - probably
Playing some Ace Combat 7 - probably
#LinuxGaming #GamingOnLinux #SimPit #Linux #EliteDangerous #EliteDangerousOdyssey #StarCitizen #PewPew #ViperPit #X4Foundations #Macross #VF1 #tech #videogames #XWing #TieFighter #Arduino #Mega #HomeCockpit
-
Playing some Ace Combat 7 - probably
Playing some Ace Combat 7 - probably
#LinuxGaming #GamingOnLinux #SimPit #Linux #EliteDangerous #EliteDangerousOdyssey #StarCitizen #PewPew #ViperPit #X4Foundations #Macross #VF1 #tech #videogames #XWing #TieFighter #Arduino #Mega #HomeCockpit
-
Short morning stream
Just testing codecs - not really streaming
#LinuxGaming #GamingOnLinux #SimPit #Linux #EliteDangerous #EliteDangerousOdyssey #StarCitizen #PewPew #ViperPit #X4Foundations #Macross #VF1 #tech #videogames #XWing #TieFighter #Arduino #Mega #HomeCockpit
-
Short morning stream
Just testing codecs - not really streaming
#LinuxGaming #GamingOnLinux #SimPit #Linux #EliteDangerous #EliteDangerousOdyssey #StarCitizen #PewPew #ViperPit #X4Foundations #Macross #VF1 #tech #videogames #XWing #TieFighter #Arduino #Mega #HomeCockpit
-
New monitor replacing my triple head setup. Banana for scale. The immersion is insane.
Brief demo in action: https://makertube.net/w/fb6fsA5PtJiFbBTxbMk67X
#Gaming #LinuxGaming #GamingOnLinux #EliteDangerous #SimPit #HomeCockpit
-
New monitor replacing my triple head setup. Banana for scale. The immersion is insane.
Brief demo in action: https://makertube.net/w/fb6fsA5PtJiFbBTxbMk67X
#Gaming #LinuxGaming #GamingOnLinux #EliteDangerous #SimPit #HomeCockpit
-
New monitor replacing my triple head setup. Banana for scale. The immersion is insane.
Brief demo in action: https://makertube.net/w/fb6fsA5PtJiFbBTxbMk67X
#Gaming #LinuxGaming #GamingOnLinux #EliteDangerous #SimPit #HomeCockpit
-
New monitor replacing my triple head setup. Banana for scale. The immersion is insane.
Brief demo in action: https://makertube.net/w/fb6fsA5PtJiFbBTxbMk67X
#Gaming #LinuxGaming #GamingOnLinux #EliteDangerous #SimPit #HomeCockpit
-
New monitor replacing my triple head setup. Banana for scale. The immersion is insane.
Brief demo in action: https://makertube.net/w/fb6fsA5PtJiFbBTxbMk67X
#Gaming #LinuxGaming #GamingOnLinux #EliteDangerous #SimPit #HomeCockpit
-
🤓 🚨
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
* HeatwarningPlus a bunch of fixes: https://github.com/bekopharm/x4-simpit
-
🤓 🚨
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
* HeatwarningPlus a bunch of fixes: https://github.com/bekopharm/x4-simpit
-
🤓 🚨
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
* HeatwarningPlus a bunch of fixes: https://github.com/bekopharm/x4-simpit
-
🤓 🚨
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
* HeatwarningPlus a bunch of fixes: https://github.com/bekopharm/x4-simpit
-
🤓 🚨
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
* HeatwarningPlus a bunch of fixes: https://github.com/bekopharm/x4-simpit
-
🔖 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://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://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://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.
-
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 https://audionautix.com/Project website on https://SimPit.dev
-
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 https://audionautix.com/Project website on https://SimPit.dev