• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
Octav

OpenGL
My first C++ game

7 posts in this topic

Hi. Before I address my questions I'd like to give a small background of my experience. I'm 16 years old, I began programming a year ago and I've been studying C++ every day since then. I have not written anything big, except a tic tac toe game in ASCII which is probably my biggest achievement.

I know I'm not so experienced with the language after a year, but I feel like I can move on from console programs into something better, so I thought "Why not make a game?" so I've been documenting what it involves, and what I need. I figured I need to learn OpenGL but after trying it I just couldn't understand what matrixes are and how it works overall (I do know the language features however)

So I'm going to address a few questions which I hope to get some answers for, in order to make my first game.

[b]1. What framework should I learn to make my first game?
2. Where can I find an easy to follow tutorial? (This includes videos, articles, etc)
3. How can I learn the syntax? When I tried learning OpenGL I found myself forgetting the syntax very easily, even after re-writing it several times, I just kept forgetting it.[/b]
[b]4. Is it best to start with a 2D game rather than a complex 3D game?[/b]

Thanks in advance for all the replies, and I'm not going to give up the idea of making a game, but I hope some experienced game makers/programmers can get me on the right path.
0

Share this post


Link to post
Share on other sites
1. You can start out with freeGLUT to get off the ground. It hides the OS specific stuff like creation a window and GL context, user input.
2. There is Nehe but it is ancient and just teaches GL 1.1 and few things like VBO.
There is the Wiki for GL 3 stuff
http://www.opengl.org/wiki/Tutorials

and all this
http://www.opengl.org/wiki/Getting_started#Tutorials_and_How_To_Guides

3. The same way you learn the syntax for any other API
4. 2D tic tac toe or Pac Man.
2

Share this post


Link to post
Share on other sites
I used opengl for my first game. The only opengl drawing command I used was: glBegin, glEnd, glColor3f (although deprecated)
And for the window, I used freeglut.

You don't need to know complicated stuff like vbo and matrices for your first game.
Start out with small 2d games like snake and start building up your experience

To learn the syntax, the opengl tutorials on youtube are fine. Edited by lride
2

Share this post


Link to post
Share on other sites
If you are exclusively targetting Windows, I'd actually start out by learning DirectX 9. OpenGL is cross-platform and pretty standard for most OS's and devices, but even with the utility libraries it has a lot of manual labor and gets quite intricate early on for a beginner. Many concepts between them are quite similar, and I do recommend eventually learning both, but DirectX is a better starting point IMO and AFAIK is the only way that you can port your games onto the Xbox360 platform (via the XNA Framework). [b][i]However[/i][/b], if you haven't familiarized yourself with the basic Win32 API concepts of window creation and GDI graphics, then yes I would definitely recommend starting with OpenGL + utility libs. Alternatively, there are 3rd-party libraries such as SDL which are both cross-platform and fairly high-level, making everything easier, so there's something to think about as well.

Google is your friend. Type in the name of the framework you wish to use + "tutorial" or "example" and you will have nearly everything you will ever need right there.

Matrices are a mathematical structure primarily used in 3D graphics programming, and are a college-level concept derived from linear algebra. For graphics, they aid in the position, scale, rotation and translation of an object in 3D world-space. Before getting involved in them, I would definitely recommend sticking to a 2D environment where simple high-school algebra and trigonometry come into play using 2-dimensional Vectors.

To learn the syntax, just keep checking the API reference docs, samples/demos, and online tutorials. Bookmark the ones you are learning along the way if you need to.
As stated by the previous poster, the same applies for any API you are learning. For Win32 API stuff, check the MSDN.

As suggested above, a good place to start is a simple game of Tic-Tac-Toe or Minesweeper, or a card game like Solitaire. Once you've done that, I'd move on to something that uses 2D sprites, such as Pong, Asteroids or Tetris, and then move up to Tile-based games such as Mario, Zelda or virtually any 2D side-scroller or top-down RPG. By then, you should be prepared to implement 3D effects in a 2D environment (using 3D vectors), and perhaps you could even try a 2.5D isometric game like Starcraft or Diablo. Then, it's finally time to move forward into a fully 3D environment. A good place to start there would be a 3D space-shooter.

It's a long path but if you stick with it and don't skip any steps, you won't regret it later on. Personally, I've had to go back and forth over the years, learning everything out of order, and it's complicated my 3D programming skills to say the least. Good luck! Edited by Rectangle
2

Share this post


Link to post
Share on other sites
[quote name='Rectangle' timestamp='1345995540' post='4973491']
If you are exclusively targetting Windows, I'd actually start out by learning DirectX 9. OpenGL is cross-platform and pretty standard for most OS's and devices, but even with the utility libraries it has a lot of manual labor and gets quite intricate early on for a beginner. Many concepts between them are quite similar, and I do recommend eventually learning both, but DirectX is a better starting point IMO and AFAIK is the only way that you can port your games onto the Xbox360 platform (via the XNA Framework). [b][i]However[/i][/b], if you haven't familiarized yourself with the basic Win32 API concepts of window creation and GDI graphics, then yes I would definitely recommend starting with OpenGL + utility libs. Alternatively, there are 3rd-party libraries such as SDL which are both cross-platform and fairly high-level, making everything easier, so there's something to think about as well.

Google is your friend. Type in the name of the framework you wish to use + "tutorial" or "example" and you will have nearly everything you will ever need right there.

Matrices are a mathematical structure primarily used in 3D graphics programming, and are a college-level concept derived from linear algebra. For graphics, they aid in the position, scale, rotation and translation of an object in 3D world-space. Before getting involved in them, I would definitely recommend sticking to a 2D environment where simple high-school algebra and trigonometry come into play using 2-dimensional Vectors.

To learn the syntax, just keep checking the API reference docs, samples/demos, and online tutorials. Bookmark the ones you are learning along the way if you need to.
As stated by the previous poster, the same applies for any API you are learning. For Win32 API stuff, check the MSDN.

As suggested above, a good place to start is a simple game of Tic-Tac-Toe or Minesweeper, or a card game like Solitaire. Once you've done that, I'd move on to something that uses 2D sprites, such as Pong, Asteroids or Tetris, and then move up to Tile-based games such as Mario, Zelda or virtually any 2D side-scroller or top-down RPG. By then, you should be prepared to implement 3D effects in a 2D environment (using 3D vectors), and perhaps you could even try a 2.5D isometric game like Starcraft or Diablo. Then, it's finally time to move forward into a fully 3D environment. A good place to start there would be a 3D space-shooter.

It's a long path but if you stick with it and don't skip any steps, you won't regret it later on. Personally, I've had to go back and forth over the years, learning everything out of order, and it's complicated my 3D programming skills to say the least. Good luck!
[/quote]
This is extremely useful and I appreciate everyone's repplies, especially this one. I thank you kindly for your advice and I'll make sure to follow it! [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]
0

Share this post


Link to post
Share on other sites
I think you should do what you want to do, go with the api you would like to use, and stick with it!
eventualy you will figure stuff out and the problems will be less "wierd"....

But, my choises if i would be creating a game would be going with C# & XNA, you dont have to worry about all the stuff c++ and dx/gl lets you handle.
and XNA is pretty neat when it comes to rapid development!
otherwise, try out a engine, like unity or udk!

If you are more into Engine programming, go with dx/og since that is more or less the only way, or build your own graphics libary [img]http://public.gamedev.net//public/style_emoticons/default/tongue.png[/img] Edited by Tordin
0

Share this post


Link to post
Share on other sites
I think you should start with c# or java and use the built in graphics API as they are pretty straight forward and require little effort to learn. You'll use eclipse/visual studio to write the code and intellisense will remember function names for you so you wont have to bother with
1- Graphics APIs/Frameworks
2- Function details/graphics pipelines
3- Windowing/keyboard-mouse input routines.

You can easily focus on actual game development/algorithms/geometry calculations.
By the time you create a game like snake that actually works you'll have learned a great deal about essentials of game programming.

Then you can move to more professional stuff like OpenGL/DirectX
0

Share this post


Link to post
Share on other sites
When it comes down to it, it's pretty much just a matter of opinion. Everyone learns in different ways using different tools in different languages, and many are proud of how far they have come (as they should be).
I was coming here to recommend [url="http://www.directxtutorial.com/Tutorial9/tutorials.aspx"]these tutorials[/url] for you, but I think you first need to decide exactly how much "flexibility versus learning curve" you are willing to endure.
If you don't want to hassle yourself with learning how graphics are programmed, then you can use something like the [url="http://www.unrealengine.com/udk/"]Unreal Development Kit[/url] to delve right into simply making a game. But you will lose some flexibility, since you can only do what the SDK or API of your choice allows you to do. OpenGL and DirectX do require a lot of learning, and it practically never ends, but you will have full control over how things are rendered. XNA is a decent middleground, but I only briefly mentioned that earlier because you said that you were working with C++, and XNA requires the use of the .NET framework which means you would have to learn either C# or VB.NET.

So it basically all boils down to deciding exactly what you want, how much time you are willing to spend on it, and how far you want to go from there. You could always try different things if you feel as if something's not working out for you, but also the best piece of advice here is to keep at it until it becomes second nature. Good luck!
1

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Similar Content

    • By Solid_Spy
      Hello, I have been working on SH Irradiance map rendering, and I have been using a GLSL pixel shader to render SH irradiance to 2D irradiance maps for my static objects. I already have it working with 9 3D textures so far for the first 9 SH functions.
      In my GLSL shader, I have to send in 9 SH Coefficient 3D Texures that use RGBA8 as a pixel format. RGB being used for the coefficients for red, green, and blue, and the A for checking if the voxel is in use (for the 3D texture solidification shader to prevent bleeding).
      My problem is, I want to knock this number of textures down to something like 4 or 5. Getting even lower would be a godsend. This is because I eventually plan on adding more SH Coefficient 3D Textures for other parts of the game map (such as inside rooms, as opposed to the outside), to circumvent irradiance probe bleeding between rooms separated by walls. I don't want to reach the 32 texture limit too soon. Also, I figure that it would be a LOT faster.
      Is there a way I could, say, store 2 sets of SH Coefficients for 2 SH functions inside a texture with RGBA16 pixels? If so, how would I extract them from inside GLSL? Let me know if you have any suggestions ^^.
    • By DaniDesu
      #include "MyEngine.h" int main() { MyEngine myEngine; myEngine.run(); return 0; } MyEngine.h
      #pragma once #include "MyWindow.h" #include "MyShaders.h" #include "MyShapes.h" class MyEngine { private: GLFWwindow * myWindowHandle; MyWindow * myWindow; public: MyEngine(); ~MyEngine(); void run(); }; MyEngine.cpp
      #include "MyEngine.h" MyEngine::MyEngine() { MyWindow myWindow(800, 600, "My Game Engine"); this->myWindow = &myWindow; myWindow.createWindow(); this->myWindowHandle = myWindow.getWindowHandle(); // Load all OpenGL function pointers for use gladLoadGLLoader((GLADloadproc)glfwGetProcAddress); } MyEngine::~MyEngine() { this->myWindow->destroyWindow(); } void MyEngine::run() { MyShaders myShaders("VertexShader.glsl", "FragmentShader.glsl"); MyShapes myShapes; GLuint vertexArrayObjectHandle; float coordinates[] = { 0.5f, 0.5f, 0.0f, 0.5f, -0.5f, 0.0f, -0.5f, 0.5f, 0.0f }; vertexArrayObjectHandle = myShapes.drawTriangle(coordinates); while (!glfwWindowShouldClose(this->myWindowHandle)) { glClearColor(0.5f, 0.5f, 0.5f, 1.0f); glClear(GL_COLOR_BUFFER_BIT | GL_DEPTH_BUFFER_BIT); // Draw something glUseProgram(myShaders.getShaderProgram()); glBindVertexArray(vertexArrayObjectHandle); glDrawArrays(GL_TRIANGLES, 0, 3); glfwSwapBuffers(this->myWindowHandle); glfwPollEvents(); } } MyShaders.h
      #pragma once #include <glad\glad.h> #include <GLFW\glfw3.h> #include "MyFileHandler.h" class MyShaders { private: const char * vertexShaderFileName; const char * fragmentShaderFileName; const char * vertexShaderCode; const char * fragmentShaderCode; GLuint vertexShaderHandle; GLuint fragmentShaderHandle; GLuint shaderProgram; void compileShaders(); public: MyShaders(const char * vertexShaderFileName, const char * fragmentShaderFileName); ~MyShaders(); GLuint getShaderProgram(); const char * getVertexShaderCode(); const char * getFragmentShaderCode(); }; MyShaders.cpp
      #include "MyShaders.h" MyShaders::MyShaders(const char * vertexShaderFileName, const char * fragmentShaderFileName) { this->vertexShaderFileName = vertexShaderFileName; this->fragmentShaderFileName = fragmentShaderFileName; // Load shaders from files MyFileHandler myVertexShaderFileHandler(this->vertexShaderFileName); this->vertexShaderCode = myVertexShaderFileHandler.readFile(); MyFileHandler myFragmentShaderFileHandler(this->fragmentShaderFileName); this->fragmentShaderCode = myFragmentShaderFileHandler.readFile(); // Compile shaders this->compileShaders(); } MyShaders::~MyShaders() { } void MyShaders::compileShaders() { this->vertexShaderHandle = glCreateShader(GL_VERTEX_SHADER); this->fragmentShaderHandle = glCreateShader(GL_FRAGMENT_SHADER); glShaderSource(this->vertexShaderHandle, 1, &(this->vertexShaderCode), NULL); glShaderSource(this->fragmentShaderHandle, 1, &(this->fragmentShaderCode), NULL); glCompileShader(this->vertexShaderHandle); glCompileShader(this->fragmentShaderHandle); this->shaderProgram = glCreateProgram(); glAttachShader(this->shaderProgram, this->vertexShaderHandle); glAttachShader(this->shaderProgram, this->fragmentShaderHandle); glLinkProgram(this->shaderProgram); return; } GLuint MyShaders::getShaderProgram() { return this->shaderProgram; } const char * MyShaders::getVertexShaderCode() { return this->vertexShaderCode; } const char * MyShaders::getFragmentShaderCode() { return this->fragmentShaderCode; } MyWindow.h
      #pragma once #include <glad\glad.h> #include <GLFW\glfw3.h> class MyWindow { private: GLFWwindow * windowHandle; int windowWidth; int windowHeight; const char * windowTitle; public: MyWindow(int windowWidth, int windowHeight, const char * windowTitle); ~MyWindow(); GLFWwindow * getWindowHandle(); void createWindow(); void MyWindow::destroyWindow(); }; MyWindow.cpp
      #include "MyWindow.h" MyWindow::MyWindow(int windowWidth, int windowHeight, const char * windowTitle) { this->windowHandle = NULL; this->windowWidth = windowWidth; this->windowWidth = windowWidth; this->windowHeight = windowHeight; this->windowTitle = windowTitle; glfwInit(); } MyWindow::~MyWindow() { } GLFWwindow * MyWindow::getWindowHandle() { return this->windowHandle; } void MyWindow::createWindow() { // Use OpenGL 3.3 and GLSL 3.3 glfwWindowHint(GLFW_CONTEXT_VERSION_MINOR, 3); glfwWindowHint(GLFW_CONTEXT_VERSION_MAJOR, 3); // Limit backwards compatibility glfwWindowHint(GLFW_OPENGL_PROFILE, GLFW_OPENGL_CORE_PROFILE); glfwWindowHint(GLFW_OPENGL_FORWARD_COMPAT, GL_TRUE); // Prevent resizing window glfwWindowHint(GLFW_RESIZABLE, GL_FALSE); // Create window this->windowHandle = glfwCreateWindow(this->windowWidth, this->windowHeight, this->windowTitle, NULL, NULL); glfwMakeContextCurrent(this->windowHandle); } void MyWindow::destroyWindow() { glfwTerminate(); } MyShapes.h
      #pragma once #include <glad\glad.h> #include <GLFW\glfw3.h> class MyShapes { public: MyShapes(); ~MyShapes(); GLuint & drawTriangle(float coordinates[]); }; MyShapes.cpp
      #include "MyShapes.h" MyShapes::MyShapes() { } MyShapes::~MyShapes() { } GLuint & MyShapes::drawTriangle(float coordinates[]) { GLuint vertexBufferObject{}; GLuint vertexArrayObject{}; // Create a VAO glGenVertexArrays(1, &vertexArrayObject); glBindVertexArray(vertexArrayObject); // Send vertices to the GPU glGenBuffers(1, &vertexBufferObject); glBindBuffer(GL_ARRAY_BUFFER, vertexBufferObject); glBufferData(GL_ARRAY_BUFFER, sizeof(coordinates), coordinates, GL_STATIC_DRAW); // Dertermine the interpretation of the array buffer glVertexAttribPointer(0, 3, GL_FLOAT, GL_FALSE, 3*sizeof(float), (void *)0); glEnableVertexAttribArray(0); // Unbind the buffers glBindBuffer(GL_ARRAY_BUFFER, 0); glBindVertexArray(0); return vertexArrayObject; } MyFileHandler.h
      #pragma once #include <cstdio> #include <cstdlib> class MyFileHandler { private: const char * fileName; unsigned long fileSize; void setFileSize(); public: MyFileHandler(const char * fileName); ~MyFileHandler(); unsigned long getFileSize(); const char * readFile(); }; MyFileHandler.cpp
      #include "MyFileHandler.h" MyFileHandler::MyFileHandler(const char * fileName) { this->fileName = fileName; this->setFileSize(); } MyFileHandler::~MyFileHandler() { } void MyFileHandler::setFileSize() { FILE * fileHandle = NULL; fopen_s(&fileHandle, this->fileName, "rb"); fseek(fileHandle, 0L, SEEK_END); this->fileSize = ftell(fileHandle); rewind(fileHandle); fclose(fileHandle); return; } unsigned long MyFileHandler::getFileSize() { return (this->fileSize); } const char * MyFileHandler::readFile() { char * buffer = (char *)malloc((this->fileSize)+1); FILE * fileHandle = NULL; fopen_s(&fileHandle, this->fileName, "rb"); fread(buffer, this->fileSize, sizeof(char), fileHandle); fclose(fileHandle); buffer[this->fileSize] = '\0'; return buffer; } VertexShader.glsl
      #version 330 core layout (location = 0) vec3 VertexPositions; void main() { gl_Position = vec4(VertexPositions, 1.0f); } FragmentShader.glsl
      #version 330 core out vec4 FragmentColor; void main() { FragmentColor = vec4(1.0f, 0.0f, 0.0f, 1.0f); } I am attempting to create a simple engine/graphics utility using some object-oriented paradigms. My first goal is to get some output from my engine, namely, a simple red triangle.
      For this goal, the MyShapes class will be responsible for defining shapes such as triangles, polygons etc. Currently, there is only a drawTriangle() method implemented, because I first wanted to see whether it works or not before attempting to code other shape drawing methods.
      The constructor of the MyEngine class creates a GLFW window (GLAD is also initialized here to load all OpenGL functionality), and the myEngine.run() method in Main.cpp is responsible for firing up the engine. In this run() method, the shaders get loaded from files via the help of my FileHandler class. The vertices for the triangle are processed by the myShapes.drawTriangle() method where a vertex array object, a vertex buffer object and vertrex attributes are set for this purpose.
      The while loop in the run() method should be outputting me the desired red triangle, but all I get is a grey window area. Why?
      Note: The shaders are compiling and linking without any errors.
      (Note: I am aware that this code is not using any good software engineering practices (e.g. exceptions, error handling). I am planning to implement them later, once I get the hang of OpenGL.)

       
    • By KarimIO
      EDIT: I thought this was restricted to Attribute-Created GL contexts, but it isn't, so I rewrote the post.
      Hey guys, whenever I call SwapBuffers(hDC), I get a crash, and I get a "Too many posts were made to a semaphore." from Windows as I call SwapBuffers. What could be the cause of this?
      Update: No crash occurs if I don't draw, just clear and swap.
      static PIXELFORMATDESCRIPTOR pfd = // pfd Tells Windows How We Want Things To Be { sizeof(PIXELFORMATDESCRIPTOR), // Size Of This Pixel Format Descriptor 1, // Version Number PFD_DRAW_TO_WINDOW | // Format Must Support Window PFD_SUPPORT_OPENGL | // Format Must Support OpenGL PFD_DOUBLEBUFFER, // Must Support Double Buffering PFD_TYPE_RGBA, // Request An RGBA Format 32, // Select Our Color Depth 0, 0, 0, 0, 0, 0, // Color Bits Ignored 0, // No Alpha Buffer 0, // Shift Bit Ignored 0, // No Accumulation Buffer 0, 0, 0, 0, // Accumulation Bits Ignored 24, // 24Bit Z-Buffer (Depth Buffer) 0, // No Stencil Buffer 0, // No Auxiliary Buffer PFD_MAIN_PLANE, // Main Drawing Layer 0, // Reserved 0, 0, 0 // Layer Masks Ignored }; if (!(hDC = GetDC(windowHandle))) return false; unsigned int PixelFormat; if (!(PixelFormat = ChoosePixelFormat(hDC, &pfd))) return false; if (!SetPixelFormat(hDC, PixelFormat, &pfd)) return false; hRC = wglCreateContext(hDC); if (!hRC) { std::cout << "wglCreateContext Failed!\n"; return false; } if (wglMakeCurrent(hDC, hRC) == NULL) { std::cout << "Make Context Current Second Failed!\n"; return false; } ... // OGL Buffer Initialization glClear(GL_DEPTH_BUFFER_BIT | GL_COLOR_BUFFER_BIT); glBindVertexArray(vao); glUseProgram(myprogram); glDrawElements(GL_TRIANGLES, indexCount, GL_UNSIGNED_SHORT, (void *)indexStart); SwapBuffers(GetDC(window_handle));  
    • By Tchom
      Hey devs!
       
      I've been working on a OpenGL ES 2.0 android engine and I have begun implementing some simple (point) lighting. I had something fairly simple working, so I tried to get fancy and added color-tinting light. And it works great... with only one or two lights. Any more than that, the application drops about 15 frames per light added (my ideal is at least 4 or 5). I know implementing lighting is expensive, I just didn't think it was that expensive. I'm fairly new to the world of OpenGL and GLSL, so there is a good chance I've written some crappy shader code. If anyone had any feedback or tips on how I can optimize this code, please let me know.
       
      Vertex Shader
      uniform mat4 u_MVPMatrix; uniform mat4 u_MVMatrix; attribute vec4 a_Position; attribute vec3 a_Normal; attribute vec2 a_TexCoordinate; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { v_Position = vec3(u_MVMatrix * a_Position); v_TexCoordinate = a_TexCoordinate; v_Normal = vec3(u_MVMatrix * vec4(a_Normal, 0.0)); gl_Position = u_MVPMatrix * a_Position; } Fragment Shader
      precision mediump float; uniform vec4 u_LightPos["+numLights+"]; uniform vec4 u_LightColours["+numLights+"]; uniform float u_LightPower["+numLights+"]; uniform sampler2D u_Texture; varying vec3 v_Position; varying vec3 v_Normal; varying vec2 v_TexCoordinate; void main() { gl_FragColor = (texture2D(u_Texture, v_TexCoordinate)); float diffuse = 0.0; vec4 colourSum = vec4(1.0); for (int i = 0; i < "+numLights+"; i++) { vec3 toPointLight = vec3(u_LightPos[i]); float distance = length(toPointLight - v_Position); vec3 lightVector = normalize(toPointLight - v_Position); float diffuseDiff = 0.0; // The diffuse difference contributed from current light diffuseDiff = max(dot(v_Normal, lightVector), 0.0); diffuseDiff = diffuseDiff * (1.0 / (1.0 + ((1.0-u_LightPower[i])* distance * distance))); //Determine attenuatio diffuse += diffuseDiff; gl_FragColor.rgb *= vec3(1.0) / ((vec3(1.0) + ((vec3(1.0) - vec3(u_LightColours[i]))*diffuseDiff))); //The expensive part } diffuse += 0.1; //Add ambient light gl_FragColor.rgb *= diffuse; } Am I making any rookie mistakes? Or am I just being unrealistic about what I can do? Thanks in advance
    • By yahiko00
      Hi,
      Not sure to post at the right place, if not, please forgive me...
      For a game project I am working on, I would like to implement a 2D starfield as a background.
      I do not want to deal with static tiles, since I plan to slowly animate the starfield. So, I am trying to figure out how to generate a random starfield for the entire map.
      I feel that using a uniform distribution for the stars will not do the trick. Instead I would like something similar to the screenshot below, taken from the game Star Wars: Empire At War (all credits to Lucasfilm, Disney, and so on...).

      Is there someone who could have an idea of a distribution which could result in such a starfield?
      Any insight would be appreciated
  • Popular Now