Advertisement Jump to content
  • Advertisement

test opty

Member
  • Content Count

    28
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About test opty

  • Rank
    Member

Personal Information

  • Interests
    Programming

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thank you all very much. I appreciate all of your help to make me step forward and make progress. Few questions to understand the rest: 1- Is OpenGL mainly for creating games? 3D games for both Windows and smartphones platforms? 2- Aren't there any tutorial videos you have watched previously and know they're good for beginners, but in C++.
  2. Thank you very much. So I start reading that book and if I have questions on the way, I will ask them here. OK?
  3. Thank you. What about my program. Do you too agree that the "only" attributes that program has are the vertexes, that is, these floating point numbers: -0.5f, -0.5f, 0.0f, // Vertex/Position 1 0.5f, -0.5f, 0.0f, // Vertex/Position 2 0.0f, 0.5f, 0.0f // Vertex/Position 3 ?
  4. Thanks to both of you. I found that some specifications like colours and lighting are attributes of the vertex shader and we can have attributes only for the vertex shader. But to be more specifier, what are all the vertex attributes existing when the link finishes rendering the triangle, please? Here is also the source code of that page for the rectangle. What are those attributes there, please copy and paste them here.
  5. Hi,Please read the Linking Vertex Attributes section of this page. I've read the term a vertex attribute many times in this page but I'm not sure what it means for real or what the author meant by that.If possible please tell me the exact meaning the author meant by vertex attributes.
  6. Hi, another question: This function: void framebuffer_size_callback(GLFWwindow* window, int width, int height) { glViewport(0, 0, width, height); } is called by this statement: glfwSetFramebufferSizeCallback(window, framebuffer_size_callback); Here the parameters width and height aren't set, so how does the function above set its arguments to be used by glViewport?
  7. Thank you very much. I appreciate all your help.
  8. Thank you. I got many things from your answer. There was some misunderstanding, but it got solved now. The picture seems very meaningful but I can't read the text. Where can I find it's large size to read them please?
  9. I got all the other stuff except this part. First off, thanks. Well, each frame is our resulting window and presumably every iteration copies the same frame as the prior one on the window! That is, coping equal frames onto each other! It does so because using the loop we tell it so. It's an infinite loop and if I don't close the window it should run forever! OK. But why 97 times or 137 or so while I haven't close the window, please?
  10. Yes, it solved the issue and demonstrated that one frame is enough for that result. Thanks. But would you please answer other questions I ask above too.
  11. I'm at the beginning of learning OpenGL, so it's not a game I think. By the way, does this convey that OpenGL is mostly for developing games? I used the statements without the loop (removed the loop) but the resulting window is shown and immediately vanishing! I even can't see it! I think the loop is also for keeping the output (window) so that we are able to see the result. As an another attempt to figure the issue out completely, I reused the loop and put a counter into it. Now I can see the resulting window. Then I couted that counter (I use C++). It showed different values, say, from 75, 97 to 137 or over! That is, we have many iterations, just for a simple window! It's also strange for me.
  12. Thanks for the reply. Please have a look at the code above. It's a simple rectangle or window. So nothing is moving/animating. How many frames are needed for that (apparently) fixed picture? I guess less than 10 per second. Once again, what does each frame do in that window? If I'm frank, I think only one frame is sufficient and no frame replacing is needed.
  13. I have new questions on the case now! Here we have a simple window. It has nothing. So how many frames are needed to complete that window? If one frame is to draw, say, a corner of the window, why do we need to replace it with a new one in the next frame?!
  14. test opty

    The simplest OpenGL example

    Sorry but these are not what I need! The window I'm talking about should presumably have only few lines of code. We want a simple, say, 800x600, window with a title like "First Window". That's all.
  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!