• 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
Josh Sanders

C++/OpenGL Chess Game Project

7 posts in this topic

So, I'm a student at UHV and I'm taking a class called Computer Graphics Applications, as is required for my degree in Computer Science - Digital Gaming and Simulation. We were assigned a final project, and I want to start working on that project now so that I can refine it until it is perfect by the end of the semester. I chose a chess game, rendered with OpenGL.
This would do three things for me: (1) Help to make me more fluent in C++. (2) Help solidify OOP concepts I've been learning. (3) Give me a head start into Game AI before I take the AI class next semester
So, I'm not sure if i will get much help on here, but any would be much appreciated. I'm not looking for somebody to tell me all of the answers, I would like to figure the code out on my own, but pointing me to the right concepts is what I really need. At this point, I'm not sure where to start.. Here is what I have:
Classes: RED
SubClasses: GREEN
Data Members: BLUE
Functions: PURPLE

enum TurnState
enum GameState

- [color=#ff0000]Player(abstract class)[/color]
- [color=#008000]Computer(inherits from Player)[/color]
- [color=#ff0000]ChessGame[/color]
- [color=#0000ff]Player p1, p2[/color]
-[color=#0000ff]TurnState turnState[/color]
- [color=#0000ff]GameState gamState[/color]
- [color=#ff0000]Move[/color]
- [color=#0000ff]*Piece[/color]
- [color=#0000ff]Location origin[/color]
- [color=#0000ff]Location destination[/color]
- [color=#ff0000]Location[/color]
- r[color=#0000ff]ow[/color]
- [color=#0000ff]col[/color]
- [color=#0000ff]*ChessBoard[/color]
- [color=#ff0000]ChessBoard[/color]
-[color=#800080]isValid(move) //checks if the move is valid[/color]
- [color=#ff0000]ChessPiece[/color](abstract class)
- [color=#800080]GetValue() //returns an int value of the peice(for scoring)[/color]
- [color=#800080]GetPosition() //returns the current position of a piece[/color]
- [color=#800080]getIsSelected() //returns a boolean, true if selected, fale if unselected[/color]
- [color=#800080]move() // moves the piece in a way dependent upon what piece[/color]
- [color=#008000]Pawn[/color]
- [color=#008000]Rook[/color]
- [color=#008000]Queen[/color]
- [color=#008000]King[/color]
- [color=#008000]Knight[/color]

So this is what I have so far. All of the pieces will inherit methods from Piece and be able to override those methods. But I have several questions:
Where and how do I tie OpenGL into this? What classes should have openGL code in them? Should I make seperate classes for openGL??
Do I still make a 2d array in memory to store the position of the pieces? Or is eveyrthing done on screen? For example, would I say, " rook location is [1][3]" or would I tell openGL "When I click on this part of the screen, select the rook", or both?

Are there classes I should add? What other functions will I need? How do i get started?

Share this post

Link to post
Share on other sites
The data structures you use to represent current game state should not depend on how it is drawn using OpenGL. That way, you can easily change the appearance if you want to make a more advanced solution without having to change anything in the main game state. You can start with making a chess game that simply prints out the positions on the dos prompt using character representations for pieces. When that works, you can replace the print functions with an interface to OpenGL, or whatever library you find.

This is a basic technique of programming. To keep the model independent on the display, sometimes called [url="http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller"]Model-View-Controller[/url]. The purpose is to minimize the need for changes propagating too far in the source code. Because changes will never stop.

Learning to use OpenGL can take a couple of months if you are experienced with C. You have to decide if you want to go for a 3D view. That would be looking at the chess board from above, with an angle. It will look the best, but requires more effort. An easier way is to divide the screen into 8x8 areas, and simply draw different bitmaps at each position. This is easier, but still the effort to get OpenGL up and running will take a lot of effort.

There are also 3:rd party game engines that can help you, so that you don't have to worry too much about the low level details. Someone else will have to give recommendations for this.

Share this post

Link to post
Share on other sites
opengl is _only_ and i mean _only_ a rasterizer.. all it does is draw stuff
you can use gpu to calculate things and get return data, but that is beyond opengl

as for pawn, i would split pawn into 2 subclasses: PawnWhite and PawnBlack, since they move very differently

for selecting a piece, you would have to use a window-library that gives you mouse events and the like
java already has this [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]

EDIT: i see now that you intend to use c++, then i recommend freeglut or glfw for opengl frontend
this should get you started though (if indeed you have to use c++, since its quite a bit harder learning curve for opengl)

sorry for the short reply, and good luck Edited by Kaptein

Share this post

Link to post
Share on other sites
Okay, first of all, thank you very much for the response! So it seems clear to me that I should write the game first, making everything modular, and then worry about openGL. So, if you would, please allow me to document my thought process here, maybe I will make this thread my diary, with you as my guidance .
So, I sat down in Visual Studio 2012, and I made all of my classes. And Then I thought, it would be better if I created the classes as I needed them. So, I started with my ChessGame class. Then my thoughts are, I should create a GameBoard right? So I made a GameBoard class, and tried to develop an algorithm that would create the board:

Problem: I need to create an 8X8 array that will serve as my chessboard. Each spot in the array will be white or black, and empty or containing a piece.

Solution 1:
Make an 8X8 int array. If it was an int array, I could specify if it were white and black by filling the array with 1's and 0's!
However, then I thought, how would I tell the program that there is a piece in that spot? And more importantly, what piece is in that spot?

Solution 2:
Make a class called Spaces and fill the array with Spaces that have a white parameter, a black parameter, and a pointer to the piece that lies on it, if any. But would this make sense? Should i have a Space class with WhiteSpace and BlackSpace subclasses? But I think this could impose another problem. First of all, each space would be a new object which.. sounds a little extreme. And secondly, Each space would have a unique name, although I suppose I could name them as coordinates. Maybe I could use structs instead?

Which brings me to the structure of my pieces. Should I have WhitePiece and BlackPiece classes? Could both of these problems be solved with an enum? Edited by frostbytes89

Share this post

Link to post
Share on other sites
Maybe you should read the book (Beginning.OpenGL.Game.Programming)written by Dave.Astle.The last chapter is a chess game sample....[img]http://public.gamedev.net//public/style_emoticons/default/ph34r.png[/img]

Share this post

Link to post
Share on other sites
[quote name='frostbytes89' timestamp='1347507798' post='4979563']
So, I sat down in Visual Studio 2012, and I made all of my classes. And Then I thought, it would be better if I created the classes as I needed them. So, I started with my ChessGame class. Then my thoughts are, I should create a GameBoard right? So I made a GameBoard class, and tried to develop an algorithm that would create the board:

You really were on the right path. Make your design up-front to avoid a lot of problems later. Writing the code should be really just that, writing code, not thinking about how/where/what to write. Think of building software as-if you're building a house. Houses need a design up front to prevent making mistakes early in the construction process (eg building walls that dont support a heavy roof), the same holds true for software.
And while you're at the design process you should really have a look at UML, it's pretty standard and alot more clear than fancy text colors. For tool you can have a look at violet uml editor, it's good for very basic designs.

As for your last question, are WhitePiece and BlackPiece really fundamentally different from eachother? Or is it just some of the behaviour that needs to change?
Also, dont worry about object count, as long as you're not making any mistakes resulting in constant copy-ing of objects, you can use many thousands of objects.

Share this post

Link to post
Share on other sites
[quote]As for your last question, are WhitePiece and BlackPiece really fundamentally different from eachother? Or is it just some of the behaviour that needs to change?
Also, dont worry about object count, as long as you're not making any mistakes resulting in constant copy-ing of objects, you can use many thousands of objects.[/quote]

Well, I thought about that, and I think the reason I came up with to make them two seperate classes, is that it might make it easier in the long run to program which moves a piece like say, the bishop is allowed to move. So Maybe I could say in psuedocode, if bishop is on black space, he can only move along other black pieces. But it seems like an enum would be better than making an entire class and object based on color. I was just thinking of the "is a" relationship, and a "has a" relationship. So the board HAS spaces, which ARE colors. So Board class is by himself. Space class is by itself with it's color that it IS rather than has. But I may be stretching that too far..

But holy crap rongshuxiacy I actually have that book right here and I've never looked into it!! I bought this book like.. 6 years ago and never thought to open it now because I was sure that all of the info and methods would be outdated and depricated. But I guess the main reason I didn't look is because I wanted to try and solve these issues without actually seeing a coded solution. I mean what use am I as a programmer if I can't even do something like this... I guess I would feel like I was cheating.

And as for the UML, I will have a look at that. I remember doing a UML back in my freshman classes. It certainly might make it easier for me to convey my code logic. And thanks for saying I'm at least on the right path

Share this post

Link to post
Share on other sites
they [pawns] are indeed fundamentally different on the movement level, and i personally chose to make Pawn -> PawnWhite, PawnBlack
it's a matter of semantics though
the hardest part is probably keeping up with some the special rules (castling, en-passant), and making sure the players aren't making illegal moves
there are some cheap tricks though =) in my PawnWhite class i simply checked if the pawn was at say y=2, then there were 2 valid moves,
since the first move by a pawn allows 1 or 2 steps forward.
i used a boolean map reference as return value for move tests, and while it certainly isnt very fast, it wasnt slow either when you dont have to write an AI [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img]
it wasnt any sort of final assignment though, just a small school project, so i dont know how far you want to go with this
playing chess is an art, but.. coding the best chess program and keeping up with the latest, is probably a more than one persons lifes work
so, my last advice is: first and foremost - make it (just) work!
presentation and visuals counts more than AI to most people, even the old professors [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] it should feel like a chessboard!
just in case though, i would probably ask what is expected... Edited by Kaptein

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
      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