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


  • Content count

  • Joined

  • Last visited

Community Reputation

100 Neutral

About Jo

  • Rank
  1. I've solved the problem other way. I loaded again the program (Vetex Shader+Frag Shader) for each object, and passed the transformations. That way the program is always fresh and clean for each vertex ; ) Meanwhile, you could give some other solutions, are always aprecciated ;) Thankz for the tips, even brief ones.
  2. That works with stock shaders, not with my vertex shader. The way you're doing (if i'm correct), for each mesh, when you do the draw, you use the same shader, but different instances (your obj class have a draw function, mine doesn´t, I use glDrawElements with the attributes in the sahder). I understand that the transformation WOULD be applied to both (is that why we use stack for the matrix transformation), but the ship should be transported to the exact same position as the sun, but it is transformed somewhat like a vector with the same direction, but like 75% of the distance. I'll put the OpenGL code: [code]glUseProgram(programId); GLuint loc = glGetUniformLocation(programId, "pMatrix"); glUniformMatrix4fv(loc, 1, GL_FALSE, (GLfloat *)&perspectiveMatrix[0]); loc = glGetUniformLocation(programId, "vMatrix"); glUniformMatrix4fv(loc, 1, GL_FALSE, (GLfloat *)&cameraMatrix[0]); /* !![NEW]!! Get the location of the model matrix in the shader */ loc = glGetUniformLocation(programId, "mMatrixShip"); /* end !![NEW]!! */ glBindVertexArray(vaoObject1); //Spaceship Movement //These rotation are meant to orientate the spaceship to it's original spot. glm::mat4 rotateZ = glm::rotate(glm::mat4(1.0), 180.0f, glm::vec3(0.0f, 0.0f, 1.0f)); glm::mat4 rotateX = glm::rotate(glm::mat4(1.0), 90.0f, glm::vec3(1.0f, 0.0f, 0.0f)); //These are the move transformations. As the keys are being pressed, the Move Struct is being altered, and these matrix are constructed with those arguments glm::mat4 rotateShip = glm::rotate(glm::mat4(1.0), ship.angle, glm::vec3(0.0f, 0.0f, -1.0f)); glm::mat4 moveShip = glm::translate(glm::mat4(1.0), glm::vec3(ship.X,ship.Y,0.0)); //Applying the rotation to the spaceship, so it's oriented as wanted, then apply the movement transformation. glm::mat4 model = moveShip * rotateShip * rotateZ * rotateX ; //Pass the modelTransformations(shipMovemnt) matrix to the shader glUniformMatrix4fv(loc, 1, GL_FALSE, (GLfloat *)&model[0]); glDrawElements(GL_TRIANGLES, spaceShip.IndexArray.size(), GL_UNSIGNED_INT, &(spaceShip.IndexArray[0])); //type of geometry; number of indices; type of indices array, indices pointer glBindVertexArray(0); //Sun Drawing and Transformations glBindVertexArray(vaoObject2); loc = glGetUniformLocation(programId, "mMatrixSun"); /*Matrix for sun Transformations, 'hand-crafted' GLfloat sunScale[] = { 5.0f, 0.0f, 0.0f, 0.0f, 0.0f, 5.0f, 0.0f, 0.0f, 0.0f, 0.0f, 5.0f, 0.0f, 0.0f, 0.0f, 0.0f, 1.0f}; GLfloat sunTranslation[] = { 1.0f, 0.0f, 0.0f, 15.0f, 0.0f, 1.0f, 0.0f, -15.0f, 0.0f, 0.0f, 1.0f, 0.0f, 0.0f, 0.0f, 0.0f, 1.0f}; */ glm::mat4 sunTranslation = glm::translate(glm::mat4(1.0), glm::vec3(-15,15.0,0.0)); glm::mat4 sunScale = glm::scale(glm::mat4(1.0), glm::vec3(5,5,5)); glm::mat4 sunModel = sunTranslation * sunScale; glUniformMatrix4fv(loc, 1, GL_FALSE, (GLfloat *)&sunModel[0]); glDrawElements(GL_TRIANGLES, sun.IndexArray.size(), GL_UNSIGNED_INT, &(sun.IndexArray[0])); glBindVertexArray(0);[/code] The commented Matrix for display, our teacher obligates (as she should) to know all the linear algebra parts of graphics. Thankz for the tips anyway, I'll try the Loadentity, I wasn´t reseting the origin.
  3. Does not anyone have an idea on how to solve this? Not a single feedback? I would really apreeciate.
  4. Hi all, I'm relatively new to OpenGL and GLSL, and I have some work to be delivered by Monday, and I'm having a trouble that I can't figure out, and hope you guys could help. So I have two meshes, a spaceship and a sun, loaded, two different VAO (I know, lame, but for now I can't do different), and in my display func, I'm doing some matrix transformations to these 2 meshes, different to booth. They're good for each of the meshs but when I put the two together, the spaceship got's translated somewhere near the sun, and it is supposed to be at the origin. I know this is probably by my vertex shader, I will paste the code: [code]layout (location=0) in vec4 vertex; layout (location=1) in vec3 color; layout (location=2) in vec4 vertex2; layout (location=2) in vec3 color2; out vec4 color_vf; out vec4 color_vf2; uniform mat4 pMatrix; uniform mat4 vMatrix; uniform mat4 mMatrixSpaceship; uniform mat4 mMatrixSun; void main() { color_vf = vec4(color,1.0f); color_vf2 = vec4(0.5f , 0.5f ,0.0f ,1.0f); gl_Position =(pMatrix * vMatrix * mMatrixSun * vertex2) + (pMatrix * vMatrix * mMatrixSpaceship * vertex) ; }[/code] The vertex is the spaceship, vertex2 the sun. pMatrix perspective, and vMatrix view, the rest I think is fairly obvious. I've tried to render the two separately, but I can't find any USEFUL documentation in the net (at least the way I'm learning, wich is kind onorthodox :/) So I would appreciate if any of you guys didn't mind helping a bit, I would be very thankful, and I think this is a good comunity to be, maybe one day I'll answer some of my one Thankz Juca