If you believe you've found a problem with ReplicatorG, be sure to let us know so we can fix it in the next revision! There are two ways to report a bug:
Distinguishing bug reports from feature requests
A bug is something going wrong with a program: a crash, a button not working, etc. A feature request is a request for a change to the way the program works— adding a new button or function, changing the UI design, etc.
Before you create a bug report, take a second to check if it's a bug or a feature request. If what you have is a feature request, please go ahead and file it, but add the words "feature request" to the bug title somewhere. We'll try to fix bugs as soon as we can, but feature requests are generally lower on our queue.
Creating a bug report
The more details you can give us about your problem, the more quickly we can find a solution. There are some basic facts you should always include in your bug reports:
- What platform are you running on? Windows 7, OS X, Ubuntu? What version?
- What machine (if any) are you running? What firmware?
- What version of ReplicatorG are you using?
Additionally, useful information includes:
- Error messages printed to the ReplicatorG console
- If you started ReplicatorG from the command line, any additional information you see presented there
- What version of Java you're running
- If the problem has to do with toolpath generation, what version of Python you're running, and where it's installed
Filing your bug report
ReplicatorG bug tracking is now handled through MakerBot Support. Email moc.tobrekam|troppus#moc.tobrekam|troppus with "ReplicatorG bug report" in your subject line.