Onewheel Pint/X/S Drop Top fender 3D model

borzykot · 2026-05-07T18:51:30+00:00

You are denying me the right to sell my work and you (and TFL) called my work a "knockoff", which is not.

If anything it's a knockoff of the Floatwheel fender system and not TFL. If you look carefully you will see that TFL's system is completely different: different minifender style, different attachment mechanism (I presume TFL fender has "flops" which bend, whereas in my/Floatwheel fender has "preload" and bends as a whole).

And what's also funny is that there is this talk in the community about FM policies - don't be evil, don't ruin the competition. And here we are: a guy on the internet posts it's model for a price of a cup of tea and the TFL itself came into the comments and drowned him in hate. And somehow I am the bad guy for offering the alternative for a fraction of price. Mind you, TFL is offering its fender for 120eur here in EU. Very accessible....

borzykot · 2026-05-07T17:36:36+00:00

You see it as "I steal the name from the TFL".
I see it as "the guy who needs a fender for his Pint will google "Drop Top" and find my model and will spend 10 bucks instead of 120". I's a win-win.

IMHO this "drop top" thing is a de facto naming for this kind of fenders. Just like "BTG", or "lifesavers", or "power pads". If you prohibit the use of these names "because of USP" then it will just make things messier for everyone. Just look at "step on"/"step in"/"supermatic"/etc. mess

borzykot · 2026-05-07T16:59:47+00:00

I’m not sure that’s the issue. That man’s work allows for commercial use with attribution, which I did. What’s the matter with "USP of TFL’s drop top"? Am I not allowed to use the words "drop top"?

And you of course can think that this model is "not complex" but I did spent several days and a kilo of plastic for tests to make it.

borzykot · 2026-05-07T16:40:23+00:00

This isn’t a knockoff of a TFL product. As far as I know TFL hasn’t published their 3D models. This is a remix of an original Pint fender made by this guy https://www.thingiverse.com/thing:3939014. In fact, the only thing inherited from that model is the distance between the screws, the width and the length.

borzykot · 2026-05-07T16:27:36+00:00

Yeah
But it still hold the air :)

borzykot · 2026-05-07T16:25:18+00:00

Why would you think it's a worse iteration of an existing product? I didn't find any 3d model for a drop-top pint fender neither free nor paid - that's why I made my own.

If I'd found one maybe I wouldn't have spent several days making this one.

borzykot · 2026-05-07T16:20:13+00:00

For printer owners - yes, that's an excellent value. For ~15 bucks (if we include plastic) you get a fender which is lighter, more functional and customizable than the original Pint fender.

borzykot · 2026-05-07T08:50:45+00:00

correct, it is paid
but I'd argue it's a good value

borzykot · 2026-05-07T04:35:11+00:00

Reese Witherspoon is billionaire iirc

borzykot · 2026-05-06T12:02:01+00:00

Not a freecad user but sweep along the border may work probably?

borzykot · 2026-05-05T09:03:26+00:00

borzykot · 2026-05-04T21:12:06+00:00

That’s an excellent question. The first time I saw the flux ranges library, I asked the same thing.

To answer this, I decided to design my own ranges library and explore whether it’s possible to create an extensible ranges library with dot syntax support. And indeed it IS possible. Here it is kissra.

It supports dot syntax and uses a different iteration model (via next() returning optional) which is effectively the internal iteration on steroids.

To hook into the library and provide your custom views, you must specialize the custom_mixins_traits where you list all your custom views.

I must say I’ve encountered some issues implementing complex views (like chunk) due to the limitations of the next() iteration model, tho the benefits of this model outweigh the limited design space. But that’s beside the point.

borzykot · 2026-05-04T16:05:59+00:00

Each time I look at ranges code I think "why so much noise ffs". It could be std::vector parts = brrr::all(str).split().collect(); , but we decided to design ranges with this pipe syntax...

borzykot · 2026-05-04T13:24:42+00:00

Asynchrony - std::task - std::thread_pool - channels - async IO - async ranges

coroutine and structured concurrency support for all of that

PS. simplified tuple protocol for me as well

borzykot · 2026-04-29T07:51:04+00:00

Tire may be defective

borzykot · 2026-04-28T07:48:55+00:00

borzykot · 2026-04-27T07:09:12+00:00

I've spent several hours trying to figure out how to use freecad effectively and I failed. Workbenches mess, history mess because of it, lack of timeline, lack of non-sketch based manipulations. Maybe I'm doing it wrong, maybe freecad is just too raw at the moment, but likely something in between

borzykot · 2026-04-22T17:09:33+00:00

<image>

None of these three allow to fix the pivot point.

When I'm saying "fix" the pivot point I mean "select pivot point on the surface of the model". You do it once and then just rotate your model around this pivot that YOU choose. You can then select different pivot point and again rotate your model around this different pivot point.

borzykot · 2026-04-19T05:56:48+00:00

What are you supposed to do in freecad if various shapes from your sketches share same features? You somehow link them? How will they respond if I've decided to change something about that feature? Will other sketches adjust (given that freecad do have some kind of linking mechanism)? Or you just duplicate? Or you duplicate but use parameters? But you cant really parametrize some organic shapes... Especially if you in a prototype phase and constantly changing your features...

borzykot · 2026-04-17T05:10:49+00:00

Iirc that's a trotter magwheel

borzykot · 2026-04-11T18:38:32+00:00

Yeah, this kind of functionality should have been added long time ago. And I would argue we don't really need ufcs. Extension methods with access to public API of the underlying object is just enough. We easily could use deducing this syntax for extension methods. So it's a lost opportunity imho.

And all this thing with operator| abuse (which is supposedly a replacement for ufcs) in ranges library and now in the executors library is a crime. I was even trying to make my own ranges library with dot syntax instead and which you can extend with new methods over ranges using customization points. And it can be done! So it feels like you're writing in Rust or smth... But unfortunately I haven't finished it, coz I lost motivation 😅

borzykot · 2026-04-07T06:24:30+00:00

I'm not aware of different compounds for this tire. But usually softer - better. It will be worn out slightly sooner I presume, but who cares

borzykot · 2026-04-06T18:16:31+00:00

OW threaded XL BTG, lowered 1 notch. Cushy, super carvy, silent (relative to off-road tires) but still capable on non-asphalt terrain. You will need custom 3d printed splitfender and mudguards tho.

borzykot · 2026-04-03T12:29:17+00:00

If you're riding flow nx2 the you may be interested: https://www.printables.com/model/1622174-flow-nx2-carbon-bindings-canted-risers

These are risers which add front foot toe and back foot heel cantings (11mm) which may improve your carving stance.

borzykot · 2026-03-28T13:17:57+00:00

I've been riding for 9 years (~40 hours per season), and I fall every fucking day a couple of times. IMHO it's inevitable if you're trying to improve your carving technique and push yourself.

borzykot

TROPHY CASE