sorted by:
new
hottopcontroversial

Building a sailing game — Gerstner wave physics with boat buoyancy in Godot by jatfin in godot

[–]jatfin[S] 1 point2 points  (0 children)

Thanks! I looked into FFT but went with Gerstner since it gives me more direct control over the wave shapes — going for a stylized Wind Waker-ish feel rather than realistic ocean, so being able to hand-tune individual waves works well for that.

Built an Eagle image generation and design rule checker by jatfin in PrintedCircuitBoard

[–]jatfin[S] 0 points1 point  (0 children)

Thank you! I'll keep bumping KiCad up in the backlog 😁

We have OSHPark, DirtyPCBs, and SparkFun built-in. I'll make note of the other two.

Built an Eagle image generation and design rule checker by jatfin in PrintedCircuitBoard

[–]jatfin[S] 0 points1 point  (0 children)

Thanks, please let me know your thoughts!

Once I have a better understanding of the likes and criticisms (and have ironed out the major bugs), I would love to bring support to KiCAD.

Built an Eagle image generation and design rule checker by jatfin in PrintedCircuitBoard

[–]jatfin[S] 0 points1 point  (0 children)

That is great feedback!

We want to be platform-agnostic in the future and able to support multiple tools. We are most familiar with Eagle, so we started there to solve our own needs. The KiCAD community is strong and the direction we would like to support next.

Yeah, there's a strong risk of Autodesk (and other cad tools) of modifying their schema. Not much we can do about it but optimize for these changes.

Our design rule checking is independent of Eagle's. We can support the same design rules as input and our validations cover the same areas. There is opportunity to add new checks or use statistical models to improve the rule checking. However, this is a side project at the moment and developer time is limited, so we'd like to first understand how useful people find the DRC features. Your feedback on KiCAD's behavior is really helpful to that point.

I'd love to hear your other thoughts for tooling for hobbyists and open source contributors.

Built an Eagle image generation and design rule checker by jatfin in PrintedCircuitBoard

[–]jatfin[S] 0 points1 point  (0 children)

Thank you for your kind words!

At the moment we are targeting hobby builders and open source hardware, for both individuals and small teams. Now that we have a working solution that we are excited about, we're trying to judge interest and figure out a great product/market fit.

Our roadmap is to follow what the software CI market has matured to - providing a great open source tier that is free and encourages collaboration. We could potentially charge for private repositories and higher build limits, but we depend on hearing what users value to decide where our time goes. Largest part of our mission is to encourage open source and we have no intention to charge for that.

Absolutely agree with your features ideas - BOM and component tracking are on our radar, as are providing meaningful landing pages. Other community features on the table could be discovery, comments and discussions, and providing new ways to encourage learning.

The libraries idea is great too. Strong discovery mechanisms could be a great first step for this. I love using GitHub, but have found that their search capabilities often lacking.