u/RaspberryCultural412

No worries at all. But you should know, this application was not "vibe coded". I am a professional developer with more than 30 years experience building applications and running software teams. Vibe coding typically means a non-coding professional is having LLM's write all their code through plain language prompting. This isn't that. In either case, I certainly respect your decision to use or not use a product. All the best and happy gaming!

Both work! You can select the dice you want to roll first, or just roll directly in your tray and let RollSight read them. Once connected, the results appear in Owlbear’s shared roll pop-up with the individual dice and total.

There’s also character-sheet support through Forge. With the integration enabled, clicking a supported roll on your Forge sheet requests the physical dice through RollSight and sends the completed result back to Forge. That currently supports public rolls with supported formulas.

It's a weird time for developers. AI for code assistance is essentially standard of practice now the same way as using IDE's have been for the last decade. It's majorly different than using AI for artwork, music, video, or narrative prose writing though. AI for coding isn't ripping off artists' creative works. The general backlash against AI for creative theft doesn't distinguish the use of AI for testing, documentation, code promotion, etc.

In my 30+ year career, I started as a coder, then ran coding teams, then enterprise architecture for a fortune 100 company, became a CIO, then CEO. Building applications of all different scales has been my entire work life and often my hobby. AI is an accelerator for coding but it certainly can't replace knowing what needs to be built and what good software and architecture actually looks like.

Everyone can use it at the same time. And the free tier is all you need to be able to play. The higher tiers just add some additional "nice to have" features like video replays sent into your game and the system keeping track of your your rolls over time so you and your friends can see your trends, or so you can see if a die is actually balanced.

Thanks! Total labor of love. When COVID hit and we moved to online for D&D, I really missed throwing real dice. (And I always had a feeling the digital dice weren't fair for some reason)

That's it exactly. Give it a try if you get the chance. It's super cool to be able to bring real dice back to the game.

The system has been trained with more than 50,000 die rolls but as you say, some unique dice it will have never seen before. Users can train their own dice locally for immediate use and share those trainings with the central server so others won't have to train the same dice.

Great minds! Have a look at what we're doing with RollSight - www.rollsight.com

RollSight exposes confidence levels to the user rolling the dice and won't send anything to the VTT if the confidence is low. The user can then confirm and train the die roll and send the tray values on. A video replay of the roll is sent to the VTT as well so the GM and other players can see the physical values that were rolled. RollSight also senses occluded dice (d4s are the worst) and will ask the user to manually move the die (without adjusting the value) out from under the other die.

Yes, sorry if it seemed like I was dodging something. I've used AI tools to help write code, but maybe not in the way you're thinking.

RollSight has nearly two years in development, and along the way I've used tools like Cursor and Codex to speed up my code writing, just as I've adopted countless other development tools over a 30+ year career in building software and leading teams in software systems engineering. IDE's have been automating and assisting code writing for decades.

For any project, I know what I want to build, how it needs to work, where it fits into the architecture, what interfaces and constraints it needs to respect, and what the expected behavior should be. Some code I write from scratch. Some code I look up online for pre-built/tested functions. Tools like Codex let me turn requirements into working implementations much faster than writing every function by hand. They're also extremely useful for generating tests, debugging, refactoring and reviewing existing code and super useful for automating cross platform deployment.

For context, much of my career has involved building complex, enterprise-scale applications in healthcare. RollSight is also a fairly substantial system at this point, spanning computer vision and ML inference, camera and hardware integration, a desktop application, encryption, licensing, cloud services and VTT integrations. These tools have dramatically accelerated the development process, but the architecture, requirements, engineering decisions and responsibility for what gets built and released remain squarely mine.

That's also very much in line with Foundry's AI policy. (https://foundryvtt.com/article/ai-policy/ - see 4.4) They permit AI-assisted and AI-generated code, while requiring developers to understand, explain, modify and maintain the code they submit. I think that's a very reasonable standard.

I would say that if your personal stance is that you want to avoid all software that has been touched by AI tools, then I'm sorry to say that you'll need to cross RollSight off the list. I'd love to have to you give it a whirl but I fully respect where you're coming from.

Percentile dice for Foundry are in now! The initial roadblock there was that Foundry had no in-built way to convert a d10 and a d10percentile die together as a d100. That's now computed in the bridge and rolls appropriately show up as a d100.

I've got a set too but its not really feasible to use those for pretty common rolls that require a large number of dice. (Fireball, etc). They're pretty neat though. Pixels or GoDice?

Thanks. Total labor of love we wanted at our own table. It really is so much more satisfying to feel the actual dice and be able to blame a very specific hunk of plastic for your shitty roll.

It depends on the platform. Foundry has the most integration-friendly platform with a full documented API and lots of opportunity to create seamless experiences for users. Other VTT's don't have open APIs at all and integration has to happen as surface layer insertions using browser plugins. We started with Foundry but we're actively working on what functionality we can also provide in Roll20, DNDBeyond Maps, and OwlBear Rodeo. Those will trickle in as we can get through the testing.

100%. I'll add this to the training roadmap. The way RollSight was built, it can accept really anything as a die shape and value with enough training. Stay tuned and we'll put this in a release soon.

Yes! Linux support is definitely on the roadmap.

RollSight is built on a largely cross-platform stack, and we’ve started looking at what it would take to add Linux. The good news is that most of the core application and dice-recognition pipeline should carry over without major changes.

We’re planning to target Linux x64 with an AppImage first. The main thing we’ll need to validate thoroughly is webcam support across different Linux hardware and distributions.

No release date to announce yet, but after digging into it, Linux support looks very achievable.

Sounds like this one may not be for you I'm afraid and I fully respect that. As the previous commenter suggested, AI coding tools like Codex, Claude Code, Cursor and such have become core resources for nearly all software development lifecycles. We'd all be very hard pressed to avoid all software that makes use of the rapid testing and code review that the aforementioned tools now provide as part of routine software development. Every major software you touch is going to have development teams speeding their work by utilizing AI code assist. Your operating systems, productivity tools, games, etc, all have teams using AI tools. Rollsight is no different. However, AI used in code development is a world of difference than AI used to write a book, a term paper or a piece of music or art. Conflating the two would be akin to comparing the use of a calculator to copying your neighbor's math homework.

If you've got foundry configured to parse rolls now, RollSight won't get in the way. It just replaces the electronic rolling and Foundry does all the rest however you have it configured. You can also skip a manual RollSight roll and let Foundry roll electronically for you any time so if you truly need speedy dice, that's always an option.

RollSight is only replacing the rolling. Foundry would parse the different damage types as it does now.

Yes on initiative rolls.

Pip dice are coming in the next version. We focused on numbered polyhedral dice for the time being but there's already a training path for pips. Stay tuned!

There are a lot of controls available for camera tuning including artificially boosting the lighting but its always going to be camera dependent. I personally use a low light arduino cam in my Dragon Rig set up and it works great in dim conditions - https://a.co/d/07pczJqI

RollSight supports virtually any camera you can connect to your machine. Phones, webcams, dedicated cameras, document cameras, etc. Resolution and low light capabilities make a difference though so your milage may vary. Give it a whirl and let me know how your setup works.

Yeah man! I put all the files for that dragon rig out on Printables for free. Feel free to print that one or modify to your heart's content. There's a whole guide for what camera and pico screen fit with that model on the website.

https://www.printables.com/model/1643456-rollsight-dragon-rig/files

That's awesome! We made a model without a dice tower to hide a small arduino camera and even a little pico screen. It's freely available on Printables - https://www.printables.com/model/1643456-rollsight-dragon-rig/files

If you come up with something that works for RollSight, we'd love to feature it on our site if you'd like. We'd also love to print it and use it ourselves!

I'm afraid actual humans designed this and took thousands of "turntable photos" and hand rolled a ridiculous number of dice to train YOLO models. 51,000+ and counting. It's not perfect by any means but it gets better the more it's used.

Great minds think alike! We've been working on a similar idea to use a real-time camera feed to inject dice rolls into Foundry and other VTTs. Shoot me a DM and maybe we can collaborate to create the ultimate solution for VTT users!

https://www.rollsight.com/