Check frcdesign.org; I'm working on that site, which will be the most up-to-date. (videos are annoying to make and update) The design learning course will probably be the smoothest transition to onshape, and switching to onshape is 100 percent to play, especially now that the learning course contains a lot of good design content.

Im from 8280. Remember that number

Give it a try and see, you can put entire equations in your dimensions!

at the left of the tool search bar there is a + sign for custom features you should search "tube converter" in there

try to make the polycarb rollers free spinning, I haven't been able to prototype for that but so that was based all on vibes.

The problem was in the ejection part, we tried that system by compressing it on both sides and it was successful. @@howlongismydesign

Thank you very much for your sharing. We produced the robot inspired by your CAD drawing, all its functions work perfectly. If you want, we can offer our robot to you.

What team are you on? I’d love to watch your team online while you compete.@@erdincugurlu9923

cad.onshape.com/documents/7746ab91f9a4d8a9b4287dca/w/eb16ba122b1116f385b90364/e/c25dedecc88a6310c7861099?renderMode=0&uiState=65a4ca687329370a4f57bfdc (its a little broken)

@@howlongismydesign thanks!

I only worry about CG when its at the stance at 1:57

Ya I'm a senior in highschool

As of right now, I just put like 0 compression on those rollers and pray, lol. I think it's like 1/8 or 1/16, then rely on the tape/silicone rubber on the tube to add the tiny bit of "grip".

Its called 2:33 am

Good onshape practices usually help, multi doc, using simpler features, simplified models, ect.

gotcha, thanks

Were you able to find it? Try this invite. discord.gg/4PBbcycz Sorry I don't check youtube that often.

what's the worse that can happen

🤔

onshape4frc.com/getting-started, check the adding feature scripts section

Mutli-doc for version control + working together with others in terms of load time and breaking things. It's especially nice for experimental designs when you want to dive into something but don't want to commit, while not accidentally breaking the main assembly. If you made a huge mistake and had to version in single doc, and someone else was working at the same time, you'll accidentally revert their progress too. It's also nicer for load times and keeping the cad "Clean" You don't have a pile of files to dig through, and when you're working on more intensive stuff, its nice to not not effect others. You have different "versions" for different sub assemblies, instead of trying to version the whole doc at once. And ya, it helps with parametric cad, though you can do the same things with single doc TBH, it's hard to explain but I've enjoyed it more. (I'm sick right now, apologies for the poor response) PS: Say hi to Mr. N for me! He helped me a ton and I don't think I would be where I'm at w/o his help.

The two major things is wheelbase + packaging space. As you go smaller, its significantly easier for you to tip, which forces you shorter unless you want to have high cg, which then forces you to accel limit and slow down to not tip. Overall, for most teams, you'll just be either really tippy or really slow. A larger wheelbase means its naturally easier to lower your cg as there's more room to package lower (as you don't need to go up to package), as well as have a large wheelbase which makes it easier to drive and build taller as necessary without sacrificing stability. 2023 was nice because you didn't have a climber, and your mechanisms were a lot simpler which meant that you could throw 50 lbs to ballast, which isn't really possible in most games. Most top teams were still 26 inches at minimum, with teams like 1323 being max chassis size, 2910 being 26 x 28 (which is massive considering how tiny they feel), and 4414/254 being at 26 x 26. In previous years you'll find top teams going max size pretty commonly though. TLDR: small robots are hard to be fast and stable, big robots much easier to do it and its a lot more forgiving.

@@howlongismydesign Thank you for the thorough explanation!

Glad it helped!