mranderson17

Step file for wheel side flange is here https://www.printables.com/model/729742-wheel-adapter-for-thrustmaster-r383-mod-rally-whee

Mosh hasn't had a release in quite a while (Oct 2022). While that's not that old, and there does appear to be somewhat active development, it's a little slow moving for something that might be open to the internet directly. I used to use it but ssh with tmux is mostly fine and makes me feel a little safer because of their wider use.

This is so cool! I will remember this when I'm tempted to buy new shiny sim rig parts that someone built something 20 times as nice as what I have out of cardboard, automotive switches, and vape juice bottle tops (among other things).

AFAIK openSCAD is a code driven mesh format. So if you want to import openSCAD models into any other CAD software you have to convert the mesh to STEP or some other actual 3d object format during which there can be lots of error if the model is complex. I don't have a lot of experience doing this but I just tried a model I had lying around from the dactyl keyboard project and converting it resulted in a lot of really broken surfaces.

This is a cool alternative that makes 3d objects instead of meshes (at least it says it does). https://zalo.github.io/CascadeStudio/ . Also open source but web based.

EDIT: I should mention that CascadeStudio seems to be abandoned, just a cool concept of a different way of doing code driven CAD.

I use FreeCAD and Assembly3 for everything and have for many years now. I sometimes use realthunder's fork of FreeCAD but right now it's quite a bit behind upstream and there are some cool new features in sketcher so I use upstream for those.

Some people get confused about workflow in FreeCAD because there are so many options and every youtube video has different opinions or tries to feature a particular workbench like curves or something. My opinion.... Pretty much your workflow starting out should be to ignore everything else and use part design and sketches, it's the simplest way:

0. enable autosave with a short interval, like 2min

1. Switch to part design workbench

2. create body

3. create sketches as the base of the features of your part attached to the xy, xz, yz planes, offset them to create a "wire frame" that resembles your project

   a. Your sketches should be fully constrained

   b. Your sketches should have as little geometry in them as possible, if you need more complex stuff make more sketches

   c. Your sketches should have closed wires, you can't pad something that doesn't create a face.

4. use pad, pocket, revolution, loft, and hole operations on those sketches to form a 3d solid

5. if you need to create additional sketches which import geometry from the previous operations (using the external geometry tool), import SKETCH geometry from the previous ops, not edges of solids, whenever possible. Hide your solid, unhide your sketch, select that with the external geometry tool.

   a. Use sketch on face sparingly.

6. Do fillets and chamfers last, if you need to change something, delete them and recreate them once you've made your changes.

To make multiple parts make multiple bodies with the same workflow as above.

Once you get pretty good at making static parts with constrained geometry, holes, threads (with the hole function), etc, which you can do with only the stuff above, then you can branch out into other workbenches like assemblies or curves, but all of those things build on the concepts above, so it's easy to get overwhelmed if you try to do it all right from the start. Learning how to recover from a mistake is just part of CAD in general, though I admit that it's a bit more effort to find what's wrong in FC vs commercial platforms, but we aren't here, on lemmy, in a linux community, to use commercial platforms.

AFAIK that's pretty much the same workflow as F360 uses for single-solid parts though things have different names. pad=extrude for example.

It's obviously far from perfect but in my opinion it's the best solution that runs natively on Linux and is actually open source. Also assembly3 uses solvespace as it's backend solver so if you make assemblies using that you are kindof using solvespace too.

Also, I hear/read a lot of complaining about instability but I've honestly never had a crash that wasn't on an experimental branch like RT or the edge release of upstream. However step 0 above should help if you're worried about that.

this one? =]

I do this too, but additionally group these outputs strategically on my 4 displays. I never thought of it like a desk with papers on it but that's very much what it is. And also how I organize papers on the few occasions that I do that.

Are they using vulkan natively (not dxvk through wine)? I posted about this when running the experimental vulkan support on BeamNG.drive https://www.beamng.com/threads/vulkan-api-%E2%80%93-feedback-known-issues-and-faq.79967/page-12#post-1617244. Looks to be very similar maybe?

My OS details are in that post but also here:

OS: Arch Linux x86_64
Kernel: 6.1.39-1-lts
Resolution: 3840x1600
WM: sway
CPU: AMD Ryzen 9 5950X (32) @ 3.400GHz
GPU: AMD ATI Radeon PRO W6800
Memory: 64209MiB

All other games, even ones that use vulkan, work fine for me, it's just BeamNG.drive

EDIT: well, I'm not on 6.1.39 anymore... I have obviously updated since that post, but the rest is the same...

I love that they say "Maybe you can order from our overseas warehouse" in the title of the product lol

And in the specs for the C5 it says "finished product". Which is very reassuring because I had a few doubts /s

Ah, thanks. Sorry I was not aware of that issue.

Could we could sticky this one and un-sticky round 4 maybe? I wonder if it would get more traction @itsmikeyd@lemmy.world and @BURN@lemmy.world

Well, I produced a time.... ~~2:22.034~~ ~~2:19.494~~ ~~2:18.101~~ 2:14.946

First time around a track with the OpenFFBoard wheel (finally got the paddles working, which is why I didn't post earlier).