-
Save your design in OpenRocket (
Ctrl+S)
➤ Save it inside theOpenRocket-Simulationsfolder. -
Run the update script
➤ Double-click the file namedwin_update.bat -
Type what you changed
➤ Like: “Switched motor to L1000 and shortened body tube” -
✅ That’s it! Your design is saved, backed up, and shared with the team.
OpenRocket files are kind of weird:
When you hit “Save”, OpenRocket actually creates a ZIP file that hides your rocket design inside it. This is bad for version control.
| Problem | Our Fix |
|---|---|
| Git sees ZIP files as binary garbage. | We automatically unzip and convert your file to readable XML (but keep the same .ork name). |
| You end up with “v2_final_FINAL.ork” chaos. | Git stores a history of every save. No renaming needed. |
| You don’t want to touch Git or terminals. | No problem. Just double-click a file like you would a game or app. |
This only has to be done once per computer!
Go here: https://git-scm.com/downloads/win
Run the installer and click “Next” for everything — the defaults are perfect.
You only need to do this once. It creates the folder where you’ll keep all OpenRocket files.
- Right-click on your Desktop or Documents folder
- Click “Git Bash Here”
(This option shows up after you install Git) - In the black window that opens, paste this:
git clone https://github.com/CURocketEngineering/OpenRocket-Simulations.git
- Press Enter
✅ A new folder named OpenRocket-Simulations will appear.
Go inside the OpenRocket-Simulations folder. You’ll see a file called win_update.bat
➡️ This is your magic “update” button.
Always save inside the OpenRocket-Simulations folder.
You can keep different rocket files here like:
10k_rocket.orkpayload_test.orkK700_flight.ork
It doesn’t matter what they’re called — the system will handle the rest.
- OpenRocket: design or modify your rocket
- Press
Ctrl+S(or File → Save)
➤ Make sure you're saving in theOpenRocket-Simulationsfolder - Double-click
win_update.bat - When it asks for a commit message, type a short description of what you changed
➤ Example:Added K700, adjusted fin span - ✅ You’re done! The file is cleaned up, converted, and backed up.
Don’t worry. Git tracks every change.
- If something breaks, we can go back to a previous version.
- You can’t break the system by saving or clicking the script.
- If you’re stuck, message a teammate — they’ll help you out.
Nope. Just double-click the .bat file. Git handles the backups behind the scenes.
Nope! Save your file with any name like TestRocket.ork or L1000Flight.ork. The update script will convert and organize things for you.
- It checks each
.orkfile in the folder - If it’s a ZIP-style OpenRocket file, it extracts and converts it to a readable format
- It adds it to the project history with the message you typed
- It pushes the file to GitHub so your teammates can see it
Yes! All .ork files will still open just fine in OpenRocket.
Ignore folders like .git — they’re part of how Git tracks versions. Just focus on your .ork files.
No worries. Just run it now. It’ll catch everything that hasn’t been uploaded yet.
✅ Save inside OpenRocket-Simulations
✅ Double-click win_update.bat
✅ Type what you changed
✅ Done — your rocket is backed up forever
If you still have questions, ask Ethan Anderson on Slack.