Providing Feedback

Introduction #

Your feedback is vital for making Notch 1.0 as good as it can be. For the closed Alpha period, nothing is off limits. We want feedback on everything, from your first impressions and bugs to node names and node connections, so please get everything you want to say over to us.

To provide feedback, we’ve provided a set of special BETA contact request types on our contactus.notch.one. Only Alpha/Beta users can see these BETA categories, so make sure you are logged in. Your feedback goes directly back to our Product team who will triage and log.

Types of feedback #

General Feedback #

This is the general catch-all for feedback.

• If you find something you love, tells us about it!
• If you find something you hate, tell us about it (nicely)!
• If you find something that doesn’t work, tell us about it!

This will help us prioritise our time on the things you want to see fixed, improved, or redesigned first. Not everyone will notice what you notice, so oversharing (about Notch) is great!

For bug reports, its always been important to follow the bug reports steps to help us identify and fix issues, but now it is even more so. We need to see:

• Repro steps. What are the exact steps you took to make this issue occur? Is it repeatable? Does it occur on the simplest possible version of a scene?
• The project file. Even on a seemingly simple scene, one enabled checkbox can make the difference for us to find and fix it.
• Screenshots and videos. We won’t always know what you are referring to in writing - a clear screen shot and/or video can help us find the issue much faster. It’s worth a thousand words after all.
• Log files. Our log files help us know exactly when and where an error occurred, and what Notch was doing under the hood. You can find them in Documents/Notch/Logs.

As always, clear and concise feedback is incredibly important to us, so please send us everything you can so we can talk to the dev team about what you are finding.

Crashes #

You are participating in an alpha build, so instability and crashes may happen along the way. If you do encounter any crashes or instability, here’s what we need.

• Repro Steps. Providing the exact steps taken to generate a crash is hugely important, as it can shed light on how you are using the tool and help us identify the issue more effectively.
• Log Files. As with bug reports, our log files help us know exactly what Notch was doing and where it went wrong. You can find them in Documents/Notch/Logs.

Project Migration #

While we don’t expect projects to migrate from 0.9.23 to 1.0 perfectly due to changes in the rendering engine, there may be some cases where things aren’t as we expect.

Check out the project migration page to get an idea of what to expect from migrating a project. [link to project migration]

In the cases which don’t line up with the project migration guide, please send over the following:

• The 0.9.23 Project File. Untouched, just as it was before going into 1.0.
• The 1.0 Project File. Including all the same resources, and all the same nodes, and the renderer node hat will have been added.
• Screenshots and videos. We need to know exactly what’s different, so screenshots and videos will help us massively in identifying the differences between two projects.

Lastly, remember you are using the worst version of this tool that will ever be released. It’s your feedback that will make it the best tool that you’ve ever used. So please don’t withhold anything - we’re looking forward to hearing from you!