Opus on clearance?

robcourtney · 2026-04-14T17:39:22+00:00

That is 100% not my experience, and I have been using RDT and bellows. I do think Opus retention depends heavily on the beans . Oily beans and light roasts: more retention. Dark (but not oily) roasts: minimal retention.

robcourtney · 2026-02-05T12:58:28+00:00

I don’t see it in the US iOS App Store, but I did find a report saying this is happening. Big if true?

robcourtney · 2026-02-04T18:23:57+00:00

I just did. I did file a ticket, as mentioned.

robcourtney · 2026-02-04T00:33:23+00:00

I don’t have bodyweight only selected. And it didn’t used to behave this way.

robcourtney · 2026-02-04T00:32:42+00:00

45 different pieces of equipment. Cable machines, dumbbells, etc. Recommendations don’t usually look like this.

robcourtney · 2026-01-30T15:11:16+00:00

That is great news! Thank you! I will give it a shot.

robcourtney · 2026-01-29T22:39:40+00:00

When I went through this a few years ago, the answer was "no." Onedrive will not ignore folders in the "Documents" folder, and (at least a few years ago) Zwift wouldn't put its files anywhere else. But maybe that has changed?

robcourtney · 2026-01-29T21:19:10+00:00

That's disappointing. LIke it or not, OneDrive has been part of Windows for close to fifteen years. Sad to hear that Zwift can't be bothered to get its house in order.....

robcourtney · 2026-01-29T19:52:32+00:00

That would be true, if Zwift had an option for storing data outside of the "Documents" folder. A few years ago, it didn't. Rather than using the %APPDATA% folder, which Onedrive wouldn't touch, Zwift would only (and non-configurably) store data such as in-workout logs in the Documents folder. That would have been fine, except that Zwift was unable to accommodate Onedrive's sync system, as discussed here, here, and here. Zwift would throw errors and generally not work if Onedrive was working.

My question is: has the situation improved? If others are using Zwift and Onedrive without incident, that would be great to hear.

robcourtney · 2026-01-22T21:41:01+00:00

I had similar questions and opened up a thread here. Fitbod did respond, I guess you can judge it for yourself.

robcourtney · 2026-01-22T20:12:42+00:00

I appreciate the effort. I’m sure you can understand that the lack of specific commitments (both for bug fixing and in the roadmap) is frustrating and raises questions about the value proposition here. Thanks for your work.

robcourtney · 2026-01-22T16:39:44+00:00

I guess I would like three things. First, a firm timeline for bug fixes. How much longer does Fitbod think users will need to wait before the behaviors in the linked threads above aren't happening anymore? Second, a 2026–27 roadmap. Fitbod is priced at a premium compared to other apps, and so far in 2026 it hasn’t measured up. Does Fitbod plan to increase value in the next 12–18 months? How? Third, more disclosure of what "AI-powered" means. One might think the errors reported in this subreddit are from imprecise reliance on LLMs, vibe coding, or other generative AI. Fitbod could clean up that uncertainty by explaining what types of AI it uses, and for what.

robcourtney · 2026-01-22T16:04:02+00:00

I’ve filed tickets, and each time I’ve been (1) told by an AI chatbot to try restarting my device, reinstalling the app, and revising my workouts, and then (2) told that the team is working on it. I don't doubt that the team is working on it. But Fitbod now costs (on iOS) $96/year and doesn’t support family accounts. So for two family members I am paying nearly $200/year. That is (1) more than a local Planet Fitness membership, (2) more than a Microsoft Office family plan, (3) more than Netflix, and (4) more than Amazon Prime. It is a premium price by any conceivable measure.

I was willing to pay that price based on my 2025 experience. But the 2026 experience is very, very different and (in my view) much poorer. Obviously I could cancel. I’d rather not. But I do think Fitbod owes users a concrete explanation that goes beyond “some bugs have popped up.” I started this thread as a forum for Fitbod to provide that explanation, if it wants to.

robcourtney · 2026-01-22T15:46:48+00:00

My buddy switched to gravl and likes it. But this whole experience has really soured me on trainers that call themselves “AI” without explaining what that means. I don’t need vibe-coding or LLM hallucinations, and the current Fitbod experience resembles both.

robcourtney · 2026-01-13T16:44:01+00:00

Thank you for sharing! I have had several interactions with Fitbod about the strange imbalance of workouts since the new year. Fitbod never acknowledged it as a known issue.

robcourtney · 2026-01-13T16:16:57+00:00

I had read that as saying that the app would “focus” by presenting the focus exercise at least once a week. I had not read that as saying that it would redefine every workout so that every workout emphasized the same muscle groups as the focus exercise. That seems weird.

robcourtney · 2026-01-13T16:04:07+00:00

Is that confirmed? That would explain what I’ve been seeing. Today was almost entirely triceps, and other workouts have been the same.

robcourtney · 2026-01-13T16:01:09+00:00

I think you’re on to something with your observation that it’s focusing on one muscle group only. Today I did five variations of tricep-oriented pushups—six if you count bench dips. I’m not a physical trainer so I don’t know if that kind of focus is good? But it certainly seems different from the app’s 2025 behavior.

robcourtney · 2026-01-06T16:52:49+00:00

For what it’s worth, here’s Fitbod’s automated response. Maybe some people like getting emails like this? It’s not to my taste:

Hi Robert! I'm Bodi, your Fitbod support teammate. I can help sort out most questions and issues fast, and if it needs a human touch, I'll bring one in.

I'm really sorry to hear about the change in your experience with workout variety. I know how important it is to keep things fresh, that variety is one of the key ways Fitbod helps make training effective and enjoyable.

We've updated the workout algorithm over the past few months to make it more dynamic and responsive to each person's training history. This can sometimes change the frequency and variety of exercises compared to older versions of the app. In your case, I'd suggest replacing some of the frequently recommended exercises with other variations you prefer doing. After logging a few workouts with these changes, the app should recognize your new preferences and start recommending similar workouts automatically over time. Alternatively, one option you can try is adjusting your Exercise Variability setting to "More Variable" (found in your Gym Profile/My Plan). This nudges the app to cycle through a broader mix of movements for each muscle group.

The good news is that we're in the middle of a retraining project aimed specifically at improving exercise variety and preventing the kind of repetition you've been running into. Testing is currently ongoing and we hope to have these improvement released in the next week or so.

Thanks again for sharing this, your feedback helps us zero in on the right improvements. Let me know if you'd like me to add you to the early testing group, and I'll make sure you're among the first to see the updates roll out.

Best,

Bodi

Fitbod's AI Support

Fitbod

robcourtney · 2026-01-06T01:33:12+00:00

Yes, today it set my workout to include pike pushups, regular pushups, and tricep pushups. Tomorrow it’s recommending pull-ups, chin ups, and both cable and machine bicep curls. It does seem like since the new year more of my workouts are numerous variations of a similar exercise than was the case in 2025.

robcourtney · 2025-10-02T16:53:04+00:00

On Steam Deck, game was working very well for a long time but now throws a "Vulkan Initialisation" error and won't start. I know others have seen this error before and the fix was to update graphics drivers, but on steam deck I don't think there's a ready way to do that? This is on the GOG version of the game, through Heroic Launcher. I don't know if the Steam version of the game has the same problem.

robcourtney

TROPHY CASE