READ FIRST : RULES FOR POSTING A PROBLEM

Post by **simonB** » Fri Dec 09, 2011 3:59 pm

TRY WITH THE LATEST BETA. A large amount of problems are posted which have already been solved!

1. Outline the steps you have taken to tackle the problem. Use bullet points. Don't say "DVC3 sucks and I don't like this and this doesn't work exactly the way I want it to and...".
2. Outline your spec at the bottom of the post in bullet points including FIRMWARE DATE, SOFTWARE DATE, OS and PRODUCT NAME (eg DVC2 512, DVC3 GOLD. Not SIUDI7, this is the circuit board name)
3. Always start a new thread unless you think that your problem is directly related to a problem being spoken about.

We want to get a great stable release of DVC3 ASAP so when bug reporting, try not to make posts which are too long and get to the point!

jimmyshy · Post by **jimmyshy** » Thu Sep 13, 2012 4:39 pm

could u give us a sample will let u easy to read the bug information?

like:

FIRMWARE:
SOFTEARE DATE:
OS:
PRODUCT NAME:

BUG:
XXXXXXXXXXXXXXX

is this right?

Post by **simonB** » Mon Sep 17, 2012 3:27 pm

yes, like that. Bugs are easier with bullet points, like this

-create a new show
-patch a 'xxxx' profile
-create a scene

etc....

MovingWaves · Post by **MovingWaves** » Wed Apr 24, 2013 1:50 am

How long before we get a reply?

Post by **simonB** » Fri Jul 19, 2013 2:53 pm

The forums are for users to discus and share information. We'll do our best to moderate the forums at least once per week (I understand this was posted in April, but I missed it!)