Forum Posting Guidelines

The best way to get help in this forum is to ask your questions in a way that makes it easiest for us to give you help. Consider the following to be a series of informal guidelines for posting questions.

Before you post

Before you ask questions of others, it is respectful to put forth some effort in solving the issue yourself. It is generally faster for you (if your question has already been answered) and it keeps down the number of redundant or simple questions the forums receive. To this end, you should do the following before asking a question:

  1. There are many good sources of information on Khronos Technology available on the web. You should check these before posting.
  2. Google is your friend. Or Bing, if you prefer. Or whatever searching service you prefer; it doesn’t matter. It would be best for all involved if your question could not be answered via a simple search based on the terms you’re interested in.
  3. Search the forum. The Khronos forums have an extensive search function, and the forums have been around for years. It is very possible that your question has been asked and answered before. Make use of those search abilities before posting (but don’t post in the thread you find unless it is a recent thread).
  4. This forum is a Khronos Technology forum, not a general coding forum. So try to focus your question(s) on Khronos Technology related matters. Questions should be about Khronos Technologies.
  5. Is your question about a homework assignment? If so, remember that the purpose of homework is to help you learn. It does you no good to be told the answer to a homework assignment. Also, this is cheating, which is generally frowned upon in academic institutions.

Posting Guidelines

  1. Use a clear thread title. A good thread title should be a very short summary of the problem. For example, if your problem seems to be with textures, then the word “texture” should be somewhere in the title. Titles probably should be 8 words or less, though more can be used when necessary.
    There is also no need to use words like “please help” or “urgent” in your thread title. By posting in the forum, you are already asking for help; simply state what the problem is. And people will generally not quickly flock to your thread just because you claim that it is urgent.

  2. Put your question in the correct forum area. There is a text description for what each forum area is for, so this should not be particularly difficult.

  3. Do not post the same thread in multiple forum areas. This is called “cross-posting,” and is not necessary for you to get help. If you make a post in the wrong forum area, only post again in the right one if people have not already started to comment on your current one. Also, lack of comments is not a sign that you have posted in the wrong area, so there is no need to post in “Advanced” if you didn’t get a response in “Beginners”.

  4. Clearly state your problem in your text. Make sure to include all relevant details. If you have only written single paragraph, that’s probably not enough detail. A single sentence is completely out of the question. While overdoing the detail is possible, it’s better to put too much detail in than not enough detail.

    Never just say “it doesn’t work;” that is almost never helpful, nor is writing a single sentence and posting a block of code. What you don’t want to do is engage in dueling dialog, where the first responder asks for clarification, you provide an additional detail, they ask for more clarification, and so on.

    To this end, your post should include:

    • What the problem you’re having is.
    • What the results you expect to see are.
    • What you are actually seeing, and how it differs from what you expect to see.

    Use pictures if it makes it easier to understand the issues around the problem. The more relevant information you provide (to a point), the more likely the forum users are to be able to solve your problem.

  5. Supply all relevant information about your setup and system. This includes:

    • State your OS, graphics card, and driver version.
    • State your programming language where relevant.
  6. Do not post in old threads. If your search on this site unearthed a thread with a similar question to yours, but that thread hasn’t been posted in for more than 6 months, resist the urge to post in that thread, no matter how appropriate it may seem. Simply make a new thread; it will decrease confusion for readers of the thread. If you need to refer back to the old one, post a link in your description.

  7. Do not request private help. Specifically, do not ask a question openly in the forum, then provide your email address and tell people to mail you the answer.

    The purpose of a discussion forum is to discuss things openly. This allows everyone to share in the discussion as well as allowing everyone to share in the results. By asking for private help, you are taking away from the forum without giving back. As you might imagine, this is quite impolite.

    Something similar goes for private messages. Do not post a thread and then private message forum members as a way of advertising it.

  8. Do not simply post a link to your question on another website/forum/etc. Post the entirety of your question here. It is fine to post links to images or code, but the actual explanation of your issue should be in the post itself.

Formatting your post

Proper formatting is always a good idea. If someone can’t read your post, they can’t answer your question.

  1. Avoid net-speak and use reasonable English. Common mistakes include:

    • Using “u” instead of “you”, or similar improper contractions.
    • Not capitalizing the word “I” or the first letter of sentences.
    • The use of multiple exclamation points or question marks at the end of a sentence.
    • The use of ellipsis marks (…) instead of periods.
  2. Paragraphs should have an empty line between them. Also, paragraphs should usually consist of more than one sentence. Putting each sentence on a paragraph is not necessary and makes the post difficult to read.

  3. Word wrapping is automatic. You do not need to manually word wrap by pressing <enter> at the end of a line.

Posting source code

It is perfectly fine to post source code. The important question is which code and how much to post. Knowing which code is relevant is not exactly easy when you don’t know how things work and what exactly is wrong. It’s a catch-22: if you post too much code, most people won’t bother sifting through it to find your problem. But if you don’t post enough code, then they’ll have to ask you to post more since the problem doesn’t appear to be in what you posted. You will have to use your own judgement to decide which source to post.

If you do post code, make sure to properly format it. Always use code tags. These tags look like this: ``` code goes here ```. Properly formatted code looks like this:

void some_func()

Make sure that the source code is properly tab indented. You don’t need to use any particular indentation style, but you need to have some kind of indentation to make it easier to read. Just copy and paste it directly from your source files. When pasting, make sure that extra line spaces don’t come out in the pasted code, which ends up looking like this:

void some_func()




Users will generally assume your code is either C or C++. If it is not, then you should say so in the text preceding the source code.

If you are having trouble with shaders, post them as well. Make sure that the version of the shader language in question is clearly stated, either in the shader code with a #version statement or somewhere in your text.

More formatting options

To help you format your posts in a way that makes the posts easy to read, these forums support three (3) different formatting languages:

  1. Markdown is easy to use. Learn more about our flavour of markdown here:
  2. BBCode has partial support.
    [ul][li]option one[/li][/ul]
  3. HTML support allows for a very small subset of the HTML tags to be used. As we don’t recommend HTML, we will assume you won’t use it, so no need to post the tags that are accepted here. :slight_smile:

Learning how to use these forums

If you wish to learn more about how to use the Khronos forums, may we suggest you take the short and fun new user tutorial from our forum bot? Simply start a direct message to @discobot with the message:

@discobot start new user

Special thanks to @Alfonse_Reinheart and all the users who were instrumental in building these guidelines.

Please help me i want this code very necessary .Code opengl with visual studio by c++ and libraries of open gl
Implement memoization/caching for shader
About the Vulkan category
How to fix warning: attempt to free a non-heap object
Create 2 framebuffers, But introduced a new problem: splash screen, the screen keeps flickering
Beginner OpenGl
Game comes up with Vulkan error (IvyBridge)
Post processing effects on unity (CommandBuffer)
[REQUEST] What is a Push Constant in Vulkan? : Khronos
Does the use of geometric shaders significantly reduce performance?
How to speed up OpenGL rendering frequency?
Texture not loading correctly not sure what is wrong
Welcome to the Khronos Forums
Displaying interrupted line in OpenGL ES 2.0
How can the following Gaussian blur shader be modified to compute shader?
How can the following Gaussian blur shader be modified to compute shader?
glDrawArrays(GL_QUADS, 0, 4); crash
MoltenVK compile with g++
GlutTools! Glut 3d model converter!
How to make KeyCallback fuction work?
OpenACC posix devel
Sound with graphics
How to write left image scrolling javascript for html?
Glfw keyboard input
Is it possible to make these subliminal messages in OpenGL?
glDrawElements not drawing all of my triangles
How to use GPU inputs in the shader?
How to rotate text in OPENGL
Help to add multiple cubes that each can rotate
Jumping sprites
Animating sprite collision
Image Scrolling using openGL on Windows
Shader code for show selected part of image
Blank output for linear search algorithm
QT and OpenGL Display Error
Draw opengl circle with sector in android
Butterfly in OpenGL
Problem with WebGL and MALI GPU
It looks black how do I fix it
Shader doesn't write the fragment color in the second pass
Crash when rendering
About the Self Promotion category
About the glTF: Showcase category
About the NNEF category
About the OpenXR category
About the glTF: Support category
About the glTF: Resources category
About the glTF: Development category
About the glTF: Art Workflow category
About the glTF category
How to create a Texture2D using nv12 byte data?
Bus Error in Android 9
PCD data needs to be converted in range which is understood by the OpenGL?
glDrawElements gives 1282 error code
MSYS ,OpenGL and CodeBlocks