As per Rad's post in a thread earlier, each bug should be posted in it's own thread in the release candidate testing forum, and the the title should start with "pre2.3".
When posting a bug:
- - Has it been posted - A little looking can save on confusion etc... Check to see if someone else has posted the same bug with the version of software you are testing.
- Try to repeat the bug before submitting it.
- If you can create a repeatable error/problem, provide detailed steps if you can, and document them clearly so you can explain them as clearly and concisely as possible.
- Be as clear and concise as possible
- this means give exact details of what is happening that is not normal including any text being given to you ( usually screen caps or copy paste if possible, are the easiest/best ).
- Provide a sequence of steps which cause this error noting exactly what you do to make it happen. It's best to do this from a common point, like start-up, or adding an obj or material, etc...
- Provide as much system information as you think makes sense, you should at minimum give the following:- - Software version you are testing(32bit, 64bit, build # if avail, etc...)
- GPU Hardware setup
- GPU Driver version
- Operating System
- Additional system or program information
- Be prepared to provide a file which can be used to reproduce it if possible (e.g. don't break an NDA to submit a bug report, try and make it happen with something which you can share if you can't do it with the file you're working on)
- It is often preferred by the company (if not legally required) that problems not be posted in very public places (ex. youtube, vimeo, big tech blogs/forums, competitors websites, etc...) as this can be negative press on a beta software that will not be a problem in the final version.
- Be polite and courteous, yes even if you're a paying beta tester, you're still a beta tester - - Software version you are testing(32bit, 64bit, build # if avail, etc...)
Dave