Hempstead

Hempstick 2.0 delay, sort of, not really.... https://blog.hempstick.org/2025/10/hempstick-20-delay-sort-of.html

The whole point is that by declaring the pre-condition of one switch box, you have to turn to a hackish solution, like every time you want to play different game, you have to re-flash your controller board, and bring headache. Why in the hell do you do that to yourself? Consider stepping back, and re-evaluate your "pre-conditions" and "assumptions" and you might just find the solution space suddenly broaden. Then, you can evaluate whether the gained new solutions is worth giving up the pre-conditions, or keeping them. For instance, what about one switch box per one controller, and each for different aircraft. Then, you never have to re-flash them ever. You just plug in different switch box and you are good to go. It's not like one switch box is ever going to ever there is. You are going to want more, if that one switch box works well. Might as well release yourself from the mental confine from the start.

Why don't you build multiple "switch boxes" and just switch the switch box?

I, on the other hand, from day one of release, have almost never lost track of position. At the beginning when it booted up Quest pro, it takes a bit to get the controllers to sync positions. But once they are in sync, I almost never lose position. However, recently, Meta has gotten really really aggressive in "power saving" so if you idle the controller for like 3 seconds, it sleeps. It takes about a second to wake it up. And there is no option to adjust how aggressive Zuck is. No wonder he and Musk wanted to meet in a Vegas ring. *sigh* What I would suggest is that since the pro controller runs SLAM using two cameras, you really want your env to be bright enough for it to work. They ain't IR cameras. For instance, if you have a pit or a desk... and your joystick/throttle is down below the desk top level... what the camera see could be darker than you are aware of.

Just some clever 3D printed clamps for the 8020 rails. https://blog.hempstick.org/2025/10/clever-little-3d-printed-clamps-for.html

The next generation Hempstick (electronics/software) prototype. https://blog.hempstick.org/2025/09/the-next-generation-hempstick-prototype.html

They fit. https://blog.hempstick.org/2025/09/ha-they-fit.html

7" Touch screen on the right Aux Console. https://blog.hempstick.org/2025/09/ubuntu-touch-screen-on-aux-console.html

Hempstick breakthrough https://blog.hempstick.org/2025/08/hempstick-breakthrough.html

A 9800X3D is selling on Amazon for USD $449, i.e. $74 dollars more than a 7800X3D. At that price diff, why would you go for the last gen Zen 4 as opposed to Zen 5 stuff? For a €3128.20 machine... adding USD$74 shouldn't be a problem, right?

Ah... I see it. Thanks! So, it's www.digitalcombatsimulator.com/Downloads need to have the file updated.

I am not seeing the document updated. It's still "DCS: F-16 Early Access Guide" dated Dec. 29, 2024 on the DCS web site. Can't seem to find the updated doc with sniper pod.

I have a static IP# assigned to my GamingPC2. And, my egress point IP# is also a static IP# (I pay quite a bit money for it monthly). So, no, there is no IP# change. And this has happened quite a bit before, like when I was in the mission editor, or browsing through my custom mission trying to decide which mission to play, or in Setting pages configuring my settings. It just kicked me out, claiming login expired. The only thing I can think of is DNS server glitch. Say, it tries to contact digitalcombatsimulator.com/.... to validate, but the DNS name could not be resolved for whatever reason... But that is very unlikely too, because once I got kicked out, login in a few seconds works fine means that is not likely to be the cause.

dcs.log.oldThat was the wrong log file... This is the correct one that it kicked me out. 2025-07-03 19:00:30.957 ERROR ASYNCNET (34508): The session has expired (401). Exiting...

dcs.log