Best Practices to post a TECHNICAL Question

Best Practices to post a TECHNICAL Question

Hi! Thank you for choosing hauzd!

Here you will find a couple of tips for posting and get answers to your questions as fast as possible;

• Make sure to always look for your question before posting, you may find your question already answered, for example; the engine throws you an error:
ERROR: Duplicate material name detected
You have 2 options to look for it,

1. The top search bar on the help desk home







• If you can´t find any related answer to your question, you can create your own question
Make sure you are already Registered in our help desk site. IMPORTANT:  This account is a separate account, you may have already an admin.hauzd.com account but still, you still need the help.hauzd.com account to post

• When Posting, Keep in mind this few tips to help us to get you an answer as quick as possible:

1. The right question will give you the right answer
Bad Example: How do I set materials for the engine? (This question is generic and may lead to several post teaching how to handle materials in general)
Good Example: I´m getting an error in Log window when importing an .fbx scene,  "ERROR: Duplicate material name detected". (This question is more specific about having a material error and asking how to solve it)

2. The more specific and detailed you are, the better
Bad Example: I´m getting import errors, how do I make it work? (This is a generic question as well, it does not say too much so it may lead to several messages going forth and back trying to figure out the exact error, more messages means more time to solve it)
Good Example: I´m getting an error in Log window when importing an .fbx scene,  "ERROR: Duplicate material name detected", (This is a specific question with a detailed error and where it happens, this leads to a quick one time answer)

3. Don´t be afraid to use attachments or screenshots 
Bad Example: There is a weird lighting on my bake, what can I do? (No attachment on this question makes hard to imagine how does it looks and what was the user expecting)
Good Example: There is a weird lighting on my bake, what can I do? (The question can stay the same but a Single image with an .fbx attached will be easy to troubleshoot for us)

4. Include every detail you think it may help us to answer your question quickly

Bad Example: There is an error with my package, I have been waiting for it to show online (If you are a studio with multiple projects, looking for all your projects to check if there is an error can take some time)
Good Example: There is an error with my package in project "X", I triggered it about 20 minutes ago (At first, just by looking at the time, in seconds we can give an answer if the project is under the regular time or not, and if its not, we can straight search for your desired project and check if there is indeed an error)



If your question is NOT TECHNICAL, but COMMERCIAL (Licensing, Fees..), or you got a BUG REPORT, you can use the live chat in left bottom corner, we will gladly assist you