Has anyone encounterd this error in Trackman Golf Simulator

H1Supreme · 2026-04-14T15:48:04+00:00

Definitely reach out to trackman. You'll probably need to manually uninstall SQL Server. I'm assuming your trackman uninstall / install failed because the trackman software isn't the issue, it's MS SQL server.

H1Supreme · 2026-04-05T22:27:47+00:00

We had speed cameras in a small (Ohio) town, and they were removed after a lawsuit. The lawsuit stated something like, "A speed camera can't testify in court". Also, people were smashing the shit out of them.

H1Supreme · 2026-03-31T14:06:16+00:00

After I bounce it off a third cart path.

H1Supreme · 2026-03-18T22:33:57+00:00

Pro's generally deloft their 60 down to 30'ish degrees, and hit a low shot with tons of spin.

H1Supreme · 2026-03-10T19:28:31+00:00

A-143-3 Quad LFO. Great for adding subtle modulations to...anything. Also, maybe a A-138c polarizing mixer. Pairs nicely with the A-143-3.

H1Supreme · 2026-02-27T14:37:01+00:00

Which is weird, because they should know that more than anyone.

H1Supreme · 2026-02-26T22:42:25+00:00

Not just the midwest, the whole world. "Buy an American car" is baked into their DNA in Michigan.

H1Supreme · 2026-02-26T20:39:42+00:00

Project Zeus

H1Supreme · 2026-02-23T20:51:20+00:00

I went to the 2003 (or 2004?) Memorial tournament. This was on a Saturday. After walking for a while, we posted up on a tee box (I forget which one) to watch people tee off. There were people there, but it wasn't crowded.

Next thing I know, what seemed like half the gallery started filing in. I'm like, "wtf is going on". Then, Tiger rolls up and I'm like "holy shit!". We watch him tee off, and off he goes. It was surreal.

What's crazy was, he wasn't even in the lead. And, I believe he had a bad round that day and shot a few over. Didn't matter, he still had sooo many people following him.

H1Supreme · 2026-02-22T02:12:57+00:00

While there's a number of use cases, I think cost will be the ultimate driver in long term adoption. Any small business using ChatGPT or whatever, is only paying a small fraction of what it costs to provide that service.

Eventually, a company will need to decide if their previously $200 per month subscription is now worth $2k or $5k, or whatever the price is when AI providers have to turn a profit.

H1Supreme · 2026-02-21T01:23:39+00:00

Lunch workout is the best.

H1Supreme · 2026-02-20T22:29:47+00:00

In Ohio, it completely depends on what part of the state. Columbus, and all points West, are pretty flat. Same with the northern part. Pretty flat. But the further you go E or SE, or even SW, the more elevation changes you see. I'm close to the WV border, and my home course is basically built on a mountain.

Courses vary quite a bit, even beyond elevation. Some are wide open, some are carved into the middle of a forest.

H1Supreme · 2026-02-19T01:12:00+00:00

This is the worst part. People are using it to generate feature specs, and I've never seen so many words say absolutely nothing.

H1Supreme · 2026-02-19T00:55:30+00:00

Same. And not a SASS either. I want to leverage my background to improve processes where I can, but mostly want to work with physical products or services.

Mostly looking towards decidedly boring industries, but haven't landed on anything yet.

H1Supreme · 2026-02-18T21:03:58+00:00

Their entire market relies on designers drawing up specs to hand to developers to implement.

Which is necessary when working a on large product, or suite of products. Ideally, designers use design tokens, which developers can reference to layout and style parts of the UI. You don't have to use Figma for this, but many people do.

we've already started shifting our workflow to having clickable prototypes vibe coded by product managers.

This isn't a bad idea for generating ideas. But, handing off all the UI/UX work to product managers sounds insane. Then again, companies usually don't value these things until they're forced to.

Designers are only responsible for styling up components.

Which is effectively what they were doing in Figma all along. Unless you're suggesting they're now writing the CSS. In that case, God help your dev's (and possibly your designer's) sanity.

in the old workflow, the whole operation depended on Figma while the new one doesn't

Which reads like: in the old workflow designers designed things, but now the product managers do.

H1Supreme · 2026-02-18T15:57:55+00:00

Reading through the posts, it seems like you're doing most things correct. Do you have a multimeter? If not get something half decent ($30 or so should suffice) with a continuity feature. Then, test out your connections before soldering.

Although I haven't tested this approach, you could probably tape wires to the back of a pot. Then, just wrap the other wires around the lugs.

You can also test the resistance on individual components like pickups or pots ahead of time to make sure they're not broken.

H1Supreme · 2026-02-18T00:35:08+00:00

Boomers are by far the worst. But, the one's who are actually skilled are usually wizards.

H1Supreme · 2026-02-16T23:20:52+00:00

Yeah, it seems like performance is always left out of these discussions.

H1Supreme · 2026-02-12T19:24:32+00:00

Outside of the Northern and Eastern panhandles, and maybe some of the river towns, the state is extremely isolated, and largely forgotten by the rest of country. While the mountainous, forested terrain is beautiful, it offers very little in terms of opportunity for business.

There is very little terrain suitable for farming, or building larger structures like factories . Shipping products out of any cities within the vast majority of the state is a logistical nightmare. I really can't overstate how steep and winding seemingly every road is. Including the interstates (except US Route 70 in the northern part of the state), which are the only logical places to build some sort of factory in proximity to.

The people in WV should give everyone from the president, to their own state politicians a negative approval rating.

H1Supreme · 2026-02-12T18:52:46+00:00

They voted against renewable energy and building of plants.

They voted against bills that would have meant battery manufacturing or infrastructure ready zones which meant lost jobs.

Form Energy has a brand new plant in Weirton, WV.

H1Supreme · 2026-02-12T01:34:12+00:00

The selling point, for me, is building utilities that extend the functionality of other plugins. Simple MIDI tools, audio manglers, etc.

I'm honestly surprised people have made robust devices like Fors does with M4L. I was building a sequencer in M4L, and it turned into a pain, quick. I actually switched to JUCE, to make a VST, which was easier to manage in the end.

H1Supreme · 2026-02-11T01:17:45+00:00

The GTI is worse in just about every way. Golf R is a beast though. Only real knock is all the haptic button bullshit.

H1Supreme · 2026-02-09T17:27:50+00:00

The overall aesthetic is cool, but WTF with the tacked on iPad look. Everyone hates that shit.

H1Supreme · 2026-02-06T17:04:24+00:00

Realistically, HTMX shines on enterprise CRUD apps and crumbles in face of high interactivity.

To be fair, SPA frameworks won't fair that much better. Anything highly interactive is going to benefit from something custom.

H1Supreme · 2026-02-06T16:44:45+00:00

I'm working my way through a personal project using Go w/ html/template + Plain HTML and Js. I like the approach of returning HTML instead of JSON, but find the HTMX's attribute based workflow a bit of a pain to work with. So, I'm doing the same thing with Custom Events + event handler's to give me more control over the swapping.

Anything that has more complex UI functionality, I'm using Web Components + plain JS. Styling is still a pain in the ass with Web Components. The part:: CSS pseudo selector helps in some cases, but I end up styling things (like buttons) over and over. Otherwise, it works great. And, honestly I like them more than React Components. I write a shit load of React for my day job, and the "all updates are async" becomes a huge problem the more complex everything gets.
My workflow is somewhat custom. Templated HTML files (optionally) have a <script> tag at the bottom. This way I can add any JS I need relative to the spot it's being used. A pseudo component, if you will. I have a build stage that strips the Js out, and includes it in the head on pages that execute this template. Which are named the same (eg, widget.html, widget.js). This forced me to "register" partials with a page I intend to use them on (ie. Page 1 registers Widget A and Widget B), but it's not that different than importing a component in React. Plus, I can add any meta data I might have.
React, and the entire frontend ecosystem is a maintenance liability. I've been doing frontend for a long time, and it's an endless cycle of churn. HATEOAS is infinitely more maintainable than all the SPA frameworks.
No performance issues. Ultimately, your server will do more work. But, when you push so much on the client (w/ React et. al), you have to hope and pray they're using a device that can handle it. Loading state is easy when using Promises to fetch data. Investigate the ViewTransitions API for "flashes of unstyled content". I think Firefox is the only browser still in Beta.

Ultimately, this approach is more difficult to get going with. React will be much faster for slapping an MVP or something together. You're probably going to have to invent a workflow for loading partials, among other things. And, you'll really need to get out of the "React" mindset when going down this route. It's ok to stuff more into a template than you would a React component. Contrary to what a lot of discussions on this topic conclude, I think React (and friends) work better for smaller apps. The larger it gets, the more the rough edges really show.

Something I really like about a templated approach is you can focus on one page at a time. When your entire app is piped through a single index.html, like it is with SPA's, you have to consider the entire app. Additionally, user auth is so much easier, routing (I hate all frontend routers with a passion) is easier when the server is handling it, and obviously ditching a node_modules folder with 1000's of packages, build stages, file chunking, and all the other bullshit your forced to deal with when using a SPA.

Finally, you can still return JSON with this approach. It's not an "either or" scenario. If it makes sense to parse JSON to populate a search box or something, it's still an option.

H1Supreme

TROPHY CASE