READ FIRST: Forum rules, and how to ask questions

Problems building or running the engine, queries about how to use features etc.
User avatar
OGRE Retired Team Member
OGRE Retired Team Member
Posts: 19269
Joined: Sun Oct 06, 2002 11:19 pm
Location: Guernsey, Channel Islands
x 66

READ FIRST: Forum rules, and how to ask questions

Post by sinbad »

Rules for Posting on the Ogre Forums

You hereby agree to abide by the following rules by using this forum. The first section is the most important, and failure to abide by it will see your posts deleted and potentially your account banned. The other 2 sections are pieces of advice which will make it more likely that your question will be answered.

Non-negotiable rules
:arrow: Intellectual Property Rights - You must not post material that is copyrighted, protected by trade secret or otherwise subject to third party proprietary rights, including privacy and publicity rights, unless you are the owner of such rights or have permission from their rightful owner to post the material. By posting here you agree to be solely responsible for ensuring this position and that the Ogre project will not be held responsible in any way for you violating any intellectual property rights, intentionally or unintentionally.
:arrow: No advertising non-OGRE related products - we do not permit free advertising of products not related to OGRE here. If your product uses or extends OGRE, clearly you are entitled to post in the Showcase section, but any posts advertising other products will be deleted.

General rules
:arrow: Do not cross-post the same question to multiple forums
:arrow: Don't PM people with requests for help unless invited, post in the public forums first
:arrow: Be polite, respect others, and don't use unnecessary profanity
:arrow: Constructive criticism is welcome, but any personal attacks will be heavily frowned upon and will likely result in a ban if you don't heed a moderator's warnings
:arrow: Don't hijack - try to keep to the original posters topic.
:arrow: Post in English - our moderators are all English speakers and we can't moderate native languages effectively. Unless your English is not good enough to express what you need to say, always post in English. You will be more likely to get a response anyway.

Posting questions

:arrow: Always search the forum and the Wiki before posting. You should also familiarise yourself with the API and Manual.
:arrow: Summarise the topic accurately in the headline. For example "HELP!!" is not a valid headline, nor is "What is going on?". A good headline might read "alpha_reject behaving differently on GL rendersystem". I reserve the right not to read any thread that is titled "Help!".
:arrow: Do your homework first. Investigate your problem by experimenting with variations, looking at logs, and using your debugger. Problem solving is a learned skill, you have to DO it to become self sufficient. We're happy to help but expect some effort from you too.
:arrow: Post just the pertinent details and explain what you've tried and what you've looked at already. Don't just post your entire codebase, say "it doesn't work!" and expect people to sort it out for you.
:arrow: Be succinct. State the problem, the symptoms, the investigation in a structured and easy to read form. Blocks of rambling text will just get you ignored.
:arrow: Post in proper English. If English isn't your first language, we'll cut you some slack, but there is no excuse for native English speakers to post contraction-filled, badly punctuated, grammatically random posts. This isn't a text message, people, and continually using contractions like 'U' and 'ur', and interspersing every second sentence with 'lol' will lead me to stop caring what you have to say in short order.
:arrow: Always use the 'Code' button to format blocks of code / script
:arrow: Don't claim to have found a bug unless you're really sure you know what you're talking about.
:arrow: Don't 'bump' threads unless you have something more to add. If you didn't get a response the first time, it's likely that you didn't provide enough information, or people thought you hadn't done enough work of your own to justify a response. Or, they just might not have known the answer.
:arrow: If you find an answer, post it in your thread, it will help others.
:arrow: If your question has been answered to your satisfaction, edit the title and add '[solved]' - it helps us identify outstanding questions

Proposing Fixes
:arrow: If you need to discuss a potential bugfix or new feature, feel free to discuss it in the forum. For final submission, please create a pull-request.

Please adhere to these rules. The forum is getting more and more busy, and it will help both you and other users if the quality of posts is kept high.