We’re very excited to release the latest version of Crash! Available for download now!
Crash is an open source plugin that enables you to make your Rhino models multi-user! Start collaborative models with your colleagues or classmates across the office or across the globe.
After 8 months of hard work the team has finalised the latest version of Crash. It has been an incredible amount of work and involved rewriting most of Crash. But the final product we hope you’ll agree has been worth the wait!
Disclaimer
Crash is a work in progress project completed in the spare time of generous contributors. If you find bugs we’re very motivated to solve them and bring you a rocksolid product. Please create a thread in the Multi-User channel or add it to GitHub (see below!).
There is no hard cap in the source code. Theoretically it’s all down to server hosting, hardware etc.
I’ve tested an azure model with 6 people and that worked pretty well! In Unit tests I’ve managed 1000 connections without any drops which is an exciting prospect.
Please give it a go, try gentle, try crazy and let me know how it goes! I’ve put guardrails where I can to inform you when there’s a failure (server drop, blips, trying to send geometry that’s oversized etc). There’s a few things locally that aren’t supported yet (grips, blocks, linestyles, layers etc). which should be nicely documented in the docs above. Most of the last 8 months was Architecture work. Adding in these items should be much more feasible now !
Terrifying to think of 1000 designers working in the same project a building may never recover. Cross disciplinary teams though for sure! 4 here, 20 there, 1 there, etc… I love the idea.
Awesome, will do. I was thinking about going the Azure route to start. Need to look at the docs and research more.
EDIT: does undo work after you’ve released changes already?
r.e the 1000 users, Crash has a nice “Follow” feature so in theory 1 person could be teaching, and 999 watching !
Undo/Redo does the inverse of what ever action happened before (Quite literally, Crash has some very nice event wrapping, and changes are handled immutably). Undo will put an object back where it was (But I don’t think it re-obtains it currently, so it will still be released for now)
That’s actually quite interesting. There’s screen sharing of course but I love the idea of an instructor “alright follow me here and I want each of you to create a dodecahedron following the steps I show you and one other primitive of your choosing nearby.”
Or “everyone, to finish of your design, create a light on the porch and render material for your small shed, we will then travel to each students shed and let them present their shed design”
Wow! I don’t think people realize how awesome that actually is haha nice!
Of course, and for so many things its really handy. Most of all you don’t need a Rhino license. But if you’ve got it, it should be a much nicer, latency free space to collaborate in.
That was my hope! It wasn’t actually my idea, but I really like it, you can also see the other users’ cameras, which is really cool if you were to present something, you can see what everyone else is focused on.
I would love to see this, it feels like a really cool and interactive way to work together!
Hello! I have been waiting for something like this since earlier stages of rhino.
I would like to try it out, and I have been reading about the way of using it but it is not that clear to me. I managed to install the plug in and also to download the crash.server, but it is not running in my PC, saying that it can’t.
For those (likely most of us) that would like to use Crash.
Could you make a “create a crash server for dummies” guide
I followed the documentation and Azure video linked in the documentation but still having an issue creating a server for my colleagues to join with me.
Thanks so much for the help, the potential here is huge!
Okay step # 1 is done.
The Release build should work. I’m not sure why it had any issues but I’ve updated some build scripts so it shouldn’t happen again.
If you navigate to the url you hosted the server at you’ll get a little welcome page that has links on the bottom left to other debugging pages as well
@CallumSykes I don’t see that while using localhost, I’m assuming I need a proper server address.
I don’t know much of anything about web hosting, azure, aws, etc.
But I’m assuming that I need to create server host address via one of those services and have Crash point to that if I want to actually use the Crash.Server with others collaboratively correct?
This looks incredible. Great work! I’ve been thinking about geometry syncing and stream to AR/VR devices (like the vision pro) and this seems like it might be a great approach. Have you looked at syncing with the iRhino viewer app at all?
You will need to navigate to http://localhost:8080 not http://0.0.0.0:8080.
Oh also the debug urls will ONLY show on a Debug build, so you might actually need to run a local debug to see them. You should still see the welcome page though.
Hey @cameronbehning it depends exactly what you want to stream and how you want to interact.
I worked on this project at a hackathon which streams the rhino viewport pixel for pixel and allows returned clicks and commands. Rhino Anywhere | Food4Rhino. (I do not spend time on this project however due to my focus on Crash.)
I have not worked on adding Crash to iRhino and I won’t make any promises I can’t guarantee .
I’m looking for a good way to stream the 3d data from Rhino to the Vision Pro so you can place a model, view it in 3d/ walk around it, all while staying up to date with the modeling happening in Rhino. So pixel for Pixel streaming wouldn’t be the solution. Based on the videos I’m seeing, you are streaming geometry, not just pixels, which is the first step of my problem. If I were to work on a branch and make a pull request, is that something you would be opening to integrating?
Also, where does this stand with grasshopper and collaboration?